uzh-dqbm-cmi / PRIDICT2

MIT License
7 stars 5 forks source link

score with PRIDICT2.0 on existing pegRNA sequences #2

Open ov26 opened 1 week ago

ov26 commented 1 week ago

Hi! I was wondering if there was a capacity to run the PRDICT2.0 scoring platform on externally designed pegRNA sequences?

mathinic commented 1 week ago

Hi, There is no option to directly go from pegRNA alone to efficiency, as this would also require the target sequence and some alignment steps to figure out your intended edit. To avoid any misalignments or wrong predictions, we do not offer this option, but rather suggest that you run PRIDICT2.0 with the standard input for the given pegRNA (NNN(X/Y)NNN) and then filter the readout based on the pegRNA.

I could however implement some guidance in the ReadMe on how to do the second step (find the pegRNA score of a specific pegRNA in the output after prediction), if this is something that would help your research? :)

Best wishes Nicolas

ov26 commented 1 week ago

Hi! thanks for the quick reply! To make it easier and perhaps faster is there a way to fix the pegRNA parameters when running pridict (ie only generate pegRNA with a pbs length of x), to avoid generating all possibilities and then filtering?

mathinic commented 1 week ago

Yes, this is possible with the current setup. You can adapt the default range by editing the parameters at the top of the main script pridcit2_pegRNA_design.py (screenshot below).

E.g. if you are only interested in PBS length 13, you can replace the default parameters with [13] (or alternatively "range(13,14)"). Same is possible for RTT overhang length. Then PRIDICT2.0 will only predict pegRNA with these parameters, making it more efficient.

Does that help, or would there be a large need to being able to define PBS/RTT length for each target separately, e.g. as an argument in the batch input file?

image