7
1 Reminder: Why reprocess? 2001-2002 data Reconstruction: DBV 12-14 DSTs: DBV 14-16 2004 data DBV-19 for reconstruction & DSTs, Run < 31690 DBV-20 for Run > 31690 What is gained by reprocessing? What complications arise? Analysis/MC compatibility, etc. What needs to be done to start?

Reminder: Why reprocess?

  • Upload
    salene

  • View
    28

  • Download
    2

Embed Size (px)

DESCRIPTION

Reminder: Why reprocess?. 2001-2002 data Reconstruction: DBV 12-14 DSTs: DBV 14-16 2004 data DBV-19 for reconstruction & DSTs, Run < 31690 DBV-20 for Run > 31690. What is gained by reprocessing? What complications arise? Analysis/MC compatibility, etc. What needs to be done to start?. - PowerPoint PPT Presentation

Citation preview

Page 1: Reminder: Why reprocess?

1

Reminder: Why reprocess?2001-2002 data

Reconstruction: DBV 12-14DSTs: DBV 14-16

2004 dataDBV-19 for reconstruction & DSTs, Run < 31690DBV-20 for Run > 31690

• What is gained by reprocessing?

• What complications arise?Analysis/MC compatibility, etc.

• What needs to be done to start?

Page 2: Reminder: Why reprocess?

2

Datarec changes DBV-14 19dE/dx code for all streams (2002 data)DEID bank

FILFO bias sampleNo BHABREJ cut in FILFODownscaled golden Bhabha sample

Many bha files deleted from tape library

kpm stream - old algorithms eliminated, new dE/dx algorithmksl stream - new KSTAGrad stream - min bias sampleclb stream - bug fixes

Bug fixed in dE/dx integration in VTXFIN (DBV-16)Mainly affects kpm stream: 2907 dkc DSTs < DBV-16

Page 3: Reminder: Why reprocess?

3

DBV-19 20 and beyond

DBV-19 20: s, boost values from HepDB BMOM(3) for all EvCl routines

• Technical points that don’t impact reconstruction quality

Also true for DBV-14 19 lists: not included

Further changes for DBV-21:

• Problems with dead-wire lists

• Thickness of DC wall 75 µm

• Cut DC hits with drift times > 2.5 µs

• Modifications to streaming code

Page 4: Reminder: Why reprocess?

4

More reprocessing issues

MC compatibility:Does reprocessing with a new version of datarec imply

re-reconstructing MC files?reprocessing MC DSTs?

Scripting:Need work on scripting to reprocess on batch queues

Page 5: Reminder: Why reprocess?

5

MC re-reconstruction?

MC re-reconstruction possibleMinor work on scripting needed

Impact of dead-wire lists:

Re-reconstruction of much/all 2001-2002 MCDead wires not masked for data reconstruction

Re-reconstruction of much/all 2004 dataDead wires masked in 2004 data reconstruction

No issue concerning MC compatibility in this case

Page 6: Reminder: Why reprocess?

6

MC development: Minor topics

BP geometry for 2004

generator

LSB insertion code

CSPS/CELE element correspondence (?)

Page 7: Reminder: Why reprocess?

7

MC development: Major topics1. Accidental cluster rates (SM)

2 weeks for module to delete excess clusters6 weeks to reprocess MC DSTs if needed

2. Correlated noise in DC for charged kaon tracks (PDS) Problem and solutions under study

3. Regeneration/nuclear interactions (MA, GL)Problem and solutions under study

4. Energy scale calibration for EmC simulation (PG) Problem and solutions under study

5. DC tracking resolution (MM) 2 months to reparameterize errors and study resolutionNeed significant input for P. de Simone

6. EmC time distribution (CG) Report this meeting