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

Batch CRISPRessoPooled #198

Open
jsacco1 opened this issue Feb 11, 2022 · 1 comment
Open

Batch CRISPRessoPooled #198

jsacco1 opened this issue Feb 11, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@jsacco1
Copy link

jsacco1 commented Feb 11, 2022

I really appreciate the Batch function, but I would like to have a feature for multiple (batch) of CRISPRessoPooled samples.

I have to currently make a custom script to make separate txt files for each CRISPRessoPooled sample (which itself corresponds to 2 fastq files). Then run each sample individually:

CRISPRessoPooled -r1 fastq_R1.fastq.gz -r2 fastq_R1.fastq.gz -f sample_name.txt

It would be great if there could be a function that mimicked Batch, because sometimes I have experiments with ~10 samples. Something like:

CRISPRessoPooled -bs input.txt

Just a function where I don't have to keep manually inputting r1 and r2. Is there a quick workaround for this?

Thanks

@kclem
Copy link
Member

kclem commented Feb 12, 2022

HI @jsacco1 Thanks for using CRISPResso!

Would the function fo this program just be to read the CRISPRessoPooled parameters in from a file, and then to run them all? Or are you hoping that it would also aggregate the results after the run and produce an html file with links to the results?

If you're hoping to aggregate, do each of your pooled runs necessarily have the same amplicons? Or how would this information be aggregated in the most useful way?

@kclem kclem added the enhancement New feature or request label Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants