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
Problem during creation of the virtual environment #3
Comments
megares_to_external_header_mappings_v2.00.zip Hi Diego, Nice to meet another MEG! Thanks for trying AMR++ and for your detailed post. I'll try to answer all of your questions. However, could you please try the latest version of AMR++ v2.0.2 that we just uploaded? We were having some issues with RGI that we patched in this last version. I think we also addressed your issue with As for your last question, in MEGARes we moved away from the "gene name" and toward a gene accession that is more informative. The gene "Group" that we use is close to the gene name, but we go based on sequence similarity instead of the gene accession's given name in their original repository. You can read more information about gene names in this paper, Resistance Gene Naming and Numbering: Is It a New Gene or Not?. Still, if you want to track the original name of any of the MEGARes accessions, you can download the mapping file from the megares.meglab.org website. I'm also attaching it to this response for you. Thanks, and let us know if you have any other questions. Best, |
Hello, I have read the latest changes. I would like to try running I believe @AroArz will be glad to be notified about the latest news. Keep up with the good work! |
Hi Diego, I'll respond here, close this issue and we can continue our discussion in the next issue you just created #4 . Thanks for the tips! We are still new at managing software on github and appreciate the insight. We made those changes to the CHANGELOG.md file and we'll clarify which CARD database to use. We used the latest CARD db, which was 3.0.8 at the time, based on the conversion in the RGI issue #93. CARD also just released v3.0.9 and I imagine it would be best to keep up with the latest updates, but you can also download the old versions using this archive: We updated our README.md file to show both options. Thanks for your continuing support! |
Dear MEG team,
Cheers, this is Diego Brambilla, research fellow at MEG (yes, we are a neighbouring group!)
I would like to thank you for the hard work you have poured into the development of both MEAGRes2.0 and amrplusplus_v2.
I would like to report a problem I ran into when executing your pipeline in MARCONI, an HPC environment with SLURM as a job scheduler.
If I run main_AmrPlusPlus_v2_withRGI.nf and main_AmrPlusPlus_v2_withRGI_Kraken.nf, the pipeline fails.
Namely Processes based on RGI fail but they are ignored:
On a closer look. the
.command.err
produced by eachRun RGI
process reports this error message:The final line makes me believe that these errors occur during the building of the
nxf_container_env()
.This is in line with issue #1 , namely this comment from @AroArz , in which it is rightly highlighted that:
Issue #1 has been close even though the evidence I here provide suggest the problem related to RGI still stands.
Consider re-opening issue #1 as you see fit.
Interestingly,
[Errno 30] Read-only file system
is an error instance that may happen during the creation of new environments, as you can see in this issue.In addition, I report that the process
FilteredKrakenResults
fails because python cannot load numpy:This should be related to the python version installed in the environment created by Singularity, and not the python in my host system.
Problems with loading python modules have been reported before with python 2 (like this one), but
amrplusplus_v2
uses python 3.Again, my guess is that this problem is linked to the setting of the environment. In fact, the previous problem involves files availability in
/usr/local/envs/AmrPlusPlus_env/lib/python3.6/site-packages/app/
If you come to different conclusion, you may value opening a separate issue for this matter.
If you wish to integrally replicate my issue, you can retrieve the input data by runnug the attached script fastqdump.txt (you need to install
sratools
beforehand).I have cloned and used the
commit dc982589c30005ca01dbc847380d6d486523d72f
from themaster
branch of your pipeline, here is the command line I have used:for running
main_AmrPlusPlus_v2_withRGI.nf
:$nextflow run main_AmrPlusPlus_v2_withRGI.nf -profile singularity --reads "data_LMFS/*_R{1,2}.fastq" --output "../output_LMFS" --work "../work_dir_LMFS"
for running
main_AmrPlusPlus_v2_withRGI_Kraken.nf
:nextflow run main_AmrPlusPlus_v2_withRGI_Kraken.nf -profile singularity --reads "data_WARFARE/*_R{1,2}.fastq" --output "../output_WARFARE" --work "../work_dir_WARFARE"
Please tell me ifI can help you in any way, and please let me know.
Thanks for your time!
An off-topic question, if I may: the final output of
main_AmrPlusPlus_v2
, which areSamDedup_AMR_analytic_matrix.csv
andAMR_analytic_matrix.csv
, do not have resistance gene names in their annotation, but only the info on the 5 annotation levels plus the eventual label "RequiresSNPConfirmation". ONly the resistance mechanism is reported. How can I get the info of resistance gene names from amrplusplus_v2 output?The text was updated successfully, but these errors were encountered: