Skip to main content

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.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyaml-test-lattice 0.3.0
File Size Uploaded
pyaml_test_lattice-0.3.0.tar.gz 34.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pyaml-test-lattice 0.3.0
File Interpreter ABI Platform
pyaml_test_lattice-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 77.6 kB

Release files / pyaml_test_lattice-0.3.0.tar.gz

Download URL pyaml_test_lattice-0.3.0.tar.gz
Size 34.7 kB
Tags Source
SHA-256 checksum
How to use checksums
f981bddda9b03061047949daab7de8c795ce438a00dab2c423b2d89820137b30
BLAKE2b-256 checksum
How to use checksums
8f52d872f3eadce1eb44215282758cb1c5082119f0deedfea7c250d4683ecb18
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 7, 2026.

Transparency log

Release files / pyaml_test_lattice-0.3.0-py3-none-any.whl

Download URL pyaml_test_lattice-0.3.0-py3-none-any.whl
Size 42.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fd7d4d5058e648522fd5168e97d0351c7259843d460aab4b8443a369d0e5e39a
BLAKE2b-256 checksum
How to use checksums
a9de1448bfb7793a981af380f2ac20e4f3c6fdb838e55ebee14bc4535ea52398
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 7, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page