spectrochempy-nmr
NMR plugin for SpectroChemPy.
This package is the home for NMR-specific readers and tools that are useful in
SpectroChemPy but should not live in the core package. It currently provides a
validated public 1D workflow for reading data and processing raw 1D FIDs
through scp.nmr.read(...) and scp.nmr.Experiment(...).
Future NMR readers or processing helpers can be added here without creating a new plugin package for each vendor format. Multi-dimensional NMR remains under active characterization and is not currently part of the public supported processing workflow.
Installation
pip install spectrochempy[nmr]
For development inside the SpectroChemPy repository:
pip install -e .
pip install -e plugins/spectrochempy-nmr
Usage
import spectrochempy as scp
dataset = scp.nmr.read("path/to/1/fid")
dataset = scp.nmr.read("path/to/1/pdata/1/1r")
dataset = scp.nmr.read("path/to/experiment", expno=1, procno=1)
experiment = scp.nmr.Experiment(dataset)
spectrum = experiment.process(apodization="em", lb=2.0, size=32768)
This explicit processing example does not imply that vendor processing parameters are automatically imported and replayed from metadata. That contract remains under active characterization.
The current explicit apodization contract covers the public modes already
exposed by Experiment.process(): em(lb=...), gm(lb=..., gb=...), and
sp(ssb=..., pow=...).
The result of Experiment.process() also records the SpectroChemPy-owned
processing trace in result.meta.nmr_processing["scp_processing"].
requested contains only the arguments explicitly provided by the user,
whereas applied contains only the operations that were actually executed and
the values they really consumed. This trace is attached to the result only:
the source dataset is not mutated, the vendor procs profile remains purely
descriptive, and phase="metadata" does not replay TopSpin PHC0/PHC1.
The NMR ppm/frequency unit context is also provided by this plugin:
from spectrochempy_nmr.units import set_nmr_context
set_nmr_context(104.3 * scp.ur.MHz)
The compatibility aliases scp.nmr.read_topspin(...) and
scp.read_topspin(...) are kept for historical usage. TopSpin is a reader, so
it is not exposed as dataset.read_topspin(...) or
dataset.nmr.read_topspin(...).
Development
python -m pytest tests/ -v
Metadata
Release files for spectrochempy-nmr 0.1.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| spectrochempy_nmr-0.1.11.tar.gz | 106.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| spectrochempy_nmr-0.1.11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 191.2 kB
Release files / spectrochempy_nmr-0.1.11.tar.gz
| Download URL | spectrochempy_nmr-0.1.11.tar.gz |
|---|---|
| Size | 106.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b430b757c4e49e4ee7145ddee5433393e9e52ec67e9fb6f437ef580e54680e0
|
|
BLAKE2b-256 checksum How to use checksums |
1aa7fc5be7d4c82737b0e99d942d3738f86a5f5a9d9507d94f69e48f25e5e5a3
|
| 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 Sep 8, 2026.
Transparency logRelease files / spectrochempy_nmr-0.1.11-py3-none-any.whl
| Download URL | spectrochempy_nmr-0.1.11-py3-none-any.whl |
|---|---|
| Size | 84.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ff976fc8c8223709f11c83487c4873cf44b8892eedd9e563d4349c157eaee6a0
|
|
BLAKE2b-256 checksum How to use checksums |
7905591da9c77212e58dac8071f4c8798fe913b4d5a337c325b231402ffcddcc
|
| 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 Sep 8, 2026.
Transparency log