An error occurred while running the tool toolshed.g2.bx.psu.edu/repos/iuc/mitos/mitos/1.1.7+galaxy0.
Execution resulted in “Fatal error: Exit code 1 ()” message.
Tool generated the following standard error:
Traceback (most recent call last):
File “/usr/local/tools/_conda/envs/__mitos@1.1.7/bin/runmitos.py”, line 458, in
featurelist = mitos(fname, args.code, args.outdir,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/tools/_conda/envs/__mitos@1.1.7/bin/runmitos.py”, line 238, in mitos
checklokalfeature(localcheck, featurelist, sequence, refdir)
File “/usr/local/tools/_conda/envs/__mitos@1.1.7/lib/python3.12/site-packages/mitos/mergefeature/init.py”, line 563, in checklokalfeature
struct = cmrealign(sseq, lname, refdir)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/tools/_conda/envs/__mitos@1.1.7/lib/python3.12/site-packages/mitos/mitfi/init.py”, line 147, in cmrealign
with open(tdir + “/cmrealign.str”) as f:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: ‘/data/jwd02f/main/073/463/73463100/tmp/tmp_3k9sbm0/cmrealign.str’
Need some help to troubleshoot the error on the execution of the MITOS tool version 1.1.7 on my one input file in fasta format. The rest input files have good, well-generated output files using the tool. Here is the link of my history: https://usegalaxy.eu/u/gerry_ramos_jr/h/unnamed-history
I cannot decipher the error message, but have you considered MITOS2? I have impression it is significantly faster that the original software. I tested MITOS2 in Europe using another file and don’t see any issue with it.
I have some reservation about the input file used for the failed job: 45% of bases are unknown (N), the remaning nucleotides are recorded in low case characters often reserved for masked sequences and the sequence name is rather long. The test file I used contains only one unknown nucleotides and no low case characters.
I have acknowledged these recommendations, @igor. If I remove the multiple N characters within the sequence in the FASTA file, does it affect the data output/result? Thank you in advance.
Hi @gerry_ramos_jr
I don’t know why the original MITOS has failed on your data. I tested it in Europe, and it works on a test file. You can remove excessive unknown nucleotide and test if it resolves the issue.
However, MITOS2 is faster and less sensitive to data. Unless you have to use the original software, MITOS2 might be a good option.
I tried removing the unknown nucleotide bases within the sequence and finally it worked regardless of the used letter case and the sequence name length. I think, too much N characters or unknown bases can actually affect the processing of an input data in the server. Thanks for this suggestion, @igor!
