GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » NUSTAR » NUSTAR PRESPEC » Lycca mh-TDC scintillators analysis (Lycca ToF analysis)
Lycca mh-TDC scintillators analysis [message #17527] Mon, 17 November 2014 18:19 Go to next message
RiccardoAvigo is currently offline  RiccardoAvigo
Messages: 14
Registered: July 2014
Location: Milano
occasional visitor
From: *mi.infn.it
Dear all,

I am checking Lycca ToF using prespec code. Till now I used MhTdcPreprocessor class to catch times from PMTs and select the hit using a proper gate. I used the output of this class as input for CirculaMembraneScintillator class and, in the end, I used ToF class to have the calibrated ToF.
Now I saw that also a TimeHitSelectionMembrane class exists.
Therefore I wondered if MhTdcPreprocessor is a good class to select the hit and which is the improvement of this TimeHitSelectionMembrane class.

thanks in advance for the help,

cheers,

Riccardo
Re: Lycca mh-TDC scintillators analysis [message #17562 is a reply to message #17527] Mon, 24 November 2014 10:43 Go to previous messageGo to next message
miree is currently offline  miree
Messages: 71
Registered: June 2014
continuous participant
From: *ikp.physik.tu-darmstadt.de
Hi Riccardo,

The MhTdc Preprocessor is selecting the hits using a simple gate.
I think TimeHitSelectionMembrane is selecting a hit if the PMT on the other side of the detector also has a hit at a similar time.
I've no experience with that one. Maybe someone can report about its performance.

Michael
Re: Lycca mh-TDC scintillators analysis [message #17757 is a reply to message #17527] Wed, 14 January 2015 09:54 Go to previous message
mlcortes is currently offline  mlcortes
Messages: 41
Registered: July 2014
Location: Darmstadt
continuous participant
From: *ikp.physik.tu-darmstadt.de
Hi Ricardo!
Sorry for the late reply Sad

If you are still interested, the TimeHitSelectionMembrane selects the hit in the Mh to used based on difference in time between opposite PMTs.
The way I am using it is:
First I put the preprocesor as it was before. I use as reference the common trigger signal and I use it mainly to shift the scale of the time histograms. Then I use the HitSelection processor like this:

processor Lycca/HitSelectionStart  UTILS.TimeHitSelectionMembrane
          input_array[0:30] <-  Lycca/TofStartPreproc0.output[0:30]
          input_array[31] <-  Lycca/TofStartPreproc0.output[0]
          display all_diff  
          display diff_visu | time_gate 
          display hit_mult  20,0,20  in HitSelectionStart/multiplicity
          display output_array  in HitSelectionStart/output
          display input_array   in HitSelectionStart/input
end


The processor takes oppopsite PMTs and make all the possible differences between hits in each one of them. In the output all_diff you can see the difference of all the hits in one of them minus the first hit in the second. The output diff_visu, is an output of all the differences, where you can put a gate. This gate should ne around zero. The processor will then select as a valid time the two PMT combination the first hit that make a difference inside the gate.
There are still some precaution to take into account: I have been using this processor for some time, but is still a bit in a "experimental stage". In principle, the sum of the times should be a constant, but it didn't work for me and I still don't understand why. The fact that the difference is around zero means that the beam was around the center (I think), and then is still a good condition to apply.
You can play around with it a bit if you want, and see if you can improve your results. If you do, please also post it so we know that it is working for more people than me Smile

Liliana



Li^2
Previous Topic: New CoreTracking Algorithm
Next Topic: prespec code
Goto Forum:
  


Current Time: Tue Jun 25 14:50:50 CEST 2024

Total time taken to generate the page: 0.00858 seconds