This release is a pre-release and may not be stable for production use.
larmorx-nc: FSL replicas for larmorx (non-commercial use only)
Non-commercial use only. larmorx-nc is distributed under the FSL Licence, the licence of FSL, from which it is translated: it may be used only for non-commercial purposes, without financial return. For commercial use, use larmorx's clean-room originals instead (below), or license FSL from Oxford University Innovation.
larmorx-nc is a companion of larmorx, the neuroimaging toolbox reimplemented in Rust. It holds bit-exact replicas of FSL 6.0.7.23's tools: Rust translations of FSL's source code, written to give FSL's output bit for bit, with every option, message, exit status and output file of the original program.
| FSL program | FSL package |
|---|---|
mcflirt |
fsl-mcflirt 2111.0 |
bet, bet2, betsurf, standard_space_roi |
fsl-bet2 2111.9 |
flirt, convert_xfm and FLIRT's other programs |
fsl-flirt 2111.4 |
fast |
fsl-fast4 2111.3 |
topup, applytopup |
fsl-topup 2203.5 |
fslmaths, fslstats, fslroi |
fsl-avwutils 2209.6 |
prelude |
fsl-fugue 2603.0 |
The wheel also installs the FSL files these programs read: three of FSL's standard images
(MNI152_T1_2mm and its masks, for bet -S, -B, -A, -A2 and standard_space_roi) and
topup's settings files (b02b0.cnf and the others), at <prefix>/share/larmorx-nc/fsl-data.
Installation
pip install larmorx-nc # by name, so that its licence is accepted knowingly
pip install "larmorx[all]" # or with everything: larmorx, larmorx-nc and larmorx-gpl
Python 3.12 or newer; wheels for Linux (x86-64, aarch64; glibc 2.28 or newer), macOS (11 or newer,
Intel and Apple silicon; on Apple silicon larmorx[all] needs macOS 12, as SciPy's and
scikit-learn's wheels do) and Windows (x64, arm64). Nothing else is needed: no FSL installation.
How larmorx uses it
larmorx-nc is a separate program, larmorx-nc; larmorx (Apache-2.0) runs it as a separate
process and imports nothing from it. Each of these tools also has a clean-room original in
larmorx itself, written without seeing FSL's source (Apache-2.0: commercial use allowed), which
gives FSL's behaviour within validated limits.
- Once larmorx-nc is installed, larmorx uses it by default for these tools:
implementation="auto"(the default oflx.fsl.bet(...),lx.mri.hmc(...)and the others) andlarmorx fsl <program> ...run the replica when its program is found, so the default results then come from FSL-licensed code.implementation="original"(orLARMORX_IMPLEMENTATION=originalon the command line) runs the clean-room original instead;pip uninstall larmorx-ncremoves the replicas. - The program can also be run directly, with the original program's arguments:
larmorx-nc fsl bet t1w.nii.gz brain.nii.gz -f 0.5(larmorx-nc --helplists the programs).
Licence and source
The FSL Licence's conditions pass to everyone who receives a copy, and it requires all original and amended source code in every copy: this package's wheel and source distribution carry FSL's original source of the replicated parts and the Rust translation, with the FSL Licence, FSL's and the other notices (Armadillo, Kiss FFT, OpenBLAS, LAPACK, fslpy, fdlibm, Arm's Optimized Routines, the SGI STL) and the Apache-2.0 larmorx crate it includes (larmorx-core). larmorx-nc does not present itself as FSL and is not endorsed by the University of Oxford.
- Source: crates-nc/ of the repository, NOTICE, licensing
- Validation against FSL, tool by tool: validation records
- Documentation: https://karellopez.github.io/larmorx_documentation/
Metadata
Release files for larmorx-nc 0.1.0rc1
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 |
|---|---|---|---|---|
| larmorx_nc-0.1.0rc1.tar.gz | 3.3 MB | With provenance | Details for larmorx_nc-0.1.0rc1.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| larmorx_nc-0.1.0rc1-py3-none-win_arm64.whl | Python 3 | none | Windows ARM64 | Details for larmorx_nc-0.1.0rc1-py3-none-win_arm64.whl |
| larmorx_nc-0.1.0rc1-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details for larmorx_nc-0.1.0rc1-py3-none-win_amd64.whl |
| larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_x86_64.whl | Python 3 | none | Linux glibc 2.28+ x86-64 | Details for larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_x86_64.whl |
| larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_aarch64.whl | Python 3 | none | Linux glibc 2.28+ ARM64 | Details for larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_aarch64.whl |
| larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_x86_64.whl | Python 3 | none | macOS 11.0+ x86-64 | Details for larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_x86_64.whl |
| larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details for larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_arm64.whl |
Total release size: 39.8 MB
Release files / larmorx_nc-0.1.0rc1.tar.gz
| Download URL | larmorx_nc-0.1.0rc1.tar.gz |
|---|---|
| Size | 3.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
821dd2e9eb0b206aa6581e58bb7343f1fa7c77de153694fd10564eaa883f2ed7
|
|
BLAKE2b-256 checksum How to use checksums |
17242ab4475ea4849be3db7c1d2e8e56160c7817cc23660e9ae014d5d33083c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / larmorx_nc-0.1.0rc1-py3-none-win_arm64.whl
| Download URL | larmorx_nc-0.1.0rc1-py3-none-win_arm64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | Python 3 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
3521dcbaa1991ff29981869a8bc308b2e5f7554189e8c87bca96bd7059f7f29a
|
|
BLAKE2b-256 checksum How to use checksums |
50f177b2e5cd1561d46e1df772eff52d255002dad10e0bc04ff7bda3563670b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / larmorx_nc-0.1.0rc1-py3-none-win_amd64.whl
| Download URL | larmorx_nc-0.1.0rc1-py3-none-win_amd64.whl |
|---|---|
| Size | 6.3 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
cb4272c528fce7d9f0df0210b0730c77a5a6b30b7aec0765190b738191ef10fc
|
|
BLAKE2b-256 checksum How to use checksums |
bf23db6b4b982d8054c42f4f2ec155b5c8e89fd8bbf21e4f736b286364196c58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_x86_64.whl
| Download URL | larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | Linux glibc 2.28+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
17142afc619364251106d83b66d9725bb174e574c8afa4432978c302634614ed
|
|
BLAKE2b-256 checksum How to use checksums |
06c284e37e6b7a2e44512d617477c7ff518bc08b392d3788bad02ac1329c944c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_aarch64.whl
| Download URL | larmorx_nc-0.1.0rc1-py3-none-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 5.9 MB |
| Tags | Linux glibc 2.28+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
793aaae7d286e22049ac1e0b1ecc3f50f11eb1dc661cf07896de43a1746fe21f
|
|
BLAKE2b-256 checksum How to use checksums |
88ac321f120ac2f51f735e3cf7493d802c9aed29dce2d047b12985ce824b8316
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_x86_64.whl
| Download URL | larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_x86_64.whl |
|---|---|
| Size | 6.2 MB |
| Tags | Python 3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
1c9b933b5cb026853804e606a8186b07a7d0e73ee9c0634c084a87f1ff1a64bf
|
|
BLAKE2b-256 checksum How to use checksums |
1ddcb7b3f6c42e8f1c635e28398cc60c3f72bbdeb393ac1c20f1e046b66d8f3c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_arm64.whl
| Download URL | larmorx_nc-0.1.0rc1-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.9 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
af291044dc9c461bf3da99df8dc76b78c4de4d1f7d66333ebcb9b9e0505b1318
|
|
BLAKE2b-256 checksum How to use checksums |
ae462640054fe4a9870e24a45fcb0e0436dcc90e694c423ca3206ef49747e315
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logSecurity for larmorx-nc 0.1.0rc1
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.
Full provenance
All 7 files in this release have been uploaded with provenance metadata.
Attestation for larmorx_nc-0.1.0rc1.tar.gz
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 Nov 11, 2026.
Transparency logA 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.