Where are you working? I’m wondering if the built-in indexes are not available at that server or similiar. They are active at the usegalaxy.* servers if you want to move over to one and try it there.
If that is not enough to help, what is the full content on the job information view for your failed job? The tool settings, inputs expanded, and logs expanded please. Copy/paste or shared link is good.
Thanks for the reply. I’m so new to this, I should have mentioned that I was on the use galaxy.org site and the mm10 worked fine for the HISAT2 step right before the featureCounts (I’m going through the video step-by-step to familiarize myself with everything). This is the URL for the history of the project:
The original files and the trimmomatic files have been purged because the system was telling me I was running out of memory, but the more recent steps are there. Does that help you find things, or is there more I should post?
The solution is to double check your inputs first. And, if the data is actually too “large” computationally, to pick a different method or consider using a scaled up private Galaxy server. The public computational resources are considerable but not appropriate for all use cases. For any situation, more available data storage space in your account is completely unrelated.
If you are ever not sure how to use a tool, Help for tools is directly on the tool form. Scroll down on any to review those resources. If a tool is included in a tutorial, you’ll find these links down in this section too.
What I noticed on the job details view (the “i” icon within any dataset):
The input BAM is on the larger side, so some tools may not be able to process it.
Filtering the BAM can be one solution. Remove any unmapped, and consider filtering for proper pairs above some minimum mapQ (20 is common). This is like a pre-filter – removing content that wouldn’t be considered anyway by the downstream tool – in an attempt to make the input “smaller” and less complicated for some tool to process.
Your inputs for this data were from a paired-end mapping but the option on the form was set to single end. This confused the tool, and the error message in the logs aligns with that guess.
I would suggest correcting that setting first, then to consider filtering if needed.