Problem with proposal name for industrial users and upload to ICAT
Marjolaine reported that sometimes the proposal name "ifx" is used for upload to ICAT on MASSIF1, for example "ifx25" instead of "fx25". This is not systematic but happens from time to time, most of the times the correct "fx25" proposal name is used.
I had a look into the MXCuBE log on id30a1control and indeed something strange is happening:
"message": "Proposal: fx25",
"severity": "INFO",
"timestamp": "2023-11-02 20:54:45,386",
--
"message": "Proposal: fx25",
"severity": "INFO",
"timestamp": "2023-11-02 20:58:52,869",
--
"message": "Proposal: ifx25",
"severity": "INFO",
"timestamp": "2023-11-02 21:00:03,043",
--
"message": "Proposal: fx25",
"severity": "INFO",
"timestamp": "2023-11-02 21:01:01,223",
--
"message": "Proposal: fx25",
"severity": "INFO",
"timestamp": "2023-11-02 21:03:07,013",
--
I used this command for retrieving this information:
id30a1control:/nobackup/id30a1control1/log/mxcube3 % grep -A 2 -w "Proposal: .*fx25" mxcube-web_ui.log.2023-11-03
On this particular day 2023-11-03 there were 14 ifx25 and 72 fx25 proposals.
The proposal for ICAT upload is obtained with this code:
proposal = f"{HWR.beamline.session.proposal_code}{HWR.beamline.session.proposal_number}"