Documentation: https://mjvolk3.github.io/torchcell/
Database: https://torchcell-database.ncsa.illinois.edu:7473/browser/ (Neo4j Browser over the served TorchCell knowledge graph)
Database releases and compatibility: https://mjvolk3.github.io/torchcell/database/compatibility.html
Datasets: https://mjvolk3.github.io/torchcell/datasets/index.html
Dataset downloads (the tc-data API): https://mjvolk3.github.io/torchcell/guide/downloads.html
Download a dataset
Built datasets are served as versioned archives (the records LMDB plus its build
manifest) by the tc-data endpoint on the database host, with Swagger at /docs. Each
page below is one supported query over the knowledge graph and bundles the datasets it
returns: what the experiments measured, one stored record each, the value distributions,
the query, and the download commands.
| Page | Datasets (records) |
|---|---|
| Gene essentiality and single-mutant fitness | Gene essentiality, SGD (1,329); single-mutant fitness, Costanzo 2016 (20,484) |
| Amino acids and betaxanthin | Amino acids, Mulleder 2016 (4,678); amine peaks, Cooper 2010 (4,313); betaxanthin, Cachera 2023 (4,719) |
With an endpoint URL and a key (see Downloading datasets), a loader fetches its archive instead of building. Export the two variables in the shell:
export TC_DATA_URL=http://torchcell-database.ncsa.illinois.edu:8724
export TC_DATA_API_KEY=<your key>
or put the same two lines, without export, in a .env file in your project and load
it before constructing a loader:
from dotenv import load_dotenv
load_dotenv() # reads the .env beside this script or in a parent directory
from torchcell.datasets.scerevisiae.mulleder2016 import AminoAcidMulleder2016Dataset
dataset = AminoAcidMulleder2016Dataset(root="data/torchcell/amino_acid_mulleder2016")
The loader reads the two variables from the process environment and does not read .env
itself. With TC_DATA_URL unset it builds from the publisher's files instead.
The full collection served by the knowledge graph (51 datasets, 52.7 million experiments at release 2026.09.21) is listed on the Datasets page.
1 maintainer
Metadata
1 maintainer
Release files for torchcell 1.6.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| torchcell-1.6.0.tar.gz | 2.1 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| torchcell-1.6.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.5 MB
Release files / torchcell-1.6.0.tar.gz
| Download URL | torchcell-1.6.0.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bb70961d210ea419ebcf5d81bbbaf91c1699367062bb824e636c6098774be480
|
|
BLAKE2b-256 checksum How to use checksums |
4c6a4e0ebba07e92cf147e3894e31353f514973f07d841e87a69706253ecfcb8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / torchcell-1.6.0-py3-none-any.whl
| Download URL | torchcell-1.6.0-py3-none-any.whl |
|---|---|
| Size | 2.5 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b2a7f6ae63ee1159e1f248608b0fb5355db31b02462495708fa65da1a9b26fc5
|
|
BLAKE2b-256 checksum How to use checksums |
41b7870e9dd35e5527614ad54bee681e1fae67d4a967371e370a6e3f6affda65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log
