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
In a reproducible way, I observe that the artdaq dispatcher disconnects its clients (in my case - a DQM client) in the end of a subrun. An example of the log printout follows.
|Info:TransferWrapper:TransferWrapper.cc [145] Received 2773-rd event, seqID == 755916014096, type == 226 (Data)
|Info:TransferWrapper:TransferWrapper.cc [145] Received 2774-th event, seqID == 755916014097, type == 229 (EndOfSubrun)
|Warning:ArtSummary: [0]
|Warning:ArtSummary: [0] TrigReport ---------- Event summary -------------
|Warning:ArtSummary: [0] TrigReport Events total = 2772 passed = 2772 failed = 0
|Warning:ArtSummary: [0]
|Warning:ArtSummary: [0] TrigReport ---------- Trigger-path summary ------------
|Warning:ArtSummary: [0] TrigReport Path ID Run Passed Failed Error Name
|Warning:ArtSummary: [0]
|Warning:ArtSummary: [0] TrigReport ---------- End-path summary ---------
|Warning:ArtSummary: [0] TrigReport Run Success Error
|Warning:ArtSummary: [0] TrigReport 2772 2772 0
|Warning:ArtSummary: [0]
|Warning:ArtSummary: [0] TrigReport ---------- Modules in End-path ----------
|Warning:ArtSummary: [0] TrigReport Run Success Error Name
|Warning:ArtSummary: [0] TrigReport 2772 2772 0 trackerDQM
|Warning:ArtSummary: [0]
|Warning:ArtSummary: [0] TrigReport ---------- Module summary ------------
|Warning:ArtSummary: [0] TrigReport Visited Run Passed Failed Error Name
|Warning:ArtSummary: [0] TrigReport 2772 2772 2772 0 0 trackerDQM
|Warning:ArtSummary: [0]
|Warning:ArtSummary: [0] TimeReport ---------- Time summary [sec] -------
|Warning:ArtSummary: [0] TimeReport CPU = 1.689956 Real = 9.845394
|Warning:ArtSummary: [0]
|Warning:ArtSummary: [0] MemReport ---------- Memory summary [base-10 MB] ------
|Warning:ArtSummary: [0] MemReport VmPeak = 3517.19 VmHWM = 477.569
|Warning:ArtSummary: [0]
|Info:TransferWrapper:TransferWrapper.cc [385] Requesting that this monitor (DQMClient01) be unregistered from the dispatcher aggregator
|Info:TransferWrapper:TransferWrapper.cc [390] Response from dispatcher is "Success"
In a reproducible way, I observe that the artdaq dispatcher disconnects its clients (in my case - a DQM client) in the end of a subrun. An example of the log printout follows.
https://github.com/art-daq/artdaq/blob/develop/artdaq/ArtModules/detail/TransferWrapper.cc#L385
The text was updated successfully, but these errors were encountered: