From 8db5a95661982ed0a287c571c2c25f9ef755ec6f Mon Sep 17 00:00:00 2001 From: Michal Rigan Date: Mon, 7 Aug 2023 18:35:02 +0200 Subject: [PATCH] Update README.md - A's comments Co-authored-by: ArturSztuc --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 074bcb83..cb74f08b 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,7 @@ The trigger is designed hierarchically. The minimal (extremely simplified) flow: * **Trigger Activity Maker (TAM)**: A general module in charge of processing the incoming stream of TPs and issuing a localised activity trigger at the granularity of single APA/CRPs (and PDS detector units in the future). TAM have with them associated an algorithm, which attempts to search the incoming TP stream for interesting physics activity. The TAs that the TAM produces are sent to the TCM. * **Trigger Candidate Maker (TCM)**: In analogy to the TAM, which identifies clusters of TPs representing activity across many wire channels, the TCM identifies clusters of TAs across many APAs/CRPs. As an example, consider a cathode crossing muon in ProtoDUNE, that generates a track on two opposite facing APAs. Should we want to trigger on this, the TCM might wait for the two corresponding tracks on the opposite APAs before issuing a TC to the Module Level Trigger. -* **Module Level Trigger (MLT)**: What you might imagine to be called the “TDMaker” at this point, is in fact the ‘edge’ of the trigger system, and we call it the Module Level Trigger. As it's name suggests, it is in charge of sending TDs to dataflow orchestrator for raw data contained within an entire DUNE FD module. +* **Module Level Trigger (MLT)**: What you might imagine to be called the “TDMaker” at this point, is in fact the ‘edge’ of the trigger system, and we call it the Module Level Trigger. As its name suggests, it is in charge of sending TDs to dataflow orchestrator for raw data contained within an entire DUNE FD module. #### Modules-Other: * **TPChannelFilter**: Filters out collection or induction *TPs* from its input *TPSets* and passes them on. One can filter out *TPs* based on their offline channel number. Useful for testing on the VDCB, where one might want to only present collection *TPs* to the **TAM** when searching for tracks. It can also filter out noisy channels.