Skip to content

Conversation

@erik-wallin
Copy link
Contributor

Started filling out the run control bindings (maybe this file should be renamed something like esa25_bindings.cxx, since it will be so specific to this test beam?)

Made two separate PyTargetHCal and PyTargetECal classes, since they have small differences. boost::Python correctly understands how these inherit from PyTarget, which is nice.

Not yet in there:

  • Config parsing. Don't know just yet how the central run control will be config:ed, but should be quick to add once we know.
  • Bittware targets (since I've been testing on the ZCU)
  • Everything we want to do in the config step. I don't think we have to do much in the other run control states, except flagging to Rogue that the transition was a success.

@erik-wallin erik-wallin linked an issue Nov 18, 2025 that may be closed by this pull request
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.

Python interface additions

2 participants