Commit b2cb7b97 authored by Pawel Sznajder's avatar Pawel Sznajder
Browse files

Update scenarios #28, #30

Update .cproject by adding NumA dependence 
parent c84d3fd2
......@@ -5,16 +5,16 @@
<storageModule buildSystemId="org.eclipse.cdt.managedbuilder.core.configurationDataProvider" id="cdt.managedbuild.config.gnu.exe.release.1310068718" moduleId="org.eclipse.cdt.core.settings" name="Release">
<externalSettings/>
<extensions>
<extension id="org.eclipse.cdt.core.ELF" point="org.eclipse.cdt.core.BinaryParser"/>
<extension id="org.eclipse.cdt.core.GASErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
<extension id="org.eclipse.cdt.core.GmakeErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
<extension id="org.eclipse.cdt.core.GLDErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
<extension id="org.eclipse.cdt.core.CWDLocator" point="org.eclipse.cdt.core.ErrorParser"/>
<extension id="org.eclipse.cdt.core.GCCErrorParser" point="org.eclipse.cdt.core.ErrorParser"/>
<extension id="org.eclipse.cdt.core.ELF" point="org.eclipse.cdt.core.BinaryParser"/>
</extensions>
</storageModule>
<storageModule moduleId="cdtBuildSystem" version="4.0.0">
<configuration artifactName="${ProjName}" buildArtefactType="org.eclipse.cdt.build.core.buildArtefactType.exe" buildProperties="org.eclipse.cdt.build.core.buildArtefactType=org.eclipse.cdt.build.core.buildArtefactType.exe,org.eclipse.cdt.build.core.buildType=org.eclipse.cdt.build.core.buildType.release" cleanCommand="rm -rf" description="" id="cdt.managedbuild.config.gnu.exe.release.1310068718" name="Release" parent="cdt.managedbuild.config.gnu.exe.release">
<configuration artifactName="${ProjName}" buildArtefactType="org.eclipse.cdt.build.core.buildArtefactType.exe" buildProperties="org.eclipse.cdt.build.core.buildType=org.eclipse.cdt.build.core.buildType.release,org.eclipse.cdt.build.core.buildArtefactType=org.eclipse.cdt.build.core.buildArtefactType.exe" cleanCommand="rm -rf" description="" id="cdt.managedbuild.config.gnu.exe.release.1310068718" name="Release" parent="cdt.managedbuild.config.gnu.exe.release">
<folderInfo id="cdt.managedbuild.config.gnu.exe.release.1310068718." name="/" resourcePath="">
<toolChain id="cdt.managedbuild.toolchain.gnu.exe.release.797122068" name="Linux GCC" superClass="cdt.managedbuild.toolchain.gnu.exe.release">
<targetPlatform id="cdt.managedbuild.target.gnu.platform.exe.release.1132366596" name="Debug Platform" superClass="cdt.managedbuild.target.gnu.platform.exe.release"/>
......@@ -27,6 +27,7 @@
<listOptionValue builtIn="false" value="&quot;${workspace_loc:/PARTONS/include}&quot;"/>
<listOptionValue builtIn="false" value="&quot;${QT_INCLUDE_DIR}&quot;"/>
<listOptionValue builtIn="false" value="&quot;${workspace_loc:/ElementaryUtils/include}&quot;"/>
<listOptionValue builtIn="false" value="&quot;${workspace_loc:/NumA++/include}&quot;"/>
</option>
<inputType id="cdt.managedbuild.tool.gnu.cpp.compiler.input.225668457" superClass="cdt.managedbuild.tool.gnu.cpp.compiler.input"/>
</tool>
......
0.1763E00|-0.1346E00|1.3651E+00|1.0000E+01
0.1763E00|-0.1346E00|1.3651E+00|2.0000E+01
0.1763E00|-0.1346E00|1.3651E+00|3.0000E+01
0.1763E00|-0.1346E00|1.3651E+00|4.0000E+01
0.1763E00|-0.1346E00|1.3651E+00|5.0000E+01
0.1763E00|-0.1346E00|1.3651E+00|6.0000E+01
0.1763E00|-0.1346E00|1.3651E+00|7.0000E+01
0.1763E00|-0.1346E00|1.3651E+00|8.0000E+01
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario demonstrates how to change the integration routine in one of modules. To make it possible, the module must inherit from MathIntegratorModule class (our doxygen documentation will tell you that).
Be careful when you perform this operation. Some integration routines may speed up computations, but at the same time they can be not accurate enough to be applied in some kinematic ranges (e.g. in low xB). The infinities are also treated differently by various integration routines (or they are not treated at all).
This scenario is the demonstration for GPD module. Note however that the way of changing the integration routine that is presented here is applicable to any type of PARTONS module.
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="Change integration routine example">
<!-- First task: evaluate GPD model for a single kinematics -->
<!-- Indicate service and its methods to be used and indicate if the result should be stored in the database -->
<task service="GPDService" method="computeGPDModel" storeInDB="0">
<!-- Define GPD kinematics -->
<kinematics type="GPDKinematic">
<param name="x" value="0.1" />
<param name="xi" value="0.2" />
<param name="t" value="-0.1" />
<param name="MuF2" value="2." />
<param name="MuR2" value="2." />
</kinematics>
<!-- Define physics assumptions -->
<computation_configuration>
<!-- Select GPD model -->
<module type="GPDModule" name="GPDMMS13">
<!-- Change integration routine -->
<param name="integrator_type" value="GK21_ADAPTIVE" />
</module>
</computation_configuration>
</task>
<!-- Second task: print results of the last computation into standard ouput -->
<task service="GPDService" method="printResults">
</task>
</scenario>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario demonstrates the evaluation of DVCS Compton Form Factors (CFF) for kinematics defined in a text file. In this file kinematic points are encoded in separate lines using the following format: "xi|t|MuF2|MuR2|Q2". The result of this scenario is printed out to the standard output. These are CFF values for all GPD types defined in the selected GPD model.
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="DVCS CFF evaluation for many kinematics example">
<!-- First task: evaluate DVCS CFF for a single kinematics -->
<!-- Indicate service and its methods to be used and indicate if the result should be stored in the database -->
<task service="ConvolCoeffFunctionService" method="computeManyKinematicOneModel" storeInDB="0">
<!-- Define DVCS CFF kinematics -->
<kinematics type="DVCSConvolCoeffFunctionKinematic">
<!-- Path to file defining kinematics -->
<param name="file" value="/home/partons/git/partons-example/bin/examples/kinematics_dvcs_cff.csv" />
</kinematics>
<!-- Define physics assumptions -->
<computation_configuration>
<!-- Select DVCS CFF model -->
<module type="ConvolCoeffFunctionModule" name="DVCSCFFStandard">
<!-- Indicate pQCD order of calculation -->
<param name="qcd_order_type" value="LO" />
<!-- Select GPD model -->
<module type="GPDModule" name="GPDMMS13">
</module>
</module>
</computation_configuration>
</task>
<!-- Second task: print results of the last computation into standard output -->
<task service="ConvolCoeffFunctionService" method="printResults">
</task>
</scenario>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario demonstrates the evaluation of DVCS observable for kinematics defined in a text file. In this file kinematic points are encoded in separate lines using the following format: "xB|t|Q2|phi|E". The result of this scenario is printed out to the standard output.
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="DVCS observable for many kinematics evaluation example">
<!-- First task: evaluate DVCS observable for a single kinematics -->
<!-- Indicate service and its methods to be used and indicate if the result should be stored in the database -->
<task service="ObservableService" method="computeManyKinematicOneModel" storeInDB="0">
<!-- Define DVCS observable kinematics -->
<kinematics type="ObservableKinematic">
<!-- Path to file defining kinematics -->
<param name="file" value="/home/partons/git/partons-example/bin/examples/kinematics_dvcs_observable.csv" />
</kinematics>
<!-- Define physics assumptions -->
<computation_configuration>
<!-- Select DVCS observable -->
<module type="Observable" name="DVCSAllMinus">
<!-- Select DVCS process model -->
<module type="ProcessModule" name="DVCSProcessGV08">
<!-- Select scales module -->
<!-- (it is used to evaluate factorization and renormalization scales out of kinematics) -->
<module type="ScalesModule" name="ScalesQ2Multiplier">
<!-- Configure this module -->
<param name="lambda" value="1." />
</module>
<!-- Select xi-converter module -->
<!-- (it is used to evaluate GPD variable xi out of kinematics) -->
<module type="XiConverterModule" name="XiConverterXBToXi">
</module>
<!-- Select DVCS CFF model -->
<module type="ConvolCoeffFunctionModule" name="DVCSCFFStandard">
<!-- Indicate pQCD order of calculation -->
<param name="qcd_order_type" value="NLO" />
<!-- Select GPD model -->
<module type="GPDModule" name="GPDMMS13">
</module>
</module>
</module>
</module>
</computation_configuration>
</task>
<!-- Second task: print results of the last computation into standard output -->
<task service="ObservableService" method="printResults">
</task>
</scenario>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario demonstrates the evaluation of GPD model for kinematics defined in a text file. In this file kinematic points are encoded in separate lines using the following format: "x|xi|t|MuF2|MuR2". The result of this scenario is printed out to the standard output. These are the values for all defined in the model GPDs, including singlet and non-singlet combinations for quarks.
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="GPD evaluation for many kinematics example">
<!-- First task: evaluate GPD model for a single kinematics -->
<!-- Indicate service and its methods to be used and indicate if the result should be stored in the database -->
<task service="GPDService" method="computeManyKinematicOneModel" storeInDB="0">
<!-- Define GPD kinematics -->
<kinematics type="GPDKinematic">
<!-- Path to file defining kinematics -->
<param name="file" value="/home/partons/git/partons-example/bin/examples/kinematics_gpd.csv" />
</kinematics>
<!-- Define physics assumptions -->
<computation_configuration>
<!-- Select GPD model -->
<module type="GPDModule" name="GPDMMS13">
</module>
</computation_configuration>
</task>
<!-- Second task: print results of the last computation into standard output -->
<task service="GPDService" method="printResults">
</task>
</scenario>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<scenario date="2016-11-30"
description="Example : compute one kinematic with one convol coeff function model (DVCSCFF) at LO with GPD model (MMS13)">
<task service="ConvolCoeffFunctionService" method="computeWithGPDModel">
<kinematics type="DVCSConvolCoeffFunctionKinematic">
<param name="xi" value="0.0088933952793878" />
<param name="t" value="-0.1346" />
<param name="Q2" value="1.5557" />
<param name="MuF2" value="4" />
<param name="MuR2" value="4" />
</kinematics>
<computation_configuration>
<module type="ConvolCoeffFunctionModule" name="DVCSCFFModel">
<param name="qcd_order_type" value="LO" />
<module type="GPDModule" name="MMS13Model" />
</module>
</computation_configuration>
</task>
<task service="ConvolCoeffFunctionService" method="printResults">
</task>
</scenario>
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<scenario date="2016-11-30"
description="Example : compute an observable with one kinematic">
<task service="ObservableService" method="computeObservable">
<kinematics type="ObservableKinematic">
<param name="xB" value="0.1763" />
<param name="t" value="-0.1346" />
<param name="Q2" value="1.3651" />
</kinematics>
<computation_configuration>
<module type="Observable" name="AcCos2phi">
<module type="ProcessModule" name="GV2008Model">
<param name="beam_energy" value="5.77" />
<module type="ScaleModule" name="Q2Multiplier">
<param name="lambda" value="1" />
</module>
<module type="XiConverterModule" name="XBToXi" />
<module type="ConvolCoeffFunctionModule"
name="DVCSCFFModel">
<param name="qcd_order_type" value="LO" />
<module type="GPDModule" name="MMS13Model" />
</module>
</module>
</module>
</computation_configuration>
</task>
<task service="ObservableService" method="printResults">
</task>
</scenario>
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<scenario date="2016-04-14" description="How to compute an observable">
<task service="ObservableService" method="computeManyKinematicOneModel">
<kinematics type="ObservableKinematic">
<param name="file"
value="/home/debian/workspace/PARTONS_release/bin/examples/Observable_kinematics.csv" />
</kinematics>
<computation_configuration>
<module type="Observable" name="Alu">
<module type="ProcessModule" name="GV2008Model">
<param name="beam_energy" value="5.77" />
<module type="ScaleModule" name="Q2Multiplier">
<param name="lambda" value="1" />
</module>
<module type="XiConverterModule" name="XBToXi" />
<module type="ConvolCoeffFunctionModule"
name="DVCSCFFModel">
<param name="qcd_order_type" value="LO" />
<module type="GPDModule" name="MMS13Model" />
</module>
</module>
</module>
</computation_configuration>
</task>
<task service="ObservableService" method="printResults">
</task>
</scenario>
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<scenario date="2016-11-30"
description="Example : compute one kinematic with one GPD model (MMS13Model)">
<task service="GPDService" method="computeGPDModel">
<kinematics type="GPDKinematic">
<param name="x" value="-0.99" />
<param name="xi" value="0.99" />
<param name="t" value="0" />
<param name="MuF2" value="1" />
<param name="MuR2" value="1" />
</kinematics>
<computation_configuration>
<module type="GPDModule" name="MMS13Model" />
</computation_configuration>
</task>
<task service="GPDService" method="printResults">
</task>
</scenario>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario demonstrates a simple task as the evaluation of DVCS Compton Form Factors (CFF) in a single kinematic point. The result of this scenario is printed out to the standard output. These are CFF values for all GPD types defined in the selected GPD model.
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="DVCS CFF evaluation for single kinematics example">
<!-- First task: evaluate DVCS CFF for a single kinematics -->
<!-- Indicate service and its methods to be used and indicate if the result should be stored in the database -->
<task service="ConvolCoeffFunctionService" method="computeWithGPDModel" storeInDB="0">
<!-- Define DVCS CFF kinematics -->
<kinematics type="DVCSConvolCoeffFunctionKinematic">
<param name="xi" value="0.01" />
<param name="t" value="-0.1" />
<param name="Q2" value="4." />
<param name="MuF2" value="4." />
<param name="MuR2" value="4." />
</kinematics>
<!-- Define physics assumptions -->
<computation_configuration>
<!-- Select DVCS CFF model -->
<module type="ConvolCoeffFunctionModule" name="DVCSCFFStandard">
<!-- Indicate pQCD order of calculation -->
<param name="qcd_order_type" value="LO" />
<!-- Select GPD model -->
<module type="GPDModule" name="GPDMMS13">
</module>
</module>
</computation_configuration>
</task>
<!-- Second task: print results of the last computation into standard output -->
<task service="ConvolCoeffFunctionService" method="printResults">
</task>
</scenario>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario demonstrates a simple task as the evaluation of DVCS observable in a single kinematic point. The result of this scenario is printed out to the standard output.
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="DVCS observable evaluation for single kinematics example">
<!-- First task: evaluate DVCS observable for a single kinematics -->
<!-- Indicate service and its methods to be used and indicate if the result should be stored in the database -->
<task service="ObservableService" method="computeObservable" storeInDB="0">
<!-- Define DVCS observable kinematics -->
<kinematics type="ObservableKinematic">
<param name="xB" value="0.2" />
<param name="t" value="-0.1" />
<param name="Q2" value="2." />
<param name="E" value="6." />
</kinematics>
<!-- Define physics assumptions -->
<computation_configuration>
<!-- Select DVCS observable -->
<module type="Observable" name="DVCSAllMinus">
<!-- Select DVCS process model -->
<module type="ProcessModule" name="DVCSProcessGV08">
<!-- Select scales module -->
<!-- (it is used to evaluate factorization and renormalization scales out of kinematics) -->
<module type="ScalesModule" name="ScalesQ2Multiplier">
<!-- Configure this module -->
<param name="lambda" value="1." />
</module>
<!-- Select xi-converter module -->
<!-- (it is used to evaluate GPD variable xi out of kinematics) -->
<module type="XiConverterModule" name="XiConverterXBToXi">
</module>
<!-- Select DVCS CFF model -->
<module type="ConvolCoeffFunctionModule" name="DVCSCFFStandard">
<!-- Indicate pQCD order of calculation -->
<param name="qcd_order_type" value="NLO" />
<!-- Select GPD model -->
<module type="GPDModule" name="GPDMMS13">
</module>
</module>
</module>
</module>
</computation_configuration>
</task>
<!-- Second task: print results of the last computation into standard output -->
<task service="ObservableService" method="printResults">
</task>
</scenario>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario demonstrates a simple task as the evaluation of GPD model in a single kinematic point. The result of this scenario is printed out to the standard output. These are the values for all defined in the model GPDs, including singlet and non-singlet combinations for quarks.
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="GPD evaluation for single kinematics example">
<!-- First task: evaluate GPD model for a single kinematics -->
<!-- Indicate service and its methods to be used and indicate if the result should be stored in the database -->
<task service="GPDService" method="computeGPDModel" storeInDB="0">
<!-- Define GPD kinematics -->
<kinematics type="GPDKinematic">
<param name="x" value="0.1" />
<param name="xi" value="0.2" />
<param name="t" value="-0.1" />
<param name="MuF2" value="2." />
<param name="MuR2" value="2." />
</kinematics>
<!-- Define physics assumptions -->
<computation_configuration>
<!-- Select GPD model -->
<module type="GPDModule" name="GPDMMS13">
</module>
</computation_configuration>
</task>
<!-- Second task: print results of the last computation into standard output -->
<task service="GPDService" method="printResults">
</task>
</scenario>
0.2|-0.1|2.|2.|2.
0.3|-0.1|2.|2.|2.
0.1|-0.1|2.|20.|6.
0.2|-0.1|2.|20.|6.
0.1|0.2|-0.1|2.|2.
0.2|0.2|-0.1|2.|2.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!--
This scenario illustrates how to select specific data from the database and write them to a file to be used e.g. for plotting purposes. To run this task you must first fill the database with some results. You can run for instance computeManyKinematicsForGPD.xml scenario with storeInDB="1". After the successful insertion PARTONS returns to the standard output unique computation_id, which you should use whenever needed to refer the inserted data.
This scenario uses generatePlotFile task, which defines SELECT...WHERE... SQL-like query. You can play with the following variables:
=====================================================================================================================
Name Description Type Possible values
=====================================================================================================================
x GPD kinematics x double
xi GPD kinematics xi double
t GPD kinematics t double
MuF2 GPD kinematics MuF2 double
MuR2 GPD kinematics MuR2 double
quark_distribution GPD value for specific quark double
quark_distribution_plus GPD singlet value for specific quark double
quark_distribution_minus GPD non-singlet value for specific quark double
gluon_distribution_value GPD value for gluons double
computation_id Unique id of related computation integer
computation_module_name Name of GPD module used in computation char string
gpd_type_short_name GPD type char string H, E, etc. see GPDType::Type
quark_flavor_short_name Quark flavor char string u, d, etc. see QuarkFlavor::Type
=====================================================================================================================
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="Get GPD result from database">
<!-- Task: generate file with data matching indicated criteria -->
<task service="GPDService" method="generatePlotFile">
<!-- Variables selected to be stored in the output file -->
<task_param type="select">
<param name="xPlot" value="x" />
<param name="yPlot" value="quark_distribution" />
</task_param>
<!-- Applied requirements -->
<task_param type="where">
<param name="computation_id" value="1" />
<param name="gpd_type_short_name" value="H" />
<param name="quark_flavor_short_name" value="u" />
</task_param>
<!-- Path to the output file -->
<task_param type="output">
<param name="filePath" value="output.dat" />
</task_param>
</task>
</scenario>
#include <ElementaryUtils/logger/LoggerManager.h>
#include <ElementaryUtils/parameters/Parameter.h>
#include <ElementaryUtils/parameters/Parameters.h>
#include <NumA/integration/one_dimension/IntegratorType1D.h>
#include <partons/beans/convol_coeff_function/DVCS/DVCSConvolCoeffFunctionKinematic.h>
#include <partons/beans/convol_coeff_function/DVCS/DVCSConvolCoeffFunctionResult.h>