-
Notifications
You must be signed in to change notification settings - Fork 72
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
medaka was stopped with "truncated file" message #186
Comments
Hi, we had the same problem and solved it by downgrading samtools from 1.10 to 1.9 Philipp |
Bump -- have same issue, sometimes medaka completes, other times errors out with the samtools error. Downgrading on Work around was to downgrade medaka in conda, and then install latest from PyPi..... |
If I recall correctly the upgrade to samtools, bcftools, and htslib 1.10 was caused by something in bioconda packaging requiring the upgrade. Therefor using the PyPI distribution is the solution currently. I don't remember ever seeing issues like this with samtools 1.9. The issue here isn't to do with medaka per se, as the log above shows at the point of error we are running minimap2 and piping the output to samtools:
If any one knows why this error is occurring... |
I've left this issue to stew for a while. The only reports we've had of it happening occur with the conda package. I don't know if that indicates something up with the samtools conda package or simply that most of medaka's users are using conda. I'm going to close this issue as it is not an bug of medaka per se. If there continue to be issues we will look to amend the conda package. |
Hi,
this one does work without any problem:
So I just edited mini_align and voila! |
I think this bug of samtools v1.10 was addressed here: So this is probably fixed in samtools v1.11 (and was working in v1.9), but:
Huh, I was under the impression that 1.9 >= 1.9, and 1.11 >= 1.9 |
I don't pretend to understand conda's package resolution, I've seen it complain about things like this before. This is probably one for the bioconda developers. |
Agreed, will post there. Changing medakas dependencies to avoid samtools 1.10 could be important though, so that the |
+1 the 1.10 samtools bug is still persisting in the Conda package build and thus also in the biocontainer. |
Think I found why medaka 1.2.1 and samtools 1.11 do not mix: medaka deps:
samtools deps:
htslib conflicting. @cjw85 Is this htslib <1.11.0a0 dependency necessary? Cheers |
Apologies for no replying sooner, since this issue is closed I don't receive alerts. The bioconda recipe isn't putting that constraint: I suggest raising an issue (or making a PR) on bioconda as we have limited resource available to support the bioconda builds. |
Describe the bug
Medaka was stopped with "truncated file" message at random location of input file.
Logging
Error example in Ubuntu 18.04 servers
In Ubuntu 16.04 server (error example 1 for the same process)
In Ubuntu 16.04 server (error example 2 for the same process)
In Ubuntu 16.04 server (error example 3 for the same process)
Environment (if you do not have a GPU, write No GPU):
VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 (Ubuntu 18)
VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a) (Ubuntu 16)
Additional context
When I try to run medaka several times, the errors were occured in different location, which means that the process of "M::worker_pipeline" is stopped at random round (Above, I attached three error examples in Ubuntu 16.04 for the sample). In another sample, medaka ran successfully after about 10th trial. But I had no problem in running medaka for several other samples in these servers. Could you please tell me why medaka had this kind of problem in several samples and stopped in random place? I think it is not input file problem because medaka went through successfully for one sample which had medaka run error several times.
Thank you.
HJK
The text was updated successfully, but these errors were encountered: