Detector configuration difference in cmsgemos and `confChamber.py`

Summary

Detector configuration achieved with cmsgemos functionalities is different from the configuration obtained with confChamber.py script.

What is the current behavior?

In the gemsupervisor xdaq application after the initialization stage, the configureAction is invoked on the various gemhardware managers to configure the detector and set the appropriate registers.

One can configure the detector independently of the xdaq applications with the confChamber.py script

The detector jconfigurations obtained in these two manners are different. In the particular case of the latency scan run, the cmsgemos configuration yields to empty histograms in the analysis output, while the histograms are correctly filled whant the configuration is applied throught the python script.

What is the expected correct behavior?

The two configuration methods should be equivalent.