# Presentation: 373512

## Reco Status and Plans

- Harry Melanson
- Feb. 14, 2003 Collaboration Meeting

**Outline of this talk:**
-  Past
-  Present
-  Future

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Past: p13

-  About one year ago, presented the pain of p10 and the delay of p11.
-  Big worries last September
-  p13 schedule
-  RECO was released and data was processed on schedule
-   Change of data format for analysis (tuple vs TMB)
-  Thumbnail in, reco_analyze out...
-  “LO, NLO corrections” done, awaiting “NNLO corrections”
-  “individual analysis formats” – still being “developed by *us****”***
-  RECO status web page:
- http://www-d0.fnal.gov/computing/algorithms/status/p13.html#history

- Harry Melanson, Fermilab

- Feb. 14, 2003

## Slide 3

- Harry Melanson, Fermilab

- Feb. 14, 2003

## Slide 4

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Present: p14

-  p14 is based on p13.08.00
-  Changes limited to RECO
-  e.g. p14 MC = p13.08
-  Current status
-  p14.00.00 has been tested on CAB with real data (Few K events)
-  will go to farms for more testing next week
-  p14.01.00 will be built to fix any problems found
-  Schedule
-  Final version week of March 4.  Install on farms week after.
-  Still on target

- Well, a few others...
- Generators, PMCS

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Present: p14

-  New tracking algorithm combination available (AA+HTF)
-  TARC2 studying now *
-  Similar hi pt efficiency as p13 (but no reliance on axial-only)
-  Lower fake rates
-  Improved efficiency for PT < 500 MeV
-  Improved efficiency for high impact parameter tracks
-  gamma conversions, K0, , etc. (Guennadi’s talk)
-  AA – not the “extended” version (x2 effic difference, x4 CPU time)
-  Begin to use offline calibration databases (SMT, CFT, CPS, MUO)
-  Remove global CFT ADC cut (20)
-  Will increase tracking efficiency
-  Vertexing – improve split PV vertex problem, fixed duplicate vertices, require 2 SMT hits in vtrkimp

-  Present: p14

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Present: p14

-  SMT
-  New HW maps (post-shutdown)
-  CPS
-  Update map
-  Include more clusters in thumbnail
-  FPS
-  Update map
-  EM Id
-  Tuned H matrices
-  Muon Id
-  Include hits in thumbnail
-  Remove storing of multiple matches
-  Turn off axial-only track matching

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Present: p14

- Thursday 20 Feb. (week following the Collaboration meeting),
-  “Jamboree" of TARC results from id and physics groups
-  1:30 – 3:30, Ninth Circle (room to be confirmed)
-  Tuesday or Wednesday 25 or 26 Feb, round 2 of jamboree of results
-  Committee report by Friday, 28 Feb.
-  Changing default algorithm is a switch of a high level rcp parameter
-  or a command line option...

-  Present: p14

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Present: p14

-  Why do p14 this way?
-  The *STABILITY* argument
-  We shouldn’t disrupt physics with an “arbitrary new version” of RECO
-  Then why should we change?
-  We should deploy a new versions of RECO if it has some significant impact on our ability to publish  physics results.  I believe P14 has that impact.
-  Qualitative tracking features: gamma conversions, K0, , etc. (in situ test beam); low PT effic; hi impact parameter effic; reduced fakes; calibration database
-  A few more “details” that are important (CPS clusters, muon hits in thumbnail, etc)
-  Seems compelling to give the experiment these features to play with.
-  Why use p13.08.00 as the base?
-  Optimize probability to converge and get on farms for post-shutdown processing to maximize sample with p14

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Future: p15

-  Schedule
-  March 11 – cut p15.00.00 based on test branch
-  April 1 – converge
-  Purpose
-  gcc conversion
-  Trigsim, Level 3, MC?
-  Provide latest development in a “stable release”
-  Platform where “even newer ideas” can be tested
-  RECO comments
-  Will not go to farms for “standard production”.
-  May be used for “semi-official” production for various studies.

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Future: “tomorrow” to “p16”

-  track resolutions ??? (MC much better than data – WHY???)
-  alignment (for example, use large J/psi sample) – SMT, CFT, MUO, CAL, ICD, CPS, FPS, ...
-  cluster optimization (MC vs RECO, data)
-  Mag field vs alignment vs calibration vs clustering ??? (K0, J/psi, Upsilon,  Z)
-  gamma conversion “test beam” (CAL calib, MC material, RECO material, ...  !)
-  dE/dx?? (lambdas (p vs pi) - !)
-  Calorimeter ...  (still a huge amount of CRUCIAL work!)
-  JES – Jet/MET ID – Calorimeter hardware - simulation
-  Data monitoring
-  New group formed

-  Future: “tomorrow” to “p16”

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Future: p16?

-  looser cuts for events with J/psi?
-  “fast” J/psi identifier + “AA extended”?
-  develop framework to “do it”
-  special vertexing based on objects?
-  can this be ready for next “RECO disruption”?
-  Can we develop useful, experiment-wide skims to run at RECO level on farms (W, Z, J/psi, ???) ?
-  develop code
-  deploy, test, integrate, maintain
-  need to discuss
-  In about 3 - 4 months (date under discussion)

-  Future: p16?

- Harry Melanson, Fermilab

- Feb. 14, 2003

##  Future and present... 

-  CPU time per event
-  p14 tracking time is about the same as p13
-  tracking time will go up with removal of CFT global ADC cut
-  total time for p14 will go up because we find more tracks
-  need to quantify
-  a continuing issue
-  Memory requirements to run
-  Memory requirements to link
-  Also very important for analysis software

- Harry Melanson, Fermilab

- Feb. 14, 2003

## Personal Comments

-  It can (especially with p14) do some really cool things.
-  We now need to approach the “long term” problems
-  The problems don’t just go away with time...
-  They must be solved with work.
-  Almost all of the RECO software is generic RUN II (a, b)
-  My advice to people doing analyses
-  consider your physics interests
-  determine the *timeframe* appropriate to you and your physics topic
-  determine *all* things that need to be done to PUBLISH the physics result you are interested in within the relevant timeframe
-  devote *your* time to completing those steps (i.e. work on fixing the problems)

- Harry Melanson, Fermilab

- Feb. 14, 2003

## Personal Comments, continued...

-  Some problems will require fixes at the hardware level.  Some at the reconstruction level.  Some at the simulation level.
-  My current reading – we have a reasonable “version 1” of RECO.
-  It **will not** yet produce world-class physics.
-     (Although clever people (all of you) can clearly do a lot with it...)
-  It is **poised** to do so, with *our* contributions.
-  There are also other areas related to RECO that are essential for rapid “physics progress”:
-  Level 3 triggering - given L1 and L2 rate advancement, if we don’t improve L3 algorithms, we don’t get the events we need.
-  Simulation (“Full” and “Parameterized”) – if we don’t understand our detector or our reconstruction program, we can’t simulate events, and vice versa.  AND, we can’t publish without a well understood simulation system.

- Harry Melanson, Fermilab

- Feb. 14, 2003

## Conclusions

-  Past – p13 RECO
-  Success
-  Present – p14 RECO
-  On track, and very interesting
-  Run it stably for 100 pb-1?  (need to discuss)
-  Future – pxx RECO
-  A lot of problems to solve
-  Many crucial to make the next step to physics publication

- Harry Melanson, Fermilab

- Feb. 14, 2003