Remove saving filesystem access from session
I whish only the NexusWriter and Lima access the saving filesystem, it would help for testing a local (dev) copy of Bliss, running locally, while reusing all the infrastructure of the beamline (or id00
).
For instance, if I run bliss locally with:
TANGO_HOST=id00:20000 BEACON_HOST=id00:25000 bliss -s sam
Running a sct()
gives an error when the session try to create the Lima folders structure since I am not running locally as opid00
and dont have /data
mounted:
File "/mnt/c/Users/debionne/Dev/bliss/bliss/scanning/writer/file.py", line 184, in prepare
self.prepare_saving(dev, images_path)
File "/mnt/c/Users/debionne/Dev/bliss/bliss/scanning/writer/file.py", line 140, in prepare_saving
device.set_image_saving(directory, prefix)
File "/mnt/c/Users/debionne/Dev/bliss/bliss/scanning/acquisition/lima.py", line 258, in set_image_saving
os.makedirs(self.acq_params["saving_directory"], exist_ok=True)
File "/home/debionne/miniconda3/envs/bliss_1_10x/lib/python3.7/os.py", line 213, in makedirs
makedirs(head, exist_ok=exist_ok)
PermissionError: [Errno 13] Permission denied: '/data'
There are probably very few saving filesystem access in a bliss session, maybe Lima is the only exception? If so, could we transfer the responsibility to create the folder structure to the Lima DS?
Edited by Samuel Debionne