Closed zktuong closed 9 months ago
Hi @zktuong,
Thank you for your detailed report. I've reviewed the changes between v1.3.0 and v1.3.1 in palantir.core
: Comparison Link. Surprisingly, I found no modifications affecting your case. Additionally, the failing call data_df.loc[early_cell, :]
remains unchanged in v1.3.0: Commit Reference.
Likewise, palantir.utils.determine_multiscale_space
appears invariant for your use case.
For debugging, could you check if the index data type undergoes a conversion, perhaps to a categorical type? This may be due to varying versions of Scanpy or pandas.
As an immediate remedy, Palantir v1.3.1 supports direct AnnData object input, eliminating the need to manually create DataFrames. Here's an example; adjust parameters as needed.
Looking forward to your insights and whether this mitigates your issue.
hi there, thanks for the prompt response!
your solution works!
However, for completeness, the source of the issue is with dm_res["EigenVectors"].index
returning a RangeIndex
instead of Index
in v1.3.1.
I tested it on v.1.2.0, 1.3.0 and 1.3.1 out over here: https://github.com/zktuong/troubleshooting_palantir/ (look at cell 8 in the 3 notebooks)
I suppose this is taken care of within anndata but if a user doesn't want to use anndata and just wants to use a pandas dataframe, then it will cause this issue.
so looking at the code, it would be here:
not sure how to adjust it without breaking stuff...
Thanks for the insightful analysis! A refactor inadvertently omitted lines that manage the index; this has been rectified in this commit. For those keen to test the hotfix, execute the following:
pip install 'git+https://github.com/settylab/Palantir'
Please free feel to report any feedback or reopen the issue if it persists regardless of the patch!
thanks for the swift update! works now!
Hi,
i'm trying to run a simple chunk like so:
but it's triggering an error:
my
pb_adata.obs_names
are['0', '1', '2', ... '1360']
in order to solve this, i had to do:
This isn't an issue in v1.3.0 but occuring for me in v1.3.1.
i see that you've made some changes to
run_diffusion_maps
recently - can you think of why this is happening?