You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried the wf-human-variation on a few of our samples and there is no calculation of the repeat expansion of the RFC1 locus. The other loci are calculated as expected.
RFC1 does not show up in the str-report and does not appear in the wf_str.straglr.tsv output file. However, when looking at the code I can see that RFC1 is configured correctly in the wf_str_repeats.bed regions file as well as the variant_catalog_hg38.json annotation file. I was not able to find anything in the code that pointed to an exclusion of the region but I am wondering if there is a deliberate omission within the nextflow workflow of RFC1 that I am not seeing?
According to this GitHub Issue it looks like the straglr developers have already considered RFC1 and implemented for the locus.
The text was updated successfully, but these errors were encountered:
Hi @vroni, we have released a new version of the workflow, v1.11.0, containing an update to straglr which allows RFC1 repeats to be called. Please let us know if you experience any further issues.
I have tried the wf-human-variation on a few of our samples and there is no calculation of the repeat expansion of the RFC1 locus. The other loci are calculated as expected.
RFC1 does not show up in the str-report and does not appear in the wf_str.straglr.tsv output file. However, when looking at the code I can see that RFC1 is configured correctly in the wf_str_repeats.bed regions file as well as the variant_catalog_hg38.json annotation file. I was not able to find anything in the code that pointed to an exclusion of the region but I am wondering if there is a deliberate omission within the nextflow workflow of RFC1 that I am not seeing?
According to this GitHub Issue it looks like the straglr developers have already considered RFC1 and implemented for the locus.
The text was updated successfully, but these errors were encountered: