-
Notifications
You must be signed in to change notification settings - Fork 80
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
Issue with SQMtools #840
Comments
Any chance this is happening when resuming a previously saved R session? |
Yes, I can reproduce that exact error by
The question is that in SqueezeMeta/lib/SQMtools/R/genericTable.R Line 55 in edf13b1
data.table:::`[.data.table` being part of our environment, but this does not happen automatically when loading SQMtools. Instead, it only seems to happen after running loadSQM
|
Yes this was using an RDS file that had been transferred between R sessions. Doing it in the original session I am having no issues. However I have noticed that in my bin_table most of the bins have NA in the completeness, contamination and strain het columns. I have never seen that before, what would be causing that data to be missing? |
Maybe some issue running checkm for those bins in particular? |
Yep sure this is the syslog: I processed my SQM object the following way:
It was in the table output that I noticed most of the bins had NAs for completeness and contamination. Which I haven't had in the past. Here is an example of the table: |
I suspect the bins with missing checkm info are coming from eukaryotes (which CheckM does not cover). |
I don't think that is the case as when I look at the bin_table.csv the tax for all of them is K_bacteria;... |
I checked the actual .fa.contigs.fa.tax files as well and the consensus tax all seem to be bacteria, for example:
However the completeness and contamination values for this bin are both NA I did go ahead and do a separate install of checkM and ran it successfully on metabat2.1187.fa.contigs.fa:
As you can see the contamination and completeness was calculated correctly |
Yes, it seems that CheckM should have worked correctly for that one. My recommendation here would be to locate the contigs that are really from prokaryotes by loking at the bin table and running CheckM manually for those. We are actually going to upgrade to CheckM2 for the next version of SqueezeMeta (which should come sometime in summer) and we have rewritten the corresponding SqueezeMeta scripts, so whatever is causing this bug will not be present (though of course new bugs might!). |
Sorry another issue. I have loaded the project into R using loadSQM, but when trying to subset taxa I am getting an error which seems to be driven by an issue with the orf$table
The text was updated successfully, but these errors were encountered: