Allow the GEM DOCs to easily "tag" and analyze runs
Description
At the moment, the calibration runs workflow is somewhat unpractical.
The GEM DOCs can take calibration runs, but the software overwrites the output of the previous scan. Therefore, the output files must be copied/moved before taking a subsequent scan of the same type. The well-known location where the data is stored is /gemdata/data
, but is only accessible to the gempro
account, so it must be done by a GEM DAQ expert.
Adding the DOCs to the gempro
account is not desired; this account is meant to run the GEM DAQ services and be used by the GEM DAQ experts for maintenance and debugging. The gemdoc
account has been created for the GEM DOCs, but benefits from too few permissions. Since the /gemdata/data
folder is the only location where the raw scans are stored, it must be preserved from accidents as much as possible.
Possible fixes
In my opinion, the solution comes in two steps:
- Complete and deploy local run number feature cmsgemos#221 (closed)
- Allow the
gemdoc
user to read and write into/gemdata/data
The completion of point 1. would allow the raw data to be safe since the /gemdata/runs
folder would remain accessible in writing only the the gempro
user.