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] Enable compatibility for .gz, maybe .cr files #73

Open
Firedrops opened this issue Feb 18, 2019 · 0 comments
Open

[Feature Request] Enable compatibility for .gz, maybe .cr files #73

Firedrops opened this issue Feb 18, 2019 · 0 comments
Labels
enhancement New feature or request tracked

Comments

@Firedrops
Copy link
Contributor

BWA can natively work with .fastq.gz files, but it appears the upstream pipeline does not directly pass the files to the aligner, but extracts information from it first. Hence .gz files do not appear to work currently.
The jobs stop at Parse FastQ data part, with no outputs.

image

It might also be a good idea to support cryfa encrypted files, which act as both compression and security in the future.

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

No branches or pull requests

3 participants