-
Notifications
You must be signed in to change notification settings - Fork 23
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
Issues with running RNA velocity (La Manno) analysis in kb_python 0.28.0 #228
Comments
--workflow lamanno is deprecated in kb-python 0.28.0. It's called the nac index now. See the recent documentation preprint: https://www.biorxiv.org/content/10.1101/2023.11.21.568164v1 |
See also pachterlab/kallisto#419 |
Hello Yenaled: Thanks for replying. https://scvelo.readthedocs.io/en/latest/VelocityBasics.html# In the previous kb version, after importing the h5ad file into Python as Anndata object, that object had two layers: Regards, |
Yes, the 3 layers (nascent, mature, and ambiguous) correspond to (unspliced, spliced, and ambiguous), respectively. Ideally I should have updated the nomenclature in the anndata. In any case, if you're ever unsure, you can manually inspect/use the .mtx files directly (which is how I recommend creating h5ad and loom files from). |
@NikTuzov I updated the nomenclature to nascent, mature, and ambiguous for the layers in kb-python version 0.28.1 which I just released. |
Hello:
Could you please help me.
Initially I used kb ref and count, in kb-python 0.27.3, as described here:
https://www.kallistobus.tools/tutorials/kb_velocity/python/kb_velocity/
and everything worked as expected.
Then I switched to kb-python 0.28.0, and kb ref began to fail:
I found that in 0.28.0 there were some changes regarding the indexes:
https://github.com/pachterlab/kallisto-transcriptome-indices
So I downloaded the four files for human index as follows:
and then tried to run La Manno workflow, but it failed:
Does it mean that RNA velocity analysis is essentially disabled in kb-python 0.28.0?
If not, how do I run it?
Regards,
Nik
The text was updated successfully, but these errors were encountered: