Difference: DIRACProductionManagement (3 vs. 4)

Revision 42009-02-18 - AndreiTsaregorodtsev

Line: 1 to 1
 
META TOPICPARENT name="DiracProject"
-- AndreiTsaregorodtsev - 17 Nov 2008

DIRAC Production Management

Line: 7 to 7
 

Workflow Framework

Changed:
<
<
The Workflow Framework provides a mechanism to describe sequences of execution units of arbitrary complexity. The execution units in the Workflow Framework are called Modules.
>
>
The Workflow Framework provides a mechanism to describe sequences of execution units of arbitrary complexity. The execution units in the Workflow Framework are called Modules.
 The Modules can be combined in Steps. Steps can be combined in complex sequences forming an execution DAG.

Production Template

Added:
>
>
The Production Template defines the workflow of LHCb production jobs using the Workflow Framework. It is a generic description of one class of production jobs. Several Production Templates cover all the possible LHCb productions. Combined with the parameters provided with the Production Request, the Production Template forms the Production Workflow which is a full description of the LHCb applications that are executed in the production runs.

 Each Step in the LHCb production procedure is created to execute one Application together with possible auxiliary modules to verify the Application software and results of the Application execution. The final Job Finalization Step takes care of the Job results bookkeeping, data uploading and creating any failover requests as needed.

Production Request

Production Request is an object which allows to capture the details of a user request to produce a set of data. It also serves as a token allowing the user to follow the progress of the request execution and to navigate to the corresponding production information.

Changed:
<
<
To be expanded
>
>
Production Request is composed of the following parametes:

  • ID and a Name
  • Identity of the requestor
  • Creation Date
  • Priority
  • Type
  • Simulation Conditions or Data Taking Conditions ( depending on the Type of the Request )
  • Processing Pass specifying the details of the Applications to be used
  • Event Type
  • Input Data specification In case of Data Processing requests

The Production Request is supposed to be created by Physics coordinators. The creation is followed by validation, testing and final approval by the LHCb Production Manager. After the Production Request is validated, the corresponding Production is created and put into operation. The Production Request monitor allow users to follow the progress of execution of the corresponding Productions.

 

Production

Production is a logical object which encapsulates all the necessary information necessary to create a workload corresponding to a Production Request. The workload is created as a number of jobs associated with the Production. Each job has a full set of parameters necessary for its execution, including the Application Workflow, input data, etc.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback