Currently, the configuration system of xpdacq is too complicated and nasty. It is better to deprecate the unnecessary configuration file that is needed. We can do all the setup in the startup of ipython collection and we don't really need any additional configuration yaml file to do that.
Expected Behavior
xpdacq doesn't need any yaml file to configure. All the configuration is done inside the .py files in the startup of profile collection by using a single function or class.
Current Behavior
We need two yaml files to set up the xpdacq and most of the information is not important for the experiment. It is only used to setup the class Beamtime
Possible Solution
A function or class that takes in use input and return the necessary stuffs in namespace for the experiment.
Currently, the configuration system of xpdacq is too complicated and nasty. It is better to deprecate the unnecessary configuration file that is needed. We can do all the setup in the startup of ipython collection and we don't really need any additional configuration yaml file to do that.
Expected Behavior
xpdacq doesn't need any yaml file to configure. All the configuration is done inside the .py files in the startup of profile collection by using a single function or class.
Current Behavior
We need two yaml files to set up the xpdacq and most of the information is not important for the experiment. It is only used to setup the class Beamtime
Possible Solution
A function or class that takes in use input and return the necessary stuffs in namespace for the experiment.
Steps to Reproduce (for bugs)
1. 2. 3.
Context
Priority
Your Environment