Skip to content
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

Inconsistent Contaminant Detection in Decontam with Read Count Threshold #153

Open
blesso13 opened this issue Nov 7, 2024 · 1 comment

Comments

@blesso13
Copy link

blesso13 commented Nov 7, 2024

Hi,
We are currently working with two types of data: DNA and RNA. To address contamination, we decided to use Decontam with a read count-based approach instead of using blanks.
A month ago, we ran Decontam on our tables and obtained a certain number of contaminants. However, when we ran the same analysis again recently, we observed different results. Specifically, Decontam is now detecting fewer contaminants than it did before.
Could you confirm if there have been any updates or modifications to the code in the past month that might account for this change? We want to ensure that any discrepancies in our results are understood and accounted for.

Thank you for your assistance!

@benjjneb
Copy link
Owner

benjjneb commented Nov 7, 2024

Could you confirm if there have been any updates or modifications to the code in the past month that might account for this change?

No updates or changes in the past few months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants