-
Notifications
You must be signed in to change notification settings - Fork 1
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
Empty outputs with lower coverage #15
Comments
Yanocomp is not really being actively developed any more, but I looked at the code to remind myself how it is working... The minimum coverage is set dynamically depending on the window size used for modelling: Lines 245 to 251 in afda4b5
So, when the default window of 3 adjacent kmers is used for modelling, the min depth (per replicate) is set to 6. This is to ensure that the number of samples used to fit the model is always greater than the number of features. Coverage in an RNA sequencing dataset can vary across several orders of magnitude depending on the gene, so it is unclear to me how you can be sure that all positions have approximately 70x, unless you are just testing one gene? |
That's exactly right, I am testing it on one gene and the coverage is close to 70x after filtering it based on total bases but there are definitely areas where the coverage dips a lot (may be due to which reads were included in the filtered dataset) |
That is weird, I'm not sure what is occurring in that case. Does it consistently happen with many different subsamples? |
I have been testing yanocomp on multiple coverage levels for the same data and for lower coverages (less than 70x), the output is empty. Is there anything with how the tool works that causes this?
In general, as the coverage is going down (from 1000x), the output keeps getting truncated in some positions (some positions does have low coverage compared to overall coverage due to the way filtering was done) and completely empty at less than 70x coverage.
It would be helpful if anyone can explain why this is happening. Thank you.
The text was updated successfully, but these errors were encountered: