The tests done during the weekend have been mostly successful, with the only persistent issue being that ITF_LOCK is requested LOW_NOISE_1 instead of LOW_NOISE_3, after an unlock.
I think I figured out that this is due to the fact that when a node gets managed (as ITF_LOCK does while being under AutoScience) it remembers the state requests of its managers, overriding the ones done manually on the interface. LOW_NOISE_1 is the last request made by the CALI node during the calibration shift last Monday, and even if ITF_CONDITIONS redundantly asks LOW_NOISE_3 when we are in LOW_NOISE_3 just before Science, apparently both requests are still valid.
Here an extract of one of the ITF_LOCK log files, where we can also see that the ITF_CONDITIONS node runs as virgorun and not virgod:
2024-12-14T17:58:45.504Z USERINPUT REQUEST: olserver52.virgo.infn.it virgod old=LOW_NOISE_3 new=LOW_NOISE_1 [leftover request done by CALI]
2024-12-14T17:58:46.487Z USERINPUT REQUEST: olserver52.virgo.infn.it virgorun old=LOW_NOISE_1 new=LOW_NOISE_1 [request by ITF_CONDITIONS, none at the time]
2024-12-14T18:03:01.119Z USERINPUT REQUEST: ctrl24.virgo.infn.it amagazzu old=LOW_NOISE_1 new=LOW_NOISE_3
2024-12-14T18:49:42.613Z USERINPUT REQUEST: olserver52.virgo.infn.it virgorun old=LOW_NOISE_3 new=LOW_NOISE_3 [request by ITF_CONDITIONS just before Science mode]
2024-12-14T19:31:20.373Z USERINPUT MODE: olserver52.virgo.infn.it virgorun old=1 new=0
2024-12-14T19:32:08.399Z USERINPUT MANAGER: olserver52.virgo.infn.it virgod old= new=CALI ['hanging' management by CALI]
2024-12-14T20:07:30.138Z USERINPUT OP: ctrl24.virgo.infn.it amagazzu old=2 new=2
2024-12-14T20:07:34.653Z USERINPUT MODE: ctrl24.virgo.infn.it amagazzu old=1 new=0
2024-12-14T20:12:38.527Z USERINPUT MANAGER: olserver52.virgo.infn.it virgorun old= new=ITF_CONDITIONS
2024-12-14T20:12:40.366Z USERINPUT MANAGER: olserver52.virgo.infn.it virgorun old=ITF_CONDITIONS new=ITF_CONDITIONS
2024-12-14T20:15:42.484Z USERINPUT REQUEST: olserver52.virgo.infn.it virgorun old=LOW_NOISE_3 new=LOW_NOISE_3
2024-12-16T07:06:13.652Z USERINPUT REQUEST: olserver52.virgo.infn.it virgod old=LOW_NOISE_3 new=LOW_NOISE_1
2024-12-16T07:39:08.277Z USERINPUT REQUEST: ctrl24.virgo.infn.it fabiog old=LOW_NOISE_1 new=LOW_NOISE_3
I think that this is because we never put much attention collectively on how to set nodes free when management is not needed anymore, i.e. setting AUTO on the managee's interface apparently is not enough; maybe writing the internal channel ezca['GRD-ITF_LOCK_MODE'] = 'AUTO' is enough, but probably it is best to use the Metatron call node.release() (which should be the opposite of nodes.set_managed()).
More testing will be done on this, other pending items (SQZ and DMS) to be checked during the week.