-
Notifications
You must be signed in to change notification settings - Fork 0
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
/mpwt/pwt_wrapper.py: ['Error', 'fatal error', 'No protein-coding genes with sequence data found.', 'Cannot continue.'] #88
Comments
Hi @Alexander20mc, It is strange because this error occurs when no proteins are found in the genome but they are present in the test files of Metage2Metabo. Which version of Pathway Tools, mpwt and Metage2Metabo are you using? Best regards, |
Hi @ArnaudBelcour , Thank you so much for your reply. I'm working on HPC cluster.......I'm not the person in charge of the system. I'm attaching all packages in the M2M's environment. for m2m, the latest version was installed (1.61), for mpwt the version is 0.86. and for pathway tools I found 22.5 and 23.0 versions installed Name Version Build Channel |
Thank you for the versions of your environment. I think that the error comes from the interaction between an old version of Pathway Tools ( A first test could be to see if your version of Pathway Tools has the latest patches for its version number by running Do you have the possibility to update to a more recent version of Pathway Tools (such as If you cannot, another way possible could be to use an older version of mpwt that could tolerate these warnings. To this end, I think that the version |
Hi, I have been trying to execute the software metage2metabo, using the command recon which uses pathway tools. I have the following error message:
****lib/python3.9/site-packages/mpwt/pwt_wrapper.py: load_errors = ['Error', 'fatal error', 'No protein-coding genes with sequence data found.', 'Cannot continue.']
I downloaded the NCBI protein database and set the ".ncbirc" file this way:
[ncbi]
/misc/scratch3/rogerlab_databases/other_dbs/blast_protein_database/
the whole error message:
###############################################
Metabolic network reconstruction
###############################################
######### Running metabolic network reconstruction with Pathway Tools #########
---------- Launching mpwt ----------
Check and delete unfinished builds of Pathway Tools.
! PGDB GCA_003433675 already in ptools-local, no PathoLogic inference will be launched on this species.
! PGDB GCA_003433665 already in ptools-local, no PathoLogic inference will be launched on this species.
|Input Check|GCA_003433665| No missing files
|Flat files creation|GCA_003433665| pathway-tools -no-patch-download -disable-metadata-saving -nologfile -load /misc/scratch3/collazos/m2m/workflow_genomes/GCA_003433665/flat_files_creation.lisp
=== Error in flat_files_creation.log for /misc/scratch3/collazos/m2m/workflow_genomes/GCA_003433665===
Error from the flat_files_creation.log file: /misc/scratch3/collazos/m2m/workflow_genomes/GCA_003433665/flat_files_creation.log
No protein-coding genes with sequence data found. Cannot continue.
------------////----------------
!!!!!!!!!!!!!!!!!-------------------- End error message for GCA_003433675 --------------------!!!!!!!!!!!!!!!!!
|Output Check|/misc/scratch3/collazos/m2m/workflow_genomes/GCA_003433675| 18 out of 23 dat files created.
|Output Check| WARNING: No pathologic.log file for /misc/scratch3/collazos/m2m/workflow_genomes/GCA_003433665, could not write log.
|Output Check| WARNING: No pathologic.log file for /misc/scratch3/collazos/m2m/workflow_genomes/GCA_003433675, could not write log.
-------------- Checking mpwt runs --------------
/!\ 2 failed runs on a total of 2 runs.
/!\ Error in GCA_003433665 during Moving output files step.
/!\ Error in GCA_003433675 during Moving output files step.
-------------- mpwt has finished in 9.06s! Thank you for using it. --------------
Something went wrong running Pathway Tools. See the log file in /misc/scratch3/collazos/m2m/recon_results4/pgdb_log/log_error.txt
The text was updated successfully, but these errors were encountered: