|
|
| Line 21: |
Line 21: |
| | | | |
| | = [[DAQ in EEL 108]] = | | = [[DAQ in EEL 108]] = |
| − |
| |
| − | How to run the DAQ in EEL building room 108.
| |
| − |
| |
| − | user: hccoda
| |
| − | Password is posted near the screen
| |
| − | computer: cdaql3
| |
| − |
| |
| − | Start/stop runs
| |
| − |
| |
| − | Usually the DAQ is already running one of the workspaces on cdaql3 (giant screen). Then it's like any other CODA system. Stop/start runs with the Run Control GUI (rcgui).
| |
| − |
| |
| − | How to CODA start from scratch.
| |
| − |
| |
| − | On hccoda@cdaql3, type "startCoda" (note the capital C). The xterms with components pops up. Those are the 3 crates nps-vme1, nps-vme2, nps-vme3, as well as the event builder PEB1. The Run Control GUI (rcgui) pops up. We normally want the configuration "NPS_3crate" for the aforementioned crates. We also have single-VME configs ("vme1", "vme2", "vme3") but they only work if the trigger is plugged into the master TI. More on trigger below.
| |
| − |
| |
| − | -
| |
| − | FADC parameters are defined in the usual config file
| |
| − |
| |
| − | ssh -X nps-vme1 -l hccoda
| |
| − | cd cfg
| |
| − | and see nps-vmeN.cfg where N = 1, 2, 3
| |
| − | Please don't modify these unless you know what you are doing.
| |
| − |
| |
| − | Trigger
| |
| − |
| |
| − | Curently (Jan 24, 2023) the trigger is a front-panel trigger going into the 7th input of the TI-master. This input is labelled "TS#1". Later we'll have a fancy VTP trigger and I'll update this. But currently the trigger consists of the "and" between a scintillator on top and bottom of the calorimeter. And each scintillator is the "or" of the two PMTs that are connected to the two ends of the scintillator.
| |
| | | | |
| | = [[NPS Controls]] = | | = [[NPS Controls]] = |
