Open gmagoon opened 6 years ago
Just wanted to follow up on this, as I now have a better picture of what is going on. I noticed that the error
module would sometimes actually intermittently work without error. I was also running a bunch of other processes at the time. Now that some of the processes have finished, both the error
and detect
modules seem to run reliably without error. I suspect one of my processes had a conflict, along the lines described here: https://unix.stackexchange.com/questions/71059/system-sending-sigterm-and-sigkill-during-normal-work . Since this seems to be a very esoteric problem specific to me, please feel free to close this issue.
Thanks for reporting this. As you've probably figured out, Atropos tries to use system gzip for compression when available, because it's much faster than using the python gzip module. However, there should probably be a way to turn off this behavior when it causes problems like what you observe. I am going to update this issue to be a request for this enhancement.
sounds great...thanks very much for the additional info, John
Hi John, I've just set up Atropos v. 1.1.17 on Ubuntu 16.04 via
pip3 install atropos
. I'm encountering issues like shown below when running basic commands with theerror
anddetect
modules. I've checked the input files withgzip -t
andgzip -l
and no problems show up (other than the known issue for the latter with files above 4GB). I've tried several fastq pairs and encountered the same error. Am I correct in suspecting that the -15 exit code corresponds to termination via SIGTERM? And if so, does this necessarily indicate a problem, if, for example, the termination signal came from atropos? I'm probably overlooking something that should be obvious, since it doesn't look like anyone else has reported seeing this error. Thanks in advance for any tips you can provide, Greg