Error in running development version of PureCN
4
0
Entering edit mode
hustlxc • 0
@hustlxc-11635
Last seen 4.5 years ago

I used PureCN to analyse a bunch of whole-exome sequencing cancer samples. I encountered the following ERROR for a few samples.

Error in if (abs(old.llik - llik) < 1e-04) { : ## source code in runAbsoluteCN

  missing value where TRUE/FALSE needed

 

Did anyone encounter the same error and fix it already?

Best,

Xiangchun

 

 

PureCN software error • 670 views
ADD COMMENT
0
Entering edit mode
@markusriester-9875
Last seen 28 days ago

Hi Xiangchun,

Haven't seen this one before. Is it possible for you to share the data for this sample for debugging? If you cannot share the data, can you send me the complete call and output of runAbsoluteCN with verbose=TRUE? 

Thanks a lot,

Markus

 

ADD COMMENT
0
Entering edit mode
hustlxc • 0
@hustlxc-11635
Last seen 4.5 years ago

Hi Markus, 

Thanks for your reply. The data is a little bit large. I need to upload it to google drive or github first and then will share the link with you. By the way, I will also re-run runAbsoluteCN with verbose=TRUE and get you the message.

Best regards,

Xiangchun

ADD COMMENT
0
Entering edit mode
@markusriester-9875
Last seen 28 days ago

Cool, thanks Xiangchun! You can try running it without the VCF, since this error happens in the SCNA fitting step. So you might only need to send me the coverage files to reproduce the bug.  

ADD COMMENT
0
Entering edit mode
hustlxc • 0
@hustlxc-11635
Last seen 4.5 years ago

Hi Markus,

I have uploaded the required data to Google drive https://drive.google.com/open?id=0B9TD9BwSoJuZaGVtRFVILWVHb00.

The bzip2 compressed file contains all the data and an R script I used to run PureCN. 

The 0116D01M200052C01_2101.log file contains logging information from runAbsoluteCN with verbose=TRUE.

Best,

Xiangchun

ADD COMMENT
0
Entering edit mode

Thanks a lot Xianchun, this is very helpful. I got the data (you can delete) and I can reproduce. Will get back to you shortly.

ADD REPLY
0
Entering edit mode

Looks like the problem was a simple double overflow in the Simulated Annealing because you set the number of iterations to 3000. This overflow should not happen and I will submit a fix soon. However, integer optimization problems should converge quickly, that's the reason the default is only 30. If it does not converge, then the solution is probably wrong or the data is very noisy.

May I ask why you increased this default? Did you observe that it sometimes improved your results?

ADD REPLY
0
Entering edit mode

I haven't compared the results from iteration=30 and iteration=3000. I just worry that 30 iterations is not enough for Simulated Annealing to converge. 

By the way, I found that PureCN works without error when I set cosmic.vcf.file=NULL and normalDB=NULL.

For a few samples, PureCN encountered similar ERROR when cosmic.vcf.file and normalDB are all set to NULL. I will re-run PureCN for these samples with default number of iterations in SA.

ADD REPLY
0
Entering edit mode

Thanks again for your reply. No worries, 30 is fine, since the SA step already starts from local optima obtained from an approximated likelihood and then just assigns integer copy numbers to copy number peaks. If this does not converge after 20 steps, it's usually very noisy data anyways and impossible to properly assign integer copy numbers to most segments. It's safe to increase to 300 or so, but won't help much.

The cosmic.vcf.file=NULL should be unrelated. normalDB in filterTargets just removes all targets with low coverage in the pool of normals. These should be exons for which the probes don't work well. 

ADD REPLY

Login before adding your answer.

Traffic: 546 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6