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 find a small deletion chr2:71600701-71602850 in DYSF.
but when i run cnvkit.py segment -m hmm-germline in.cnr -o out.cns , the deletion is merged to chr2:10500-90402011 which is not a real CNV.
I have confirm this deletion is a real positive deletion using QPCR, so i think there is a false negative result of cnvkit.py segment.
How can it output the chr2:71600701-71602850 deletion in cns file?
Of course, i have run cnvkit.py segment --drop-low-coverage -m hmm-germline in.cnr -o out.cns too.
for method “hmm-germline”,to set the window(-t)== 2 can resolve it.
but it is not active in hmm.py cnarr["log2"] = cnarr.smooth_log2() # window).
we need rewrite it with cnarr["log2"] = cnarr.smooth_log2(window), can you fix it? @etal
I find a small deletion chr2:71600701-71602850 in DYSF.
but when i run
cnvkit.py segment -m hmm-germline in.cnr -o out.cns
, the deletion is merged to chr2:10500-90402011 which is not a real CNV.I have confirm this deletion is a real positive deletion using QPCR, so i think there is a false negative result of
cnvkit.py segment
.How can it output the chr2:71600701-71602850 deletion in cns file?
Of course, i have run
cnvkit.py segment --drop-low-coverage -m hmm-germline in.cnr -o out.cns
too.the cnr lines are:
the cns line is:
cnvkit_data.zip
The text was updated successfully, but these errors were encountered: