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
I'm imagining step 2 becomes "Projection" instead of "UMAP" and then there is a toggle to switch between umap and phate.
The Setup UI would then need to show slightly different parameters.
I'm thinking this would be implemented as a new phater.py script similar to umapper.py that does PHATE and outputs phate-001.parquet etc.
Then when you cluster you could pass in either a umap-001 or phate-001. Perhaps renaming the umaps folder to projections and allowing either umap-* or phate-* would be the way to go, as the outputs will be essentially identical, but recording the inputs will be important.
This would also mean having references to umap_id in cluster-.json and scope-.json be updated to projection_id
The text was updated successfully, but these errors were encountered:
It would be interesting to be able to swap PHATE for UMAP for dimensionality reduction.
https://phate.readthedocs.io/en/stable/
I'm imagining step 2 becomes "Projection" instead of "UMAP" and then there is a toggle to switch between umap and phate.
The Setup UI would then need to show slightly different parameters.
I'm thinking this would be implemented as a new
phater.py
script similar toumapper.py
that does PHATE and outputs phate-001.parquet etc.Then when you cluster you could pass in either a umap-001 or phate-001. Perhaps renaming the
umaps
folder toprojections
and allowing either umap-* or phate-* would be the way to go, as the outputs will be essentially identical, but recording the inputs will be important.This would also mean having references to umap_id in cluster-.json and scope-.json be updated to projection_id
The text was updated successfully, but these errors were encountered: