User Tools

Site Tools


timing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
timing [2016/08/01 13:01]
pereira [Timing]
timing [2020/04/02 20:58]
pereira [MTDC]
Line 16: Line 16:
   * The XFP detector signal is sent to a {{:wiki:Manual_Canberra_CFD_454.pdf|CANBERRA CFD 454 CFD}} in data U6 (patch panel #1 from data U1). The output from the CFD is then sent back to the MCFD in S3 via patch panel #70   * The XFP detector signal is sent to a {{:wiki:Manual_Canberra_CFD_454.pdf|CANBERRA CFD 454 CFD}} in data U6 (patch panel #1 from data U1). The output from the CFD is then sent back to the MCFD in S3 via patch panel #70
   * The MTDC timing signals do not require external delay adjustments because the matching window is sufficiently wide    * The MTDC timing signals do not require external delay adjustments because the matching window is sufficiently wide 
-  * The width and delay of the matching window can be changed in file **vmusbdaqconfig.tcl** in directory **/user/s800/converged_daq/Scripts** +  * The width and delay of the matching window can be changed in file **vmusbdaqconfig.tcl** in directory **/user/s800/s800daq/Scripts** 
-  * SpecTcl calculates the OBJ-FP and XFP-FP ToFs by substracting the E1 up time (MTDC channel 15) to the OBJ time (MTDC channel 3) and the XFP time (MTDC channel 2) +  * The S800 SpecTcl used for online analysis calculates the OBJ-FP and XFP-FP ToFs by substracting the E1 up time (e.g. MTDC channel 0) to the OBJ time (MTDC channel 3) and the XFP time (MTDC channel 2). (Note that a better way to calculated these ToFs should use the average time E1_up and E1_down.)
   * Note that the same flat ribbon cable connected to the MTDC is also feeding the scaler module. Thus, the 16 channels in the MTDC are exactly the same as channels 16-31 of the scaler module   * Note that the same flat ribbon cable connected to the MTDC is also feeding the scaler module. Thus, the 16 channels in the MTDC are exactly the same as channels 16-31 of the scaler module
   * Copies of the timing signals from XF and OBJ used for the TAC ToF were included in channels 8 and 9 of the MTDC (also the scaler)    * Copies of the timing signals from XF and OBJ used for the TAC ToF were included in channels 8 and 9 of the MTDC (also the scaler) 
Line 38: Line 38:
 ^ E1 up ^ 14  | LeCroy Var. ampl. -> Mesytec MCFD ch #0  -> ECL-NIM -> Fan in/out -> Fan in/out -> Fan in/out -> NIM-ECL | ^ E1 up ^ 14  | LeCroy Var. ampl. -> Mesytec MCFD ch #0  -> ECL-NIM -> Fan in/out -> Fan in/out -> Fan in/out -> NIM-ECL |
 ^ E1 up ^ 15  | LeCroy Var. ampl. -> Mesytec MCFD ch #0  -> ECL-NIM -> Fan in/out -> Fan in/out -> NIM-ECL | ^ E1 up ^ 15  | LeCroy Var. ampl. -> Mesytec MCFD ch #0  -> ECL-NIM -> Fan in/out -> Fan in/out -> NIM-ECL |
 +^ II PPAC2 anode  ^ 16  | Mesytec MCFD2 ch #0 |
 +^ II PPAC2 down  ^ 17  | Mesytec MCFD2 ch #1 |
 +^ II PPAC2 up  ^ 18  | Mesytec MCFD2 ch #2 |
 +^ II PPAC2 right  ^ 19  | Mesytec MCFD2 ch #3 |
 +^ II PPAC2 left  ^ 20  | Mesytec MCFD2 ch #4 |
 +^ II PPAC1 anode  ^ 21 | Mesytec MCFD2 ch #5 |
 +^ II PPAC1 down  ^ 22 | Mesytec MCFD2 ch #6 |
 +^ II PPAC1 up  ^ 23 | Mesytec MCFD2 ch #7 |
 +^ II PPAC1 right  ^ 24 | Mesytec MCFD2 ch #8 |
 +^ II PPAC1 left  ^ 25 | Mesytec MCFD2 ch #9 |
 +
  
 The multi-hit capability requires some special attention. Let's imagine a situation where the rate from OBJ detector is much higher than from the FP detector. During this window, the MTDC will record one hit from the FP scintillator (E1 up, which SpecTcl uses as the start ToF reference) and multiple hits from the OBJ scintillator (stops). As a results, SpecTcl will generate an array of OBJ-FP ToFs  called **s800.fp.vmetdc.obj.i**, where i=0 stands for the first hit, i=2 second hit and so on (the corresponding array for XFP-FP TOF is **s800.fp.vmetdc.xfp.i**). The multi-hit capability requires some special attention. Let's imagine a situation where the rate from OBJ detector is much higher than from the FP detector. During this window, the MTDC will record one hit from the FP scintillator (E1 up, which SpecTcl uses as the start ToF reference) and multiple hits from the OBJ scintillator (stops). As a results, SpecTcl will generate an array of OBJ-FP ToFs  called **s800.fp.vmetdc.obj.i**, where i=0 stands for the first hit, i=2 second hit and so on (the corresponding array for XFP-FP TOF is **s800.fp.vmetdc.xfp.i**).
Line 72: Line 83:
  
 ==== Phillips TDC ==== ==== Phillips TDC ====
 +**ATTENTION: Since the end of the GRETINA-2017 campaign, this module is no longer used**
 +
   * Before going to the TDC, the OBJ and XFP detector signals are sent to a {{:wiki:Manual_Canberra_CFD_454.pdf|CANBERRA CFD 454 CFD}} in data U6 via patch panel #54 and #1, respectively   * Before going to the TDC, the OBJ and XFP detector signals are sent to a {{:wiki:Manual_Canberra_CFD_454.pdf|CANBERRA CFD 454 CFD}} in data U6 via patch panel #54 and #1, respectively
   * The TDC start is provided by the [[Trigger|ULM trigger module]]. Since the delay of the S800 trigger may be adjusted during tuning of the S800 (XDT), the stop signals (e.g. from OBJ or XFP) need to be re-adjusted so that the ToF fits into the 400-ns range of the TDC. This is done manually for OBJ and XFP, and remotely via [[XLM Delay|XLM delay module]] (operated by the [[S800 DAQ tools#Delay Window|Delay GUI]]) for other timing signals    * The TDC start is provided by the [[Trigger|ULM trigger module]]. Since the delay of the S800 trigger may be adjusted during tuning of the S800 (XDT), the stop signals (e.g. from OBJ or XFP) need to be re-adjusted so that the ToF fits into the 400-ns range of the TDC. This is done manually for OBJ and XFP, and remotely via [[XLM Delay|XLM delay module]] (operated by the [[S800 DAQ tools#Delay Window|Delay GUI]]) for other timing signals 
timing.txt · Last modified: 2020/04/02 20:58 by pereira