-
Notifications
You must be signed in to change notification settings - Fork 145
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
Catch MACS error #35
Comments
A quick and ugly fix is to add |
Is there a special error code that MACS generates in such a case? That would be interesting to catch and issue a warning for that sample. |
You mean an exit code? Not sure. I was saying to @orzechoj that we could implement a similar strategy to the one that we have in the rnaseq pipeline though, where we check the log files: |
Yeah, exit code was in my mind actually. I thought the failing MACS process issues an exit code |
The problem with the exit code is that it probably doesn’t differentiate for why it fails - we only want to catch these specific failures. I could be wrong though! |
I fear so, too! If I find some time I'll have a look. |
The exit code is 1, which isn't so informative. But
|
Closing in favour of #128 |
Sometimes MACS fails because the data are so bad that it can make a model of the peaks. The error message
Too few paired peaks (0) so I can not build the model!
is given. This causes the entire pipeline to crash, even if there is only one bad data set.A better solution would perhaps be to report this error, but then continue?
The text was updated successfully, but these errors were encountered: