Issues running dada from DADA2

[jennaj]

Hi @Laura_Peirson

If a dataset is gray, that means the job is queued. How this works:

@jennaj

When working at UseGalaxy.org, UseGalaxy.eu, or UseGalaxy.org.au, your analysis jobs execute at large scale academic clusters. Hundreds of thousands of jobs process each month!

• Use a Workflow for batch work.
• Allow queued (grey color) and executing (yellow-orange) datasets to finish processing.
• Deleting and rerunning puts your job back at the end of the queue again!
• Job priority is the exactly the same for everyone.
• Be patient. Galaxy is a free service, when a lot of people are using it, you may have to wait longer than usual (especially for ‘big’ jobs, e.g. alignments).

Then, if you are looking for a protocol to follow, this is probably what you are looking for.

• Hands-on: Building an amplicon sequence variant (ASV) table from 16S data using DADA2 / Building an amplicon sequence variant (ASV) table from 16S data using DADA2 / Microbiome

I just ran through that tutorial as a test, and everything was working. I used the input data and workflow without any changes to create this reference/example.

• https://usegalaxy.org/u/jen-galaxyproject/h/building-an-amplicon-sequence-variant-asv-table-from-16s-data-using-dada2

Maybe those two resources can help you understand what is going on in your own history? But if you would like feedback here instead, you will need to post the link for your shared history back here with your question about it.

Right now it just seems to be queued – be sure to not stop/restart a job repeatedly or it may never get a chance to run!