Create the experiment class and move all scans to have HDF5 files saved

[gfabbris]

• Creates an experiment class that will hold the experiment information.
• The most critical of these are the experiment.base_experiment_path and experiment.file_base_name, as the scans will raise an error if these are not setup.
• To setup the experiment, run setup_experiment() and follow the prompts, or pass the information as keyword arguments.
• By default, it is very opinionated. You can choose to use the 'data managment' or 'dserv' locations, and the data will be saved using "run name"/"experiment name"/"sample name" (for example: 2024-3/iridium_hp/Sr2IrO3).
• After running the setup, the ipython session will move to that folder.
• Every scan is saved to both the Bluesky catalog and HDF5 files.
• See change_sample to change to a new sample.

[prjemian]

After running the setup, the ipython session will move to that folder.

What about log files.

[gfabbris]

After running the setup, the ipython session will move to that folder.

What about log files.

Good point. What do you think about saving all logs to the same folder? I can see the advantage of getting the logs to the "appropriate" folder, but at the same time I think the users will rarely use it.

[prjemian]

You can save all the log files to a specific directory by configuring the logging to use an absolute directory address instead of a relative address. In the newer ms_model_instrument, there are two configuration items (logger and IPython In/Out).

The older configuration used one directory in the iconfig.yml file.

These log file locations are configured only at startup of each session. Since you are changing the user's present working directory, a single directory might work better for you. You would not have to restart logging each time the PWD is changed.