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

Dorado basecalling workflow enhancements #713

Open
fraser-combe opened this issue Jan 8, 2025 · 2 comments · May be fixed by #659
Open

Dorado basecalling workflow enhancements #713

fraser-combe opened this issue Jan 8, 2025 · 2 comments · May be fixed by #659
Assignees

Comments

@fraser-combe
Copy link
Contributor

fraser-combe commented Jan 8, 2025

🆒

📌 Explain the Request

Propose enhancing the Dorado workflow with the following new features:

  • Add a --notrim Option in Dorado demux task: Allow users to retain reads with barcodes untrimmed, which can be useful for troubleshooting. For instance, users can inspect untrimmed reads in the "unclassified" folder when data issues arise, such as mis-binned reads.

  • Expose Custom Primer Trimming Options: Enable users to specify a custom set of primers for PCR primer trimming during the demultiplexing step. This will be achieved by integrating Dorado's --primer-sequences option, which accepts a FASTA file containing custom primer sequences. Note that using this option overrides the built-in primer sequences in Dorado.

Custom Primer Trimming Documentation from Dorado GitHub

Docker image could also be updated to Dorado 0.9.0 there is currently a PR for this on Staph-B

@AndrewLangvt
Copy link
Contributor

@fraser-combe this work is being implemented in #659, correct?

@fraser-combe
Copy link
Contributor Author

Yes ill update the PR once I complete it to refer to this issue

@fraser-combe fraser-combe linked a pull request Jan 24, 2025 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants