You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 2, 2021. It is now read-only.
There are no longer warning flags in the BU table when BUs detect bad data. E.g. in http://daq-expert.cms/daq2view-react/?setup=cdaq&time=2018-03-29-09:17:55, the RUs have detected CRC errors from some of the ECAL FEDs. This is also seen in the BUs, which have 'nbEventsWithCRCerrors' > 0 in the corresponding snapshot. However, the DAQView page does not show it.
I would suggest to add this feature, which was there in the old DAQView, for the following cases:
nbCorruptedEvents > 0 -> display #bad: with the count
nbEventsWithCRCerrors > 0 -> display #CRC: with the count
nbEventsMissingData > 0 -> display #incomplete: with the count
Note that the last case will not be present in production, as the configuration forbids any incomplete events.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are no longer warning flags in the BU table when BUs detect bad data. E.g. in http://daq-expert.cms/daq2view-react/?setup=cdaq&time=2018-03-29-09:17:55, the RUs have detected CRC errors from some of the ECAL FEDs. This is also seen in the BUs, which have 'nbEventsWithCRCerrors' > 0 in the corresponding snapshot. However, the DAQView page does not show it.
I would suggest to add this feature, which was there in the old DAQView, for the following cases:
Note that the last case will not be present in production, as the configuration forbids any incomplete events.
The text was updated successfully, but these errors were encountered: