-
Notifications
You must be signed in to change notification settings - Fork 37
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
The data contains non-finite values. #252
Comments
Hey @yhj-j, Thank you for using TOBIAS. My first guess as to the reason for your error would be that you may have used a different peak file during To troubleshoot, please rerun Hope this helps! Best regards, |
Thank you for your response. I have split the problematic peak file into 12 parts based on chromosome number and carried out ATACorrect, Scorebigwig, and BINDetect separately on each. However, I still encounter the same error with the peak file for chromosome 12.
|
Okay, that does sound peculiar. May I ask how you generated those bed files? Perhaps for chromosome 12, there is a region written down in the file that is outside of the actual chromosome range and thus, no reads can be fetched from there, resulting in missing scores. You could also have a look whether all regions in your bed file have reads in the bam file / scores in the ScoreBigwig file associated with them (for example using bedtools intersect). If you want, you can also send me your input files so I can reproduce the error and see what might be causing the problem locally. |
Hello-thanks for the great tool! I am experiencing the same error for TOBIAS BINDetect 0.16.1. I used the same peak file for both ScoreBigwig and BINDetect, so that shouldn't be my issue. I realized, however, that ATACorrect output identical bigwig files for the corrected and uncorrected bigwigs, and the expected/bias bigwig files were empty. Not sure if these errors are linked? The test datasets run perfectly. I am now testing an older version of TOBIAS. Any other thoughts on how to troubleshoot? Thanks a lot! edit to add: version 0.14.0 had the same issue. |
"I encountered this error while performing the analysis, how should I troubleshoot it?
When I process another peak file with the same BAM file, there is no problem, but the peak file that reported the error seems fine when I import it into IGV.
Here is the code:
The text was updated successfully, but these errors were encountered: