niess
Table of Contents
Installation
pip install niess
License
niess is distributed under the terms of the BSD-3-Clause license.
Motivation
This package is intended to hold information about the Neutron Insruments of the European Spallation Source for use in defining Monte Carlo ray-tracing simulations, file-layout information for use by the ESS file-writers, and other yet-undefined uses; in a use-agnostic approach.
The information required about an instrument for McStas and NeXusStructure is
similar but not identical -- the latter attempts to hold all information needed to
produce a valid NeXus file, which requires geometry information inspired by the
McCode implementation used by McStas.
The two uses each have their own vocabulary, and the vocabulary used here is more
closely in line with that of McCode. The basic building block of the two uses
is the Comp in McCode and the NXclass in NeXus; here the term 'component' is
used to refer to such a building block.
Since there are sometimes slight differences between the 'same' Comp and NXclass
in how equivalent information is stored, niess is intended to be component-aware as
a single translation between the two is not possible globally.
Rather than attempting to store one implementation or the other, niess components
are an independent low-level representation of the properties of a component.
This representation can be written as a dictionary with pre-defined keys, and
it is intended that serializing to and deserializing from such a representation can be
used to provide calibrated instrument information to McStas and NeXusStructure.
Use
niess describes an instrument once, as calibration data, and emits it as a McStas
instrument, ESS NeXus Structure JSON, or CAD geometry:
from niess.bifrost import Primary, Tank
from niess.bifrost.parameters import primary_parameters, tank_parameters
from niess.instrument import Instrument, Mount
from niess.nexus import to_nexus_structure
from niess.nexus.bifrost import BIFROST_REGISTRY
bifrost = Instrument(name='bifrost', origin='sample_origin', parts=(
Mount(name='primary', content=Primary.from_calibration(primary_parameters())),
Mount(name='tank', content=Tank.from_calibration(tank_parameters()),
relative_to='sample_origin'),
))
structure = to_nexus_structure(bifrost, registry=BIFROST_REGISTRY)
Full documentation, including how to translate an existing McStas .instr into a
niess submodule and how to write your own NeXus translators, is at
https://mcdotstar.github.io/niess/.
1 maintainer
Metadata
1 maintainer
Release files for niess 0.9.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 | |
|---|---|---|---|
| niess-0.9.1.tar.gz | 760.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| niess-0.9.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / niess-0.9.1.tar.gz
| Download URL | niess-0.9.1.tar.gz |
|---|---|
| Size | 760.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e64ad1eb4b19915240dd09f7bdda34307f36d4fe8718925c2992c1d6a6e9c949
|
|
BLAKE2b-256 checksum How to use checksums |
c9032342bef86f5466fd47146247642e67c19ccbbc299c01cdffbb37061bd70e
|
| 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 Oct 6, 2026.
Transparency logRelease files / niess-0.9.1-py3-none-any.whl
| Download URL | niess-0.9.1-py3-none-any.whl |
|---|---|
| Size | 249.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4c053b17218ad53596e8cee2ac961a2df1410d2b9dbf23f7d73dcdbd676100b
|
|
BLAKE2b-256 checksum How to use checksums |
44be463a24dbef01172144a85a2df02dc5cffe99bbb4b132e086e1118f8759d4
|
| 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 Oct 6, 2026.
Transparency log
