Skip to content
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

Maintaining the Trigger Replay App #208

Open
3 tasks
MRiganSUSX opened this issue Apr 12, 2023 · 0 comments
Open
3 tasks

Maintaining the Trigger Replay App #208

MRiganSUSX opened this issue Apr 12, 2023 · 0 comments
Assignees
Labels
maintenance Addresses user request or change in another part of the system

Comments

@MRiganSUSX
Copy link
Contributor

The Trigger Replay App is a tool for running the trigger system in isolation from the rest of the DAQ apps.
replay_tp_to_chain

It accepts input file(s) that are simple '.txt' TPs and runs your configured algorithm over them. These could be real streamed TPs (from the cold-box for example) or simulated ones, maybe in LArSoft.
How to use:

  • python -m trigger.replay_tp_to_chain runs the configuration generation code here
  • -s 10 slows down the input by a factor 10 (by decreasing the clock rate by that factor) which is useful when outputting
    large logs/debugging information for example
  • --trigger-activity-plugin specifies the name of the TAMaker you
    would like to use
  • --trigger-candidate-plugin identifies the TCMaker
  • --trigger-activity-config provides a dictionary, which maps the configuration for your specified TAMaker, triggering thresholds etc. This can be done for the TCMaker too
  • -l specifies the number of times you would like to play the data file through the system
  • --input-file points to your input TPs file, which have the standard format:

A good sample of real TPs taken from the March 2023 Vertical Drift ColdBox (VDCB) runs can be found on the DUNE GPVMS [here](/nashome/c/cbatchel/Public/tp dataset run020472 60s.txt). These are 60 seconds of streamed TPs directly from readout, on CRP 004, across all induction and collection channels.

Example code to run:

python -m trigger.replay_tp_to_chain -s 10 --trigger-activity-plugin TriggerActivityMakerHorizontalMuonPlugin --trigger-activity-config
‘dict(adjacency_threshold=100, window_length=10000, adj_tolerance=20)‘ --trigger-candidate-plugin
TriggerCandidateMakerHorizontalMuonPlugin --trigger-activity-config ‘dict(adjacency_threshold=100, window_length=10000, adj_tolerance=20)‘ -l 1 --input-file $TPDATA/run_020472_tps_2seconds.txt json

There are several tasks that are required for the replay app:

  • Make sure the hardware map is overwritten (or give a warning)
  • Multiple APAs? E.g. 5 APAs, 10 links each (so 10 Zippers, ActivityMaker)
  • Add the .dot graph generation to the replay app
@MRiganSUSX MRiganSUSX added the maintenance Addresses user request or change in another part of the system label Apr 12, 2023
@MRiganSUSX MRiganSUSX self-assigned this Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Addresses user request or change in another part of the system
Projects
None yet
Development

No branches or pull requests

1 participant