# Presentation: 403529

## Goals and milestones for DØ 

- for the next five months
- Goals are physics driven:
- Present first results at Moriond, showing that the detector is working and we are on track for new physics results in 2002
- Present first physics results at the summer conferences, based on about 200pb-1 ( or whatever we have)
- We have defined a set of physics results that we want for Moriond; in turn, these define priorities for detector operations, computing, software, and the ID and physics groups.
- A. Boehnlein, B. Klima, J. Kotcher, K.W. Merritt, H. Weerts, J. Womersley

## Physics priorities for Spring 2002 conferences

- e(mET) , ee, 
- (mET), eejj

- Ks, J/** **
- b –  tag ; b- J/ tag
- b lifetime

- W + jets ( b tag ?)
- Z + jets (b tag ?)

- W + jets ( b tag ?)
- Z + jets (b tag ?)
- Z -> bb

- Jets – high Pt, dijets
- Diffraction

- Z  ee, 
- W -> e/ ;
- W -> e/ +
- Z’ -> ee

- Topics

- To be shown at Moriond
- ( data and MC)

- Physics group

- trilepton events & bg est. mET distributions in  and dilepton final states

- NP

- J/****mass plot
- K0 mass and lifetime
- Signed IP distribution
- b lifetime

- B

- W/Z+ *n* jets vs. *n*

- Top

- W/Z+ *n* jets vs. *n*
*bb *candidate display

- Higgs

- Incl. Jet Pt spectrum
- Diffractive event display

- QCD

- Z mass
- W transverse mass
- W/Z cross sections
- W candidate displays

- W/Z

- Defines priorities in ID and algorithm groups

- Note:  Moriond is a major milestone along the way to presenting new physics results at the 2002 summer conferences.

## Time line (working backwards):

- Results ready for approval:  March 1, 2002
- Last day of data taking to be included: Feb 1, 2002
- Stable physics running: end of shutdown (nominally Nov 17) + 3 weeks (~ Dec 8)  until Feb 1, 2002
- Shutdown starts October 8, 2001

- This sets the time scale for when things have to be done AND that time scale is VERY short.

- Data taking period is defined by ~2 months and **not** integrated luminosity.

## Weekly reporting/status

- We need regular reports, with quantitative
- measures, of operations:
- Smoothness & efficiency of data taking
- Data Processing (is it keeping up with data taking)
- Smoothness & efficiency of data access (SAM, etc.)
- MC generation for target analyses & background
- Goal: monitor with the aim of identifying and
- addressing problems, and increasing our efficiency
- Also need progress and status reports on:
- Software releases
- Analysis and Reconstruction Tools

## Analysis and Reconstruction Tools

- Luminosity info /run
- Calibration of triggers
- Certified SMT tracking (isolated high PT tracks)
- Certified Electron ID ( high PT isolated)
- 	with photon candidates as a byproduct
- Certified Muon ID ( high PT isolated)
- Certified Jet ID and JES (R= 0.5, 0.7)
- Certified Global Tracking (isolated high PT tracks)
- Missing ET in selected final states
- Muon ID in jets for b-ID
- Tracking efficiency in jets
- 	understand performance, even if not
- 	enough time to optimize it
- Secondary vertices for b-ID
- We will monitor progress and manpower in the above areas, and reassign if necessary

- -  Tau ID
- -  Electrons in jets
- -  JES for KT and Run 1 algorithms
- -  Sophisticated analysis techniques

- Not on the list (for Moriond):

## Certified Electron ID

- This includes:

- energy scale
- at least one ID method (with known efficiency at all levels)
- documentation
- known resolution
- fake rate/backgrounds
- MC and data comparison
- sign off by a defined procedure

-  able to do physics:

- Z mass distribution
- W transverse mass
- W/Z cross sections

- Example

## October 15
W/Z -> e signal
reporting and oversight established
establish a plan for analysis infrastructure (e.g. event display, luminosity tools) and for farm operations during shutdown
November 1
W/Z ->  signal
luminosity available by run and trigger
November 15
J/  -> signalfor calibration 
Operations:
20 Hz to tape
Examines,  online monitoring of data quality
production offline capable of keeping up with data taking & plans to cope with increases
use new tape handling system
Last date for major changes to Dec 1 software release
December 1
start stable global running; freeze global triggerlist (L1 and L3)
Establish EM scale
b tagging with muons
P10.x software release (= final reco code for Moriond)

- W/Z -> e signal
- reporting and oversight established
- establish a plan for analysis infrastructure (e.g. event display, luminosity tools) and for farm operations during shutdown
- November 1
- W/Z ->  signal
- luminosity available by run and trigger
- November 15
- J/  -> signalfor calibration
- Operations:
- 20 Hz to tape
- Examines,  online monitoring of data quality
- production offline capable of keeping up with data taking & plans to cope with increases
- use new tape handling system
- Last date for major changes to Dec 1 software release
- December 1
- start stable global running; freeze global triggerlist (L1 and L3)
- Establish EM scale
- b tagging with muons
- P10.x software release (= final reco code for Moriond)

## 
January 10
certified e, mu physics objects (p10.x)
certified tracks (p10.x)
certified jet physics objects and certified JES
February 1
b tagging with sec vtx or IP
complete data taking for Moriond
February 8
complete data processing for Moriond
March 1
Plots/results ready for approval

- January 10
- certified e, mu physics objects (p10.x)
- certified tracks (p10.x)
- certified jet physics objects and certified JES
- February 1
- b tagging with sec vtx or IP
- complete data taking for Moriond
- February 8
- complete data processing for Moriond
- March 1
- Plots/results ready for approval