Feature: tuning tools restore feature

[simoneliuzzo]

@kparasch, @GamelinAl, Ivan Morozov, Julian Gethmann

Would be nice to have a "Restore feature" with some history

hold the delta tune correction and quadrupoles values in a short (5 corrections for example) buffer history

[gupichon]

Should this be a feature handled by an (small and probably homemade) execution engine? It could also deal with interruption policies.

[gubaidulinvadim]

@gupichon In general, yes, but there's also a use case of having a "golden" value of tune or other parameter (the nominal operational parameters). This value could also be specified in a catalog-like-structure and there's a use case to have a utility function to reset to this value.

[simoneliuzzo]

This was discussed in WG4 at the workshop. An example is available in the discussion.
I think and execution engine is not needed.

[gubaidulinvadim]

@simoneliuzzo I think the whole "execution engine" is a strange name. Would you agree that we could have a Measurement class with standard methods for all measurements? This is partially what you did in WG4. It's just a question of branding it as a small homemade execution engine or just calling it a StandardMeasurement class.

[GamelinAl]

This could work with a "cache" mechanism (like in accml ?), i.e., some function or class method is added to each measurement script and records the initial values and the changes that are applied.

Some possible features:

• The cached steps should be written to disk in a standard file (to avoid issues where the steps are stored in memory if there is a crash of python or power shortage).
• The default number of cached steps can be set in a .yaml configuration file.
• Each cached step should be somewhat documented (type of measurement, what changed, ...) so you can now what you are doing when you go back.

[simoneliuzzo]

@gubaidulinvadim and @gupichon this is ok for me!