Difference: SamplePWA (1 vs. 6)

Revision 6
23 Feb 2016 - Main.JulianPychy
Line: 1 to 1
 
META TOPICPARENT name="FirstStepInstructions2"

Tutorial: performing an Example Partial Wave Analysis

Changed:
<
<
For testing and benchmarking purposes, an example PWA of Monte Carlo toy data is located in the directory /Pawian/Examples/benchmark . It is an analysis of the antiproton-proton annihilation into π0 π0 η with only the f2(1270) and the a2(1320) as intermediate resonances.
>
>
For testing and benchmarking purposes, an example PWA of Monte Carlo toy data is located in the directory Pawian/Examples/benchmark/pbarp . It is an analysis of the antiproton-proton annihilation into π0 π0 η with only the f2(1270) and the a2(1320) as intermediate resonances.
 

This is a step by step tutorial on running this example.
Line: 17 to 17
 
toyDataModel.dat The "experimental" toy data as an ASCII file containing four-vectors
toyDataMC.dat The phasespace distributed toy Monte Carlo data as an ASCII file containing four-vectors
defaultparams.dat A list of default start parameters for the fit
Changed:
<
<
benchmark_runscript A shell script to run the PWA in client/server-mode
>
>
benchmark*runscript Shell scripts to run the PWA in different modes
 

Setting the Environment

Line: 35 to 35
  To start any PWA, a list of start parameters has to be given. A default list can be generated by running
Changed:
<
<
pbarpReactionApp -c pbarpReactionDefault.cfg --mode dumpDefaultParams
>
>
$TOP_DIR/bin/singleChannelApp --pbarpFiles pbarpReactionDefault.cfg --mode dumpDefaultParams
 

Line: 44 to 44
  This example PWA is performed using the client/server mode with two clients, each one using two threads. The relevant configuration file options are
Changed:
<
<
serverPort = 22225
serverAddress = localhost
noOfClients = 2
noOfThreads = 2
>
>
serverPort = 50001
serverAddress = localhost
noOfClients = 2
noOfThreads = 2
 

To start the server run
Changed:
<
<
pbarpReactionApp -c pbarpReactionDefault.cfg --mode server --paramFile defaultparams.dat
>
>
$TOP_DIR/bin/singleChannelApp --pbarpFiles pbarpReactionDefault.cfg --mode server --paramFile defaultparams.dat
 

However, you may want to pipe the output into a log file, e.g.
Changed:
<
<
pbarpReactionApp -c pbarpReactionDefault.cfg --mode server --paramFile defaultparams.dat !>& server.log &
>
>
$TOP_DIR/bin/singleChannelApp --pbarpFiles pbarpReactionDefault.cfg --mode server --paramFile defaultparams.dat !>& server.log &
 

Wait some seconds and then start the two clients on the same machine:
Changed:
<
<
pbarpReactionApp -c pbarpReactionDefault.cfg --mode client --paramFile defaultparams.dat !>& client1.log &
pbarpReactionApp -c pbarpReactionDefault.cfg --mode client --paramFile defaultparams.dat !>& client2.log &
>
>
$TOP_DIR/bin/singleChannelApp --pbarpFiles pbarpReactionDefault.cfg --mode client --paramFile defaultparams.dat !>& client1.log &

$TOP_DIR/bin/singleChannelApp --pbarpFiles pbarpReactionDefault.cfg --mode client --paramFile defaultparams.dat !>& client2.log &
 

In the server.log, lines similar to the following should appear:
Changed:
<
<
INFO: ********* Server mode ****************
INFO: Listening on port 22225
INFO: Number of clients for channel 0 : 2
INFO: Waiting for 2 clients ...
INFO: Client pc17 logged in (ID 0).
INFO: Client pc17 logged in (ID 1).
INFO: All clients ready.
INFO: start migrad
>
>
INFO: ********* Server mode ****************
INFO: Listening on port 50001
INFO: Number of clients for channel 0 : 2
INFO: Waiting for 2 clients ...
INFO: Client pc17 logged in (ID 0).
INFO: Client pc17 logged in (ID 1).
INFO: All clients ready.
INFO: start migrad
 

During the minimization, the current values of the likelihood are printed
Line: 80 to 82
  while the current parameter values (with default errors) are frequently dumped into a file named currentResult.dat. After the minimization has finished, the logfile should show
Changed:
<
<
**************** Minuit FunctionMinimum information ******************
Function minimum is valid.
Covariance matrix is valid.
Final LH: -7163.214059
# of function calls: 2868
minimum edm: 4.96117168e-06
>
>
**************** Minuit FunctionMinimum information ******************
INFO: Function minimum is valid.
INFO: Covariance matrix is valid.
INFO: Final LH: -7163.214059
INFO: # of function calls: 2868
INFO: minimum edm: 4.96117168e-06
 

The file finalResult.dat now holds the list of final fit parameters with proper errors. Another file serializedOutput.dat is created in which (currently only) the covariance matrix is stored for later use.
Line: 91 to 93
  Start the QA mode by running
Changed:
<
<
pbarpReactionApp -c pbarpReactionDefault.cfg --mode qaMode --paramFile finalResult.dat !>& logQA.log &
>
>
$TOP_DIR/bin/singleChannelApp --pbarpFiles pbarpReactionDefault.cfg --mode qaMode --paramFile finalResult.dat !>& logQA.log &
 

A ROOT file pawianHists.root is created (this may take some time). This file holds:
Revision 5
10 Feb 2015 - Main.BertramKopf
Line: 1 to 1
 
META TOPICPARENT name="FirstStepInstructions2"

Tutorial: performing an Example Partial Wave Analysis

Revision 4
25 Jul 2014 - Main.JulianPychy
Line: 1 to 1
 
META TOPICPARENT name="FirstStepInstructions2"

Tutorial: performing an Example Partial Wave Analysis

Line: 95 to 95
 

A ROOT file pawianHists.root is created (this may take some time). This file holds:
Changed:
<
<
  • two ROOT trees _dataFourvecs and _fittedFourvecs where the latter are the Monte Carlo data but with an additional weight representing the amplitude value for this event
>
>
  • two ROOT trees _dataFourvecs and _fittedFourvecs where the latter are the Monte Carlo data but with an additional weight representing the fitted intensity for this event
 
  • Histograms of masses and angles, as chosen in the configuration file. The histograms have prefixes "Data", "MC" and "Fit", so to quickly estimate the goodness of fit, you can plot the "Data" and the corresponding "Fit" histogram on the same canvas.
Examples:
Revision 3
08 Jul 2014 - Main.BertramKopf
Line: 1 to 1
 
META TOPICPARENT name="FirstStepInstructions2"

Tutorial: performing an Example Partial Wave Analysis

Changed:
<
<
For testing and benchmarking purposes, an example PWA of Monte Carlo toy data is located in the directory /Pawian/Examples/benchmark . It is an analysis of the antiproton-proton annihilation into Pi0 Pi0 Eta with only the f2(1270) and the a2(1320) as intermediate resonances.
>
>
For testing and benchmarking purposes, an example PWA of Monte Carlo toy data is located in the directory /Pawian/Examples/benchmark . It is an analysis of the antiproton-proton annihilation into π0 π0 η with only the f2(1270) and the a2(1320) as intermediate resonances.
 

This is a step by step tutorial on running this example.
Line: 22 to 22
 

Setting the Environment

Changed:
<
<
To run PAWIAN, some environment variables have to be set. An example is given in the file "SetEnv_rub" in the top directory of the PAWIAN installation. On the bochum site, you only have to "cd" into that directory and type
>
>
To run PAWIAN, some environment variables have to be set. An example is given in the file "SetEnv_rub" in the top directory of the PAWIAN installation. On the Βochum site, you only have to "cd" into that directory and type
 

source SetEnv_rub
Revision 2
07 Jul 2014 - Main.JulianPychy
Line: 1 to 1
 
META TOPICPARENT name="FirstStepInstructions2"

Tutorial: performing an Example Partial Wave Analysis

Line: 30 to 30
 

Otherwise, you'll have to set the relevant environment variables ROOTSYS, TOP_DIR, LD_LIBRARY_PATH and BOOST_BUILD_PATH yourself. Additionally, ${ROOTSYS}/bin has to appear in your PATH variable.
Changed:
<
<

Generating the default parameter list

>
>

Generating the default Parameter List

 

To start any PWA, a list of start parameters has to be given. A default list can be generated by running
Line: 39 to 39
 

Changed:
<
<

Starting the server and the clients

>
>

Starting the Server and the Clients

 

This example PWA is performed using the client/server mode with two clients, each one using two threads. The relevant configuration file options are
Line: 97 to 97
  A ROOT file pawianHists.root is created (this may take some time). This file holds:
  • two ROOT trees _dataFourvecs and _fittedFourvecs where the latter are the Monte Carlo data but with an additional weight representing the amplitude value for this event
  • Histograms of masses and angles, as chosen in the configuration file. The histograms have prefixes "Data", "MC" and "Fit", so to quickly estimate the goodness of fit, you can plot the "Data" and the corresponding "Fit" histogram on the same canvas.
Changed:
<
<
in progress
>
>
Examples:

invMassPi0Pi0.pnginvMassPi0Eta.png
 

-- JulianPychy - 07 Jul 2014
Added:
>
>
META FILEATTACHMENT attachment="invMassPi0Eta.png" attr="" comment="Invariant pi0eta mass" date="1404746518" name="invMassPi0Eta.png" path="invMassPi0Eta.png" size="13620" user="JulianPychy" version="1"
META FILEATTACHMENT attachment="invMassPi0Pi0.png" attr="" comment="Invariant pi0pi0 mass" date="1404746531" name="invMassPi0Pi0.png" path="invMassPi0Pi0.png" size="13919" user="JulianPychy" version="1"
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding PANDA Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)