You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in #577 , we dicussed sequences using blocks. One of those, called the Configurator is:
configurator: block allowing to change the configuration of several actuators and detectors (settings for both) and set value (move_abs) for actuators. A particular state of a configurator could be "configured" elsewhere and called here. Looks a bit like a genralized overshoot configuration
This discussion is therefore meant to discuss implementation of an extension allowing to specify some settings for controller modules (exposure for instance), and target_value for actuators (a particular waveplate config to transform the polarization state of a laser for instance).
Each such configuration would be given a name and a few values (at least one). One value being a particular state of settings and target_value.
For instance, if I have two waveplates on rotations in a setup. I would create a configuration comprized of those two actuators with values such as:
Horizontal: two particular angles setting the output polarisation as linear horizontal
Vertical: two particular angles setting the output polarisation as linear Vertical
Circular Right: two particular angles setting the output polarisation as circular right
Circular Left: two particular angles setting the output polarisation as circular left
Any of these configuration could be called anytime, but in particular at given steps within a sequence!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
in #577 , we dicussed sequences using blocks. One of those, called the Configurator is:
configurator: block allowing to change the configuration of several actuators and detectors (settings for both) and set value (move_abs) for actuators. A particular state of a configurator could be "configured" elsewhere and called here. Looks a bit like a genralized overshoot configuration
This discussion is therefore meant to discuss implementation of an extension allowing to specify some settings for controller modules (exposure for instance), and target_value for actuators (a particular waveplate config to transform the polarization state of a laser for instance).
Each such configuration would be given a name and a few values (at least one). One value being a particular state of settings and target_value.
For instance, if I have two waveplates on rotations in a setup. I would create a configuration comprized of those two actuators with values such as:
Any of these configuration could be called anytime, but in particular at given steps within a sequence!
Beta Was this translation helpful? Give feedback.
All reactions