Python Binding
Distribution name: nirs4all-core
Import name: nirs4all_core
This binding intentionally avoids the nirs4all import name so it can be
installed next to the full Python nirs4all package during parity checks.
The canonical source repository is nirs4all-core; only the Python
distribution carries the -core suffix because the production nirs4all
Python package already owns the bare name.
An additive import facade is available for governed topology work:
n4amirrors the fullnirs4all_coreaggregate surface.
Archive V2 bridge
nirs4all_core.read_portable_predictor_package_v2(path) invokes the embedded
Rust Archive V2 reader and returns the exact validated DAG-ML Package V2 bytes.
It does not parse ZIP members in Python, deserialize the package, or execute a
prediction. Pass the returned bytes to DAG-ML's typed package/replay surface;
the aggregate remains only the container and integrity boundary.
Portable Execution
nirs4all_core.run_portable_pipeline(source, dataset) executes the shared
portable JSON/YAML subset through the nirs4all-methods Python bindings:
KennardStoneSplitterStandardNormalVariate/SNVSavitzkyGolaysklearn.cross_decomposition.PLSRegression_range_sweeps overn_components
Savitzky-Golay defaults to mode="interp" for full Python nirs4all parity and
preserves explicit methods-backed modes (mirror, constant, nearest,
wrap, interp) plus cval.
The aggregate does not implement numerical kernels. Install the optional
methods extra, or make n4m and pls4all importable, before calling it:
python -m pip install "nirs4all-core[methods]"
The strict local parity gate compares all shared fixtures against the full
Python nirs4all oracle and reports max prediction/RMSE deltas on failure:
PYTHONPATH=bindings/python/src:/path/to/nirs4all-methods/bindings/python/src \
N4M_LIB_PATH=/path/to/libn4m.so \
NIRS4ALL_CORE_REQUIRE_METHODS_PARITY=1 \
python -m unittest bindings/python/tests/test_execution_parity.py -v
1 maintainer
Metadata
1 maintainer
Release files for nirs4all-core 0.3.22
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| nirs4all_core-0.3.22.tar.gz | 155.3 kB | Details |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nirs4all_core-0.3.22-cp311-abi3-win_amd64.whl | CPython 3.11 | abi3 | Windows x86-64 | Details |
| nirs4all_core-0.3.22-cp311-abi3-manylinux_2_28_x86_64.whl | CPython 3.11 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| nirs4all_core-0.3.22-cp311-abi3-macosx_11_0_arm64.whl | CPython 3.11 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 1.8 MB
Release files / nirs4all_core-0.3.22.tar.gz
| Download URL | nirs4all_core-0.3.22.tar.gz |
|---|---|
| Size | 155.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
00cc72e841b785d31112f3d0f996a5a05f87337cd65b3a7280b22f39e7376fe7
|
|
BLAKE2b-256 checksum How to use checksums |
9e2a8e338d4b035e153241dbe5811035bf5fd5325e242dbd868e368be623b13b
|
| 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 Aug 27, 2026.
Transparency logRelease files / nirs4all_core-0.3.22-cp311-abi3-win_amd64.whl
| Download URL | nirs4all_core-0.3.22-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 383.4 kB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
613a710fc4dbb888480c7ca9ccf619b5423a5025f9eeca8a9635a727eece90d5
|
|
BLAKE2b-256 checksum How to use checksums |
8e3beda0c645f1439d4bfc60499e9fdd0c2cc7e698104f629565df36df4782be
|
| 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 Aug 27, 2026.
Transparency logRelease files / nirs4all_core-0.3.22-cp311-abi3-manylinux_2_28_x86_64.whl
| Download URL | nirs4all_core-0.3.22-cp311-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 813.5 kB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
bcade945d45169b8762ab3971c24957532fcb4297473f4fe12cea0b503399f57
|
|
BLAKE2b-256 checksum How to use checksums |
7363deb2b431b3f59b2132a0e18c1e8b4945cfd0c82612d7fcd25a2ce02c57fa
|
| 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 Aug 27, 2026.
Transparency logRelease files / nirs4all_core-0.3.22-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | nirs4all_core-0.3.22-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 454.9 kB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1b2982a0063e09285b1321f649873e454c78ca3e32389e7b55ddfad8b6816a1a
|
|
BLAKE2b-256 checksum How to use checksums |
6d5eadb4503c54bc51e248b1ced7992335cb6b0a33b7efbaf82f5f5588337c05
|
| 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 Aug 27, 2026.
Transparency log
