SiPM Model with Mirco simulation file

Requisite

If you want to use directly the generated verilog-a file you only need Cadence and the SiPM model. You can download them on https://lbredmine.cern.ch/projects/pacific/files (file va0.v to va12.v), the number is the runId.

If you want to generate your own verilog-a files with the python script you need:

  • The Mirco simulations files (available on /afs/cern.ch/user/m/mdeckenh/public/noIrrad_withMirror_1kEventsPerRun_20130621.root)
  • root with the python extension
  • python

Mirco files (from Mirco)

The ROOT files contain the following information:

  • attLengthHistogramScintCore
TH1F, 1D histogram with the attenuation length depending on the wavelength as measured by Blake

  • AttenuationLengths TTree, attenuation length as used in the simulation after calculating effect of radiation and a correction factor
    • energy : photon energy in eV
    • wavelength : photon wavelength in nm
    • sectionNo : the fibre is divided into equal sections, sectionNo=0 is close to the SiPM
    • dose : dose in kGy taken from Neus' FLUKA simulations
    • attLength : absorption length in the scintillating core of the fibre

  • ProducedPhotons TTree, contains information about all the photons that were produced in the simulation. These information correspond to the time when the photons are generated.
    • energy : photon energy in eV
    • wavelength : photon wavelength in nm
    • localtime : time since generation of the photon
    • abstime : absolute time, the time since generation of the MIP
    • length : track length of the photon
    • x : x position of the photon in mm, this corresponds to the Y (DIRECTION IN THE CAVERN -> direction along the fibre)
    • y : ...
    • z : ...
    • excitationpoint : location of excitation (interaction of MIPs with fibre) in mm, 0 is the middle of the fibre, -1250 is where the mirror is placed (Y=0 in the cavern), 1250 is at the SiPM
    • runId: every run in the simulation corresponds to one excitation point
    • eventId: every MIP event in a single run has a particular ID

  • DetectedPhotons TTree, contains information about all the photons arriving at the SiPM.
    • energy : see above
    • wavelength : see above
    • localtime : see above
    • abstime : see above
This is the IMPORTANT VALUE FOR THE TIMING, since it gives the time of arrival at the SiPM including the scintillation decay time.
    • length : see above
    • x : see above
    • y : ...
    • z : ...
    • excitationpoint : see above
    • runId: see above
    • eventId: see above

If you want to compare the results for different excitation points, you have to take into account the number of produced photons at the particular excitation point for normalization. Although 1000 MIPs, each producing O(100) photons, were generated per point of excitation, the number of produced photons differs more than sqrt(N). This is kind of a systematic error.

runId

The runId is related to the excitation point (see the section above). The following picture allows to quickly relate the runId to the excitation point :

logo

0 is the middle of the fibre, -1250 is where the mirror is placed (Y=0 in the cavern), 1250 is at the SiPM

Using the python program

  • monoevent.py
This program allows to generate one particular event.

The eventId, runId, and verilog-a module name are defined at the beginning of the python program. Adjust them to you need then use:

python monoEvent.py
* multiEvent.py This program allows to merge several event with the same excitation point (runId). The choice of the event is made with the eventN variable which can be set at different values during Cadence simulations.

The runId, and verilog-a module name and the number of event/file are defined at the beginning of the python program. Adjust them to you need then use:

python multiEvent.py

TODO

  • Include the PDE of the SiPM
  • Merge several event (eventId) in the same verilog-a event to be able to simulate different fibre attached to the same SiPM channel (for now as the PDE is not taken into account, we have roughly a 0.2PDE using only one fibre)

Event example

These events are generated using the Hamamatsu SiPM model. There is a lot of statistical fluctation between event in the same runId, hence the picture bellow are only examples without any significance.

logo logo logo logo logo logo logo logo logo logo logo logo logo

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng evVSexc.png r2 r1 manage 17.2 K 2013-07-18 - 11:26 ChanalHerve  
PNGpng ha0.png r1 manage 29.5 K 2013-07-19 - 10:40 ChanalHerve  
PNGpng ha1.png r2 r1 manage 29.3 K 2013-07-19 - 10:47 ChanalHerve  
PNGpng ha10.png r2 r1 manage 26.6 K 2013-07-19 - 10:48 ChanalHerve  
PNGpng ha11.png r2 r1 manage 26.3 K 2013-07-19 - 10:48 ChanalHerve  
PNGpng ha12.png r2 r1 manage 24.3 K 2013-07-19 - 10:48 ChanalHerve  
PNGpng ha2.png r2 r1 manage 27.8 K 2013-07-19 - 10:47 ChanalHerve  
PNGpng ha3.png r2 r1 manage 28.5 K 2013-07-19 - 10:48 ChanalHerve  
PNGpng ha4.png r2 r1 manage 26.1 K 2013-07-19 - 10:48 ChanalHerve  
PNGpng ha5.png r2 r1 manage 28.5 K 2013-07-19 - 10:48 ChanalHerve  
PNGpng ha6.png r2 r1 manage 28.0 K 2013-07-19 - 10:47 ChanalHerve  
PNGpng ha7.png r2 r1 manage 32.4 K 2013-07-19 - 10:47 ChanalHerve  
PNGpng ha8.png r2 r1 manage 31.5 K 2013-07-19 - 10:47 ChanalHerve  
PNGpng ha9.png r2 r1 manage 27.9 K 2013-07-19 - 10:47 ChanalHerve  
Texttxt monoEvent.py.txt r1 manage 1.1 K 2013-07-18 - 11:14 ChanalHerve  
Texttxt multiEvent.py.txt r1 manage 1.4 K 2013-07-18 - 11:14 ChanalHerve  
Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2018-11-27 - BlakeLeverington
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LHCb All webs login

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