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
There is a bug when running cloneHD in SNV mode with --snv ${snv}, --avail-cn ${avail_cn} and --mean-tcn ${mean_tcn}. If the number of chromosomes in ${avail_cn} is greater than the number of chromosomes in ${snv}, cloneHD exits with a segmentation fault. @vmustonen has tested this for get_avail_cn in cloneHD-functions.cpp, but it may also affect get_mean_tcn.
The problem only seems to happen if the last chr in ${avail_cn} does not have any SNV hits. One can skip intermediate chrs without a problem so this seems to be a boundary case that has not occurred. This corner case is very rare with whole-genome data, but it is likely to cause problem for exome data.
We should build a safe guard, such that the chr count in ${avail_cn} should only run to max(SNVs chr). A solution would be to set max(SNVs chr)== max(avail-cn chr).
The text was updated successfully, but these errors were encountered:
There is a bug when running cloneHD in SNV mode with
--snv ${snv}
,--avail-cn ${avail_cn}
and--mean-tcn ${mean_tcn}
. If the number of chromosomes in${avail_cn}
is greater than the number of chromosomes in${snv}
, cloneHD exits with a segmentation fault. @vmustonen has tested this forget_avail_cn
incloneHD-functions.cpp
, but it may also affectget_mean_tcn
.The problem only seems to happen if the last chr in
${avail_cn}
does not have any SNV hits. One can skip intermediate chrs without a problem so this seems to be a boundary case that has not occurred. This corner case is very rare with whole-genome data, but it is likely to cause problem for exome data.We should build a safe guard, such that the chr count in
${avail_cn}
should only run to max(SNVs chr). A solution would be to set max(SNVs chr)== max(avail-cn chr).The text was updated successfully, but these errors were encountered: