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

.fastq files stay uncompressed for a long time if input is bam #78

Open
dwuab opened this issue Mar 20, 2019 · 2 comments
Open

.fastq files stay uncompressed for a long time if input is bam #78

dwuab opened this issue Mar 20, 2019 · 2 comments
Assignees

Comments

@dwuab
Copy link

dwuab commented Mar 20, 2019

I don't think this is a bug, but the default behavior could be problematic. If the input files are of .bam format, .bam files will be converted into .fastq files, uncompressed (according to bam_input() in MToolBox.sh). The uncompressed files will be compressed only after all .bam files have been converted (according to fastq_input() in MToolBox.sh). So during the time of conversion, there will be lots of uncompressed .fastq files in the output directory, occupying ridiculous amounts of space if you have lots of input samples. I think .fastq files should be compressed right after they were created.

@domenico-simone
Copy link
Member

Hi,

thanks for this remark, this is a possible improvement for the next update.

Domenico

@dwuab
Copy link
Author

dwuab commented Mar 20, 2019

Hi,

thanks for this remark, this is a possible improvement for the next update.

Domenico

Thanks for your reply! I also noticed that in the final results, there are uncompressed .sam and .fastq files. Would be great if those are compressed as soon as they are generated.

@clody23 clody23 assigned clody23 and domenico-simone and unassigned clody23 Jul 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants