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

feature request: support unmapped BAMs as input #17

Open
znorgaard opened this issue Jul 3, 2024 · 1 comment
Open

feature request: support unmapped BAMs as input #17

znorgaard opened this issue Jul 3, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@znorgaard
Copy link

For some workflows, you may already have unmapped BAMs when you're ready to use splitcode and it would be helpful if you weren't required to convert them back to FASTQs.

As a specific example, PacBio HiFi data comes off instrument demultiplexed as unmapped BAMs. To do additional tag based extraction or demultiplexing with splitcode you currently need to convert to FASTQ.

@Yenaled Yenaled added the enhancement New feature or request label Jul 3, 2024
@Yenaled
Copy link
Collaborator

Yenaled commented Jul 3, 2024

Thanks -- I do think it'd be very useful as a feature (I mostly just hate writing the code to read/write BAM files which is why I haven't implemented it haha). Labeling this as an enhancement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants