Thanks for sharing the history as @igor suggested. Very helpful!
And I can see that you have tried the prior help from here (standardizing the fasta format) → MITOS2 error can't run job
I can also see the warning on the Mitos2 tool form when selecting the different fasta formatted datasets in your history. For you and anyone running into this issue later on, it will look something like this. A bit confusing with the programming logic exposed, but whenever the Run Tool button has a hover-over message, this indicates a data conflict issue that needs to be resolved (or, expect problems!) with any tool.
From what I can tell, the problem is that while these inputs are in the correct format there is still a conflict with the content of the files. Mitos2 is expecting an input with a single fasta sequence record. Your datasets contain fasta datasets with multiple records. How to check? Inspect using the eye icon for small datasets, or run a tool like Fasta Statistics and review the report.
Help
MITOS2 does a de-novo annotation of a given metazoan mitochondrial sequence.
Inputs
- A fasta formatted sequence
- MITOS2 processes only FASTA files containing a single sequence. If you have a FASTA file with multiple sequences you may use the tool Split Fasta files into a collection. The resulting collection can then used as input to MITOS2.
- The correct genetic code needs to be selected
- Reference data needs to be selected (can be provided by an administrator using the MITOS data manager)
I would try running Collection Operations → Split Fasta files into a collection on your file. You can then run Mitos2 on the entire collection as a batch.
Please give that a try and let us know what happens! If you still have problems, a screenshot of the tool form filled out with your input choices (input dataset and other parameters) will help with more troubleshooting. Thanks! 