Skip to content

Calibration: use a Scan Manager entry (pymodaq 5.3) - #60

Draft
seb5g wants to merge 2 commits into
5.3.xfrom
fix/calibration-scan-5.3
Draft

seb5g wants to merge 2 commits into
5.3.xfrom
fix/calibration-scan-5.3

Conversation

@seb5g

@seb5g seb5g commented Oct 27, 2026

Copy link
Copy Markdown
Collaborator

The SLM calibration (BeamShapingCalibration, a DAQScan with the custom Scan1DCalibration scanner) was configured by an XML file of the pre-5.3 scanner manager, which no longer exists.

  • resources/holography_calibration.scan: Scan Manager entry selecting the detector Camera, the actuator Shaper and the BeamShapingCalibration scanner. The extension executes it with scan_manager.execute_entry(CALIBRATION_ENTRY); the old holography_calibration.xml is removed.
  • scripts/make_calibration_entry.py regenerates the entry with the Scan Manager itself (mock modules named Camera and Shaper), if the entry format changes.
  • BeamShapingCalibration.show_widgets uses the DAQScan 5.3 attributes (dock_command, get_toolbar), save_calibration no longer fails when the calibration cannot be loaded, stray cProfile import removed, docs mention the Camera / Shaper names.
  • Tests: scanner phase extraction on synthetic fringes (0.59 rad per 16 grey levels expected and obtained), and the extension configured by the entry on a dashboard with Camera and Shaper.

Not tested on a real SLM and camera.


Generated by Claude Code

…d scanner xml

The BeamShapingCalibration scanner selects Camera and Shaper through a .scan entry generated by
scripts/make_calibration_entry.py. Also adapt the extension to the DAQScan 5.3 attributes.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CAhZwmbyCSpSgfTyicUxuS
…utside tmp_path

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CAhZwmbyCSpSgfTyicUxuS
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants