Global Control Screen: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 3: | Line 3: | ||
* Section 2 of the screen inside the green rectangle allows the user to set operational parameters for all the signals. The TrigMode, MinCompWin and MaxCompWin controls are the most commonly modified controls in this region. The TrigMode enables or disables the use of the trigger system to select specific events. TrigMode has two modes: IntAcptAll and TTCL. In the IntAcptAll mode, every AcceptedHit will get read out. In the TTCL mode, only the subset of AcceptedHits that meet the selection criteria of the trigger are read out. When this is selected, the MinCompWin and MaxCompWin controls select the time window relative to the timestamp contained within the Trigger Accept message during which events will be marked for readout. These timing values are related to the values of the [[Gammasphere Waveform Buffers|“M Window”, “K0 window” and “K window”]]. The green parameters act immediately upon the user setting a new value (no “Load Delays” is required like in Section 1). | * Section 2 of the screen inside the green rectangle allows the user to set operational parameters for all the signals. The TrigMode, MinCompWin and MaxCompWin controls are the most commonly modified controls in this region. The TrigMode enables or disables the use of the trigger system to select specific events. TrigMode has two modes: IntAcptAll and TTCL. In the IntAcptAll mode, every AcceptedHit will get read out. In the TTCL mode, only the subset of AcceptedHits that meet the selection criteria of the trigger are read out. When this is selected, the MinCompWin and MaxCompWin controls select the time window relative to the timestamp contained within the Trigger Accept message during which events will be marked for readout. These timing values are related to the values of the [[Gammasphere Waveform Buffers|“M Window”, “K0 window” and “K window”]]. The green parameters act immediately upon the user setting a new value (no “Load Delays” is required like in Section 1). | ||
* Section 3 of the screen inside the blue rectangle encloses a separate set of controls that, like the red and green areas, control) how the digitizer channels process the analog data. These controls, however, are focused upon generic parameters that would apply to any signal as opposed to the other control parameters used to tune the response to specific timings and signal shapes. | * Section 3 of the screen inside the blue rectangle encloses a separate set of controls that, like the red and green areas, control) how the digitizer channels process the analog data. These controls, however, are focused upon generic parameters that would apply to any signal as opposed to the other control parameters used to tune the response to specific timings and signal shapes. | ||
* Section 4 of the screen inside the orange rectangle has to do with how the digitizer sends data to the [[Triggers|trigger system]] and how the [[Digitizers|digitizer]] responds to the trigger system. Under normal circumstances the average user will never change these controls, the only exception is situations where setups are being used when only “clean” (non-scattered) gamma-ray hits should ever be read out. In this case the “EN VETO” box would be checked to allow the trigger system to automatically strip all “dirty” hits from the GeCenter/BGOsum channel pair before they can be selected for readout. | |||
* | |||
[[File:GlobalCtls.png|1200px|center]] | [[File:GlobalCtls.png|1200px|center]] | ||
''Go back to [[DGS Commander EDM Screens]]'' | ''Go back to [[DGS Commander EDM Screens]]'' |
Revision as of 18:54, March 16, 2023
The global control screen allows a user to set control values that are written to all the digitizers in Gammasphere's DAQ system - in other words, it allows a user to specify the parameters of their desired waveform.
- Section 1 of the screen inside the red rectangle has four columns, each of which represent the different signals sent from detectors. The user sets these parameters so the time values can determine which signal shapes should be saved as waveform data, and how much of it should be saved. The threshold, PARST delay and CFD fraction are used to select how sensitive the digitizer is to the amplitude of the expected signals. Once all the values in the red section 1 are set, the user has to send a "load delays" command (the green button), which restarts the firmware and processes the data with the newly set values.
- Section 2 of the screen inside the green rectangle allows the user to set operational parameters for all the signals. The TrigMode, MinCompWin and MaxCompWin controls are the most commonly modified controls in this region. The TrigMode enables or disables the use of the trigger system to select specific events. TrigMode has two modes: IntAcptAll and TTCL. In the IntAcptAll mode, every AcceptedHit will get read out. In the TTCL mode, only the subset of AcceptedHits that meet the selection criteria of the trigger are read out. When this is selected, the MinCompWin and MaxCompWin controls select the time window relative to the timestamp contained within the Trigger Accept message during which events will be marked for readout. These timing values are related to the values of the “M Window”, “K0 window” and “K window”. The green parameters act immediately upon the user setting a new value (no “Load Delays” is required like in Section 1).
- Section 3 of the screen inside the blue rectangle encloses a separate set of controls that, like the red and green areas, control) how the digitizer channels process the analog data. These controls, however, are focused upon generic parameters that would apply to any signal as opposed to the other control parameters used to tune the response to specific timings and signal shapes.
- Section 4 of the screen inside the orange rectangle has to do with how the digitizer sends data to the trigger system and how the digitizer responds to the trigger system. Under normal circumstances the average user will never change these controls, the only exception is situations where setups are being used when only “clean” (non-scattered) gamma-ray hits should ever be read out. In this case the “EN VETO” box would be checked to allow the trigger system to automatically strip all “dirty” hits from the GeCenter/BGOsum channel pair before they can be selected for readout.
Go back to DGS Commander EDM Screens