...
Since the allocated beam time is not very much, we should exploit the capability of operating the CU with multiple trigger engines. This was demonstrated to work at CERN, we need to define more engines and test them.
Moreover, effects like pedestal drift and different investigations to be performed, suggest that we run in such mode to cover more topics in a short data-taking time.
SUch operation must be verified prior to start with beam, and immediately when the beam is on Multiple trigger engines worked with the CU both at CERN-SPS and at INFN with CR tests.
Such operation will be verified again at GSI, with CR and beam, to make sure that the CU operates in the expected way and we can proceed with the test in such mode.
The CNO trigger, in combination with TKR and CAL triggers will be the main trigger for the test. Some runs will be taken with external trigger, others will be taken with standard internal trigger made with TKR and CAL primitives.
A periodic trigger, with variable frequency, will be in parallel to the main particle trigger for most of the runs, in order to sample the hardware status with random triggers.
Below is the list of proposed engines:
*BT42
Trigger | Readout configuration |
|---|---|
CNO&&TKR&&CAL-LO | 4-range, NZS |
periodic(5Hz) | 4-range, NZS |
*BT43
Trigger | Readout configuration |
|---|---|
CNO&&TKR&&CAL-LO | auto-range, ZS |
periodic(5Hz) | 4-range, NZS |
*BT44
Trigger | Readout configuration |
|---|---|
CNO | 4-range, NZS |
periodic(5Hz) | 4-range, NZS |
*BT45
Trigger | Readout configuration |
|---|---|
TKR or CAL | auto-range, ZS |
periodic(5Hz) | 4-range, NZS |
List of runs
Below is a list of specific run requests. Plese update the table and notify Luca so that a proper run schedule can be developed and agreed with GSI
...