Hi @Mark_C
We weren’t able to see the details for the job in your history, or the inputs, so guessing what the error was coming up is hard to guess. In general, if a tool fails really quickly, there is some content issue with the inputs or possibly the server has some issue the administrators need to resolved. We can help to troubleshoot this.
Also keep in mind that several of the annotation modules for this tool are only available on a private version of Galaxy (or command line version). The public servers are only able to host the data that is not under a license. Example → Interproscan log4j error - #2 by jennaj.
Then, to troubleshoot on your own, you can review the tutorials we have that include the tool. The example data formats are probably what will be most interesting for you.
GTN Tutorails for Interproscan → Galaxy Training!
- Ecology / Marine Omics identifying biosynthetic gene clusters
- Genome Annotation / Genome annotation with Funannotate
- Genome Annotation / Functional annotation of protein sequences
What to do
- Compare to the examples for where the tool is usually used in protcols, plus common data preparation steps.
- The input should be in
fastaformat. A tool like NormalizeFasta can help! Or Fasta Statistics to check the bases. - How many sequences is hard to guess since the content of those sequences will matter more.
- Try with a subsample to see what happens if you think the content is exceeding resources (this use case usually involves the tool running for longer, then eventually dying, instead of a quick failure).
- For large work, running Split Fasta can reduce the job into smaller jobs, then you can use Collapse Collection after to merge. Be careful about the output format if you decide to use this – TSV is usually the safest choice.
For reviewing your history, if you want to toggle the sharing off then on again, and include the error you would like feedback for, including the inputs to that job, we can try again! Thanks! 