Difference: TriggerIdeas (1 vs. 32)

Revision 322015-07-04 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
This page contains discussion of the trigger setup of the one of 2014's winning experiments: Pion Decay experiment from the team Odysseus' Comrades.

Revision 302014-09-01 - CenkYildiz

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 7 to 7
 Acceptance Numbers: Percentage of particles (electrons or muons) that were observed in detector to the whole population (pions?) that decayed after SC0, before Calorimeters

Beam Energy Electron Muon
Changed:
<
<
1.0GeV 26.5216403443 84.8026598618
2.0GeV 47.0292019499 100.0
3.0GeV 61.4142658715 100.0
4.0GeV 71.3699477061 100.0
5.0GeV 78.2642460341 100.0
6.0GeV 83.1637160705 100.0
7.0GeV 86.6343925914 100.0
8.0GeV 89.2105570978 100.0
9.0GeV 91.1121123504 100.0
10.0GeV 92.5705790319 100.0
>
>
1.0GeV 26.52 84.8
2.0GeV 47.03 100.0
3.0GeV 61.41 100.0
4.0GeV 71.37 100.0
5.0GeV 78.26 100.0
6.0GeV 83.16 100.0
7.0GeV 86.63 100.0
8.0GeV 89.21 100.0
9.0GeV 91.11 100.0
10.0GeV 92.57 100.0
  Acceptance Numbers: Percentage of particles (electrons or muons) that were observed in detector to the whole population (pions?) that decayed after SC0. This is a more important number, since the ones that decayed after SC0 are the pions that trigger the DAQ. It assumes calorimeter at 10m from SC0.

Beam Energy Electron(%) Muon(%)
Changed:
<
<
1.0GeV 3.41129 10.9035
2.0GeV 3.19166 6.77732
3.0GeV 2.82785 4.59988
4.0GeV 2.48666 3.48444
5.0GeV 2.19166 2.80365
6.0GeV 1.94586 2.34055
7.0GeV 1.74234 2.01486
8.0GeV 1.5731 1.76403
9.0GeV 1.43235 1.56844
10.0GeV 1.31148 1.4159
>
>
1.0GeV 3.4 10.90
2.0GeV 3.19 6.77
3.0GeV 2.83 4.59
4.0GeV 2.49 3.48
5.0GeV 2.19 2.80
6.0GeV 1.94 2.34
7.0GeV 1.74 2.01
8.0GeV 1.57 1.76
9.0GeV 1.43 1.56
10.0GeV 1.31 1.41
 

Triggers and Measurements

Revision 292014-08-31 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 129 to 129
 

Direct Electron trigger: Selects pions decaying into electrons based on Lead Glass signal (preliminary).

Changed:
<
<
It has been proposed to use the LG detector for triggering on electrons. To trigger on the total signal from the LG is complicated. A simpler trigger derived from four LG blocks would be simpler. A minimum of four is required to contain the electron signal and provide a reasonable acceptance. The latter could be about 25-30% of one corresponding to the full surface of the LG, depending on beam momentum.
>
>
It has been proposed to use the LG detector for triggering on electrons. To trigger on the total signal from the LG is complicated. A simpler trigger derived from four LG blocks would be simpler. A minimum of four is required to contain the electron signal and provide a reasonable acceptance. The latter could be about 25-30% of the one corresponding to the full surface of the LG, depending on beam momentum.
  BL4SDirectElectronTrigger.jpg

The analogue signals from four blocks are split by an (active) analogue fanout (LeCroy428F?). Four outputs go (unchanged) to the QDC. Four others are input to a FIFO where the analogue sum is formed. This requires precise timing of the inputs to the first FIFO. An output goes to a discriminator with a high threshold to produce a signal for electrons (possibly including a tail of hadrons). This is put into a coincidence with the Pion Trigger to produce an event trigger. This trigger could be an alternative to the rather complicated electron/muon trigger

  • additional hardware requirements:
Changed:
<
<
    • analogue fanout and fanin (LeCroy 428F?). Coincidence channel. Scaler channel.
>
>
    • analogue fanout and fanin (LeCroy 428F?). Coincidence channel. Scaler channel.
 

Possible Measurement:

Revision 282014-08-31 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 129 to 129
 

Direct Electron trigger: Selects pions decaying into electrons based on Lead Glass signal (preliminary).

Changed:
<
<
It has been proposed to use the LG detector for triggering on electrons. To trigger on the total signal from the LG is complicated. A simpler trigger derived from a single LG block could be simpler. Since only one block is used, the acceptance decreases to about 25-30% of one corresponding to the full surface og the LG.
>
>
It has been proposed to use the LG detector for triggering on electrons. To trigger on the total signal from the LG is complicated. A simpler trigger derived from four LG blocks would be simpler. A minimum of four is required to contain the electron signal and provide a reasonable acceptance. The latter could be about 25-30% of one corresponding to the full surface of the LG, depending on beam momentum.
 
Changed:
<
<
One of the middle LG blocks is centrered on the beam. The analogue signal from this block is split by an (active) analogue fanout. One of the outputs goes to a discriminator with a high threshold to produce a signal for electrons (possibly including a tail of hadrons). This is put into a coincidence with the Pion Trigger to produce an event trigger. Since only one block is used the acceptance is lower
>
>
BL4SDirectElectronTrigger.jpg

The analogue signals from four blocks are split by an (active) analogue fanout (LeCroy428F?). Four outputs go (unchanged) to the QDC. Four others are input to a FIFO where the analogue sum is formed. This requires precise timing of the inputs to the first FIFO. An output goes to a discriminator with a high threshold to produce a signal for electrons (possibly including a tail of hadrons). This is put into a coincidence with the Pion Trigger to produce an event trigger. This trigger could be an alternative to the rather complicated electron/muon trigger

 
  • additional hardware requirements:
Changed:
<
<
* an analog fanout. This trigger could be an alternative to the rather complicated electron/muon trigger.
>
>
    • analogue fanout and fanin (LeCroy 428F?). Coincidence channel. Scaler channel.
  Possible Measurement:
  • from data, find a sample of pion to electron decays, N(e, observed).
Changed:
<
<
  • correct this for acceptance calculated from the surface of the trigger LG block . We then have the number of pions that decayed into electrons N(pion, electron) after SC0: N( SC0, electrons)
>
>
  • correct this for acceptance calculated from the surface of the four trigger LG blocks used in the trigger . We then have the number of pions that decayed into electrons N(pion, electron) after SC0: N( SC0, electrons)
 
  • correct for deadtime, in this case it's negligible since decays into electrons are rare.
  • we know the number of pions (triggers) at SC0: N( SC0, pions). This is the scaler count PionTriggers.
  • BR(e+) = N( SC0,electrons)/ N( SC0,pions)
Line: 201 to 204
 
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409136719" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="20773" user="jorgen" version="1"
Added:
>
>
META FILEATTACHMENT attachment="BL4SDirectElectronTrigger.jpg" attr="" comment="" date="1409492433" name="BL4SDirectElectronTrigger.jpg" path="BL4SDirectElectronTrigger.jpg" size="39211" user="jorgen" version="3"

Revision 272014-08-30 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 127 to 127
 
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
Added:
>
>

Direct Electron trigger: Selects pions decaying into electrons based on Lead Glass signal (preliminary).

It has been proposed to use the LG detector for triggering on electrons. To trigger on the total signal from the LG is complicated. A simpler trigger derived from a single LG block could be simpler. Since only one block is used, the acceptance decreases to about 25-30% of one corresponding to the full surface og the LG.

One of the middle LG blocks is centrered on the beam. The analogue signal from this block is split by an (active) analogue fanout. One of the outputs goes to a discriminator with a high threshold to produce a signal for electrons (possibly including a tail of hadrons). This is put into a coincidence with the Pion Trigger to produce an event trigger. Since only one block is used the acceptance is lower

  • additional hardware requirements: * an analog fanout. This trigger could be an alternative to the rather complicated electron/muon trigger.

Possible Measurement:

  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance calculated from the surface of the trigger LG block . We then have the number of pions that decayed into electrons N(pion, electron) after SC0: N( SC0, electrons)
  • correct for deadtime, in this case it's negligible since decays into electrons are rare.
  • we know the number of pions (triggers) at SC0: N( SC0, pions). This is the scaler count PionTriggers.
  • BR(e+) = N( SC0,electrons)/ N( SC0,pions)
 

Deadtime

The discussion below the figure is probably too complicated and obsolete.

Revision 262014-08-28 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 165 to 165
 
Logical names Physical names Scaler channels Comment Config File Tags for channels of scalers
EventTriggers CoTwo (Main Trigger) 0 # CORBO triggers = # Events in the datafile N_EVENT_TRIGGER_CH ; N_EVENT_CH
Changed:
<
<
PionTriggers CoPion 1 # pions at SC0 N_PI_TRIGGER_CH ; N_DETECTOR_COINCIDENCE_CH
>
>
DetectorTriggers CoDetector 1 Events coming from the selected detector trigger N_DETECTOR_COINCIDENCE_CH ; N_DETECTOR_CH
 
T9Scintillator SC0 2 # hits in SC0 N_T9_SCINTILLATOR_CH ; N_SCINTILLATOR0_CH
CerenkovPionMuonElectron C0 3 Higher pressure to accept pions, muons, electrons N_CHERENKOV0_CH
CerenkovMuonElectron C1 4 Lower pressure to accept muons, electrons N_CHERENKOV1_CH
MuonAfterFilter SC1 5 Hits in the muon scintillator SC1 N_MU_AFTER_FILTER_CH ; N_MUON_SCINTILLATOR_CH ; N_SCINTILLATOR1_CH
PionMuonAfterLeadGlass SC2 6 Hits in the scintillator after the leadglass (SC2) N_PI_MU_AFTER_LG_CH ; N_SCINTILLATOR2_CH
Changed:
<
<
ElectronTriggers CoE+ 7 Initial particle: Pion Final Particle: Electron N_E_TRIGGER_CH
SimpleElectronMuonTriggers OrE+Muon 8 Final Particle: Electron or Muon N_SIMPLE_E_MU_TRIGGER_CH
ElectronMuonTriggers CoE+Mu 9 Initial particle: Pion Final Particle: Electron or Muon N_E_MU_TRIGGER_CH
MilliSeconds   10 real time counter in ms N_MILISECONDS_CH ; N_SECONDS_CH
>
>
PionTriggers CoPion 7 # pions at SC0 N_PI_TRIGGER_CH
ElectronTriggers CoE+ 8 Initial particle: Pion Final Particle: Electron N_E_TRIGGER_CH
SimpleElectronMuonTriggers OrE+Muon 9 Final Particle: Electron or Muon N_SIMPLE_E_MU_TRIGGER_CH
ElectronMuonTriggers CoE+Mu 10 Initial particle: Pion Final Particle: Electron or Muon N_E_MU_TRIGGER_CH
MilliSeconds   11 real time counter in ms N_MILLISECONDS_CH ; N_SECONDS_CH
  -- CenkYildiz - 20 Aug 2014 -- SaimeSarikaya - 28 Aug 2014

Revision 252014-08-28 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 35 to 35
 

Triggers and Measurements

Trigger Units:

Changed:
<
<
  • CH1 -> Set above pion mass (accepts pions muons electrons)
  • CH2 -> Set below pion mass (accepts muons electrons)
>
>
  • CH0 -> Set above pion mass (accepts pions muons electrons)
  • CH1 -> Set below pion mass (accepts muons electrons)
 
  • SC0 (T9)
  • SC1 (Muon)
  • SC2 (Pion/Muon)
Line: 68 to 68
 
  • it is seen that the e+ trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it may be higher since it includes muons.
Changed:
<
<
  • In order to switch from the pion trigger to the electron trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+. Connect an output from CoE+ to COTwo. Or the output from CoE+ could go into another input of CoTwo, then no re-cabling at all is required.
>
>
  • In order to switch from the pion trigger to the electron trigger two cables changes are required: an output from CoPi goes to a second coincidence CoTwo. Move it to the input of CoE+. Connect an output from CoE+ to CoTwo. Or the output from CoE+ could go into another input of CoTwo, then no re-cabling at all is required.
 
  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible. In more details: the pion(trigger) is delayed due to the coincidence unit CoPion (~10 ns). Due to the time of flight, the signal from S2 is delayed ~30 ns(10m) but if the cable is shorter by 10m this delay is compensated. Thus switching from the pion to the electron trigger may not require any timing adjustments.
  • additional hardware requirements:
Line: 109 to 109
 
  • it is seen that the e+/muon trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+/muon trigger signal is interesting in itself without being used as a trigger.
Changed:
<
<
  • In order to switch from the pion trigger to the e+/muon trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+Muon. Connect an output from CoE+Muon to COTwo. Or , simpler, the output of CoE+Muon goes into another input of CoTwo.
>
>
  • In order to switch from the pion trigger to the e+/muon trigger two cables changes are required: an output from CoPi goes to a second coincidence CoTwo. Move it to the input of CoE+Muon. Connect an output from CoE+Muon to CoTwo. Or , simpler, the output of CoE+Muon goes into another input of CoTwo.
 
Changed:
<
<
  • the veto from SC1 should be before the SC2 signal which may require inserting a delay in the SC2 signa (only the discriminator output cable from SC2 to CoPiLg). This could be avoided if the cable from SC1 is even shorter than the cable from SC2. The time-of-flight from SC2 to SC1 is about 7 ns so a reduction in cable length of 2-3 m would be sufficient.
>
>
  • the veto from SC1 should be before the SC2 signal which may require inserting a delay in the SC2 signal (only the discriminator output cable from SC2 to CoPiLg). This could be avoided if the cable from SC1 is even shorter than the cable from SC2. The time-of-flight from SC2 to SC1 is about 7 ns so a reduction in cable length of 2-3 m would be sufficient.
 
  • additional hardware requirements (SC1 is already there ..):
Line: 179 to 179
 -- CenkYildiz - 20 Aug 2014 -- SaimeSarikaya - 28 Aug 2014

META FILEATTACHMENT attachment="BL4SElectronTrigger.jpg" attr="" comment="" date="1408723612" name="BL4SElectronTrigger.jpg" path="BL4SElectronTrigger.jpg" size="33972" user="jorgen" version="3"
Changed:
<
<
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
>
>
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1409233153" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37485" user="jorgen" version="3"
 
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409136719" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="20773" user="jorgen" version="1"

Revision 242014-08-28 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 45 to 45
 

Pion Trigger

Changed:
<
<
BL4SPionTrigger.jpg
>
>
BL4SPionTrigger.jpg
  Possible Measurement:
Line: 64 to 64
  The idea behind the electron trigger is based on a simple observation: the electrons from pion decays between S0 and the LG are absorbed in the LG. Therefore, a scintillation counter placed behind the LG detecting pions and muons and used as a veto, allows to "remove" pions and muons from the pion triggers and thus select the pion to electron decays - or at least to provide an event sample with a significantly increased number of electrons.
Changed:
<
<
BL4SElectronTrigger.jpg
>
>
BL4SElectronTrigger.jpg
 
  • it is seen that the e+ trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it may be higher since it includes muons.
Line: 89 to 89
  The electron trigger selects pions that decayed to electrons before the LG. The SC1 scintillator selects muons after the muon filter. The logical OR between them then defines a sample of pions that decay to electrons before the LG and pions that decay to muons before SC1.
Changed:
<
<
BL4SSimpleElectronOrMuonTrigger.jpg
>
>
BL4SSimpleElectronOrMuonTrigger.jpg
  Possible Measurement:
Line: 105 to 105
  The idea behind the electron/muon trigger is similar to the electron trigger. A scintillation counter placed behind the muon filter detecting muons and used as a veto, allows to "remove" muons from the SC1 trigger and thus select the pions, only, after the LG. If this signal is used, in turn, as a veto for the pion trigger at SC0, we are left with electrons and muons from pion decays at SC0. This trigger may also include background muons from the pion trigger at SC0.
Changed:
<
<
BL4SElectronOrMuonTriggerV2.jpg
>
>
BL4SElectronOrMuonTriggerV2.jpg
 
  • it is seen that the e+/muon trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+/muon trigger signal is interesting in itself without being used as a trigger.
Line: 137 to 137
  DeadTime (%) = 100 - DeadTime(%)
Changed:
<
<
BL4SDeadTimeTwo.jpg
>
>
BL4SDeadTimeTwo.jpg
 
  • the first question is: do we need to know the deadtime during a run?
  • can the burst structure be measured i.e. is there a precise burst signal available?
Line: 163 to 163
  This section should probably not be here .. The purpose is to define more consistent naming conventions related to scalers and detectors and to define the corresponding scaler channels in the V560. In cable diagrams, signal plots and Twikis names are used in a somewhat inconsistent and sometimes misleading way. The logical names in the table should be 'intuitively' understandable and could be used in outputs of scaler information in monitor programs, run summaries etc.. The 'physical' name are used in cabling diagrams, signal timing diagrams, Twiki trigger pages etc.
Changed:
<
<
Logical names Physical names Scaler channels Comment
EventTriggers CoTwo (Main Trigger) 0 # CORBO triggers = # Events in the datafile
PionTriggers CoPion 1 # pions at SC0
ParticleT9 SC0 2 # hits in SC0
CerenkovPionMuonElectron C1 3 Higher pressure to accept pions, muons, electrons
CerenkovMuonElectron C2 4 Lower pressure to accept muons, electrons
MuonAfterFilter SC1 5 Hits in the muon scintillator SC1
PionMuonAfterLeadGlass SC2 6 Hits in the scintillator after the leadglass (SC2)
ElectronTriggers CoE+ 7 Initial particle: Pion Final Particle: Electron
SimpleElectronMuonTriggers OrE+Muon 8 Final Particle: Electron or Muon
ElectronMuonTriggers CoE+Mu 9 Initial particle: Pion Final Particle: Electron or Muon
MilliSeconds   10 real time counter in ms
>
>
Logical names Physical names Scaler channels Comment Config File Tags for channels of scalers
EventTriggers CoTwo (Main Trigger) 0 # CORBO triggers = # Events in the datafile N_EVENT_TRIGGER_CH ; N_EVENT_CH
PionTriggers CoPion 1 # pions at SC0 N_PI_TRIGGER_CH ; N_DETECTOR_COINCIDENCE_CH
T9Scintillator SC0 2 # hits in SC0 N_T9_SCINTILLATOR_CH ; N_SCINTILLATOR0_CH
CerenkovPionMuonElectron C0 3 Higher pressure to accept pions, muons, electrons N_CHERENKOV0_CH
CerenkovMuonElectron C1 4 Lower pressure to accept muons, electrons N_CHERENKOV1_CH
MuonAfterFilter SC1 5 Hits in the muon scintillator SC1 N_MU_AFTER_FILTER_CH ; N_MUON_SCINTILLATOR_CH ; N_SCINTILLATOR1_CH
PionMuonAfterLeadGlass SC2 6 Hits in the scintillator after the leadglass (SC2) N_PI_MU_AFTER_LG_CH ; N_SCINTILLATOR2_CH
ElectronTriggers CoE+ 7 Initial particle: Pion Final Particle: Electron N_E_TRIGGER_CH
SimpleElectronMuonTriggers OrE+Muon 8 Final Particle: Electron or Muon N_SIMPLE_E_MU_TRIGGER_CH
ElectronMuonTriggers CoE+Mu 9 Initial particle: Pion Final Particle: Electron or Muon N_E_MU_TRIGGER_CH
MilliSeconds   10 real time counter in ms N_MILISECONDS_CH ; N_SECONDS_CH
 
Changed:
<
<
-- CenkYildiz - 20 Aug 2014
>
>
-- CenkYildiz - 20 Aug 2014 -- SaimeSarikaya - 28 Aug 2014
 
META FILEATTACHMENT attachment="BL4SElectronTrigger.jpg" attr="" comment="" date="1408723612" name="BL4SElectronTrigger.jpg" path="BL4SElectronTrigger.jpg" size="33972" user="jorgen" version="3"
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"

Revision 222014-08-28 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 173 to 164
 This section should probably not be here .. The purpose is to define more consistent naming conventions related to scalers and detectors and to define the corresponding scaler channels in the V560. In cable diagrams, signal plots and Twikis names are used in a somewhat inconsistent and sometimes misleading way. The logical names in the table should be 'intuitively' understandable and could be used in outputs of scaler information in monitor programs, run summaries etc.. The 'physical' name are used in cabling diagrams, signal timing diagrams, Twiki trigger pages etc.

Logical names Physical names Scaler channels Comment
Changed:
<
<
EventTriggers CoTwo 0 # CORBO triggers = # Events in the datafile
>
>
EventTriggers CoTwo (Main Trigger) 0 # CORBO triggers = # Events in the datafile
 
PionTriggers CoPion 1 # pions at SC0
ParticleT9 SC0 2 # hits in SC0
CerenkovPionMuonElectron C1 3 Higher pressure to accept pions, muons, electrons
CerenkovMuonElectron C2 4 Lower pressure to accept muons, electrons
MuonAfterFilter SC1 5 Hits in the muon scintillator SC1
Changed:
<
<
PionMuonAfterLeadGlass SC2 ? Hits in the scintillator after the leadglass (SC2)
ElectronTriggers CoE+ ?
SimpleElectronMuonTriggers OrE+Muon ?
ElectronMuonTriggers CoE+Mu ?
MilliSeconds   8 real time counter in ms
>
>
PionMuonAfterLeadGlass SC2 6 Hits in the scintillator after the leadglass (SC2)
ElectronTriggers CoE+ 7 Initial particle: Pion Final Particle: Electron
SimpleElectronMuonTriggers OrE+Muon 8 Final Particle: Electron or Muon
ElectronMuonTriggers CoE+Mu 9 Initial particle: Pion Final Particle: Electron or Muon
MilliSeconds   10 real time counter in ms
  -- CenkYildiz - 20 Aug 2014

Revision 212014-08-27 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Added:
>
>

Acceptance calculations

Acceptance Numbers: Percentage of particles (electrons or muons) that were observed in detector to the whole population (pions?) that decayed after SC0, before Calorimeters

Beam Energy Electron Muon
1.0GeV 26.5216403443 84.8026598618
2.0GeV 47.0292019499 100.0
3.0GeV 61.4142658715 100.0
4.0GeV 71.3699477061 100.0
5.0GeV 78.2642460341 100.0
6.0GeV 83.1637160705 100.0
7.0GeV 86.6343925914 100.0
8.0GeV 89.2105570978 100.0
9.0GeV 91.1121123504 100.0
10.0GeV 92.5705790319 100.0

Acceptance Numbers: Percentage of particles (electrons or muons) that were observed in detector to the whole population (pions?) that decayed after SC0. This is a more important number, since the ones that decayed after SC0 are the pions that trigger the DAQ. It assumes calorimeter at 10m from SC0.

Beam Energy Electron(%) Muon(%)
1.0GeV 3.41129 10.9035
2.0GeV 3.19166 6.77732
3.0GeV 2.82785 4.59988
4.0GeV 2.48666 3.48444
5.0GeV 2.19166 2.80365
6.0GeV 1.94586 2.34055
7.0GeV 1.74234 2.01486
8.0GeV 1.5731 1.76403
9.0GeV 1.43235 1.56844
10.0GeV 1.31148 1.4159
 

Triggers and Measurements

Trigger Units:

Line: 30 to 62
 
  • BR(e+) = N(e,electrons) / N( SC0, pions)
The main tool for identication of electrons and muons is the lead glass (LG) detector, using a cut in the energy spectrum or a fitting method. The difficult part is to find a sample of pion to electron decays. The acceptance plots show that ~2% of the pion (triggers) decay between S0 and the lead glass calorimeter. Of those 1/10000 are decays to electrons. Therefore, in 10**6 events we can expect a few decays to electrons. This corresponds in best conditions to 30 minutes of data recording. The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.
Deleted:
<
<
Acceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0, before Calorimeters
Beam Energy Electron Muon
1.0GeV 26.5216403443 84.8026598618
2.0GeV 47.0292019499 100.0
3.0GeV 61.4142658715 100.0
4.0GeV 71.3699477061 100.0
5.0GeV 78.2642460341 100.0
6.0GeV 83.1637160705 100.0
7.0GeV 86.6343925914 100.0
8.0GeV 89.2105570978 100.0
9.0GeV 91.1121123504 100.0
10.0GeV 92.5705790319 100.0
 
Deleted:
<
<
Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0. This is a more important number, since the ones that decayed after SC0 is the pions that trigger our DAQ. It assumes calorimeter at 10m from SC0.
Beam Energy Electron(%) Muon(%)
1.0GeV 3.41129 10.9035
2.0GeV 3.19166 6.77732
3.0GeV 2.82785 4.59988
4.0GeV 2.48666 3.48444
5.0GeV 2.19166 2.80365
6.0GeV 1.94586 2.34055
7.0GeV 1.74234 2.01486
8.0GeV 1.5731 1.76403
9.0GeV 1.43235 1.56844
10.0GeV 1.31148 1.4159
 

Electron trigger: Selects pions decaying into electrons

Line: 83 to 91
  Comment: not really a trigger comment. It's not clear that DWc2 is really useful? IF not it should be removed since it will be in the way for a lot of electrons??
Added:
>
>

Electron/muon trigger: A simpler version

The electron trigger selects pions that decayed to electrons before the LG. The SC1 scintillator selects muons after the muon filter. The logical OR between them then defines a sample of pions that decay to electrons before the LG and pions that decay to muons before SC1.

BL4SSimpleElectronOrMuonTrigger.jpg

Possible Measurement:

  • from data, find a sample of pion to muon decays with pions decaying BEFORE the LG. Events must have a hit in the SC1 (all triggers should have ..) AND a muon signal in the LG.
  • correct this for acceptance. We then have the number of pions that decayed into muons after SC0: N( SC0, muons)
  • from data, find a sample of pion to electron decays, N(e, observed) like in the case of the electron trigger.
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
 

Electron/muon trigger: Selects pions decayed into electrons/muons

The idea behind the electron/muon trigger is similar to the electron trigger. A scintillation counter placed behind the muon filter detecting muons and used as a veto, allows to "remove" muons from the SC1 trigger and thus select the pions, only, after the LG. If this signal is used, in turn, as a veto for the pion trigger at SC0, we are left with electrons and muons from pion decays at SC0. This trigger may also include background muons from the pion trigger at SC0.

Line: 110 to 135
 
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
Deleted:
<
<

Electron/muon trigger: A simpler version

The electron trigger selects pions that decayed to electrons before the LG. The SC1 scintillator selects muons after the muon filter. The logical OR between them then defines a sample of pions that decay to electrons before the LG and pions that decay to muons before SC1.

BL4SSimpleElectronOrMuonTrigger.jpg

Possible Measurement:

  • from data, find a sample of pion to muon decays with pions decaying BEFORE the LG. Events must have a hit in the SC1 (all triggers should have ..) AND a muon signal in the LG.
  • correct this for acceptance. We then have the number of pions that decayed into muons after SC0: N( SC0, muons)
  • from data, find a sample of pion to electron decays, N(e, observed) like in the case of the electron trigger.
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
 
Changed:
<
<

Deadtime

>
>

Deadtime

  The discussion below the figure is probably too complicated and obsolete.
Line: 158 to 168
  The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsSC0 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime
Changed:
<
<

Scaler naming conventions

>
>

Scaler and Detector naming conventions

  This section should probably not be here .. The purpose is to define more consistent naming conventions related to scalers and detectors and to define the corresponding scaler channels in the V560. In cable diagrams, signal plots and Twikis names are used in a somewhat inconsistent and sometimes misleading way. The logical names in the table should be 'intuitively' understandable and could be used in outputs of scaler information in monitor programs, run summaries etc.. The 'physical' name are used in cabling diagrams, signal timing diagrams, Twiki trigger pages etc.

Revision 202014-08-27 - CenkYildiz

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 43 to 43
 
9.0GeV 91.1121123504 100.0
10.0GeV 92.5705790319 100.0
Changed:
<
<
Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0. This is a more important number, since the ones that decayed after SC0 is the pions that trigger our DAQ.
>
>
Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0. This is a more important number, since the ones that decayed after SC0 is the pions that trigger our DAQ. It assumes calorimeter at 10m from SC0.
 
Beam Energy Electron(%) Muon(%)
1.0GeV 3.41129 10.9035
2.0GeV 3.19166 6.77732

Revision 192014-08-27 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 20 to 20
 Possible Measurement:

  • from data, find a sample of pion to muon decays, N( muons, observed).
Added:
>
>
    • the muons are identified by a muon signal in the LG and a hit in SC1 (and SC2?)
 
  • correct this for acceptance. We then have the number of pions that decayed into muons after SC0: N( SC0, muons)
  • from data, find a sample of pion to electron decays, N(e, observed).
Added:
>
>
    • the electrons are identified by a signal in the LG
 
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
Line: 62 to 64
 
  • it is seen that the e+ trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it may be higher since it includes muons.
Changed:
<
<
  • In order to switch from the pion trigger to the electron trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+. Connect an output from CoE+ to CO2. Or the output from CoE+ could go into another input of CoTwo, then no re-cabling at all is required.
>
>
  • In order to switch from the pion trigger to the electron trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+. Connect an output from CoE+ to COTwo. Or the output from CoE+ could go into another input of CoTwo, then no re-cabling at all is required.
 
Changed:
<
<
  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible. In more details: the pion(trigger) is delayed due to the coincidence unit CoPion (~10 ns). Due to the time of flight, the signal from S2 is delayed ~30 ns(10m) but if the cable is shorter by 10m this delay is compensated. Thus switching from the pion to the electron trigger may not require any timing adjustments.
>
>
  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible. In more details: the pion(trigger) is delayed due to the coincidence unit CoPion (~10 ns). Due to the time of flight, the signal from S2 is delayed ~30 ns(10m) but if the cable is shorter by 10m this delay is compensated. Thus switching from the pion to the electron trigger may not require any timing adjustments.
 
  • additional hardware requirements:
Changed:
<
<
    • a scintillator (SC2), and a support. Actually, two scintillators may be useful, the OR between them would increase the efficiency. We have two ISOTDAQ scintillators in the lab bdg.40
    • a 'short' cable from SC2 to the control room (30m?). Actually a short cable would also be useful for SC1.
>
>
    • a scintillator (SC2), and a support. Actually, two scintillators may be useful, the OR between them would increase the efficiency. We have two ISOTDAQ scintillators in the lab bdg.40
    • a 'short' cable from SC2 to the control room (30m?). Actually a short cable would also be useful for SC1.
 
    • coincidence, discriminator, TDC channel, two scaler channels
Added:
>
>
 Possible Measurement:
  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance. We then have the number of pions that decayed into electrons N(pion, electron) after SC0: N( SC0, electrons)
Line: 73 to 76
 
  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance. We then have the number of pions that decayed into electrons N(pion, electron) after SC0: N( SC0, electrons)
  • correct for deadtime, in this case it's negligible since decays into electrons are rare.
Changed:
<
<
  • we know the number of pions (triggers) at SC0, ungated: N( SC0, pions)
>
>
  • we know the number of pions (triggers) at SC0: N( SC0, pions). This is the scaler count PionTriggers.
 
  • BR(e+) = N( SC0,electrons)/ N( SC0,pions)

Comment: as we discussed briefly, one could make a downscaled veto trigger, so that only a KNOWN fraction (e.g. 95%) are used to veto. For eaxmple using a coincidence between a regular pulse train and the veto signal one can remove a fraction of the signals.

Line: 90 to 93
 
  • In order to switch from the pion trigger to the e+/muon trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+Muon. Connect an output from CoE+Muon to COTwo. Or , simpler, the output of CoE+Muon goes into another input of CoTwo.
Changed:
<
<
  • the veto from SC1 should be before the SC2 signal which may require inserting a delay in the SC2 signa (only the discriminator output cable from SC2 to CoPiLg). This could be avoided if the cable from SC1 is even shorter than the cable from SC2. The time-of-flight from SC2 to SC1 is about 7 ns so a reduction in cable length of 2-3 m would be sufficient.
>
>
  • the veto from SC1 should be before the SC2 signal which may require inserting a delay in the SC2 signa (only the discriminator output cable from SC2 to CoPiLg). This could be avoided if the cable from SC1 is even shorter than the cable from SC2. The time-of-flight from SC2 to SC1 is about 7 ns so a reduction in cable length of 2-3 m would be sufficient.
 
  • additional hardware requirements (SC1 is already there ..):
Line: 125 to 128
 

Deadtime

Added:
>
>
The discussion below the figure is probably too complicated and obsolete.

From the scaler counts we know the number of triggers of each type: XTriggers where X = Pion, Electron, ElectronMuon or SimpleElectronMuon depending on which trigger is used. Then

LiveTime (%) = EventTriggers/!XTriggers and * How do we calculate the LiveTime in seconds - bursts *!LiveTime(secs) = LiveTime(%) * MilliSeconds/1000

DeadTime (%) = 100 - DeadTime(%)

 BL4SDeadTimeTwo.jpg

  • the first question is: do we need to know the deadtime during a run?
Line: 152 to 163
 This section should probably not be here .. The purpose is to define more consistent naming conventions related to scalers and detectors and to define the corresponding scaler channels in the V560. In cable diagrams, signal plots and Twikis names are used in a somewhat inconsistent and sometimes misleading way. The logical names in the table should be 'intuitively' understandable and could be used in outputs of scaler information in monitor programs, run summaries etc.. The 'physical' name are used in cabling diagrams, signal timing diagrams, Twiki trigger pages etc.

Logical names Physical names Scaler channels Comment
Changed:
<
<
EventTriggers CoTwo 0
PionTriggers CoPion 1
ParticleT9 SC0 2
>
>
EventTriggers CoTwo 0 # CORBO triggers = # Events in the datafile
PionTriggers CoPion 1 # pions at SC0
ParticleT9 SC0 2 # hits in SC0
 
CerenkovPionMuonElectron C1 3 Higher pressure to accept pions, muons, electrons
CerenkovMuonElectron C2 4 Lower pressure to accept muons, electrons
Changed:
<
<
MuonAfterFilter SC1 5
PionMuonAfterLeadGlass SC2 ?
ElectronTrigger CoE+ ?
SimpleElectronMuonTrigger OrE+Muon ?
ElectronMuonTrigger CoE+Mu ?
>
>
MuonAfterFilter SC1 5 Hits in the muon scintillator SC1
PionMuonAfterLeadGlass SC2 ? Hits in the scintillator after the leadglass (SC2)
ElectronTriggers CoE+ ?
SimpleElectronMuonTriggers OrE+Muon ?
ElectronMuonTriggers CoE+Mu ?
 
MilliSeconds   8 real time counter in ms

-- CenkYildiz - 20 Aug 2014

Revision 182014-08-27 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 170 to 170
 
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
Added:
>
>
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409136719" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="20773" user="jorgen" version="1"

Revision 172014-08-27 - SaimeSarikaya

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"

Triggers and Measurements

Trigger Units:

Changed:
<
<
  • CH1 -> Set above pion mass (accepts pions muons electrons)
  • CH2 -> Set below pion mass (accepts muons electrons)
>
>
  • CH1 -> Set above pion mass (accepts pions muons electrons)
  • CH2 -> Set below pion mass (accepts muons electrons)
 
  • SC0 (T9)
  • SC1 (Muon)
  • SC2 (Pion/Muon)
Line: 28 to 26
 
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
Changed:
<
<
The main tool for identication of electrons and muons is the lead glass (LG) detector, using a cut in the energy spectrum or a fitting method. The difficult part is to find a sample of pion to electron decays. The acceptance plots show that ~2% of the pion (triggers) decay between S0 and the lead glass calorimeter. Of those 1/10000 are decays to electrons. Therefore, in 10**6 events we can expect a few decays to electrons. This corresponds in best conditions to 30 minutes of data recording. The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.
>
>
The main tool for identication of electrons and muons is the lead glass (LG) detector, using a cut in the energy spectrum or a fitting method. The difficult part is to find a sample of pion to electron decays. The acceptance plots show that ~2% of the pion (triggers) decay between S0 and the lead glass calorimeter. Of those 1/10000 are decays to electrons. Therefore, in 10**6 events we can expect a few decays to electrons. This corresponds in best conditions to 30 minutes of data recording. The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.
  Acceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0, before Calorimeters
Beam Energy Electron Muon
Line: 105 to 94
 
  • additional hardware requirements (SC1 is already there ..):
Added:
>
>
 
    • a 'short' cable from SC1 to the control room (30m?).
Deleted:
<
<
 Possible Measurement:

  • from data, find a sample of pion to muon decays, N( muons, observed).
Line: 164 to 149
 

Scaler naming conventions

Changed:
<
<
This section should probably not be here .. The purpose is to define more consistent naming conventions related to scalers and detectors and to define the corresponding scaler channels in the V560. In cable diagrams, signal plots and Twikis names are used in a somewhat inconsistent and sometimes misleading way. The logical names in the table should be 'intuitively' understandable and could be used in outputs of scaler information in monitor programs, run summaries etc.. The 'physical' name are used in cabling diagrams, signal timing diagrams, Twiki trigger pages etc.
>
>
This section should probably not be here .. The purpose is to define more consistent naming conventions related to scalers and detectors and to define the corresponding scaler channels in the V560. In cable diagrams, signal plots and Twikis names are used in a somewhat inconsistent and sometimes misleading way. The logical names in the table should be 'intuitively' understandable and could be used in outputs of scaler information in monitor programs, run summaries etc.. The 'physical' name are used in cabling diagrams, signal timing diagrams, Twiki trigger pages etc.
 
Logical names Physical names Scaler channels Comment
Changed:
<
<
EventTriggers CoTwo 0
PionTriggers CoPion 1
ParticleT9 SC0 2
>
>
EventTriggers CoTwo 0
PionTriggers CoPion 1
ParticleT9 SC0 2
 
CerenkovPionMuonElectron C1 3 Higher pressure to accept pions, muons, electrons
CerenkovMuonElectron C2 4 Lower pressure to accept muons, electrons
Changed:
<
<
MuonAfterFilter SC1 5
PionMuonAfterLeadGlass SC2 ?
ElectronTrigger CoE+ ?
SimpleElectronMuonTrigger OrE+Muon ?
ElectronMuonTrigger CoE+Mu ?
>
>
MuonAfterFilter SC1 5
PionMuonAfterLeadGlass SC2 ?
ElectronTrigger CoE+ ?
SimpleElectronMuonTrigger OrE+Muon ?
ElectronMuonTrigger CoE+Mu ?
 
MilliSeconds   8 real time counter in ms
Deleted:
<
<
 -- CenkYildiz - 20 Aug 2014
Deleted:
<
<
 
META FILEATTACHMENT attachment="BL4SElectronTrigger.jpg" attr="" comment="" date="1408723612" name="BL4SElectronTrigger.jpg" path="BL4SElectronTrigger.jpg" size="33972" user="jorgen" version="3"
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
Line: 189 to 170
 
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409136289" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="20773" user="jorgen" version="2"

Revision 162014-08-27 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 189 to 189
 
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409128191" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="18665" user="jorgen" version="1"
>
>
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409136289" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="20773" user="jorgen" version="2"

Revision 152014-08-27 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 120 to 120
 

Electron/muon trigger: A simpler version

Changed:
<
<
The electron trigger selects pions that decayed to electrons before the LG. The SC1 scintillator selects muons after the muon filter. The logical OR between then defines a sample of pions that decay to electrons before the LG and pions that decay to muons before SC1.
>
>
The electron trigger selects pions that decayed to electrons before the LG. The SC1 scintillator selects muons after the muon filter. The logical OR between them then defines a sample of pions that decay to electrons before the LG and pions that decay to muons before SC1.
 

BL4SSimpleElectronOrMuonTrigger.jpg

Line: 128 to 128
  Possible Measurement:
Changed:
<
<
  • from data, find a sample of pion to muon decays with pions decaying BEFORE the LG. Events must have a hit in the SC1 (all triggers have ..) AND a muon signal in the LG.
>
>
  • from data, find a sample of pion to muon decays with pions decaying BEFORE the LG. Events must have a hit in the SC1 (all triggers should have ..) AND a muon signal in the LG.
 
  • correct this for acceptance. We then have the number of pions that decayed into muons after SC0: N( SC0, muons)
  • from data, find a sample of pion to electron decays, N(e, observed) like in the case of the electron trigger.
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
Line: 189 to 189
 
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
Added:
>
>
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409128191" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="18665" user="jorgen" version="1"

Revision 142014-08-26 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 34 to 34
 The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.
Changed:
<
<
Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0, before Calorimeters
>
>
Acceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0, before Calorimeters
 
Beam Energy Electron Muon
1.0GeV 26.5216403443 84.8026598618
2.0GeV 47.0292019499 100.0
Line: 162 to 162
  The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsSC0 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime
Added:
>
>

Scaler naming conventions

This section should probably not be here .. The purpose is to define more consistent naming conventions related to scalers and detectors and to define the corresponding scaler channels in the V560. In cable diagrams, signal plots and Twikis names are used in a somewhat inconsistent and sometimes misleading way. The logical names in the table should be 'intuitively' understandable and could be used in outputs of scaler information in monitor programs, run summaries etc.. The 'physical' name are used in cabling diagrams, signal timing diagrams, Twiki trigger pages etc.

Logical names Physical names Scaler channels Comment
EventTriggers CoTwo 0
PionTriggers CoPion 1
ParticleT9 SC0 2
CerenkovPionMuonElectron C1 3 Higher pressure to accept pions, muons, electrons
CerenkovMuonElectron C2 4 Lower pressure to accept muons, electrons
MuonAfterFilter SC1 5
PionMuonAfterLeadGlass SC2 ?
ElectronTrigger CoE+ ?
SimpleElectronMuonTrigger OrE+Muon ?
ElectronMuonTrigger CoE+Mu ?
MilliSeconds   8 real time counter in ms
 

-- CenkYildiz - 20 Aug 2014

Revision 132014-08-26 - CenkYildiz

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 47 to 47
 
9.0GeV 91.1121123504 100.0
10.0GeV 92.5705790319 100.0

Changed:
<
<
Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after start of decay area (Halo counter)
Energy Electron Muon
1.0GeV 3.53419639003 11.3050389772
2.0GeV 3.24412029473 6.9046733737
3.0GeV 2.85934500531 4.65866434102
4.0GeV 2.50755860023 3.51671701896
5.0GeV 2.20765969812 2.82147641348
6.0GeV 1.9589751512 2.35462219467
7.0GeV 1.75267680109 2.02265488202
8.0GeV 1.58190057406 1.77267067438
9.0GeV 1.43753707784 1.57808315915
10.0GeV 1.31395459622 1.42089385874
>
>
Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0. This is a more important number, since the ones that decayed after SC0 is the pions that trigger our DAQ.
Beam Energy Electron(%) Muon(%)
1.0GeV 3.41129 10.9035
2.0GeV 3.19166 6.77732
3.0GeV 2.82785 4.59988
4.0GeV 2.48666 3.48444
5.0GeV 2.19166 2.80365
6.0GeV 1.94586 2.34055
7.0GeV 1.74234 2.01486
8.0GeV 1.5731 1.76403
9.0GeV 1.43235 1.56844
10.0GeV 1.31148 1.4159
 

Electron trigger: Selects pions decaying into electrons

Revision 112014-08-26 - CenkYildiz

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 34 to 34
 The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.
Added:
>
>
Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after SC0, before Calorimeters
Beam Energy Electron Muon
1.0GeV 26.5216403443 84.8026598618
2.0GeV 47.0292019499 100.0
3.0GeV 61.4142658715 100.0
4.0GeV 71.3699477061 100.0
5.0GeV 78.2642460341 100.0
6.0GeV 83.1637160705 100.0
7.0GeV 86.6343925914 100.0
8.0GeV 89.2105570978 100.0
9.0GeV 91.1121123504 100.0
10.0GeV 92.5705790319 100.0

Aceptance Numbers: Percentage of particles that was observed in detector to the whole population that decayed after start of decay area (Halo counter)

Energy Electron Muon
1.0GeV 3.53419639003 11.3050389772
2.0GeV 3.24412029473 6.9046733737
3.0GeV 2.85934500531 4.65866434102
4.0GeV 2.50755860023 3.51671701896
5.0GeV 2.20765969812 2.82147641348
6.0GeV 1.9589751512 2.35462219467
7.0GeV 1.75267680109 2.02265488202
8.0GeV 1.58190057406 1.77267067438
9.0GeV 1.43753707784 1.57808315915
10.0GeV 1.31395459622 1.42089385874
 

Electron trigger: Selects pions decaying into electrons

Line: 146 to 171
 
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409052080" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="17929" user="jorgen" version="1"

Revision 102014-08-26 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 92 to 93
 
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
Added:
>
>

Electron/muon trigger: A simpler version

The electron trigger selects pions that decayed to electrons before the LG. The SC1 scintillator selects muons after the muon filter. The logical OR between then defines a sample of pions that decay to electrons before the LG and pions that decay to muons before SC1.

BL4SSimpleElectronOrMuonTrigger.jpg

Possible Measurement:

  • from data, find a sample of pion to muon decays with pions decaying BEFORE the LG. Events must have a hit in the SC1 (all triggers have ..) AND a muon signal in the LG.
  • correct this for acceptance. We then have the number of pions that decayed into muons after SC0: N( SC0, muons)
  • from data, find a sample of pion to electron decays, N(e, observed) like in the case of the electron trigger.
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
 

Deadtime

BL4SDeadTimeTwo.jpg

Line: 126 to 146
 
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"
Added:
>
>
META FILEATTACHMENT attachment="BL4SSimpleElectronOrMuonTrigger.jpg" attr="" comment="" date="1409052080" name="BL4SSimpleElectronOrMuonTrigger.jpg" path="BL4SSimpleElectronOrMuonTrigger.jpg" size="17929" user="jorgen" version="1"

Revision 92014-08-25 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 17 to 17
 

Pion Trigger

Changed:
<
<
BL4SPionTrigger.jpg
>
>
BL4SPionTrigger.jpg
  Possible Measurement:
Line: 26 to 26
 
  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
Changed:
<
<
  • from data, find a sample of pions that don't decay, N(pions, observed).
  • correct this for acceptance. We then have the number of pions that did not decay after SC0: N( SC0, pions)
>
>
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
 
  • BR(e+) = N(e,electrons) / N( SC0, pions)

The main tool for identication of electrons and muons is the lead glass (LG) detector, using a cut in the energy spectrum or a fitting method.

Line: 46 to 45
 
  • it is seen that the e+ trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it may be higher since it includes muons.
Changed:
<
<
  • In order to switch from the pion trigger to the electron trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+. Connect an output from CoE+ to CO2.
>
>
  • In order to switch from the pion trigger to the electron trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+. Connect an output from CoE+ to CO2. Or the output from CoE+ could go into another input of CoTwo, then no re-cabling at all is required.
 
  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible. In more details: the pion(trigger) is delayed due to the coincidence unit CoPion (~10 ns). Due to the time of flight, the signal from S2 is delayed ~30 ns(10m) but if the cable is shorter by 10m this delay is compensated. Thus switching from the pion to the electron trigger may not require any timing adjustments.
  • additional hardware requirements:
Line: 67 to 66
 Comment: not really a trigger comment. It's not clear that DWc2 is really useful? IF not it should be removed since it will be in the way for a lot of electrons??

Electron/muon trigger: Selects pions decayed into electrons/muons

Deleted:
<
<
(CH1 & NOT CH2 & SC0 & NOT SC2 & NOT SC1)
 
Changed:
<
<
Add a logic diagram here. Also to know if we have HW enough!
>
>
The idea behind the electron/muon trigger is similar to the electron trigger. A scintillation counter placed behind the muon filter detecting muons and used as a veto, allows to "remove" muons from the SC1 trigger and thus select the pions, only, after the LG. If this signal is used, in turn, as a veto for the pion trigger at SC0, we are left with electrons and muons from pion decays at SC0. This trigger may also include background muons from the pion trigger at SC0.

BL4SElectronOrMuonTriggerV2.jpg

  • it is seen that the e+/muon trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+/muon trigger signal is interesting in itself without being used as a trigger.

  • In order to switch from the pion trigger to the e+/muon trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+Muon. Connect an output from CoE+Muon to COTwo. Or , simpler, the output of CoE+Muon goes into another input of CoTwo.

  • the veto from SC1 should be before the SC2 signal which may require inserting a delay in the SC2 signa (only the discriminator output cable from SC2 to CoPiLg). This could be avoided if the cable from SC1 is even shorter than the cable from SC2. The time-of-flight from SC2 to SC1 is about 7 ns so a reduction in cable length of 2-3 m would be sufficient.

  • additional hardware requirements (SC1 is already there ..):

    • a 'short' cable from SC1 to the control room (30m?).
  Possible Measurement:
Changed:
<
<
  • Number of pions that decayed into electrons: Ne
  • Number of pions that decayed into muons: Nmu
>
>
  • from data, find a sample of pion to muon decays, N( muons, observed).
  • correct this for acceptance. We then have the number of pions that decayed into muons after SC0: N( SC0, muons)
  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
  • the number of pions at SC0 = # events in the datafile = N(SC0, pions) during livetime
  • BR(e+) = N(e,electrons) / N( SC0, pions)
 

Deadtime

Deleted:
<
<
VERY preliminary ..
 
Changed:
<
<
The description below the figure is too simple. The problem is that the burst structure or the active time t(active) during a run has to be known i.e. the time during a run when the beam was active. The number of busy counts N(busy) has to scaled by the t(active)/t(real time).
>
>
BL4SDeadTimeTwo.jpg
 
  • the first question is: do we need to know the deadtime during a run?
  • can the burst structure be measured i.e. is there a precise burst signal available?
Line: 97 to 113
  deadtime = N(busy)/N(burst)
Deleted:
<
<
The deadtime is measured as shown in the diagram below.

BL4SDeadTime.jpg

 We should check that these signals are sent to scaler channels.

The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsSC0 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime

Line: 109 to 121
  -- CenkYildiz - 20 Aug 2014
Changed:
<
<
META FILEATTACHMENT attachment="BL4SElectronOrMuonTrigger.jpg" attr="" comment="" date="1408716199" name="BL4SElectronOrMuonTrigger.jpg" path="BL4SElectronOrMuonTrigger.jpg" size="40300" user="jorgen" version="1"
>
>
 
META FILEATTACHMENT attachment="BL4SElectronTrigger.jpg" attr="" comment="" date="1408723612" name="BL4SElectronTrigger.jpg" path="BL4SElectronTrigger.jpg" size="33972" user="jorgen" version="3"
Deleted:
<
<
META FILEATTACHMENT attachment="BL4SDeadTime.jpg" attr="" comment="" date="1408720316" name="BL4SDeadTime.jpg" path="BL4SDeadTime.jpg" size="26441" user="jorgen" version="1"
 
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"
Added:
>
>
META FILEATTACHMENT attachment="BL4SDeadTimeTwo.jpg" attr="" comment="" date="1408973491" name="BL4SDeadTimeTwo.jpg" path="BL4SDeadTimeTwo.jpg" size="29282" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronOrMuonTriggerV2.jpg" attr="" comment="" date="1408981047" name="BL4SElectronOrMuonTriggerV2.jpg" path="BL4SElectronOrMuonTriggerV2.jpg" size="45500" user="jorgen" version="1"

Revision 82014-08-24 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 35 to 35
 The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.
Deleted:
<
<

Deadtime

The deadtime is measured as shown in the diagram below.

BL4SDeadTime.jpg

We should check that these signals are sent to scaler channels.

The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsSC0 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime

 

Electron trigger: Selects pions decaying into electrons

Line: 83 to 75
 
  • Number of pions that decayed into electrons: Ne
  • Number of pions that decayed into muons: Nmu
Added:
>
>

Deadtime

VERY preliminary ..

The description below the figure is too simple. The problem is that the burst structure or the active time t(active) during a run has to be known i.e. the time during a run when the beam was active. The number of busy counts N(busy) has to scaled by the t(active)/t(real time).

  • the first question is: do we need to know the deadtime during a run?
  • can the burst structure be measured i.e. is there a precise burst signal available?
  • if we assume that the bursts are identical and regular in time, t(active)/t(real) = 1.4s/6s (?????????)
  • if the value of the ms counter is recorded is recorded with every event, can the exact burst structure or 'active beam time' t(active) be computed from the data in a run?
    • for example: assume that there is at least 'some' events per burst and that the minimum time between bursts is known
    • find the events in the first burst(check on count 'close' in time).
    • find the events in the next burst ....
    • compute the number of bursts in the run
    • assuming that the burst time t(burst) is constant : t(active) = sum(t(burst))
      • if there are 'many' events per burst, t(burst) = t(last event in burst) - t(first event in burst)

If we know the active beam time then we can compute the deadtime:

# counts with active beam N(burst) = N(pulses) * t(active) / t(real)

deadtime = N(busy)/N(burst)

The deadtime is measured as shown in the diagram below.

BL4SDeadTime.jpg

We should check that these signals are sent to scaler channels.

The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsSC0 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime

 

Revision 72014-08-24 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 30 to 30
 
  • correct this for acceptance. We then have the number of pions that did not decay after SC0: N( SC0, pions)
  • BR(e+) = N(e,electrons) / N( SC0, pions)
Changed:
<
<
The main tool for identication of electrons and muons is the lead glass detector, using a cut in the energy spectrum or a fitting method.
>
>
The main tool for identication of electrons and muons is the lead glass (LG) detector, using a cut in the energy spectrum or a fitting method.
 The difficult part is to find a sample of pion to electron decays. The acceptance plots show that ~2% of the pion (triggers) decay between S0 and the lead glass calorimeter. Of those 1/10000 are decays to electrons. Therefore, in 10**6 events we can expect a few decays to electrons. This corresponds in best conditions to 30 minutes of data recording. The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.
Line: 47 to 47
 

Electron trigger: Selects pions decaying into electrons

Added:
>
>
The idea behind the electron trigger is based on a simple observation: the electrons from pion decays between S0 and the LG are absorbed in the LG. Therefore, a scintillation counter placed behind the LG detecting pions and muons and used as a veto, allows to "remove" pions and muons from the pion triggers and thus select the pion to electron decays - or at least to provide an event sample with a significantly increased number of electrons.
 BL4SElectronTrigger.jpg
Changed:
<
<
  • first, it can be noted that the e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it may be higher since it includes muons.
>
>
  • it is seen that the e+ trigger is an add-on to the pion trigger, it doesn't require any recabling of the pion trigger. The e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it may be higher since it includes muons.
 
Changed:
<
<
  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible.
>
>
  • In order to switch from the pion trigger to the electron trigger two cables changes are required: an output from CoPi goes to a second coincidence CO2. Move it to the input of CoE+. Connect an output from CoE+ to CO2.

  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible. In more details: the pion(trigger) is delayed due to the coincidence unit CoPion (~10 ns). Due to the time of flight, the signal from S2 is delayed ~30 ns(10m) but if the cable is shorter by 10m this delay is compensated. Thus switching from the pion to the electron trigger may not require any timing adjustments.
 
  • additional hardware requirements:
    • a scintillator (SC2), and a support. Actually, two scintillators may be useful, the OR between them would increase the efficiency. We have two ISOTDAQ scintillators in the lab bdg.40
    • a 'short' cable from SC2 to the control room (30m?). Actually a short cable would also be useful for SC1.
Line: 64 to 69
 
  • we know the number of pions (triggers) at SC0, ungated: N( SC0, pions)
  • BR(e+) = N( SC0,electrons)/ N( SC0,pions)
Deleted:
<
<
In order to switch from the pion trigger to the electron trigger:
  • an output from CoPi goes to a second coincidence. Move it to the input of CoE+. Connect an output from CoE+ to the second coincidence.
  Comment: as we discussed briefly, one could make a downscaled veto trigger, so that only a KNOWN fraction (e.g. 95%) are used to veto. For eaxmple using a coincidence between a regular pulse train and the veto signal one can remove a fraction of the signals.

Revision 62014-08-23 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 28 to 28
 
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
  • from data, find a sample of pions that don't decay, N(pions, observed).
  • correct this for acceptance. We then have the number of pions that did not decay after SC0: N( SC0, pions)
Changed:
<
<
  • BR(e+) = N(e,electrons) / n( SC0, pions)
>
>
  • BR(e+) = N(e,electrons) / N( SC0, pions)
  The main tool for identication of electrons and muons is the lead glass detector, using a cut in the energy spectrum or a fitting method. The difficult part is to find a sample of pion to electron decays. The acceptance plots show that ~2% of the pion (triggers) decay between S0 and the lead glass calorimeter. Of those 1/10000 are decays to electrons. Therefore, in 10**6 events we can expect a few decays to electrons. This corresponds in best conditions to 30 minutes of data recording.
Line: 42 to 42
  We should check that these signals are sent to scaler channels.
Changed:
<
<
The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsS1 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime
>
>
The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsSC0 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime
 

Electron trigger: Selects pions decaying into electrons

BL4SElectronTrigger.jpg

Changed:
<
<
  • first, it can be noted that the e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it maybe higher.
>
>
  • first, it can be noted that the e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it may be higher since it includes muons.
 
  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible.
  • additional hardware requirements:
Line: 61 to 61
 
  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance. We then have the number of pions that decayed into electrons N(pion, electron) after SC0: N( SC0, electrons)
  • correct for deadtime, in this case it's negligible since decays into electrons are rare.
Changed:
<
<
  • we know the number of pions (triggers) at SC0, ungated: N( SC0, pion)
>
>
  • we know the number of pions (triggers) at SC0, ungated: N( SC0, pions)
 
  • BR(e+) = N( SC0,electrons)/ N( SC0,pions)

In order to switch from the pion trigger to the electron trigger:

Revision 52014-08-23 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Added:
>
>

Triggers and Measurements

 Trigger Units:
  • CH1 -> Set above pion mass (accepts pions muons electrons)
  • CH2 -> Set below pion mass (accepts muons electrons)
Line: 20 to 22
 Possible Measurement:

  • from data, find a sample of pion to muon decays, N( muons, observed).
Changed:
<
<
  • correct this for acceptance. We then have the number of pions that decayed into muons after S1: N( S1, muons)
>
>
  • correct this for acceptance. We then have the number of pions that decayed into muons after SC0: N( SC0, muons)
 
  • from data, find a sample of pion to electron decays, N(e, observed).
Changed:
<
<
  • correct this for acceptance. We then have the number of pions that decayed into electrons after S1: N( S1, electrons)
  • BR(e+) / BR(muons)= N( S1, electrons) / N( S1, muons)
>
>
  • correct this for acceptance. We then have the number of pions that decayed into electrons after SC0: N( SC0, electrons)
  • BR(e+) / BR(muons)= N( SC0, electrons) / N( SC0, muons)
 
  • from data, find a sample of pions that don't decay, N(pions, observed).
Changed:
<
<
  • correct this for acceptance. We then have the number of pions that did not decay after S1: N( S1, pions)
  • BR(e+) = N(e,electrons) / n( S1, pions)
>
>
  • correct this for acceptance. We then have the number of pions that did not decay after SC0: N( SC0, pions)
  • BR(e+) = N(e,electrons) / n( SC0, pions)

The main tool for identication of electrons and muons is the lead glass detector, using a cut in the energy spectrum or a fitting method. The difficult part is to find a sample of pion to electron decays. The acceptance plots show that ~2% of the pion (triggers) decay between S0 and the lead glass calorimeter. Of those 1/10000 are decays to electrons. Therefore, in 10**6 events we can expect a few decays to electrons. This corresponds in best conditions to 30 minutes of data recording. The electrons have a spread in energy (fig) and may be partially absorbed by the frame of DWC2. In addition, in the energy spectrum in the lead glass detector there is a hadron tail. It's not clear that an electron sample can be found. To address this problem, another trigger is proposed as described in a section below.

 

Deadtime

The deadtime is measured as shown in the diagram below.
Line: 42 to 49
  BL4SElectronTrigger.jpg
Changed:
<
<
  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). To avoid or at least minimise this, the cable from SC2 should be as short as possible.
  • additional hardware requirements: coincidence, discriminator, TDC channel, two scaler channels
>
>
  • first, it can be noted that the e+ trigger signal is interesting in itself without being used as a trigger. The scaler counts of e+ should be compared to the count of the pion trigger - it maybe higher.

  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). The pion(trigger) is already delayed (a bit) by the pion trigger logic but to avoid or at least minimise the delay, the cable from SC2 should be as short as possible.
  • additional hardware requirements:
    • a scintillator (SC2), and a support. Actually, two scintillators may be useful, the OR between them would increase the efficiency. We have two ISOTDAQ scintillators in the lab bdg.40
    • a 'short' cable from SC2 to the control room (30m?). Actually a short cable would also be useful for SC1.
    • coincidence, discriminator, TDC channel, two scaler channels
  Possible Measurement:
  • from data, find a sample of pion to electron decays, N(e, observed).
Changed:
<
<
  • correct this for acceptance. We then have the number of pions that decayed into electrons N(pion, electron) after S1: N( S1, electrons)
>
>
  • correct this for acceptance. We then have the number of pions that decayed into electrons N(pion, electron) after SC0: N( SC0, electrons)
 
  • correct for deadtime, in this case it's negligible since decays into electrons are rare.
Changed:
<
<
  • we know the number of pions (triggers) at S1, ungated: N( S1, pion)
  • BR(e+) = N( S1,electrons)/ N( S1,pions)
>
>
  • we know the number of pions (triggers) at SC0, ungated: N( SC0, pion)
  • BR(e+) = N( SC0,electrons)/ N( SC0,pions)
  In order to switch from the pion trigger to the electron trigger:
Changed:
<
<
  • an output from CoPi goes to a second coincidence. Move it to the input of CoE+. Connect an output from CoE+ to the second coincidence.
>
>
  • an output from CoPi goes to a second coincidence. Move it to the input of CoE+. Connect an output from CoE+ to the second coincidence.
 
Changed:
<
<
Comment: as we discussed briefly, one could make a downscaled veto trigger, so that only a KNOWNtion (e.g. 95%) are used to veto. For eaxmple using a coincidence between a regular pulse train and the veto signal one can remove a fraction of the signals.
>
>
Comment: as we discussed briefly, one could make a downscaled veto trigger, so that only a KNOWN fraction (e.g. 95%) are used to veto. For eaxmple using a coincidence between a regular pulse train and the veto signal one can remove a fraction of the signals.
  Comment: not really a trigger comment. It's not clear that DWc2 is really useful? IF not it should be removed since it will be in the way for a lot of electrons??

Revision 42014-08-22 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 12 to 12
 

Trigger Types

Deleted:
<
<

Pion Trigger: Selects pions

(CH1 & NOT CH2 & SC0)
 
Changed:
<
<
ADD a logic diagram here!
>
>

Pion Trigger

BL4SPionTrigger.jpg

  Possible Measurement:
Deleted:
<
<
  • Number of pions that decayed into muons: Nmu
  • Number of pions that decayed into electrons: Ne
  • Number of pions that did not decay
  • Number of muons that did not decay (it is there because we may accept some muons instead of electrons)
 
