Return to Question

Each line of the fastq bioinformatics format comprises 4 lines chunks (id, dna sequence, "+", quality score).

 

Downsampling a fastq is going to select n number of chunks or select x% of chunks. But I don't handle the downsampling: I just pass parameters to a tool called seqtk to handle that.

Each line of the fastq bioinformatics format comprises 4 lines chunks (id, dna sequence, "+", quality score).

Downsampling a fastq is going to select n number of chunks or select x% of chunks. But I don't handle the downsampling: I just pass parameters to a tool called seqtk to handle that.

A fastq is bioinformatics format and is comprised of 4 lines chunks (id, dna sequence, "+", quality score) fastq format. Downsampling a fastq is going to select n number of chunks or select x% of chunks. But i don't handle the downsampling i just pass parameters to a tool called seqtk to handle that.

Each line of the fastq bioinformatics format comprises 4 lines chunks (id, dna sequence, "+", quality score). 

Downsampling a fastq is going to select n number of chunks or select x% of chunks. But I don't handle the downsampling: I just pass parameters to a tool called seqtk to handle that.

I'm working on a project to downsample some fastqs (files that contain sequences). I'd like some insights on the bash I use to process the options. I especially feel like there's something to have a store_true action for the -t flag.

I'm working on a project to downsample some fastqs (files that contain sequences).

A fastq is bioinformatics format and is comprised of 4 lines chunks (id, dna sequence, "+", quality score) fastq format. Downsampling a fastq is going to select n number of chunks or select x% of chunks. But i don't handle the downsampling i just pass parameters to a tool called seqtk to handle that.

I'd like some insights on the bash I use to process the options. I especially feel like there's something to have a store_true action for the -t flag.