Closed northwestwitch closed 1 week ago
Attention: Patch coverage is 0%
with 1 line
in your changes missing coverage. Please review.
Project coverage is 84.78%. Comparing base (
fb8ae32
) to head (8fbcbc9
). Report is 1 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
scout/__version__.py | 0.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
🚨 Try these New Features:
Great! We should get a hasta release out asap for the cat 8 issue. We may be in a decent position to get #4976 and #4985 in here as well - Ill have a look.
Database update (all tables) - Hasta stage:
scout --config /home/proj/stage/servers/config/hasta.scilifelab.se/scout-stage.yaml download everything --api-key blablabla
scout --config /home/proj/stage/servers/config/hasta.scilifelab.se/scout-stage.yaml update hpo --hpoterms hpo.obo --hpo-to-genes phenotype_to_genes.txt
scout --config /home/proj/stage/servers/config/hasta.scilifelab.se/scout-stage.yaml update diseases -f .
scout --config /home/proj/stage/servers/config/hasta.scilifelab.se/scout-stage.yaml update genes -f .
scout --config /home/proj/stage/servers/config/hasta.scilifelab.se/scout-stage.yaml update omim --institute cust002 --genemap2 genemap2.txt --mim2genes mim2genes.txt
scout --config /home/proj/stage/servers/config/hasta.scilifelab.se/scout-stage.yaml update panelapp-green -i cust002 --force
Took me forever to find a variant with conflicting classification, then I reasoned that first I'd find it in the db then I search it in scout:
For instance this query, with limit=1
{"clnsig.value":{"$in":[8]}}
Returns a variant in this case.
In fact if you filter the research variants by conflicting clinsig you get 23 hits
Tested
By editing the config file of this case and reuploading it.
In the config file Ive removed the alignment of the first individual and added custom_images: {}
, as instructed in the comments of the relative fix PRs.
Case loaded OK:
Unfortunately when I click on this buttom the IGV page crashes:
✅ The issue https://github.com/Clinical-Genomics/scout/issues/4789 is indeed fixed by IGV 3.0.9:
✅ Caller AF is now prioritised on a previously problematic balasamic variant, with AD values way off:
✅ Same count of ClinVar hits with latest prod version (4.90.1) compared to PR, indicating that the simplified clinvar pathogenic check is ok.
✅ STR TRID export (before, after)
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
scout update hpo --hpoterms hpo.obo --hpo-to-genes phenotype_to_genes.txt
scout update diseases -f .
scout update genes -f .
scout update omim --institute cust002 --genemap2 genemap2.txt --mim2genes mim2genes.txt
scout update panelapp-green -i cust002 --force
Deployed on hasta prod:
Deployed on cg-services-prod
:
[4.91]
Added
Changed
/api/v1/hpo-terms
returns pymongo OperationFailure errors when provided query string contains problematic charactersname_query
parameter, only ImmutableMultiDict (form data)Fixed
Review: