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

DSL2: Ensure that all sharded fastQs make it into mapping. #1089

Open
TCLamnidis opened this issue Sep 27, 2024 · 3 comments
Open

DSL2: Ensure that all sharded fastQs make it into mapping. #1089

TCLamnidis opened this issue Sep 27, 2024 · 3 comments
Labels
bug Something isn't working DSL2
Milestone

Comments

@TCLamnidis
Copy link
Collaborator

TCLamnidis commented Sep 27, 2024

(Preface: I might be under caffeinated and seeing things, BUT)

I think the sharded FastQs never actually make it to mapping?
It looks like a channel ch_input_for_mapping is correctly created with them, but then all mappers in the if/else section of the MAP SWF start with: ch_input_for_mapping = reads, which pulls the original unsharded reads again... 🤔

I also get the feeling that the mapping output files should actually contain the shard number, to ensure they are kept when merging lanes. 🤔 🤔

@TCLamnidis TCLamnidis added bug Something isn't working DSL2 labels Sep 27, 2024
@TCLamnidis TCLamnidis added this to the 3.0 Augsburg milestone Sep 27, 2024
@TCLamnidis
Copy link
Collaborator Author

@nf-core/eager Could I get a second opinion? Am I missing something?

@shyama-mama
Copy link

shyama-mama commented Sep 27, 2024

Yes you are right we are using the original unsharded reads. We should be using ch_input_for_mapping.reads instead. Under caffeinated brain works just as well as the caffeinated one ;)

@shyama-mama
Copy link

Made simple changes to fix the bug.
#1090

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

No branches or pull requests

2 participants