You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very important in my opinion to have some info in the docstring about the format that the time point annotation needs to have in order to results in the expected results. It would also be good to check the dtype of the passed .obs annotation and to create the timepoint connections accordingly, as this is really critical.
The text was updated successfully, but these errors were encountered:
Hey @Marius1311
Thank you for reporting this issue. Will have this fixed in Scanpy. We will force data type as categorical for time points, and make the proper checkup and changes to the code, and docstring.
In my AnnData object, I have a field
adata.obs['day']
, which is categorical, callingadata.obs['day'].cat.categories
yieldsSo the values are strings in the right order. However, when I call Harmony using the scanpy interface, the timepoint connections are created using
which permutes my timepoints to a random order. To keep the order, I need to change this to
It would be very important in my opinion to have some info in the docstring about the format that the time point annotation needs to have in order to results in the expected results. It would also be good to check the dtype of the passed
.obs
annotation and to create the timepoint connections accordingly, as this is really critical.The text was updated successfully, but these errors were encountered: