Difference: ParserArguments (1 vs. 10)

Revision 10
25 Sep 2014 - Main.BertramKopf
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Line: 27 to 27
 
production {particle1} {particle2} Adds the production of two particles to the amplitude
replaceParamSuffix {string1} {string2} Replace a part of a parameter name ({string1}) with {string2}. This option can be used to merge parameters.
replaceMassKey {particle name} {new name} Replace the name of a particle inside the Mass/Width parameter name. This option can be used to merge parameters.
Changed:
<
<
useProductionBarrier {bool} Enable or disable barrier factors for the production system
>
>
useProductionBarrier {bool} {double) Enable or disable barrier factors for the production system and optioal an argument for setting th​e qR-barrier constant (default: 0.197) can be added
 
massRange {min} {max} {particle1} {particle2} ... {particleN} Set mass interval for the invariant mass of particle1 particle2 ... particleN
productionFormalism {string} Choose formalism for the production process: "Heli", "Cano" or "Tensor" are supported
Revision 9
24 Sep 2014 - Main.BertramKopf
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Line: 20 to 20
 

Option Arguments Description
Changed:
<
<
addDynamics {particle} {dynamic} [k-matrix configuration file] Adds a dynamic amplitude to the decay of a particle. When the k-matrix formalism is used a configuration file has to be given.
>
>
addDynamics {particle} {dynamic} [argument1 ...] Adds a dynamic amplitude to the decay of a particle. Arguments have to be added for specific dynamics. When the k-matrix formalism is used a configuration file has to be given.
 
cloneParticle {particle1} {particle2} Create a new particle {particle2} in the particle table that has the same properties as particle {particle1}
decay {formalism} [noiso] {particle1} To {particle2} {particle3} Adds the decay of particle1 to the amplitude using a certain spin formalism. The [noiso] option is optional and disables isospin couplings
finalStateParticle {name} Name of one final state particle. The order of final state particles in the configuration file has to be the same as in the data/monte carlo files
Line: 66 to 66
 
Option Arguments Description
cacheAmps {bool} enable/disable caching of amplitudes
mnParFix {parameter name} Fix parameter
Added:
>
>
doScaling {bool} enable/disable pwa fit just for scaling (scaling parameter free; remaining parameter fixed)
 
contributionError {none} Calculate error of wave contribution in qa mode
evoIterations {int} Max number of iterations for evolutionary minimizer
evoPopulation {int} Population size for evolutionary minimizer
Revision 8
08 Jul 2014 - Main.JulianPychy
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Line: 52 to 52
 
orderInFile {string1} {string2} {string3} {string4} Order of the 4-vetor elements in input files: "Px Py Pz E" and "E Px Py Pz" are supported.
serializationFile {path} Path to serialization file (for qa, sdm modes)
name {string} Set a name that is attached to all output file names
Changed:
<
<
noOfDataEvents {value} Set number of data events for PWA- or QA-mode
>
>
noOfDataEvents {value} Set maximum number of data events for PWA- or QA-mode
 
paramFile {path} Path to file containing start parameters
pdgTableFile {path} Path of the pdg-table file, containing particle definitions and properties
preFactor {value} Set prefactor for an individual amplitude
Line: 104 to 104
 

Option Arguments Description
Changed:
<
<
serializationFile {path} The serialization file contains the error-matrix of the pwa result. This file is needed for error calculation.
>
>
serializationFile {path} The serialization file contains the covariance matrix of the pwa result. This file is needed for later error calculations.
 
contributionError {bool} Calculates the error of the total contribution and the individual contributions defined by the option "calcContribution". The --serializationFile argument needs to be set.
Changed:
<
<
calcContribution {name} withZeroAmp {string} {string} ... Calculates the number of events for the contribution "name" by setting the amplitudes... listed as arguments after the Keyword "withZeroAmp" to Zero. This should be the magnitudes and phi-angles of production amplitudes.
saveContributionHistos {bool} Generates an additional root-File with Histogramms for each contribution defined with the option "calcContribution" in the config-file. The name of the rootfile is composed by the general option "name" and the "name" of the contribution as set in the calcContribution option.
>
>
calcContribution {name} withZeroAmp {string} {string} ... Calculates the number of events for a part of the full amplitude (i.e. only for a certain resonance). This is done by setting all parameters that include {string} as a substring in their name to zero. The calculated contribution ist tagged with {name}.
saveContributionHistos {bool} Generates an additional root-File with histogramms for each contribution defined with the option "calcContribution" in the configuration file. The name of the rootfile is composed by the general option {name} and the {name} of the contribution as set in the calcContribution option.
 

-- JulianPychy - 03 Jul 2014
Revision 7
08 Jul 2014 - Main.JulianPychy
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Deleted:
<
<

Arguments to define the PWA model

 

Exactly one PWA application is provided for each individual reaction (e.g. pbarpReactionApp, epemReactionApp or .gammapReactionApp). The choice of the application mode, the definition of the decay trees and a lot of other parser options can be set by a configuration file. An example of such a configuration file can be found in the tutorial. All supported parser options are listed below:
Added:
>
>

Arguments required in the Command Line

The following arguments can not be used in the configuration file but only in the command line when running the respective application

Option Arguments Description

-c

--configFile

{path} Path to the configuration file

-C

--coupledChannelConfigFile

{path} Path to another configuration file for a coupled channel

Arguments to define the PWA model

 

Common

Line: 18 to 28
 
replaceParamSuffix {string1} {string2} Replace a part of a parameter name ({string1}) with {string2}. This option can be used to merge parameters.
replaceMassKey {particle name} {new name} Replace the name of a particle inside the Mass/Width parameter name. This option can be used to merge parameters.
useProductionBarrier {bool} Enable or disable barrier factors for the production system
Deleted:
<
<
unitInFile {string: GEV or MEV} Chosen unit in the ASCII input files
orderInFile {string1} {string2} {string3} {string4} Order of the 4-vetor elements in input files: "Px Py Pz E" and "E Px Py Pz" are supported.
 
massRange {min} {max} {particle1} {particle2} ... {particleN} Set mass interval for the invariant mass of particle1 particle2 ... particleN
Deleted:
<
<
noOfDataEvents {value} Set number of data events for PWA- or QA-mode
 
productionFormalism {string} Choose formalism for the production process: "Heli", "Cano" or "Tensor" are supported
Deleted:
<
<
errLogMode {string} Choose mode for error logger: "debug", "trace", "routine", "warning", "error" and "alert" are supported.
 
Changed:
<
<

Antiproton-proton-annihilation

>
>

Antiproton-Proton-Annihilation

 

Option Arguments Description
Line: 40 to 46
 
Option Arguments Description
datFile {path} Path to file containing data events
Added:
>
>
errLogMode {string} Choose mode for error logger: "debug", "trace", "routine", "warning", "error" and "alert" are supported.
 
mode {mode name} Set execution mode. See list of modes.
mcFile {path} Path to file containing monte carlo events
Added:
>
>
orderInFile {string1} {string2} {string3} {string4} Order of the 4-vetor elements in input files: "Px Py Pz E" and "E Px Py Pz" are supported.
 
serializationFile {path} Path to serialization file (for qa, sdm modes)
name {string} Set a name that is attached to all output file names
Added:
>
>
noOfDataEvents {value} Set number of data events for PWA- or QA-mode
 
paramFile {path} Path to file containing start parameters
Changed:
<
<
pdgTableFile {path} Path of the pdg-table file
ratioMcToData {value} Limit number of read monte carlo events by setting a ratio
>
>
pdgTableFile {path} Path of the pdg-table file, containing particle definitions and properties
 
preFactor {value} Set prefactor for an individual amplitude
Added:
>
>
ratioMcToData {value} Limit number of read monte carlo events by setting a ratio
unitInFile {string: GEV or MEV} Chosen unit in the ASCII input files
useEventWeight {bool} Read a (leading) weight for each set of four-vectors in the datFile (NOT mcFile currently)
 

Minimization

Line: 67 to 78
 
histAngles {particle name 1} from {particle name 1} {particle name 2} ... Create histogram of angles of particle 1 in the cms frame of (particle 1)+(particle 2)+...
histMass {particle name 1} {particle name 2} ... Create histogramm of the invariant mass of the specified particles
Changed:
<
<

Options for the client/server-mode

>
>

Options for the Client/Server-Mode

 

Option Arguments Description
Line: 75 to 86
 
serverPort {value} Port for server. Default is 22222
noOfClients {value} Number of clients the server expects
Changed:
<
<

Options for coupled channel mode

>
>

Options for Coupled Channel Mode

 

Option Arguments Description
clientNumberWeights {weight channel 1} {weight channel 2} ... Weights to assign the number of clients to the respective channels. If the option is not given the clients are auto-assigned. The weights become normalized so "clientNumberWeights = 0.2 0.8" is the same as "clientNumberWeights = 5 20"
Changed:
<
<

Options for event generator

>
>

Options for Event Generator

 

Option Arguments Description
Revision 6
07 Jul 2014 - Main.BertramKopf
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Arguments to define the PWA model

Changed:
<
<
Exactly one PWA application is provided for each individual reaction (e.g. pbarpReactionApp, epemReactionApp or .gammapReactionApp). The choice of the application mode, the definition of the decay trees and a lot of other parser options can be set by a configuration file. An example of such a configuration file can be found in the tutorial. All supported parser options are listed below:
>
>
Exactly one PWA application is provided for each individual reaction (e.g. pbarpReactionApp, epemReactionApp or .gammapReactionApp). The choice of the application mode, the definition of the decay trees and a lot of other parser options can be set by a configuration file. An example of such a configuration file can be found in the tutorial. All supported parser options are listed below:
 

