Commit 93c1b91d authored by Pawel Sznajder's avatar Pawel Sznajder
Browse files

Add new scenarios for extracting data from DB

Reorganize scenarios
parent 01e98f70
<?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 computeManyKinematicsForDVCSComptonFormFactor.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
===============================================================================================================================
xi CFF kinematics xi double
t CFF kinematics t double
MuF2 CFF kinematics MuF2 double
MuR2 CFF kinematics MuR2 double
Q2 CFF kinematics Q2 double
real_part CFF value real part double
img_part CFF singlet imaginary part double
computation_id Unique id of related computation integer
computation_module_name Name of CFF module used in computation char string
gpd_type_short_name GPD type char string H, E, etc. see GPDType::Type
observable_channel_short_name Channel type char string DVCS, HEMP, see ObservableChannel::Type
===============================================================================================================================
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="Get CFF result from database">
<!-- Task: generate file with data matching indicated criteria -->
<task service="ConvolCoeffFunctionService" method="generatePlotFile">
<!-- Variables selected to be stored in the output file -->
<task_param type="select">
<param name="xPlot" value="xi" />
<param name="yPlot" value="real_part" />
</task_param>
<!-- Applied requirements -->
<task_param type="where">
<param name="computation_id" value="1" />
<param name="gpd_type_short_name" value="H" />
</task_param>
<!-- Path to the output file -->
<task_param type="output">
<param name="filePath" value="output.dat" />
</task_param>
</task>
</scenario>
<?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 computeManyKinematicsForDVCSObservable.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
====================================================================================================================================
xB observable kinematics xB double
t observable kinematics t double
Q2 observable kinematics Q2 double
E observable kinematics E double
phi observable kinematics phi double
observable_value observable value double
computation_id Unique id of related computation integer
computation_module_name Name of observable module used in computation char string
observable_name Observable name (should be the same as computation_module_name) char string
====================================================================================================================================
-->
<!-- Scenario starts here -->
<!-- For your convenience and for bookkeeping provide creation date and unique description -->
<scenario date="2017-07-18" description="Get observable result from database">
<!-- Task: generate file with data matching indicated criteria -->
<task service="ObservableService" method="generatePlotFile">
<!-- Variables selected to be stored in the output file -->
<task_param type="select">
<param name="xPlot" value="xB" />
<param name="yPlot" value="observable_value" />
</task_param>
<!-- Applied requirements -->
<task_param type="where">
<param name="computation_id" value="1" />
<param name="observable_name" value="DVCSAllMinus" />
</task_param>
<!-- Path to the output file -->
<task_param type="output">
<param name="filePath" value="output.dat" />
</task_param>
</task>
</scenario>
......@@ -25,8 +25,8 @@ computation.nb.processor = 1
xml.schema.file.path = ../partons/data/automation/xmlSchema.xsd
# Temporary working directory
temporary.working.directory.path = bin/tmp
temporary.working.directory.path = /home/partons/git/partons-example/bin/tmp
gpd.service.batch.size = 10000
ccf.service.batch.size = 1000
observable.service.batch.size = 1000
\ No newline at end of file
observable.service.batch.size = 1000
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment