This library runs code associated with the TrajectoryNet paper [1].
Installation
TrajectoryNet is available in pypi. Install by running the following
pip install TrajectoryNet
This code was tested with python 3.7 and 3.8.
Example
Basic Usage
Run with
python -m TrajectoryNet.main --dataset SCURVE
To use a custom dataset expose the coordinates and timepoint information according to the example jupyter notebooks in the /notebooks/ folder.
TrajectoryNet requires the following:
An embedding matrix titled [embedding_name] (Cells x Dimensions)
A sample labels array titled sample_labels (Cells)
(Optionally) a delta embedding representing RNA velocity titled delta_[embedding_name] (Cells x Dimensions)
To run TrajectoryNet with a custom dataset use:
python -m TrajectoryNet.main --dataset [PATH_TO_NPZ_FILE] --embedding_name [EMBEDDING_NAME]
python -m TrajectoryNet.eval --dataset [PATH_TO_NPZ_FILE] --embedding_name [EMBEDDING_NAME]
See notebooks/EB-Eval.ipynb for an example on how to use TrajectoryNet on a PCA embedding to get trajectories in the gene space.
References
[1] Tong, A., Huang, J., Wolf, G., van Dijk, D., and Krishnaswamy, S. TrajectoryNet: A Dynamic Optimal Transport Network for Modeling Cellular Dynamics. In International Conference on Machine Learning, 2020. arxiv ICML
—
If you found this library useful, please consider citing:
@inproceedings{tong2020trajectorynet,
title = {TrajectoryNet: A Dynamic Optimal Transport Network for Modeling Cellular Dynamics},
shorttitle = {{{TrajectoryNet}}},
booktitle = {Proceedings of the 37th International Conference on Machine Learning},
author = {Tong, Alexander and Huang, Jessie and Wolf, Guy and {van Dijk}, David and Krishnaswamy, Smita},
year = {2020}
}
Metadata
Release files for TrajectoryNet 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| TrajectoryNet-0.2.4.tar.gz | 52.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| TrajectoryNet-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 117.0 kB
Release files / TrajectoryNet-0.2.4.tar.gz
| Download URL | TrajectoryNet-0.2.4.tar.gz |
|---|---|
| Size | 52.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4f284b80f3e2bf87f72ab0f700b9442284002d94a0887cf740906524ea80f840
|
|
BLAKE2b-256 checksum How to use checksums |
9aa117f596e6d0fd322f034c6da8d7731d558bd8ac10cc7b08b99d87609689a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.10.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Release files / TrajectoryNet-0.2.4-py3-none-any.whl
| Download URL | TrajectoryNet-0.2.4-py3-none-any.whl |
|---|---|
| Size | 64.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2d912fe0d63f57ae7a2dcf53a22b3d5de26abf850f5d5158bf15070f4cfd261c
|
|
BLAKE2b-256 checksum How to use checksums |
ad27e1a922f43c1ca4f1c4aba55adcda33c8791ae68a14d2cae7d5a2ad4be87e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.8.2 readme-renderer/32.0 requests/2.27.1 requests-toolbelt/0.9.1 urllib3/1.26.8 tqdm/4.62.3 importlib-metadata/4.10.1 keyring/23.5.0 rfc3986/2.0.0 colorama/0.4.4 CPython/3.9.10
|
Security for TrajectoryNet 0.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.