Today, around 8h55 UTC, I changed the config of Hrec to connect it to FbmFE instead of FbmAlp and use the science mode flag DQ_META_ITF_Mode_FE
instead of DQ_META_ITF_Mode and use the lock index flag META_ITF_LOCK_index_FE instead of META_ITF_LOCK_index.
Since 20/04 8h30 UTC, this new configuration was tested on HrecN test process and showed a decrease of the mean latency and an independence
with respect to the latency glitches present on FbmAlp (see plot1).
To do this connection of Hrec to FbmFE, I had to install a new version of Hrec code v5r13 in virgoApp.
To fix this issue that was preventing Virgo data to be injected into astrophysical pipelines, I modified the config of Hrec running online and stop/restart hrec at ~13h40, so that the config with which Hrec runs, reads again from FbmAlp (and uses the corresponding ITF_Mode flag), until the bug is found. This change was done without preventing the control room, so that the manual flag of 'Science Mode' was not changed to 'Adjusting'. This is seen in Figure 2 from VIM.
After this action, the Virgo data was tagged as Science mode by astrophysical pipelines back again, what can be seen in the plot broadcasted gwistat (Figure 3)