Common

Revision 5
07 Jul 2014 - Main.BertramKopf
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Arguments to define the PWA model

Added:
>
>

Exactly one PWA application is provided for each individual reaction (e.g. pbarpReactionApp, epemReactionApp or .gammapReactionApp). The choice of the application mode, the definition of the decay trees and a lot of other parser options can be set by a configuration file. An example of such a configuration file can be found in the tutorial. All supported parser options are listed below:
 

Common

Line: 16 to 18
 
replaceParamSuffix {string1} {string2} Replace a part of a parameter name ({string1}) with {string2}. This option can be used to merge parameters.
replaceMassKey {particle name} {new name} Replace the name of a particle inside the Mass/Width parameter name. This option can be used to merge parameters.
useProductionBarrier {bool} Enable or disable barrier factors for the production system
Added:
>
>
unitInFile {string: GEV or MEV} Chosen unit in the ASCII input files
orderInFile {string1} {string2} {string3} {string4} Order of the 4-vetor elements in input files: "Px Py Pz E" and "E Px Py Pz" are supported.
massRange {min} {max} {particle1} {particle2} ... {particleN} Set mass interval for the invariant mass of particle1 particle2 ... particleN
noOfDataEvents {value} Set number of data events for PWA- or QA-mode
productionFormalism {string} Choose formalism for the production process: "Heli", "Cano" or "Tensor" are supported
errLogMode {string} Choose mode for error logger: "debug", "trace", "routine", "warning", "error" and "alert" are supported.
 

Antiproton-proton-annihilation

Line: 39 to 47
 
paramFile {path} Path to file containing start parameters
pdgTableFile {path} Path of the pdg-table file
ratioMcToData {value} Limit number of read monte carlo events by setting a ratio
Added:
>
>
preFactor {value} Set prefactor for an individual amplitude
 

Minimization

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

Parser arguments

Line: 8 to 8
 

Option Arguments Description
Changed:
<
<
finalStateParticle {name} Name of one final state particle. The order of final state particles in the configuration file has to be the same as in the data/monte carlo files
>
>
addDynamics {particle} {dynamic} [k-matrix configuration file] Adds a dynamic amplitude to the decay of a particle. When the k-matrix formalism is used a configuration file has to be given.
 
cloneParticle {particle1} {particle2} Create a new particle {particle2} in the particle table that has the same properties as particle {particle1}
Deleted:
<
<
production {particle1} {particle2} Adds the production of two particles to the amplitude
 
decay {formalism} [noiso] {particle1} To {particle2} {particle3} Adds the decay of particle1 to the amplitude using a certain spin formalism. The [noiso] option is optional and disables isospin couplings
Added:
>
>
finalStateParticle {name} Name of one final state particle. The order of final state particles in the configuration file has to be the same as in the data/monte carlo files
production {particle1} {particle2} Adds the production of two particles to the amplitude
replaceParamSuffix {string1} {string2} Replace a part of a parameter name ({string1}) with {string2}. This option can be used to merge parameters.
replaceMassKey {particle name} {new name} Replace the name of a particle inside the Mass/Width parameter name. This option can be used to merge parameters.
 
useProductionBarrier {bool} Enable or disable barrier factors for the production system
Changed:
<
<
addDynamics {particle} {dynamic} [k-matrix configuration file] Adds a dynamic to the decay of a particle. When the k-matrix formalism is used a configuration file has to be given.
>
>
 

Antiproton-proton-annihilation

Revision 3
04 Jul 2014 - Main.JulianPychy
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Revision 2
04 Jul 2014 - Main.JulianPychy
Line: 1 to 1
 
META TOPICPARENT name="PawianPwaSoftware"

Parser arguments

Arguments to define the PWA model

Common

Added:
>
>

Option Arguments Description
finalStateParticle {name} Name of one final state particle. The order of final state particles in the configuration file has to be the same as in the data/monte carlo files
cloneParticle {particle1} {particle2} Create a new particle {particle2} in the particle table that has the same properties as particle {particle1}
production {particle1} {particle2} Adds the production of two particles to the amplitude
decay {formalism} [noiso] {particle1} To {particle2} {particle3} Adds the decay of particle1 to the amplitude using a certain spin formalism. The [noiso] option is optional and disables isospin couplings
useProductionBarrier {bool} Enable or disable barrier factors for the production system
addDynamics {particle} {dynamic} [k-matrix configuration file] Adds a dynamic to the decay of a particle. When the k-matrix formalism is used a configuration file has to be given.
 

Antiproton-proton-annihilation

 
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)