19 months ago by
United States
Hello,
When I have examined results in the past that came out this way, there was a problem with one of the following:
- Input data too large and the job ran out of memory at the Trinity assembly site (external)
- Inputs had some type of formatting problem, triggering a job failure (reasons can vary)
- That same external site performing the Trinity assembly had some technical issues beyond the user's control
- The host Galaxy server experienced connection issues with the external site (could be from either end - Galaxy or Trinity site)
For the first two, input changes are required. Read the help for Trinity. The tool in Galaxy is a wrapped version of the baseline tool (or rather, tools - all three are bundled in the wrapper).
For the last two, try rerunning. If repeated re-runs fail, then going back and checking for content-related reasons for the failure is the way forward. Should that not work, please send us a bug report: https://galaxyproject.org/issues/#usage-problem-reporting
Thanks! Jen, Galaxy team