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

Cellranger mkref resource flags incorrect #329

Closed
RPSeaman opened this issue May 13, 2024 · 3 comments
Closed

Cellranger mkref resource flags incorrect #329

RPSeaman opened this issue May 13, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@RPSeaman
Copy link

RPSeaman commented May 13, 2024

Description of the bug

Hey all, I am looking at the cellranger mkref module and noticed that automatic available resources detection has been added, but I think I have spotted an inconsistency in the flags used for memory and cores:

In their docs (https://www.10xgenomics.com/support/software/cell-ranger/latest/resources/cr-command-line-arguments) they specify --memgb and --nthreads as the two flags for cpu and memory, not --localmem and --localcores as specified in the module.

Screenshot 2024-05-13 at 3 33 42 PM

Let me know you further clarification is needed.

Command used and terminal output

No response

Relevant files

No response

System information

nf-core/scrnaseq 2.6.0

@RPSeaman RPSeaman added the bug Something isn't working label May 13, 2024
@grst
Copy link
Member

grst commented May 15, 2024

--localmem and --localcore are global options passed to the martian runtime (martian is actually a workflow manager similar to nextflow). They should apply to all cellranger tools that are based on martian and mkref was changed from a simple script to the martian runtime in the last release.

https://www.10xgenomics.com/support/software/cell-ranger/latest/resources/cr-command-line-arguments

However, given the documentation you point at I'm wondering if we should additionally pass --nthreads because otherwise star index generation likely only runs on a single core which takes forever.

If you could update the module on nf-core/modules that would be fantastic!

@grst
Copy link
Member

grst commented Aug 8, 2024

Fixed in nf-core/modules#6136

@grst
Copy link
Member

grst commented Aug 12, 2024

fixed in dev

@grst grst closed this as completed Aug 12, 2024
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

2 participants