Skip to main content

hartmannActor

Versions Test codecov

The hartmann actor is responsible for taking and analysing Hartmann door exposures to determine the optimal focus for the BOSS spectrographs at APO and LCO (sp1 and sp2, respectively). It also commands the spectrograph collimator motors to adjust the focus.

Procedure

The hartmann actor performs the following steps:

  • Turns on the appropriate arc lamps and waits for them to warm up.
  • Takes two BOSS exposures, each one with a different Hartmann door closed (left and right). For a perfectly focused system, the exposures would be identical. As spectrograph focus degrades, the position of the spectral lines in one of the Hartmann images shifts vertically with respect to the other. The shift is proportional to the amount of defocus, which can be corrected by either adjusting the collimator position or the position of the blue or red cameras via the camera "rings". In practice only ring needs to be adjusted, with the other camera being the reference one and its focus optimised by the collimator. The blue ring/camera is the one that is adjusted.
  • The images are analysed to determine the vertical shift. This is done by applying vertical shifts to one of the images and computing the product of both images. The product will be maximised when the vertical shift is correct. A calibration is applied to convert the vertical shift to a collimator movement.
  • If the collimator can correct the focus for both cameras, within a tolerance, the collimator is moved that amount. Otherwise, the necessary ring movement is computed and the user is instructed to move the blue ring by that amount and rerun the hartmann collimate command.

Usage

See hartmann --help for usage instructions. In general the hartmann collimate command runs the entire sequence. --no-move can be used to run the sequence without moving the collimator. Other flags such as --exposure-time or --ignore-residuals can be used to change the command behaviour.

Code style and development

hartmannActor uses uv for package and dependency management, and ruff for code style enforcement. ty is the recommended type checker. See pyproject.toml for configuration details.

Metadata

Release files for sdss-hartmannActor 3.1.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 sdss-hartmannActor 3.1.0
File Size Uploaded
sdss_hartmannactor-3.1.0.tar.gz 18.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for sdss-hartmannActor 3.1.0
File Interpreter ABI Platform
sdss_hartmannactor-3.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 40.5 kB

Release files / sdss_hartmannactor-3.1.0.tar.gz

Download URL sdss_hartmannactor-3.1.0.tar.gz
Size 18.2 kB
Tags Source
SHA-256 checksum
How to use checksums
daabfe57ec20a6f76ce42f5101256eafd76d4a75fb6d26402d9a3418442a7690
BLAKE2b-256 checksum
How to use checksums
b0a900110ca0ee2bb2af7efd39929394352c4cc30515df02b610c8f82ec9235a
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 3, 2026.

Transparency log

Release files / sdss_hartmannactor-3.1.0-py3-none-any.whl

Download URL sdss_hartmannactor-3.1.0-py3-none-any.whl
Size 22.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c574774009e18c9ce0b820c2a6fce450a19046412e11fff2f22ec47902937e45
BLAKE2b-256 checksum
How to use checksums
13fbbb4c6e73511b8001024a382a1b5eeaa61d287461114eb2f510bc886c14c4
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 3, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

3.1.0 This release

2 release files

3.0.0

2 release files

2.0.2

2 release files

2.0.1

2 release files

2.0.0

2 release files

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