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.

Sign up for GitHub

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

Jump to bottom

DSL2: Add library merge step after damage_manipulation #1039

Closed
TCLamnidis opened this issue Jan 26, 2024 · 1 comment · Fixed by #1043
Closed

DSL2: Add library merge step after damage_manipulation #1039

TCLamnidis opened this issue Jan 26, 2024 · 1 comment · Fixed by #1043
Labels
DSL2
Milestone
3.0 Augsburg

Comments

@TCLamnidis
Copy link
Collaborator

Currently, lanes are merged after mapping to the library level. Deduplication and damage manipulation take place at this granularity, but genotyping onwards should happen AFTER merging libraries to the sample level.
@TCLamnidis TCLamnidis added this to the 3.0 Augsburg milestone Jan 26, 2024
@TCLamnidis TCLamnidis linked a pull request Mar 18, 2024 that will close this issue
DSL2: library merge #1043
Merged
11 tasks
@TCLamnidis
Copy link
Collaborator Author

Addressed in #1043.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
DSL2
Projects
None yet
Milestone
3.0 Augsburg
Development

Successfully merging a pull request may close this issue.

DSL2: library merge nf-core/eager
1 participant
@TCLamnidis