8000 creating SAM file headers · Issue #3235 · seqan/seqan3 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

creating SAM file headers 8000 #3235

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
Open
notestaff opened this issue Feb 16, 2024 · 1 comment
Open

creating SAM file headers #3235

notestaff opened this issue Feb 16, 2024 · 1 comment
Labels
documentation documentation is missing to close this issue feature/proposal a new feature or an idea of

Comments

@notestaff
Copy link

The SAM/BAM handling tutorial (https://docs.seqan.de/seqan3/main_user/tutorial_sam_file.html) is quite helpful, but is missing examples on handling of SAM file headers: how to create them from scratch, how to access them, how to specify the reference sequences, how to reuse/update headers from an existing file. I was able to find most of this by searching the code, but it would be useful if these functions were included in the tutorial.
@notestaff notestaff added the feature/proposal a new feature or an idea of label Feb 16, 2024
@smehringer smehringer added the documentation documentation is missing to close this issue label Feb 21, 2024
@smehringer
Copy link
Member

Hi @notestaff,

thanks a lot for the feedback! Indeed we are missing documentation on the header functionality and a tutorial would also be helpful. We'll see what we can manage in the near future with our limited resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels 4014
documentation documentation is missing to close this issue feature/proposal a new feature or an idea of
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@notestaff @smehringer
0