Monitors and actuators acces from tuning tools - #418
Merged
Merged
Conversation
simoneliuzzo
previously approved these changes
Sep 15, 2026
Member
|
No there is no reason to keep it private. |
Member
|
@gubaidulinvadim tune2 = Tune('ALTUNE', quad_array_name='QCORR', response_matrix='respmat.json', betatron_tune_name='BETATRON_TUNE2')
tune2.attach(sr.design)
tune2.attach(sr.live)
print(tune2.tune_monitor)should be: tune2 = Tune('ALTUNE', quad_array_name='QCORR', response_matrix='respmat.json', betatron_tune_name='BETATRON_TUNE2')
sr.add(tune2)
print(tune2.tune_monitor) |
Member
Author
Thanks, that's clear. I've only written it to explain in the PR that this will be improved later. |
Member
Author
|
@simoneliuzzo @JeanLucPons Sorry, there was a merge conflict with main (in the docstrings). This needs to be reapproved. |
simoneliuzzo
approved these changes
Sep 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@simoneliuzzo this answers #178 and makes a public access to monitors and actuators of tuning tools in pyAML. @JeanLucPons is there any reason to keep them "private"?
It is possible to do now, for example,
to access the quadrupole array used for tune correction. Before, it was "hidden" as a private attribute _quadrupoles.
For #414 , public access to monitors and actuators would need to be made a requirement for a generic tuning tool.
@simoneliuzzo I am trying to also answer #177, but I think this is already implemented. I am not sure if your issue also means something like swapping the tune monitor for an existing Tune tuning tool or simply a request on the interface in the constructor.
Currently, you can make a Tune tuning tool with a selected betatron_tune_name (tune monitor name). You'd still need to attach it to the simulator or control system after creation, but this is a general pyAML interface as of now for interactive object creation.
Resolves #178
Resolves #177