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 -->
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 -->
<scenariodate="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 -->
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 -->
<scenariodate="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 -->
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 -->
<scenariodate="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 -->
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 -->
<scenariodate="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 -->
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 -->
<scenariodate="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 -->
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 -->
<scenariodate="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 -->
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:
