Nico Trummer

Hey, your config looks overly complicated - I would recommend you using the [resourceLimits](https://www.nextflow.io/docs/latest/reference/process.html#resourcelimits) config instead. Also, did you use the latest version of the pipeline and nextflow?

Hey, [STAR_GENOMEGENERATE](https://github.com/nf-core/circrna/blob/1a64623bcd6c4e5247fba6044fdf53c167db05a9/modules/nf-core/star/genomegenerate/main.nf#L3) comes with the resource label [`process_high`](https://github.com/nf-core/circrna/blob/1a64623bcd6c4e5247fba6044fdf53c167db05a9/conf/base.config#L43), which requests up to 72GB of memory on the first attempt. On subsequent attempts, the request is increased to `attempt * 72GB`....

This sounds like a different problem then. Could you provide the `.nextflow.log` file of a run where this happened?

Okay so my interpretation of the log is: 1. `STAR_GENOMEGENERATE` is submitted, picked up and fails due to memory issues (yesterday, 13:00) 2. `STAR_GENOMEGENERATE` is retried and submitted 3. The...

I will assume this has been solved, if not, feel free to re-open

@BiocondaBot please add label

We will soon bring this back to live in a dedicated nf-core/hadge hackathon

We are working on this on the `sponging` branch, we'll split the large sequence files into many smaller ones and process them independently. After that, the individual results will be...

You can skip it by not providing `params.mature`. If you are using iGenomes, you can override the default by setting `params.mature = null` manually. The proper fix will be added...

Hey, I think this should be fixed by now, if not feel free to reopen!