What to improve in the next round of ReReco?

Do it from RAW data

  • proxy DB ??? Thomass N.
    - hardware requirements - machine, disk space ...?
    - software , -modifications?
    - tests ?
    ....

    • Do TMBs merging outside FNAL

  • needs, requirements ?
    - eventuel problems ? - SAM related, parentage?
    --> Mike D. - how have you done it?
    - need portable, robust merge script
    - caveats:
    ---- intensive sam DB access
    ---- requires central access to all output files from a run
    --> Patrice - proposal?

    • Can we use GRID ?

  • What about SAM-Grid ?
    - in rather advanced phase for MC-production
    - could it be adapted to ReReco without great pain?
  • EDG experience
  • What about LCG ?
    - premature ?

    • Improve book-keeping

  • automate/ generalize book-keeping
    - which parts of Lyon system are reusable and how to generalize them ?
    - remove any local dependancies, paths
    - what can be used from the GridKa procedure ?
  • do we have in SAM a functionality not used yet, similar to those of Lyon system ?
  • recovery/resubmission procedure
    -
  • additional crosschecks in the remote procedures ?
    - number of events produced (compare with expectation from raw file/sam)
    - check readability of output files ?

    • Data set preparation

    1. project assignment

  • avoid manual assignment of datasets (-> common bookkeeping)
    - web page where sites can sign up for specified datasets
    ----- ensure unique assignement (1 project - 1 site)
    ----- general information about the status of project
    (assigned to X, dataset copied to X, dataset done, dataset in sam, dataset copied back)
    - in Lyon done for local repro - based on Oracle

    2. data delivery

  • dedicated node with Gb connections and large buffer space ?
    ---- specify out server to handle both data delivery of raw files and storage of DSTs & thumbnails
  • avoid the need for (manual) prestaging of input data?
    Tibor Kurca
    Last modified: Tue Feb 4 15:55:37 CST