pyaml-test-lattice
Lattices and configuration files used for pyAML integration tests and tutorials.
Usage
The package discovers files automatically from its packaged data/lattice and
data/configuration directories. Access them through separate registries:
from pyaml_test_lattice import configurations, lattices
lattice_file = lattices["fodo_1gev_6d.json"]
config_file = configurations["pyaml/tango/fodo_1gev_6d_pyaml.yaml"]
Registry entries are filesystem paths, so they can be passed directly to lattice and configuration loaders:
simulator = Simulator(name="design", lattice=lattice_file)
accelerator = Accelerator.load(config_file)
New files placed below either data directory are available automatically using their path relative to that directory.
Optional descriptions can be added without changing the registry. Place a
file named <filename>.description next to any lattice or
configuration file. Its text is displayed when printing the registry:
fodo_1gev_6d.json.description
To list the available files and their description, print a registry:
print(configurations)
Named arrays and tuning tools
The fodo_1gev_6d pyAML configurations (pyaml/tango/tango-pyaml/fodo_1gev_6d_pyaml.yaml
and pyaml/tango/pyaml-cs-oa/fodo_1gev_6d_pyaml-oa.yaml) declare the arrays and tools
used by the pyAML examples/use_cases notebooks, under the same canonical names:
| Name | Description |
|---|---|
QForTune |
Quadrupoles used for tune correction (all QF_* and QD_*) |
HCorr / VCorr |
Horizontal / vertical orbit correctors (COR_*.hcorrector, COR_*.vcorrector) |
BPM |
Beam position monitors (BPM_*) |
BETATRON_TUNE |
Betatron tune monitor |
CHROMATICITY_MONITOR |
Chromaticity monitor (RF frequency scan) |
DEFAULT_TUNE_CORRECTION |
Tune correction tool → SR.tune (uses pyaml/trm.json) |
DEFAULT_TUNE_RESPONSE_MATRIX |
Tune response matrix tool → SR.trm |
DEFAULT_ORBIT_CORRECTION |
Orbit correction tool → SR.orbit (uses pyaml/orm.json) |
DEFAULT_ORBIT_RESPONSE_MATRIX |
Orbit response matrix tool → SR.orm |
DEFAULT_DISPERSION |
Dispersion measurement tool → SR.dispersion |
pyaml/trm.json and pyaml/orm.json are shared by both configurations; they were
measured in design mode (pyAT) and are loaded automatically.
from pyaml.accelerator import Accelerator
from pyaml_test_lattice import configurations
sr = Accelerator.load(configurations["pyaml/tango/pyaml-cs-oa/fodo_1gev_6d_pyaml-oa.yaml"])
SR = sr.design
SR.tune.set([0.19, 0.28], iter=10, wait_time=0.0)
Metadata
Release files for pyaml-test-lattice 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyaml_test_lattice-0.2.0.tar.gz | 34.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyaml_test_lattice-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 77.5 kB
Release files / pyaml_test_lattice-0.2.0.tar.gz
| Download URL | pyaml_test_lattice-0.2.0.tar.gz |
|---|---|
| Size | 34.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b405cc32395158c5d020985e3b7bda1d3484672ed4f937a3fc24dd907ca52e57
|
|
BLAKE2b-256 checksum How to use checksums |
3f4042d61f0bbacd259014bfe59c97e377604c673ba71cd56cd58dfb2fa4c186
|
| 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 16, 2026.
Transparency logRelease files / pyaml_test_lattice-0.2.0-py3-none-any.whl
| Download URL | pyaml_test_lattice-0.2.0-py3-none-any.whl |
|---|---|
| Size | 42.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0bfe1aa32b661e074951d50fa3553c605e87d79902581831854456d22af4ea1
|
|
BLAKE2b-256 checksum How to use checksums |
48109e6b6746c2a5abc64715e4ae303bf0aec45de11a8d8d29cb6b851d2e788c
|
| 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 16, 2026.
Transparency log