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

CRISPRessoPooled with --alternate_alleles #358

Open
GreenSeaBug opened this issue Dec 4, 2023 · 2 comments
Open

CRISPRessoPooled with --alternate_alleles #358

GreenSeaBug opened this issue Dec 4, 2023 · 2 comments

Comments

@GreenSeaBug
Copy link

Hello,

When using CRISPRessoPooled with the --alternate_alleles parameter, what goes in the AMPLICON_NAME and AMPLICON_SEQUENCE columns of the description file? Should all alleles go in those columns or just one? Does the region_name column of the alternate alleles file correspond to the AMPLICON_NAME of the description file and, if so, must they be exactly the same?

And what happens if the gRNA is mismatched on non-target alleles? Will this affect the analysis in a bad way?

Thank you

@kclem
Copy link
Member

kclem commented Dec 4, 2023

The --alternate_alleles function is used when two (or more) alleles are amplified by a primer pair. This could be because a SNP exists in your amplicon, and you want to quantify editing on each allele separately.

The --alternate_alleles parameter accepts a separate file as a parameter. The names in 'region_name' must exactly match with the -f name. Your primary amplicon should be present in the -f file, and other amplicons can be provided in the --alternate_alleles file.

I find it simplest to create a file with potential alternate alleles by running CRISPRessoPooled once with --compile_postrun_references. You can then change the names and delete amplicon sequences in this file as appropriate, and pass this file in as --alternate_alleles.

If the gRNA is mismatched on non-target alleles, CRISPResso will align the reference and alternate alleles, and use the corresponding positions of the reference allele in the alternate alleles.

@GreenSeaBug
Copy link
Author

Thank you for clarifying that. All makes sense.

Just one thing: I found in my testing is that all alleles must be provided in the alternate_alleles file. If you only provide the other alleles (i.e. all alleles except the primary target allele), then it doesn't appear to make any output files for the primary target allele, even though the primary target allele is in the -f file.

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

2 participants