The self-trigger system is currently under development in the feature/self-trigger branch of dune-artdaq . git tags and the corresponding configurations are given in the table below. When you push changes that require a new configuration, please tag the change (git tag TAGNAME; git push origin TAGNAME) and note it in the table.

Tag Configuration Notes
self-trigger-2019-06-26 np04_self_trigger_00001  
self-trigger-2019-06-28 np04_self_trigger_00001 Hit finding: fixed NUMA allocation and double-hits bug
self-trigger-2019-06-28a np04_self_trigger_00002 Added "send_fragments" (currently false) option to timing BR so hardware triggers can be propagated if necessary
self-trigger-2019-07-01 np04_self_trigger_00003 Made the list of "bad" channels a fcl param ("channels_to_suppress"). If not present, no channels are suppressed
  np04_self_trigger_00005 Fix the CPU pinning for APA 6 so that subscriber threads are on NUMA 0 and hit-finding threads are on NUMA 1
self-trigger-2019-07-09 np04_self_trigger_00006 Add separate thread to Candidate & SWTrigger BRs to handle TPsets and mitigate latency.
  np04_self_trigger_00007 Rearrange netio subscriber and hit-finding threads so half the links are on each NUMA node. See https://its.cern.ch/jira/projects/NP04DAQ/issues/NP04DAQ-96
self-trigger-2019-07-13 np04_self_trigger_00010 Add trigger candidate generation. Config folds in Kurt's changes which were added to np04_self_trigger_00009
self-trigger-2019-07-17 np04_self_trigger_00012 Use fhicl config+RC to only listen to the active components in the aggregation steps
  np04_self_trigger_00013 (commit on 12 August 2019) Switch Candidate (TC generation) and MLT BR (TD generation) to ptmp-tcs.
self-trigger-2019-08-15 np04_self_trigger_00014 Update artdaq version. Update to ptmp v0_4_0 and ptmp_tcs v0_0_4. Send hit fragments from FELIX BR as separate fragment type
self-trigger-2019-08-27 np04_self_trigger_00020 Update to ptmp v0_5_0 and ptmp_tcs v0_1_1. Add readout of SSPs in response to trigger message

Graphite and grafana metrics

We're storing self-trigger metrics in the graphite database running on np04-srv-009. It's connected to a grafana instance for displaying the data. To send metrics to graphite from artdaq-based code, use the graphite plugin by adding a stanza like this to the metrics section of the fhicl config for your board reader:

     graphite: {
         metricPluginType: graphite
         level: 5
         reporting_interval: 5.0
         host: "np04-srv-009.cern.ch"
         port: 2003
         namespace: "artdaq.metrics.test."
      }

To view metrics in grafana, connect (from inside the CERN network) to http://np04-srv-009:3000 . For view-only access, username is np04daq. If you need write access, request from Pengfei Ding (dingpf@FNALNOSPAMPLEASE.GOV). The current dashboard name is shown at the top left: click on it to see all available dashboards. There is a folder for self trigger metrics dashboards.

If for some reason you need to connect directly to the graphite web viewer (which you probably don't: use grafana as described above), you need to make a connection from np04-srv-009 to np04-srv-009:80 (connections from other machines receive an apache test page). One way to achieve this is to set up a local port forward with ssh -N -L 8082:localhost:80 np04-srv-009 and then point your web browser at http://localhost:8082 .

-- PhilipAndrewRodrigues - 2019-06-26

Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2019-08-27 - PhilipAndrewRodrigues
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CENF All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback