J 4.1 BaBar     Status Date 01-Apr-08     90 days
Owner: Fergus Wilson
Number Title Due Date Status Links More…
1 4.1.1 A1: Assessment of BaBar requirements for data analysis over the next 3 years  01-Jan-05 Complete I  
I
Metric  Assessment Document                
Risk/Dep   [1]                  
History   [2]                  
2 4.1.2 A2:  Data analysis using a BaBar physics topic using currently available GRID infrastructure.  01-Jul-05 Complete I  
I
Metric  Analysis pf 100 fb-1        
Risk/Dep   [3]                  
History   [4]                  
3 4.1.3 A3: Distributed analysis possible at all participating BaBar Tier 1 and 2 sites.  01-Jan-06 Complete I  
I
Metric  Successful distribution of analysis of 200 fb-1 among BaBar UK Tier 2.        
Risk/Dep                     
History                     
4 4.1.4 A4: Transition to full LCG infrastructure for analysis at all participating BaBar UK sites  01-Jul-06 Complete    
I But Manchester is only participating UK site
Metric  Ability to complete analysis at non-BaBar UK site        
Risk/Dep                     
History                     
5 4.1.5 Design and code new Task Manger software to enable BaBAr skimming on the Grid" 01-Sep-07 Complete    
I
Metric  Multiple users performing multiple analyses at multiple sites            
Risk/Dep                     
History  ChangeForm1                  
6 4.1.6 "Run large scale skim production at Manchester Tier 2" 14-May-07 Complete    
I Ran 37,703 jobs in 6 months with 93.6% effiency (email Bailey via Barlow 1/10/07)
Metric  One month of continuous skimming using at least 200 machines with 90% efficiency and maximum 48 hour latency            
Risk/Dep                     
History  ChangeForm1                  
7 4.1.7 B1: Official BaBar production of simulated events using core LCG components on 2 or more BaBar UK Tier 2 sites.  01-Jul-05 Complete I I
I
Metric  2 million events per week per 100 cpus.            
Risk/Dep                     
History                     
8 4.1.8 B2: 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 01-Jan-06 Complete I  
I
Metric  1 million events per week per site.            
Risk/Dep                     
History                     
9 4.1.9 B3: Official BaBar production of simulated events using enhanced LCG at one or more non-BaBar UK Tier 2 site   In Progress    
I According to 07Q3 this is substantially complete
Metric  1 million events per week at non-BaBar UK Tier 2.            
Risk/Dep                     
History  ChangeForm1                  
10 4.1.10 B4: Official BaBar production of simulated events using all LCG features at all accessible UK GRID resources.   In Progress    
I According to 07Q3 this is substantially complete
Metric  Efficient production (90%) with numbers dependent on resources            
Risk/Dep                     
History  ChangeForm1                  
11 4.1.11 B5: Official BaBar production of simulated events at all available European and some US GRID sites   Not Started    
I According to 07Q3 this is substantially complete
Metric  Take up of production by sites aiming for 1 million events per week per 25 cpus.            
Risk/Dep                     
History  ChangeForm1                  
12 4.1.12 B6: Production at all available US GRID sites using LCG or non-LCG GRID software    Not Started    
I According to 07Q3 this is substantially complete
Metric  Uptake of production by all contributing US sites at for 1 million events per week per 25 cpus.            
Risk/Dep                     
History  ChangeForm1                  
13 4.1.13          
I
Metric               
Risk/Dep                     
History                     
14 4.1.14          
I
Metric               
Risk/Dep                     
History                     
15 4.1.15          
I
Metric               
Risk/Dep                     
History                     
Link to Deliverable A1.1
Link to Something
[1]
Fill this in with code from Risk Register or use comments to note particular risks or dependencies
[2]
Links to ChangeForms if necessary
[3]
Fill this in with code from Risk Register or use comments to note particular risks or dependencies
[4]
Links to ChangeForms if necessary