AIDA
GELINA
BRIKEN
nToF
CRIB
ISOLDE
CIRCE
nTOFCapture
DESPEC
DTAS
EDI_PSA
179Ta
CARME
StellarModelling
DCF
K40
ISOLDE
Draft saved at 00:00:00
Fields marked with
*
are required
Entry time:
Mon Aug 18 06:40:35 2025
Author
*
:
Subject
*
:
> Tom et al. tuned the trigger this evening, before we began the runs. (Run 82, or Run 83??) > > ===TRIGGER=== > > Trigger condition is: E OR HI/ds > > We count the CAMAC OR signals as follows: A,B > A: Which CAMAC module? Left to right, 1,2,3,4,5 > B: Which module channel? This is the number engraved on the module by the LEMO output. > > ==E Definition== > All p-n sides of E detector: > RAL 109 discrim cable numbers: 4, 5, 7 > => Corresponds to CAMAC OR Numbers 2,2; 2,1; 3,1, respectively. > > ==HI/ds Definition== > All p-n sides of HI detector: 8, 9, 11 > RAL 109 discrim cable numbers > => Corresponds to CAMAC OR Numbers 4,3; 4,2; 5,3, respectively. > > ds=Downscale; ds factor is 8 = 2^8 = 256 > > ===SCALARS=== > > 0: Ungated > 1: Gated > 2: dE (n-n) [Cable 3] > 3: E (n-n) [Cable 6] > 4: HI (n-n) [Cable 10] > 5: Pulser > 6: Clock > > ===DISCUSSION=== > The n-n side of the E detector seems to be noisier than the p-n side. Thus the p-n side is used for the trigger logic, whilst the n-n side is used for the scalar. > > However, there seems to be something confusing about using the p-n side for the true trigger but the n-n side for the scalars. It means we cannot compare the scalars self- > consistently to each other. That is, the gated or ungated signals do not have a strong correlation with the individual detector scalars. In principle if we have enough LEMO > cables and Fan In/Fan Out modules, we should simply propagate the p-n signals to both the trigger (when relevant, i.e. E detector) and the scalars alike. For now we don't > touch anything, though.
Encoding
:
HTML
ELCode
plain
Suppress Email notification
Attachment 1:
Drop attachments here...
Draft saved at 00:00:00
ELOG V3.1.4-unknown