-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger latency monitoring configuration #126
Changes from 3 commits
9d83aa9
4c737ce
bb0d891
f0a52c3
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -80,7 +80,7 @@ | |||||
|
||||||
<oks-schema> | ||||||
|
||||||
<info name="" type="" num-of-items="49" oks-format="schema" oks-version="862f2957270" created-by="asztuc" created-on="np04-srv-019.cern.ch" creation-time="20231211T133151" last-modified-by="eflumerf" last-modified-on="ironvirt9.mshome.net" last-modification-time="20240903T185336"/> | ||||||
<info name="" type="" num-of-items="49" oks-format="schema" oks-version="862f2957270" created-by="asztuc" created-on="np04-srv-019.cern.ch" creation-time="20231211T133151" last-modified-by="mrigan" last-modified-on="np04-srv-016.cern.ch" last-modification-time="20240912T162108"/> | ||||||
|
||||||
<include> | ||||||
<file path="schema/confmodel/dunedaq.schema.xml"/> | ||||||
|
@@ -136,6 +136,7 @@ | |||||
<superclass name="DataReaderConf"/> | ||||||
<attribute name="prescale" description="Prescale factor to apply to HSIEvent input" type="u32" init-value="1" is-not-null="yes"/> | ||||||
<relationship name="signals" class-type="HSISignalWindow" low-cc="one" high-cc="many" is-composite="no" is-exclusive="no" is-dependent="no"/> | ||||||
<relationship name="latency_monitoring_conf" class-type="LatencyMonitoringConf" low-cc="zero" high-cc="zero" is-composite="yes" is-exclusive="yes" is-dependent="yes"/> | ||||||
</class> | ||||||
|
||||||
<class name="HSIEventToTCApplication"> | ||||||
|
@@ -169,6 +170,7 @@ | |||||
<attribute name="td_out_of_timeout" type="bool" init-value="true" is-not-null="yes"/> | ||||||
<attribute name="buffer_timeout" type="u32" init-value="100" is-not-null="yes"/> | ||||||
<attribute name="td_readout_limit" type="u32" init-value="1000" is-not-null="yes"/> | ||||||
<relationship name="latency_monitoring_conf" class-type="LatencyMonitoringConf" low-cc="zero" high-cc="zero" is-composite="yes" is-exclusive="yes" is-dependent="yes"/> | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't this be
Suggested change
|
||||||
</class> | ||||||
|
||||||
<class name="MLTModule"> | ||||||
|
@@ -210,6 +212,7 @@ | |||||
<class name="StandaloneTCMakerConf" is-abstract="yes"> | ||||||
<attribute name="template_for" type="class" init-value="StandaloneTCMakerModule" is-not-null="yes"/> | ||||||
<attribute name="timestamp_method" type="enum" range="kTimeSync,kSystemClock" init-value="kTimeSync" is-not-null="yes"/> | ||||||
<relationship name="latency_monitoring_conf" class-type="LatencyMonitoringConf" low-cc="zero" high-cc="zero" is-composite="yes" is-exclusive="no" is-dependent="yes"/> | ||||||
</class> | ||||||
|
||||||
<class name="StandaloneTCMakerModule"> | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Personally I think an entire new class to overlay a boolean is a bit of an overkill.
On one hand being able to switch all the monitoring on with one object is nice, but on the other hand, it adds extra complexity when we want to switch only one of these on. And I imagine e.g. by default we might it off, say,
RawDataProcessor
andTPDataProcessor
(especially since now it's on per-TP, not per-TPSet basis) but on in theTCDataProcessor
and in theMLT
. It could also be added inDataProcessor
, so it doesn't need to be in all the derived processors separately.Perhaps @glehmannmiotto has a more elegant solution here? Perhaps enabling latency monitoring via application? There are other non-
DataProcessor
-derived objects that also need this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with your assessment @ArturSztuc, and think that we should only add a boolean attribute. The question for @MRiganSUSX is who is in charge of the monitoring. Is it the application, the module or the data processor? Depending on this we should put the attribute in the right class (DataProcessor may be the right one). If you are worried about the ease of enabling/disabling this monitoring feature (although, why would you ever want to disable it?), then it is easy to add a python utility in daqconf that changes the value of the attribute for an application, a class of applications, or all.