-
Notifications
You must be signed in to change notification settings - Fork 27
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
R crashes with very specific input #35
Comments
More error details when running the same code on a Linux system (error is not platform dependent):
|
@kendrickkoo Hello, I just got this same error after attempting to run ~140 samples at once. Were you successful in fixing? |
@halessi |
Hi, has anyone found a solution to this, or at least an explanation? I've just encountered the same exact error, on a Linux platform:
The sample giving this error has a mean target coverage of 657X, so I don't think the problem here is due to low read depths, unless it is caused by low read depths in specific regions... Thanks! |
Just in case someone is having the same issue: we found that using the bedfile of the design for extracting the read counts instead of the exon positions for the hg19 build of the human genome provided by the package solved this problem. |
When looping through a large number of samples, I found that ExomeDepth would induce a crash on very specific files. This manifests as a termination of R with no error message. I have dug down into the function code and have attached data and code to reproduce the error.
The error only happens with the specific order of inputs (i.e. column 2 in "fail" as the test and column 1 as the reference). When flipping the two, the code executes without any issue. I have attempted to trace the error deeper but when running the ExomeDepth constructor piecemeal, a crash cannot be induced.
It is perplexing that specific data would cause such a crash. There is nothing unique about the sample associated with the test column even on manual inspection of the data.
failure_file.txt
The text was updated successfully, but these errors were encountered: