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
On discussion with the EMU instrument scientists, we have agreed to store TPAR (temperature parameter) files in the configurations git repository.
As an instrument scientist, I would like instrument scripts to do the following:
Mark a known set of the TPAR files as "good" (for example, using a git tag or branch?)
Restore files to this known set (e.g. using git checkout from a known state, saved by the above command)
This is so that, if a user changes a TPAR file during an experiment, the scientists can change them back to a known state afterwards
Notes:
This is not required by EMU for the upcoming cycle (this has been checked with the scientists). It is a "nice-to-have" addition that would make certain workflows easier.
The text was updated successfully, but these errors were encountered:
This was mentioned to me today, under SECI each TPAR file was stored in a manager mode protected sub-configuration, so a fresh copy was always copied out when a configuration was changed. This was the "associated files" option in SECI.
On discussion with the EMU instrument scientists, we have agreed to store
TPAR
(temperature parameter) files in the configurations git repository.As an instrument scientist, I would like instrument scripts to do the following:
git tag
or branch?)git checkout
from a known state, saved by the above command)This is so that, if a user changes a TPAR file during an experiment, the scientists can change them back to a known state afterwards
Notes:
The text was updated successfully, but these errors were encountered: