search

DUNE-DAQ / dqm

Data Quality Monitoring module, does processing data from the readout, trigger primitives and trigger records. In charge of preparing the data for the analysis and monitoring platforms and raise alerts in case of integrity issue in the data.
0 stars 1 forks source link

Readout DQM app reporting repeated invalid timestamps / not updating #147

Closed wesketchum closed 1 year ago

wesketchum commented 1 year ago

While running at EHN1, getting repeated warning messages:

The timestamp 18446744073709551615 is not valid

I believe this comes from here: https://github.com/DUNE-DAQ/dqm/blob/e66442e9b68997781daada65f63499ed205256ae/plugins/DQMProcessor.cpp#L479

This was not happening in v3.2.2.

The timestamp estimate pieces haven't changed as far as I can tell, but the timestamp sync reciever pieces have. E.g.

https://github.com/DUNE-DAQ/dqm/blob/e66442e9b68997781daada65f63499ed205256ae/plugins/DQMProcessor.cpp#L68

is new.

I think the issue comes in the init configuration. In the produced dqmrunp04srv0280_init.json file, I see something like:

        {
            "data": {
                "conn_refs": [
                    {
                        "name": "timesync_input",
                        "uid": "timesync_runp04srv028_0_.*"
                    },
                    (...)
                ]
            },
            "inst": "dqmprocessor",
            "plugin": "DQMProcessor"
        }

But, in the readout modules, the timesyncs have the form timesync_runp04_srv_028_0_.*. Manually overriding to the latter fixes the issue.

wesketchum commented 1 year ago

Believed fixed. Can reopen if issue.