Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash when specifying existing --star_index using star aligner #277

Open
ffmmulder opened this issue Dec 15, 2023 · 6 comments
Open

Crash when specifying existing --star_index using star aligner #277

ffmmulder opened this issue Dec 15, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@ffmmulder
Copy link

Description of the bug

When specifying an existing STAR index using the --star_index parameter the pipeline crashes and gives the following error:

Missing process or function map([Script_396cc086$_runScript_closure1$_closure2$_closure5@20bc6f4d])

 -- Check script '/hpc/ubec/tools/pipelines/nfcore/scrnaseq/./workflows/scrnaseq.nf' at line: 170 or see '.nextflow.log' file for more 
details

This is because in this case the ch_star_index is defined as a file instead of a tuple which is expected by the starsolo subworkflow (and which is also returned by STAR_GENOMEGENERATE in case no existing star genome is specified).

scrnaseq.nf:

ch_star_index = params.star_index ? file(params.star_index) : []

This can be fixed by adjust the line above to:

ch_star_index = params.star_index ? Channel.fromPath(params.star_index).map{f -> [[id:f.baseName], f] } : []

Command used and terminal output

Command

nextflow run /path/to/nfcore/scrnaseq/main.nf \
--input /path/to/amplesheet.csv \
--star_index /path/to/reference/star \
--fasta /path/to/fasta.fna \
--gtf /path/to/reference.gtf \
--protocol 10XV3 \
--aligner star \
--outdir /path/to/output

Output:

N E X T F L O W  ~  version 23.04.2
WARN: It appears you have never run this project before -- Option `-resume` is ignored
Launching `/hpc/ubec/tools/pipelines/nfcore/scrnaseq/main.nf` [mighty_pasteur] DSL2 - revision: bd078e3da5
[-        ] process > NFCORE_SCRNASEQ:SCRNASEQ:INPUT_CHECK:SAMPLESHEET_CHECK -
Missing process or function map([Script_396cc086$_runScript_closure1$_closure2$_closure5@20bc6f4d])

 -- Check script '/hpc/ubec/tools/pipelines/nfcore/scrnaseq/./workflows/scrnaseq.nf' at line: 170 or see '.nextflow.log' file for more details



### Relevant files

_No response_

### System information

* Nextflow version: 23.04.2
* Hardware: HPC
* Executor: Slurm
* Container engine: singularity
* OS: CentOS8 Rocky
* version of nf-core/scrnaseq: 2.4.1
@ffmmulder ffmmulder added the bug Something isn't working label Dec 15, 2023
@grst
Copy link
Member

grst commented Dec 15, 2023

Thanks for reporting!

Would you like to submit a PR with the fix?

@ffmmulder
Copy link
Author

Sure, currently doing a small test to make sure all works fine but looks ok... will see if I can do it later today!

@pinin4fjords
Copy link
Member

I'm still seeing this behaviour in 2.6.0 - did this fix not work?

@Billsfriend
Copy link

I met similar problem in 2.6.0. Setting --star_index with "/path/to/folder/" will end up with:

ERROR ~ ERROR: Validation of pipeline parameters failed!

 -- Check 'ye.1.log' file for details
The following invalid input values have been detected:

* --star_index: '/home/gjsx/append-ssd/work/star_index/' is not a file, but a directory (/home/gjsx/append-ssd/work/star_index/)

 -- Check script '/home/gjsx/.nextflow/assets/nf-core/scrnaseq/./workflows/../subworkflows/local/utils_nfcore_scrnaseq_pipeline/../../nf-core/utils_nfvalidation_plugin/main.nf' at line: 57 or see 'ye.1.log' file for more details

@grst
Copy link
Member

grst commented May 13, 2024

I'm still seeing this behaviour in 2.6.0 - did this fix not work?

I don't think anyone made the PR up to now.

@j-andrews7
Copy link

This is also a problem for all other aligners as far as I can tell.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants