CoCoLIT (AAAI'26)
CoCoLIT: ControlNet-Conditioned Latent Image Translation for MRI to Amyloid PET Synthesis
Alec Sargood*,
Lemuel Puglisi*,
James Cole,
Neil Oxtoby,
Daniele Ravì†,
Daniel C. Alexander†
* Joint first authors,
† Joint senior authors
News
- 2025-10: Our paper CoCoLIT has been accepted at AAAI 2026 (17% acceptance rate).
Installation
This repository requires Python 3.10 and PyTorch 2.0 or later. To install the latest version, run:
pip install cocolit
Usage
After installing the package, you can convert a T1-weighted MRI to a Florbetapir SUVR map by running:
mri2pet --i /path/to/t1.nii.gz --o /path/to/output.nii.gz
If your MRI has not been preprocessed yet, you can run the full preprocessing pipeline directly from the CLI (skull-stripping, affine registration to MNI space, and WhiteStripe normalization):
mri2pet --i /path/to/t1.nii.gz --o /path/to/output.nii.gz \
--preprocess
Optionally, save intermediate preprocessing files with:
mri2pet --i /path/to/t1.nii.gz --o /path/to/output.nii.gz \
--preprocess \
--preprocess_out /path/to/preproc_outputs
To replicate the results presented in the paper, include the --m 64 flag.
Training & Reproducibility
To reproduce the experiments reported in the paper, please follow the reproducibility guide.
Disclaimer
This software is not intended for clinical use. The code is not available for commercial applications. For commercial inquiries, please contact the corresponding authors.
Citing
Arxiv Preprint:
@article{sargood2025cocolit,
title={CoCoLIT: ControlNet-Conditioned Latent Image Translation for MRI to Amyloid PET Synthesis},
author={Sargood, Alec and Puglisi, Lemuel and Cole, James H and Oxtoby, Neil P and Rav{\`\i}, Daniele and Alexander, Daniel C},
journal={arXiv preprint arXiv:2508.01292},
year={2025}
}
Contacts
For any inquiries, please contact:
- Alec Sargood: alec.sargood.23@ucl.ac.uk
- Lemuel Puglisi: lemuel.puglisi@phd.unict.it
Metadata
Release files for cocolit 0.3.1
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 | Actions |
|---|---|---|---|---|
| cocolit-0.3.1.tar.gz | 28.4 kB | Without provenance | Details for cocolit-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cocolit-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for cocolit-0.3.1-py3-none-any.whl |
Total release size: 58.6 kB
Release files / cocolit-0.3.1.tar.gz
| Download URL | cocolit-0.3.1.tar.gz |
|---|---|
| Size | 28.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c6d696d4fd2719b648c166d98eb6cea3a3a1a687f7543695cc56fae3a033945a
|
|
BLAKE2b-256 checksum How to use checksums |
c2dfbac5bc4cce5f6cf7a44f08142d45069f2f0dae2267c7db72f0ed81626e02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.0
|
Release files / cocolit-0.3.1-py3-none-any.whl
| Download URL | cocolit-0.3.1-py3-none-any.whl |
|---|---|
| Size | 30.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
db8777024106d4eb12516dd3f7a24f76c572adadd35b4867f43dee86965c79e0
|
|
BLAKE2b-256 checksum How to use checksums |
e9f8f8b11e66a1f7b74be70b65cec0d6f714e1506c93509bd48b1e7eb17eb801
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.0
|
Security for cocolit 0.3.1
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.