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

22.6.2012 - Kamil Sedlak

Browse Source 
1) Small changes of the musrSimAna documentation
2) A new type of condition added to musrSimAna
3) A few more examples of macro files added
This commit is contained in:
sedlak
2012-06-22 08:40:31 +00:00
parent 8a787cf4a0
commit d191e96ca0
14 changed files with 854 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
doc/musrSimAna.tex
View File

@ -1,5 +1,5 @@
\documentclass[twoside]{dis04}
\usepackage{epsfig}
\usepackage{epsfig}
\def\runauthor{PSI}
\def\shorttitle{musrSimAna}
\begin{document}
@ -328,7 +328,7 @@ All events should/have to be (?) saved in the Root tree
This is just a technical thing serving to test the analysis software -- it should not
have any effect on the analysis results.
\item{\bf musrTH1D \emph{histoName} \emph{histoTitle} \emph{nBins} \emph{min} \emph{max} \emph{variable}
[{\tt rotreference} $\nu_{\rm RRF}$ $\phi_{\rm RRF}$]} \\
[{\tt rotreference} $\nu_{\rm RRF}$ $\phi_{\rm RRF}$] $|$ [correctexpdecay]} \\
Defines a histogram (or more precisely an array of histograms, where the number of histograms
in the array is given by the number of conditions, see section~\ref{howToAnalyse}).
The name of the histogram is defined by \emph{histoName} + the number of the condition.
@ -338,6 +338,10 @@ All events should/have to be (?) saved in the Root tree
The optional keyword ``{\tt rotreference}'' signals that the given histogram will be filled in
rotating reference frame (RRF) with the frequency of $\nu_{\rm RRF}$ and a phase shift of $\phi_{\rm RRF}$.
\\
The optional keyword ``{\tt correctexpdecay}'' signals that the given histogram will be corrected
for the muon exponential decay (i.e. multiplied by a factor $\exp(t/2.19703)$. It is meaningful
only for time variables.
\\
The \emph{variable} stands for the variable that will be
filled into the histogram. The \emph{variable} can be any variable from the output Root tree
of musrSim (see ``Manual of musrSim'') (except for the array variables like
@ -461,9 +465,10 @@ All events should/have to be (?) saved in the Root tree
the M-counter for the whole pile-up time window of $\sim$\,10\,$\mu s$.
Unlike in the case of {\tt VCOINCIDENCEW}, here the \emph{units} are not TDC bins, but
rather time in ``nanosecond'' or ``microsecond''.
\item{\bf fit \emph{histogramName} \emph{function} \emph{min} \emph{max} \emph{p$_1$} \ldots \emph{p$_n$}} \\
\item{\bf fit \emph{histogramName} \emph{function} \emph{option} \emph{min} \emph{max} \emph{p$_1$} \ldots \emph{p$_n$}} \\
Fits the histogram by a given function, where \emph{min}, \emph{max} define the range of the fit
on the $x$-axis of the histogram, and \emph{p$_1$} \ldots \emph{p$_n$} are (typically, with some exceptions)
on the $x$-axis of the histogram, \emph{option} is a string defining fit options (see Root manual for details),
and \emph{p$_1$} \ldots \emph{p$_n$} are (typically, with some exceptions)
the initial values of the function parameters. The following functions are currently predefined:
\begin{description}
\item[pol0] $=p_0$ \ldots a constant (1 parameter) - typically used to fit background.
@ -473,6 +478,10 @@ All events should/have to be (?) saved in the Root tree
\item[funct2] $=p_3 \exp((p_4 - x)/2.19703) \cdot (1+p_2 \cos(p_0 x+p_1)) + p_5$
% \item[funct3] the same as {\tt funct2}
\item[funct4] $=p_3 \exp((- x)/2.19703) \cdot (1+p_2 \cos(p_0 x+p_1)) + p_4$
\item[TFieldCos] $=p_3 (1+p_2 \cos(p_0 x + p_1))$ \hspace{1cm} (this function is useful when the histogram is filled with {\tt ``correctexpdecay''} keyword.)
\item[TFieldCosPLUSbg] $=p_3 (1+p_2 \cos(p_0 x + p_1)) + p_4 \exp(x/2.19703)$
\hspace{1cm} (this function is useful when the histogram is filled with {\tt ``correctexpdecay''} keyword.)
\item[gaus] ... Gauss distribution
\end{description}