Shared modules used by the labscript suite. Includes a graphical exception handler, debug tools, configuration management, cross platform filepath conversions, unit conversions and custom GUI widgets.
Other
0
stars
0
forks
source link
labconfig should do some initialisation on config files #2
When a LabConfig is instantiated, it should call a general initialisation function that tries to make sense of the labconfig file.
This should do things like:
Ensure the experiment name is a valid python module name
Automatically create a subfolder for the experiment in analysislib and labscriptlib, with an init.py in each (if they don't already exist).
Ensure paths to shared drive exist
And there are more things I'm sure, which are currently scattered throughout the programs that use labconfig, but ought to be in a consistent place.
This initialisation should be able to be suppressed with a keyword argument.
Perhaps also this is where setting of default arguments should live, rather than in the individual programs. We don't have 'runmanagerconfig' and 'BLACSconfig', so so long as we have one config file, all its defaults should probably live in the same place.
Original report (archived issue) by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).
When a LabConfig is instantiated, it should call a general initialisation function that tries to make sense of the labconfig file.
This should do things like:
And there are more things I'm sure, which are currently scattered throughout the programs that use labconfig, but ought to be in a consistent place.
This initialisation should be able to be suppressed with a keyword argument.
Perhaps also this is where setting of default arguments should live, rather than in the individual programs. We don't have 'runmanagerconfig' and 'BLACSconfig', so so long as we have one config file, all its defaults should probably live in the same place.