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

Support for CRAM submission #30

Closed
edsu7 opened this issue Aug 26, 2022 · 3 comments
Closed

Support for CRAM submission #30

edsu7 opened this issue Aug 26, 2022 · 3 comments
Assignees
@edsu7
Labels
Epic

Comments

@edsu7
Copy link
Contributor

edsu7 commented Aug 26, 2022

No description provided.

@edsu7 edsu7 self-assigned this Sep 15, 2022
@edsu7 edsu7 added the Epic label Oct 5, 2022
@edsu7
Copy link
Contributor Author

edsu7 commented Oct 13, 2022 •
edited
Loading

A potential issue is that submitter provides incorrect md5sum and filesize with CRAM file.
Current seq-tools check would miss this as it only checks the converted BAM and not the original CRAM. Adding seq-tools check for nested CRAM info assuming standardized format.

See #40

@puneet-oicr
Copy link

All tickets closed, Edmund working on documentation

@b-f-chan
Copy link

Closing, documentation done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@edsu7 edsu7

Labels
Epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@edsu7 @b-f-chan @puneet-oicr