As additional advice to that provided by @gallardoalba, it appears that your reference GTF
contains header lines. Header lines are out of specification for strict GTF
format (even though many data providers include them). When present, those lines can cause odd errors with many tools – and usually not mapping tools (if incorporated) – but instead with downstream tools. It is strongly recommended to remove any GTF
headers to avoid technical errors (whether a tool is run in Galaxy, or not).
Please try removing the header lines, rerun, and see if that resolves the error as a first-pass solution. If it doesn’t, then do investigate the GTF
content closer. The genome appears to have just one sequence/chromosome with the name “Chromosome”. If that is not a match for the sequence/chromosome label in your BAM
datasets, due to the genome mapped against having a different sequence/chromosome label, that can also cause conflicts but can be addressed.
“How to” is covered here:
- Overview: Extended Help for Differential Expression Analysis Tools
- Specifics for
GTF
formatting: Common datatypes explained >> Datatypes - Galaxy Community Hub (review theGTF
“tips”) - Other related help:
This is also covered in much prior Q&A:
- Searches: Search results for 'gtf' - Galaxy Community Help && Search results for 'htseq' - Galaxy Community Help
- The summary in this post is concise. Don’t worry about the specific tool/context of the original post – the format help for
GTF
data applies across analysis methods/tools:
Many things could be going wrong content-wise, but those are the top issues that tend to produce errors like yours. My guess is that you are hitting the “GTF formatting” issue first, then could possibly hit a “chromosome mismatch problem”. Verify/fix both as needed – full details are in the FAQs above.
Note: The GTF
is also a hybrid format (GFF3
transformed into a GTF
), but that will probably not be a problem with this particular tool.
Thanks!