pyaml presentation #14
Replies: 2 comments 13 replies
-
|
I would say that a general unit conversion that Yoshi was talking about (even if for most non-magnet elements it's a simple multiplication factor) is useful. Even if TANGO already allows to do this. I didn't quite follow what @yhidaka meant by his BPM example though. If it is a conversion between different type of signals (Vertical difference, vs diagonal difference) or a constant offset, I would not say that this falls under unit conversion concept. |
Beta Was this translation helpful? Give feedback.
-
|
@JeanLucPons I'm wondering how you plan in your proposal that the automatic generation of metadata and saving the results in a standardized structure will be done? If I understood correctly you are not planning to include something like a measurement execution engine that should handle it? Can you perhaps explain a bit your thoughts about the part in the slides that says "user pyaml scripts"? Is the idea that this part should be implemented using something like plans/flows like @yhidaka and how will the metadata and data be saved? One requirement that is very important for us is that this should not be implemented on an application basis because then it will be like in MML where data management is only done for the standard application while the scripts the physicists write themselves to do a quick measurement during machine time will have poor data management and they have to waste time trying to figure out a good format to save it in, headings etc. The second requirement is that we want to be able to redo analysis without having to redo measurements. That is also a problem in MML where many scripts don't have separation between the different steps. So if you realise the analysis had problem you need to spend a lot of time trying to extract the measurement data from the saved data and write a separate script to redo the analysis. I think that was one of the reasons behind the flows @yhidaka suggests. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Please find my proposal for pyaml architecture (Maintainers meeting 25/072025):
PyAML prototype.pdf
More details on EBS combined function magnets can be found here, source code and calibration curves for magnetic models can be found here.
UnitConv will be renamed to MagnetModel as suggested by Yoshi.
A unit conversion module dedicated to conversion from non standard unit (SI) can be added.
pySC dependency is still under investigation.
Asynchronous calls (DOOCS and EPICS) for fast family access is under investigation.
Beta Was this translation helpful? Give feedback.
All reactions