1. data-coordinator report Lian-You SHAN ACC15 Jan 9, 2010, IHEP

2. Outline  T3 resources  Data quality (DQ) aware analyses

3. T3 resources  Two UI &128 CPU  40 for MC queue & 80 for analyses  Good batch jobs of V15.6.1 on V14.x MC from T2  80 T storage  1T Data0 for frequent backup  Data1 (Calo)& data2 (Muon) public real data  Data3 private real data  Data4 public MonteCarlo samples  Data5 private MC samples  Please DO NOT abuse disks ErMing’s tallk 4 details

4. Known data on T3  Via T2 ( dpns-ls /dpm/ihep.ac.cn/home/atlas )  Real data in atlasdatadisk  MuonswBeam, L1CaloEM …  data09_900GeV, data09_2TeV AOD (DESD)  Geome/condit tags ?  MonteCarlo samples in atlasmcdisk  topmix-0108175-electron is still missing  mc09_7TeV for W/Z,top ( & mc08_10TeV samples ? )  AMI check w/ time&energy  Eric Lancon ? Thanks to L.W. YAO

5. Known data on T3(ctd)  On local disks  data1/public  zhangdl, wanghl, MC…  DY, Zmumu, tau, Wtau…  Haven’t V12 recon || 14TeV samples obsolete ?  data2  baiy, yuanl, zhanghq, ruanxf, zhanzc  data4/data5  data4 for common/big backgrounds (W/Z, top … )  Data5 for your signal/special BCKG  physics channel name for continuance, e.g. WZ, RPV, ttH ? Would you please try DPD ?

6. DQ aware analyses  A report from Dec’09 Atlas PP meeting  More data than physics/analyses  Readiness papers  DD backgrounds analysis  Sub systems w/ data  Trigger, performance …  Data quality  Analyses aware of data quality How can we involve in these HOT scene ?!

7. Data quality (offline)  Assigned per lumi-block ( not trigger aware )  situations of main detectors, trigger … in ~60s  Also qualities from combined performance Grp  Physics working Grp can refine their own DQ  Release of DQ flags  5-color traffic light flags  Stored mainly in condition DB (COOL)  Also in (d)AOD via meta-data  Evolution/update with months duration  Controlled by DQ Grp ( good-run list = GRL )

8. Analyses aware of DQ  Understanding the DQ flags  DQ work/contribution are also welcome  Possible re-define the good-run list  Access DQ flags in AOD/NTP runs  Utilize provided good-run list  Only path sofar  Browse DQ flags via COOL  dumpFileMetaData.py  Quick & simple until match to athena  LumiBlockMetaDataTool  Within athena but tooo complicated/cautionful

9. official_GRL usage  Given an official list  Official_GRL_XXYYZZ.xml ( possible private_prepared )  Trace its evolustion w/ reconstructions  Interface it to user AOD processing  Configure ones jobOs  See https://twiki.cern.ch/twiki/bin/viewauth/Atlas/GoodRunsListsTutorial  Check ones output  Ntuple w/ only events in good runs  Full/resonable Luminosity estimation  Possible procedure to merge many GRLs

10. Proxy servers ?  Frequently updating data  Calibration constants (d)  DCS values (s) & DQ flags (m)  Sometime needed in analyses  Oracle servers ?  Replicated to Oracle servers in each tier1  Frontier or Squid proxy servers on T2 ?  Cache/mirror T1 database dynamically  Prepare & use POOL data locally ?  Effective but chaos inviting

11. Backup(I)  AOD files in data09_900GeV/2TeV  L1Calo  F174_m268, f179_m283, f181_m293, f191_m315  F185_m298, f186_m298, f190_m310, f193_m320  f189_m304, r988_p62  L1Calo & MuonswBeam  F175_m273, f180_m288, f183_m298  F187_m304, f189_m304, f196_m325, r988_p62

12. Backup for data4  Wjet  Zjet  topT1  Di-jets  DrYn Minbias  Latest simulation/reconstruction  Complement of T2 MC data sets

13. Backup for data5  SM  Wjet, Zjet, WW, WZ, Zg (only for special/small prod )  Top  Wpola, Spcol, single, Xsec  Higgs  TtH, WH, Gam2  SUSY  RPVemu, S2top, S4top, ZgMet  XTC  W1wz  DPD  AANT, DAOD, TAG, LOGs