Offline Event Processing Overview:

1
Offline Event Processing Overview Philosophy,
Goals, Questions J. Urheim Saturday, July 13
2002 offline data processing parallel session

2
Philosophy

• Whatever we do will have to be redone
• calibrations, reconstruction pkgs will improve
• feedback from initial pass will be useful for 2nd
  pass
• The sooner we get started processing data the
  better
• scale learning curves regarding operational
  issues
• we shouldnt wait for everything to be perfect
• But we still want this to be useful for data
  analysis / detector performance studies
• treat 1st pass as a serious production
• aim for frozen executables/constants
• aim to carry out quality control monitoring

3
Initial Goals of Processing

• Work out the technical aspects
• FNAL batch farms, set up infrastructure (Alex)
• Offline software performance, robustness
• Provide output that is useful for collaborators
• Try to process all events, minimal filtering
• Set up to do nearly real-time processing for
  quick turnaround
• Output should be useful for further development
  of reconstruction ? should contain raw data
  candidates
• Output should be useful for higher-level data
  analysis ?output ntuple(s)?

4
Questions Issues

• What to run?
• DigitListModule - yes!
• DeMuxCosmicsModule - yes!
• TrackSR et al. - yes!
• BubbleSpeak - yes!
• what else ?
• Which candidates do we write out ?
• Do we write out an ntuple ?
• Do we do any filtering ?
• non-snarl records ?
• events with fewer than N planes with hits ? N
  ?
• Multiple output streams ?
• Event classification i.e., stopping muons, fully
  contained events, multiple muons, etc