Changed:
<
<
Due to deadtime, it accepts a fraction of events, but we can measure branching ratio. Branching ratio: Ne/Nmu
>
>
  • from data, find a sample of pion to muon decays, N( muons, observed).
  • correct this for acceptance. We then have the number of pions that decayed into muons after S1: N( S1, muons)
  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance. We then have the number of pions that decayed into electrons after S1: N( S1, electrons)
  • BR(e+) / BR(muons)= N( S1, electrons) / N( S1, muons)
  • from data, find a sample of pions that don't decay, N(pions, observed).
  • correct this for acceptance. We then have the number of pions that did not decay after S1: N( S1, pions)
  • BR(e+) = N(e,electrons) / n( S1, pions)

Deadtime

The deadtime is measured as shown in the diagram below.

BL4SDeadTime.jpg

 
Changed:
<
<
Comment: Nmu is the number of muons SEEN by the detector. To find the real number of muon decays one has to correct for acceptance? Similar remark for electrons - where the acceptance is lower.
>
>
We should check that these signals are sent to scaler channels.
 
Changed:
<
<
About deadtime: we can (and should) measure the deadtime. For example, make a coincidence between the signal generator and the CORBO busy and count this signal. Compare to the free running signal generator. This can more generally be done for other signals: count the number of ungated signals and those on coincidence with the BbusyBAR. We should review the scaler inputs to include these channels.
>
>
The deadtime measurement allows to compute the real number of events in a run from the observed number: Nreal = Nobserved/!LiveTime e.g NPionsS1 = NpionsObserved/LiveTime = NEventsInDatafile/!LiveTime
 
Deleted:
<
<

Electron trigger: Selects pions decayed into electrons

(CH1 & NOT CH2 & SC0 & SC2)
 
Changed:
<
<
Add a logic diagram here.
>
>

Electron trigger: Selects pions decaying into electrons

BL4SElectronTrigger.jpg

  • the veto from SC2 should be before the pion(trigger) signal which may require inserting a delay in the pion(trigger). To avoid or at least minimise this, the cable from SC2 should be as short as possible.
  • additional hardware requirements: coincidence, discriminator, TDC channel, two scaler channels
  Possible Measurement:
Changed:
<
<
  • Number of pions that decayed into electrons: Ne
>
>
  • from data, find a sample of pion to electron decays, N(e, observed).
  • correct this for acceptance. We then have the number of pions that decayed into electrons N(pion, electron) after S1: N( S1, electrons)
  • correct for deadtime, in this case it's negligible since decays into electrons are rare.
  • we know the number of pions (triggers) at S1, ungated: N( S1, pion)
  • BR(e+) = N( S1,electrons)/ N( S1,pions)
 
Changed:
<
<
Since electron decays are rare, it is not affected by deadtime. No branching ratio measurement only from this.
>
>
In order to switch from the pion trigger to the electron trigger:
  • an output from CoPi goes to a second coincidence. Move it to the input of CoE+. Connect an output from CoE+ to the second coincidence.
 
Deleted:
<
<
Comment: the number of electron events have to be corrected for acceptance. Do we know and rely on that? As described above, one can correct for deadtime by measuring(counting) the number of pion triggers when the experiment is 'alive' by ANDing with the CORBO busy. Add a logic diagram. Therefore one could compare to runs with other triggers?? Or am I missing something??
  Comment: as we discussed briefly, one could make a downscaled veto trigger, so that only a KNOWNtion (e.g. 95%) are used to veto. For eaxmple using a coincidence between a regular pulse train and the veto signal one can remove a fraction of the signals.
Line: 64 to 73
 

-- CenkYildiz - 20 Aug 2014

Added:
>
>
META FILEATTACHMENT attachment="BL4SElectronOrMuonTrigger.jpg" attr="" comment="" date="1408716199" name="BL4SElectronOrMuonTrigger.jpg" path="BL4SElectronOrMuonTrigger.jpg" size="40300" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SElectronTrigger.jpg" attr="" comment="" date="1408723612" name="BL4SElectronTrigger.jpg" path="BL4SElectronTrigger.jpg" size="33972" user="jorgen" version="3"
META FILEATTACHMENT attachment="BL4SDeadTime.jpg" attr="" comment="" date="1408720316" name="BL4SDeadTime.jpg" path="BL4SDeadTime.jpg" size="26441" user="jorgen" version="1"
META FILEATTACHMENT attachment="BL4SPionTrigger.jpg" attr="" comment="" date="1408723213" name="BL4SPionTrigger.jpg" path="BL4SPionTrigger.jpg" size="37477" user="jorgen" version="2"

Revision 32014-08-21 - CenkYildiz

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 13 to 13
 

Trigger Types

Pion Trigger: Selects pions

Changed:
<
<
(CH1 & CH2 & SC0)
>
>
(CH1 & NOT CH2 & SC0)
  ADD a logic diagram here!
Line: 34 to 34
 We should review the scaler inputs to include these channels.

Electron trigger: Selects pions decayed into electrons

Changed:
<
<
(CH1 & CH2 & SC0 & SC2)
>
>
(CH1 & NOT CH2 & SC0 & SC2)
  Add a logic diagram here.
Line: 52 to 52
 Comment: not really a trigger comment. It's not clear that DWc2 is really useful? IF not it should be removed since it will be in the way for a lot of electrons??

Electron/muon trigger: Selects pions decayed into electrons/muons

Changed:
<
<
(CH1 & CH2 & SC0 & SC2 & SC1)
>
>
(CH1 & NOT CH2 & SC0 & NOT SC2 & NOT SC1)
  Add a logic diagram here. Also to know if we have HW enough!

Revision 22014-08-20 - JorgenPetersen

Line: 1 to 1
 
META TOPICPARENT name="BeamLineForSchools"
Line: 14 to 14
 

Pion Trigger: Selects pions

(CH1 & CH2 & SC0)
Added:
>
>
ADD a logic diagram here!
 Possible Measurement:
  • Number of pions that decayed into muons: Nmu
  • Number of pions that decayed into electrons: Ne
Line: 23 to 26
 Due to deadtime, it accepts a fraction of events, but we can measure branching ratio. Branching ratio: Ne/Nmu
Added:
>
>
Comment: Nmu is the number of muons SEEN by the detector. To find the real number of muon decays one has to correct for acceptance? Similar remark for electrons - where the acceptance is lower.

About deadtime: we can (and should) measure the deadtime. For example, make a coincidence between the signal generator and the CORBO busy and count this signal. Compare to the free running signal generator. This can more generally be done for other signals: count the number of ungated signals and those on coincidence with the BbusyBAR. We should review the scaler inputs to include these channels.

 

Electron trigger: Selects pions decayed into electrons

(CH1 & CH2 & SC0 & SC2)
Added:
>
>
Add a logic diagram here.
 Possible Measurement:
  • Number of pions that decayed into electrons: Ne

Since electron decays are rare, it is not affected by deadtime. No branching ratio measurement only from this.

Added:
>
>
Comment: the number of electron events have to be corrected for acceptance. Do we know and rely on that? As described above, one can correct for deadtime by measuring(counting) the number of pion triggers when the experiment is 'alive' by ANDing with the CORBO busy. Add a logic diagram. Therefore one could compare to runs with other triggers?? Or am I missing something??

Comment: as we discussed briefly, one could make a downscaled veto trigger, so that only a KNOWNtion (e.g. 95%) are used to veto. For eaxmple using a coincidence between a regular pulse train and the veto signal one can remove a fraction of the signals.

Comment: not really a trigger comment. It's not clear that DWc2 is really useful? IF not it should be removed since it will be in the way for a lot of electrons??

 

Electron/muon trigger: Selects pions decayed into electrons/muons

Changed:
<
<
(CH1 & CH2 & SC0 & SC2 & SC1)
>
>
(CH1 & CH2 & SC0 & SC2 & SC1)

Add a logic diagram here. Also to know if we have HW enough!

 Possible Measurement:
  • Number of pions that decayed into electrons: Ne
  • Number of pions that decayed into muons: Nmu

Revision 12014-08-20 - CenkYildiz

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="BeamLineForSchools"

Trigger Units:

  • CH1 -> Set above pion mass (accepts pions muons electrons)
  • CH2 -> Set below pion mass (accepts muons electrons)
  • SC0 (T9)
  • SC1 (Muon)
  • SC2 (Pion/Muon)

Trigger Types

Pion Trigger: Selects pions

(CH1 & CH2 & SC0) Possible Measurement:
  • Number of pions that decayed into muons: Nmu
  • Number of pions that decayed into electrons: Ne
  • Number of pions that did not decay
  • Number of muons that did not decay (it is there because we may accept some muons instead of electrons)

Due to deadtime, it accepts a fraction of events, but we can measure branching ratio. Branching ratio: Ne/Nmu

Electron trigger: Selects pions decayed into electrons

(CH1 & CH2 & SC0 & SC2) Possible Measurement:
  • Number of pions that decayed into electrons: Ne

Since electron decays are rare, it is not affected by deadtime. No branching ratio measurement only from this.

Electron/muon trigger: Selects pions decayed into electrons/muons

(CH1 & CH2 & SC0 & SC2 & SC1) Possible Measurement:
  • Number of pions that decayed into electrons: Ne
  • Number of pions that decayed into muons: Nmu

-- CenkYildiz - 20 Aug 2014

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback