-
Notifications
You must be signed in to change notification settings - Fork 695
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
--soloCBwhitelist option not working #5863
Labels
bug
Something isn't working
Comments
What module is this an issue for? |
My bad, this is for the Starsolo module (star/starsolo) |
matq007
added a commit
to matq007/modules
that referenced
this issue
Jul 31, 2024
Whitelist is set as optional because it is only used by `CB_UMI_Simple` and `CB_UMI_Complex`
matq007
added a commit
to matq007/modules
that referenced
this issue
Jul 31, 2024
Whitelist is set as optional because it is only used by `CB_UMI_Simple` and `CB_UMI_Complex`
github-merge-queue bot
pushed a commit
that referenced
this issue
Aug 1, 2024
* fix: wrong stub output files * fix: issue #5863 Whitelist is set as optional because it is only used by `CB_UMI_Simple` and `CB_UMI_Complex` * fix: convert star/starsolo from pytest to nf-test * fix: ignore Summary.csv * revert: Summary.csv works fine on when tested locally * Update snapshot --------- Co-authored-by: Simon Pearce <[email protected]>
Can be also closed now? @SPPearce |
Solved in #6062 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you checked the docs?
Description of the bug
The way --soloCBwhitelist takes an argument does not seem to work because it is written as metadata but the barcode whitelist needs to be in a (value) channel so it can be loaded into the Docker or Singularity container, and a file cannot be part of metadata. Can you fix it, please? Thank you. (I also think that having the solo as either part of the metadata or as a separate value channel in the input would be preferable.)
Command used and terminal output
No response
Relevant files
No response
System information
No response
The text was updated successfully, but these errors were encountered: