-
Notifications
You must be signed in to change notification settings - Fork 8
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
Error running large no. of samples & spectra #2
Comments
Hello, this error might appear, if you have very few mutations in a specific sample. If you try more signatures than there are channels occupied in a sample, the log-likelihood contribution for that sample cannot be computed (line 785-803 in MutSpec.cpp). I have a look for a workaround. But do you really want that many signatures? On 30 Jun 2014, at 06:41, yangchoo wrote:
The Wellcome Trust Sanger Institute is operated by Genome Research |
Ah.. I see. Does that mean the contribution of a particular signature from a sample has to be non-zero? |
Hi yangchoo, thanks again for your question. It turns out it is aimed at the very heart of the EMu model. The technical reason for the error is described above, but underlying is the assumption that all the processes are, in principle, present in all the samples. The case that some processes are strictly absent, i.e. their activity is zero, is not well handled with the current implementation. That is mainly due to a saddle point approximation which is used to calculate the log-likelihood, but is not well defined for zero activity. |
Hi,
first off, thanks for the awesome program!
Everything works fine for hundreds of samples, but I'm running into periodic determinant = 0 errors while running EMu with a large number of samples (~6000). [Err msg: In get_llhood for m=6***, det(Hf) = 0.... ]
The program works fine up to ~15 spectra, then such errors start occuring periodically. I am thus unable to run EMu to completion for anything beyond 15 spectra.
Let me know if you need my .mutations or .opp. file.
Thanks!
The text was updated successfully, but these errors were encountered: