Skip to main content

xiRT 2.0

xiRT

Retention-time prediction for linear and crosslinked peptides using PyTorch. The default model learns modification-aware peptide embeddings, shares a recurrent encoder between crosslink branches, and predicts continuous RTs or fraction labels. It runs on CPU or CUDA.

Install and run

Requires Python 3.12–3.14; the default development interpreter is 3.13. The PyPI distribution is xirt-torch; the Python import and CLI remain xirt.

uv sync --locked --extra cpu
uv run --no-sync xirt -p xirt_params.yaml -s learning_params.yaml
# Edit the generated configurations for your input columns and targets.
uv run --no-sync xirt -i psms.csv -o results -x xirt_params.yaml -l learning_params.yaml

Replace --extra cpu with --extra cuda for the locked CUDA backend. Optional extras provide local MLflow tracking (tracking), TensorBoard (tensorboard), Lion (experiments), and local ESM-C embeddings (esm, Python 3.12 only). ESM model access and licensing are separate.

Fine-tuning

Native recurrent models support full fine-tuning, frozen-encoder head training, and GRU-weight LoKr or LoRA. Checkpoints retain architecture and adapter settings. See fine-tuning for the API, YAML and measured comparison.

TensorFlow is no longer an application dependency or supported backend. Historical TF and PyTorch predictions, checkpoint provenance, tables and plots are preserved under benchmark-tf-torch/<cohort>/results/. PyTorch had lower mean held-out RMSE on two of five evaluated cohorts, not all five. See benchmark results. Keras .h5 models cannot be loaded by xiRT 2.0.

Examples

CPU notebooks cover training, checkpoint-based prediction and all four fine-tuning strategies with 2,048 observed peptide pairs. Training uses up to 150 epochs with validation-based early stopping:

uv run --no-sync marimo edit examples/train_predict.py --host 127.0.0.1
uv run --no-sync marimo edit examples/fine_tune.py --host 127.0.0.1
# Run both without a notebook server:
make examples

Development

make sync
make check
make build

pixi run sync bootstraps the same locked uv environment. make help lists documentation, notebook, test and release commands. Benchmark code lives in xirt/data_pipelines/benchmarks/ and is excluded from the production wheel.

Documentation · Configuration · Migration · Development

Citation

Giese, S.H., Sinn, L.R., Wegner, F. et al. Retention time prediction using neural networks increases identifications in crosslinking mass spectrometry. Nature Communications 12, 3237 (2021). https://doi.org/10.1038/s41467-021-23441-0

Contributors: Sven Giese and Ludwig Sinn.

Metadata

Release files for xirt-torch 2.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for xirt-torch 2.0.0
File Size Uploaded Provenance
xirt_torch-2.0.0.tar.gz 1.1 MB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for xirt-torch 2.0.0
File Interpreter ABI Platform
xirt_torch-2.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 1.1 MB

Release files / xirt_torch-2.0.0.tar.gz

Download URL xirt_torch-2.0.0.tar.gz
Size 1.1 MB
Tags Source
SHA-256 checksum
How to use checksums
95217a5e32745e82414fa46951cd1926d73801ed54acb984386a2fad0b894fef
BLAKE2b-256 checksum
How to use checksums
dc42e09b6ed8201f72288f0488ba20e8862539b7e1b66b079d6e8941933f451c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Release files / xirt_torch-2.0.0-py3-none-any.whl

Download URL xirt_torch-2.0.0-py3-none-any.whl
Size 68.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a526fd565fafd5b38006075374ee06432b44fef438131e34d5b927100ac5a34b
BLAKE2b-256 checksum
How to use checksums
c36a23c2bd04f60b196151613e4a78caca16bb5a4a8f114c6a545de2ad3a85b9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.14

Security for xirt-torch 2.0.0

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.

Release history Release notifications | RSS feed

This release

2.0.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page