LMU/musrsim
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

27.1.2011 Kamil Sedlak

Browse Source 
1) correction of volume that is assigned to optical photons
   (odet_ID) - now it is the volume from postStepPoint instead of
   preStepPoint
2) new variable added (nOptPhot) - number of optical photons
   generated in the event
This commit is contained in:
sedlak
2011-01-27 14:36:03 +00:00
parent 543a0e667b
commit 7a8ea16943
7 changed files with 137 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/musrSim.pdf
View File

Binary file not shown.

49
doc/musrSim.tex
View File

@ -688,8 +688,16 @@ Three special volumes ``Target, M0, M1 and M2''.
Normaly the simulation of ``detected signal'' stops at the level of the deposited energy in
a sensitive volume (e.g.\ in a scintilator tile). However, in some special cases, one would
like to know how the light is propagated through the scintillators. In such case simulation
of optical photons is possible. It will, however, significantly (in some cases dramatically)
reduce the speed of the simulation. The output of the optical photon simulation is stored
of optical photons is possible. Note that the optical photon in Geant are treaded as a class
of particles distinct from higher energy gamma particles -- and there is no smooth transition
between the two. Some additional material properties
of an active detector and of the detector surface have to be defined for optical photons.
We strongly recommend the users willing to simulate optical photons to read the
chapter ``Optical Photon Processes'' in~\cite{geantUserManual} to understand the rest of
this chapter.
The simulation of optical photons will significantly (in some cases dramatically)
reduce the speed of the program. The output of the optical photon simulation is stored
in variables starting with the string ``odet\_''. The user has to specify several parameters
in order to simulate optical photons:
%
@ -700,21 +708,46 @@ in order to simulate optical photons:
will be ignored internally in musrSim, and the user therefore does not have to
comment out other parameters connected with optical photons in the macro file.
\item{\bf /musr/command materialPropertiesTable \emph{MPT\_name} \emph{property} \emph{n} \emph{val(1)} ... \emph{val(n)} \emph{E(1)} ... \emph{E(n)} \\
\item{\bf /musr/command materialPropertiesTable \emph{MPT\_name} \emph{property} \emph{n}
\emph{E(1)} ... \emph{E(n)} \emph{val(1)} ... \emph{val(n)} } \\
Defines some optical \emph{property} of a given material (e.g.\ absorption lenght,
refractive index, scintillation yield, ...} to a material property table.
refractive index, scintillation yield, ...) to a material property table.
\emph{MPT\_name} stands for the material property table name. The table has
\emph{n} different values \emph{val(1)} ... \emph{val(n)} for the same number
of optical photon energies \emph{E(1)} ... \emph{E(n)} expressed in MeV.
If \emph{n}=0, the \emph{property} is called ``constant property''.
Possible \emph{property} keywords are: ABSLENGTH, RINDEX, FASTCOMPONENT, SLOWCOMPONENT,
SCINTILLATIONYIELD, and constant \emph{properties} are SCINTILLATIONYIELD, RESOLUTIONSCALE,
FASTTIMECONSTANT, SLOWTIMECONSTANT, and YIELDRATIO.
Some of the possible \emph{property} keywords are: ABSLENGTH, RINDEX, FASTCOMPONENT, SLOWCOMPONENT,
SCINTILLATIONYIELD, and some of the constant \emph{properties} are SCINTILLATIONYIELD, RESOLUTIONSCALE,
FASTTIMECONSTANT, SLOWTIMECONSTANT, and YIELDRATIO. See other \emph{property} keywords
in chapter ``Optical Photon Processes'' in~\cite{geantUserManual}.\\
\begin{description}
\item{\bf SCINTILLATIONYIELD} ... nr. of photons per 1\,MeV of deposited energy.
\item{\bf RESOLUTIONSCALE} ... intrinsic resolution -- normally 1, larger than
1 for crystals with impurities, smaller than 1 when Fano factor plays a role.
\item{\bf YIELDRATIO} ... relative strength of the fast component as a fraction
of total scintillation yeald.
\end{description}
\item {\bf /musr/command setMaterialPropertiesTable \emph{MPT\_name} \emph{material\_name}} \\
Assigns a material property table defined by ``/musr/command materialPropertiesTable''
to a given material.
\item {\bf /musr/command opticalSurface \emph{surface\_name} \emph{phys\_volName1} \emph{phys\_volName2} \emph{surfaceType} \emph{surfaceFinish} \emph{surfaceModel} \emph{MPT\_name}}\\
Defines ``border surface'' (G4LogicalBorderSurface, see subsection ``Boundary Process''
of chapter ``Optical Photon Processes'' in ~\cite{geantUserManual}).
\begin{description}
\item{\bf surface\_name} name of the newly defined surface.
\item{\bf phys\_volName1, phys\_volName2} names of the physics volume in question (it is an ordered pair!).
\item{\bf surfaceType} one of the following: dielectric\_dielectric, dielectric\_metal, dielectric\_LUT, firsov, x\_ray.
\item{\bf surfaceFinish} surface finish properties, such as: polished, ground, etchedair, ...
\item{\bf surfaceModel} one of the following: glisur, unified, LUT.
\item{\bf MPT\_name} optional ``material properties table name'' which should be assigned to the surface.
E.g.\ REFLECTIVITY or EFFICIENCY for a given surface may be assigned this way.
\end{description}
One has to assign a non-zero EFFICIENCY and a REFLECTIVITY smaller than 1 to a boundary surface
between the scintillator and sensitive device (e.g.\ an APD).
\end{description}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@ -1097,6 +1130,8 @@ in~\cite{Aktas:2004px}.
Nucl. Inst. and Meth. in Phys. Res. A 389 (1997) 81.%-86.
See also http://root.cern.ch/.
\bibitem{geantUserManual} Geant4 User Manual
\bibitem{turtle}
K.L.~Brown, Ch.~Iselin, D.C.~Carey, {\it``Decay Turtle''}, CERN 74-2 (1974). \\
U.~Rohrer, {\it ``Compendium of Decay Turtle Enhancements''},