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

Allow lists of reads in file? #100

Open
mhoban opened this issue Sep 25, 2024 · 1 comment
Open

Allow lists of reads in file? #100

mhoban opened this issue Sep 25, 2024 · 1 comment

Comments

@mhoban
Copy link
Owner

mhoban commented Sep 25, 2024

Would it be useful to be able to specify your reads in text files? This would be in addition to the current thing where you can do a directory or a glob.

This could be useful if you have a whole ton of reads but only some of them are relevant for your pipeline run, like if you have a folder with

marker1_r1.fastq
marker1_r2.fastq
marker2_r1.fastq
marker2_r2.fastq
marker3_r1.fastq
marker3_r2.fastq

And you just want to do a run with one of those markers, you could do something like:

$ rainbow_bridge.nf --reads-file reads.txt

Or:

$ rainbow_bridge.nf --fwd-file reads_fwd.txt --rev-file reads_rev.txt

Where reads.txt look like:

marker2_r1.fastq
marker2_r2.fastq

And reads_fwd.txt looks like (do s/r1/r2/ for reads_rev.txt):

marker1_r1.fastq
marker3_r1.fastq

This is obviously a simple case where you could just use a glob, but there are others where this could be more useful. Particularly if someone has used the 'combined' multiplexing method (indices AND barcodes)

@mhoban
Copy link
Owner Author

mhoban commented Sep 26, 2024

Maybe reads should actually be a csv:

sample read1
sample1 marker2_sample1.fastq
sample2 marker3_sample2.fastq
... ...

or

sample read1 read2
sample1 marker2_sample1_r1.fastq marker2_sample1_r2.fastq
sample2 marker3_sample2_r1.fastq marker3_sample2_r2.fastq
... ... ...

This is how nf-core/radseq does it. Another advantage of this is that you can use arbitrary file names/extensions

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant