azimuth Python package and azimuth web service yield different scores

MicrosoftResearch / Azimuth

Machine Learning-Based Predictive Modelling of CRISPR/Cas9 guide efficiency

BSD 3-Clause "New" or "Revised" License

228 stars 89 forks source link

azimuth Python package and azimuth web service yield different scores #25

Closed dariomel closed 6 years ago

dariomel commented 6 years ago

this script reproduces the problem.

Also, the scores obtained by that script from the azimuth Python package seem to agree with those produced by https://crispr.ml when submitting ENSG00000100823 (APEX1), and with those produced by GPP sgRNA Designer when submitting gene ID 328 (also APEX1), indicating that both servers ignore the parameters "Target Cut Length" and "Target Cut %" when calculating the "On-Target Efficacy Score". This limitation is not obvious from the documentation.

jjc2718 commented 6 years ago

The web service (called by your script) is running an outdated version of the code. See https://github.com/MicrosoftResearch/Azimuth/tree/v1.0 for details on what has changed.

Because of this, we're no longer officially supporting the web service. The results produced by https://crispr.ml and the sgRNA Designer tool are correct (and we recommend using those services going forward), as well as the results produced by the code in the latest version of this repo.