-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix end coordinates in ClinVar for indels #4593
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4593 +/- ##
=======================================
Coverage 84.58% 84.58%
=======================================
Files 310 310
Lines 18634 18634
=======================================
Hits 15762 15762
Misses 2872 2872 ☔ View full report in Codecov by Sentry. |
Tested on stage with this variant Main branch:![]() This branch:![]() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Test / check docs for how they want end coords described: it may not be on VCF standard. 😊
@@ -107,7 +107,7 @@ def _get_snv_var_form(variant_obj, case_obj): | |||
var_form.variations_ids.data = var_ids.split(";")[0] | |||
var_form.chromosome.data = variant_obj.get("chromosome") | |||
var_form.start.data = variant_obj.get("position") | |||
var_form.stop.data = variant_obj.get("position") | |||
var_form.stop.data = variant_obj.get("end") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you check the docs or test with their stage endpoint to see if this is correct in terms of inclusive coords (off by one or not)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope. I can try!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And before they would have failed it? 😊
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, yes, but I would be a wealthy person if I got a minute amount of currency for every off-by-one error I've had.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you check the JSON summary report from the dry-run? It should be available with that sub nr right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's try like this. We can fix if they complain. It's not that they make us test better using the test endpoint
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested on validate preClinVar endpoint and this fix is effective. There is another error related to the condition that perhaps needs fixing. but this is good to merge
@@ -276,7 +276,7 @@ def parse_variant_form_fields(form): | |||
clinvar_var["variations_ids"] = form["dbsnp_id"] | |||
|
|||
if clinvar_var.get("ref_seq") and clinvar_var.get("hgvs"): | |||
# Variant is described by RefSeq and HGVS already, remove redundanti fields from submission | |||
# Variant is described by RefSeq and HGVS already, remove redundant fields from submission |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😄
|
This PR adds a functionality or fixes a bug.
Testing on cg-vm1 server (Clinical Genomics Stockholm)
Prepare for testing
scout-stage
and the server iscg-vm1
.ssh <USER.NAME>@cg-vm1.scilifelab.se
sudo -iu hiseq.clinical
ssh localhost
podman ps
systemctl --user stop scout.target
systemctl --user start scout@<this_branch>
systemctl --user status scout.target
scout-stage
) to be used for testing by other users.Testing on hasta server (Clinical Genomics Stockholm)
Prepare for testing
ssh <USER.NAME>@hasta.scilifelab.se
us; paxa -u <user> -s hasta -r scout-stage
. You can also use the WSGI Pax app available at https://pax.scilifelab.se/.conda activate S_scout; pip freeze | grep scout-browser
bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_scout -t scout -b <this_branch>
us; scout --version
paxa
procedure, which will release the allocated resource (scout-stage
) to be used for testing by other users.How to test:
Expected outcome:
The functionality should be working
Take a screenshot and attach or copy/paste the output.
Review: