BaBar GridPP Milestones

Objective 2 (labeled B):

Descriptive Name: Distributed Monte Carlo production system for BaBar using the GRID.

Purpose : To provide a distributed Monte Carlo production system capable of meeting the requirements of a 2 ab-1 B-factory using GRID LCG software and middleware to access BaBar and non-BaBar hardware.

Principal Client : BaBar Collaboration. Successful Objective : All BaBar UK simulation production to use the production system on BaBar and non-BaBar hardware.

Secondary objective: Take-up by the non-UK community of BaBar.

High Level Risks:

1. LCG infrastructure outside our control.
2. Middleware reliability.
3. Divergence of US and European GRID middleware.
4. Running at non-BaBar sites requires elimination of Objectivity as the database. Scheduled for removal Q4 2005.

Deliverables:

1. Official BaBar production of simulated events using core LCG components on 2 or more BaBar UK Tier 2 sites.
   (end Q2 2005)
   Metric: 2 million events per week per 100 cpus.
   1. Breakdown of the current BaBar Monte Carlo Production System into modules and identification of replacement GRID components. Identification of synergies with other groups e.g. Italy
      (end Q1 2005)
      (Metric: document)
   2. Install necessary LCG GRID software on one BaBar UK Tier 2 farm.
      (end Q1 2005)
      (Metric: successful submission/retrieval of simple jobs).
   3. (end Q2 2005)
      Convert the current Globus/VDT system to use minimal LCG and BaBar VO on one BaBar UK Tier 2.
      (Metric: acceptance and official BaBar validation of the generated events).
   4. (end Q2 2005)
      Rollout the minimal LCG system on 2 or more BaBar UK Tier 2 sites.
      (Metric: Successful production of 2 million events per week per 100 cpus).
2. (end Q4 2005)
   Official BaBar production of simulated events using core LCG components on all participating BaBar UK Tier 2 sites and testing on non-BaBar UK Tier 2 site.
   (Metric: 1 million events per week per site.)
   1. (end Q3 2005)
      Install necessary LCG GRID software on all participating BaBar UK Tier 2 farms. Implement monitoring of sites.
      (Metric: job submission and monitoring are working).
   2. (end Q3 2005)
      Rollout the minimal LCG system onto all participating BaBar UK Tier 2 sites.
      (Metric: Successful production of 1 million events per week per site)
   3. (end Q3 2005)
      Assess experience with LCG and identify problems/improvements. Plan for replacement of Objectivity Database (due to be implemented around this time). Plan use of full LCG functionality
      (metric: Review and planning documents)
   4. (end Q4 2005)
      Identify one non-BaBar UK Tier 1 or 2 test site resource. Install BaBar software. Run MC generation.
      (metric: successful official generation of events, aim for 2 M/week/100 cpus).
3. (end Q2 2006) Official BaBar production of simulated events using enhanced LCG at one or more non-BaBar UK Tier 2 site.
   (Metric: 1 million events per week at non-BaBar UK Tier 2.)
   1. (end Q1 2006)
      Automate the updating of conditions and configurations at sites running MC production using GRID tools.
      (Metric: release of meta-data distribution tool.)
   2. (end Q1 2006)
      Documentation, guidelines, instructions and packaging of code for production at non-BaBar UK Tier 1 or 2 resource.
      (metric: documentation, successful reinstallation following guidelines)
   3. (end Q2 2006)
      Roll out production to a non-BaBar UK Tier 2 site (e.g. SouthGrid).
      (metric: successful official generation of events, aim for 2 million per week per 100 cpus).
   4. (end Q2 2006)
      Implementation of first tranche of non-core elements of LCG as defined in deliverable B2.3. Primarily the RB and load balancing
      (metric: implementation in official production).
4. (end Q4 2006) Official BaBar production of simulated events using all LCG features at all accessible UK GRID resources.
   (Metric: efficient production (90%) with numbers dependent on resources).
   1. (end Q3 2006)
      Assess stability of production, identify problems and report back to BaBar/LCG.
      (metric: review and documentation of problems, efficiency etc…).
   2. (end Q3 2006)
      Further implementation of non-core elements of LCG (e.g. Resource Broker etc…).
      (metric: implementation in official production).
   3. (end Q4 2006)
      Roll out production to as many non-BaBar UK Tier 2 sites as possible.
      (metric: successful official generation of events, aim for 2 million per week per 100 cpus).
   4. (end Q4 2006)
      Assessment of current situation in US with view to using US resources.
      (metric: ongoing discussions, possible MOU, planning document).
   5. (end Q4 2006)
      Depending on BaBar computing plan, implement multi-point distribution of MC output direct to Tier 1 sites rather than only to SLAC.
      (metric: implementation of data distribution framework).
5. (end Q2 2007) Official BaBar production of simulated events at all available European and some US GRID sites.
   (Metric: Take up of production by sites aiming for 1 million events per week per 25 cpus.)
   1. (end Q1 2007)
      Full use of LCG features at BaBar and non-BaBar specific sites.
      (metric: assessment via review document).
   2. (end Q2 2007)
      Implementation of production at non-UK LCG sites wherever possible.
      (metric: increasing production and partnerships with other sites).
   3. (end Q2 2007)
      Implementation of production at US sites wherever possible.
      (metric: either successful running at one or more US LCG sites or specification design of US non-LCG production).
6. (end Q3 2007)
   Production at all available US GRID sites using LCG or non-LCG GRID software
   (metric: uptake of production by all contributing US sites at for 1 million events per week per 25 cpus.)
   1. (end Q3 2007)
      Depending on deliverable A5.3, integration of non-LCG requirements for running at US sites.
      (metric: successful running at one or more US sites).
   2. (end Q3 2007)
      Full documentation, instructions and review of project.
      (Metric: documentation).