Conversation
…f pySC ResponseData type)
…ack to default configuration when not specified
…e-arrays Update arrays documentation
|
About the part: "If we decide to limit pyAML to a single control system per Accelerator then this PR is not mandatry and we can change the controls field to control and fix the name to live." Wouldn't that mean that you no longer can configure the virtual accelerator? For me that would be a second controls with a different host/PV prefix? |
If we limit to one single CS per accelerator, it will be possible to load a second accelerator. So instead of writing: sr.live...
sr.shadow...You will write: sr.live...
shadow.live... |
…rbit-correction-and-orm Orbit correction and Orbit Response Matrix measurement through pySC.
Hmm... I think that will be confusing and potentially unsafe since then it's no longer given that Also, what would that mean for the simulators? There would be one set of simulator objects for the live and another one for the shadow? Feels like that also potentially could cause problems. |
…init-hook Added post_init() hook
…n-accelerator-middle-layer/pyaml into cs-refurbishment-multiple-csprefix
|
It is now possible to write and run it without any backend installed: sr = Accelerator.load("tests/config/EBSOrbit.yaml",ignore_external=True)
print(sr.design.get_magnets("VCorr").strengths.get())@TeresiaOlsson , @gubaidulinvadim is it ok for you ? |
Array of None are necessary
|
It's okay for me. I'm also working on something for the factory for issue #28 which might remove the need for this but I'm not sure yet and it will likely take a while until I manage to finish my suggestion... |
|
It would be nice that this PR is rapidly merged as it has a strong probability of merge conflict. |
I agree since what you are doing in the |
gubaidulinvadim
left a comment
There was a problem hiding this comment.
Approved. Strangely, GitHub shows to me in the diff that tuning_tools/dispersion and some others is added in this PR when it should already be on the main branch.
The merge-base changed after approval.
|
We should also add a minor version bump as it will break compatibility with tango/ophyd-async bindings |
The aim of this PR is:
int_cs()call.It shows minimum modifications to handle the above and change the way to handle external magnet model and CS backend. This new branch is not compatible with the present Tango backend.
If this PR is accepted then I'll port the Tango backend.
If we decide to limit pyAML to a single control system per
Acceleratorthen this PR is not mandatry and we can change thecontrolsfield tocontroland fix the name tolive.