|
DUNE-DAQ
DUNE Trigger and Data Acquisition software
|
:warning: daqconf_inspector is in active development and is likely to evolve significantly the near future. :warning:
daqconf_inspector is a commandline utility created to explore new ways to visualize and verify DAQ configurations and the objects they contain. daqconf_inspector provides a set of commands to probe different aspects of a configuration database. The commands are accessible using with the usual syntax
where CONFIG_FILE is the path to the configuration database being inspected. Detailed help is available for each command (including daqconf_inspector via the -h/--help flags).
list-classesDisplays the list of classes known to the schema loaded fom the database, together with the ids of objects belonging to that class fond in the database.
| Example |
|---|
daqconf_inspector ./ehn1-daqconfigs/sessions/np02-session.data.xml list-classes |
|
show-object-treeShow the relationship tree of the OKS object with identifier UID.
UID is the unique object identifier in the database, composed by object name and class name. The UID format argument is <object name><class>.
Starting from the selected object, attributes and objects refererd by relationships are shown recursively as hierarchical tree. By default the command recursively crawls through relationship without limits. The recursion level can be limited with the corresponding optional parameter (see below). In case focussing on a relationship branch is helpful, the focus path option (see below for details) allows to specify the branch to focus on, starting trom the top object. If a focus path is specified, the recursion level is applied starting from the last element of the focus path. The focus path syntax combines relationhsip and object names, using . separators, and [] to select a single item in multi-value relatiosnips. The structure of the focus path specifier is <relationship>[<optional object name>].<relationship>[<optional object name>]. Note: specifiying the object name is required
| Example |
|---|
daqconf_inspector ./ehn1-daqconfigs/sessions/np02-session.data.xml show-object-tree df-03@DFApplication -f network_rules[td-trb-net-rule].descriptor -l 6 |
|
show-objects-of-classShow attributes and relationships of all objects in the database belonging to KLASS
| Example |
|---|
daqconf_inspector ./ehn1-daqconfigs/sessions/np02-session.data.xml show-objects-of-class Segment |
|
show-sessionShow details of each session available in the configuration database
For each session found in the the database, show-session displays:
The high-level session view, including segments, controllers and applications as hierarchical tree. ID and Class are shown for applications and controllers, along with their host and services (open ports) The icon in front of segments and appliations indicate the enable/disable.
Optionally, it displays the path of the the database file where the object is define
Legend
| Icon | Meaning |
|---|---|
| ✅ | Resource enabled |
| ❌ | Resource directly disabled (included in the Session disable list) |
| ⭕️ | Resource indirectly disabled by algorithm |
| 🔵 | Not a resource |
| Example |
|---|
daqconf_inspector ./ehn1-daqconfigs/sessions/np02-session.data.xml show-sessions |
|
show-smartapp-modsExecutes the generate modules method for the selected smart application and session, and displays the results as a hierarchical tree. Resource objects are displaied with their status.
In case visualising a single relationship branch is desired, the focus path option (see below for details) allows to specify the branch to focus on, starting trom the top object. If a focus path is specified, the recursion level is applied starting from the last element of the focus path. The focus path syntax combines relationhsip and object names, using . separators, and [] to select a single item in multi-value relatiosnips. The structure of the focus path specifier is <relationship>[<optional object name>].<relationship>[<optional object name>]. Note: specifiying the object name is required .
Legend
| Icon | Meaning |
|---|---|
| ✅ | Resource enabled |
| ❌ | Resource directly disabled (included in the Session disable list) |
| ⭕️ | Resource indirectly disabled by algorithm |
| 🔵 | Not a resource |
| Example |
|---|
daqconf_inspector ehn1-daqconfigs/sessions/np02-session.data.xml show-smartapp-mods np02-session crp4-wiec -f hermes-ctrl-crp4-wiec-np02-wib-1006 -l 2 |
|
show-d2d-connectionsShows the DetectorToDAQ connections in the database
The receiver id and summary sender informations for each connection are shown in a compact table.
| Example |
|---|
daqconf_inspector ehn1-daqconfigs/sessions/np02-session.data.xml show-d2d-connections |
| TODO |
verify-detstreamsPerforms basic validation of detector datastreams in a database.
It checks the collection of all detastreans in the database for uiniqueness. It also checks that all geo_ids references by detecor streams are unique.
| Example |
|---|
daqconf_inspector ehn1-daqconfigs/sessions/np02-session.data.xml verify-detstreams |
|
|
verify-smart-appsPerforms basic validation on smart daq applications a database.
Implemented tests:
exposes_service attribute. The tedt fails if any of the network rules services is not present in exposes_service.| Example |
|---|
daqconf_inspector ehn1-daqconfigs/sessions/np04-session.data.xml verify-smart-apps |
|