Automatic masking in the trigger path
Description
The full granularity of automatic masking is now implemented in the DAQ path. So far, no automatic masking is implemented in the trigger path. This can, and probably does, create confusion when having a look at the results. The only masking in the trigger path consists in disabling the unstable links at configure time.
The same or reduced DAQ masks should be applied to the trigger path(s). Individual VFAT can be masked at the OptoHybrid level while the links to the EMTF can be masked at the GEM backend level. It is the responsibility of the CSC to mask at the OTMB level.
Possible fixes
The DAQ masks can be applied to the trigger path after each automatic masking iteration. It is unclear how to handle unstable slow-control communication with the OptoHybrid FPGA: disable the OH in the EMTF path, mask the OH in the DAQ, perform some re-tries?
The final solution, like for the DAQ automatic masking comes with a firmware implementation. Feedback from the software-based automatic however cannot hurt.