Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
### Enhancements & fixed

- Automate release creation. By @Aratz [#235](https://github.com/nf-core/pixelator/pull/235)
- Document how to configure DuckDB temporary storage environment variables. By @johandahlberg [#238](https://github.com/nf-core/pixelator/pull/238/)
- Automate post-release backsync to `dev`. By @Aratz [#239](https://github.com/nf-core/pixelator/pull/239)

## [[5.0.0](https://github.com/nf-core/pixelator/releases/tag/5.0.0)] - 2026-07-13
Expand Down
21 changes: 21 additions & 0 deletions docs/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -310,6 +310,27 @@ Specify the path to a specific config file (this is a core Nextflow command). Se

## Custom configuration

### DuckDB temporary storage

When Pixelator runs memory-constrained DuckDB work (for example `denoise` or component filtering), it can spill
temporary data to disk. For container profiles, nf-core/pixelator sets
`PIXELATOR_DUCKDB_TEMP_DIR` to `TMPDIR` if it is set, otherwise to `/tmp`, so spill files land on local disk rather than next to the
`.pxl` file (which may live on networked storage such as S3/Fusion).

That default works on most systems. Override it when it does not — for example if `/tmp` or `TMPDIR` is too
small, is on a networked or otherwise unsuitable filesystem, or is not writable inside the container.
You can also set `PIXELATOR_DUCKDB_MAX_TEMP_DIR_SIZE` to cap how much disk DuckDB may use for spill files
(unset means no limit). Values use DuckDB size syntax (for example `"10GB"`).

Set either variable in a Nextflow config passed with `-c`:

```groovy
env {
PIXELATOR_DUCKDB_TEMP_DIR = '/path/to/local/tmp'
PIXELATOR_DUCKDB_MAX_TEMP_DIR_SIZE = '10GB'
}
```

### Resource requests

Whilst the default requirements set within the pipeline will hopefully work for most people and with most input data, you may find that you want to customise the compute resources that the pipeline requests. Each step in the pipeline has a default set of requirements for number of CPUs, memory and time. For most of the pipeline steps, if the job exits with any of the error codes specified [here](https://github.com/nf-core/rnaseq/blob/4c27ef5610c87db00c3c5a3eed10b1d161abf575/conf/base.config#L18) it will automatically be resubmitted with higher resources request (2 x original, then 3 x original). If it still fails after the third attempt then the pipeline execution is stopped.
Expand Down
Loading