Minimal ECAL reconstruction manpower @ equilibrium
  • 1 person for Clustering (code development/improving, testing, prompt bug-fixing)
  • 1 person for RecoLocalCalo, especially UncalibRecHit producer (code development/improving, testing, prompt bug-fixing)
  • 1 person for Validation (releaser, pre-release checking, problem spotting and further investigations in collaboration with Clustering and RecoLocalCalo persons)
  • 1 person for overall management + accessory work (DataFormat, DB interactions, AoB)

Short term action items - startup

  • check and improve ECAL (electronics) mapping to have a coherent system across trigger-laser-offline
  • RecoLocalCalo: verify the chain
    • UncalibRecHit producers (timing and weights)
    • new flagging/recovering system
  • Clustering
    • integrate rechit flags in clustering algos
    • testing of local containment correction
  • Fully integrate preshower in reconstruction

ECAL reconstruction

  • Trigger
    • Trigger Primitives (TP)
      • medium frequency ongoing changes (for TP configuration, I think)
    • Selective Readout Process (SRP)
      • critical, low frequency changes, low long-term devel
    • Trigger Emulators
      • no idea

  • Unpacker
    • EB/EE
      • critical, low frequency changes, ?
    • ES
      • critical, ?, ?

  • Uncalibrated Rec Hits
    • Amplitude reconstruction
      • critical, medium frequency changes, medium short-term devel
        • channel recovery, especially in the EE
        • affected by trigger optimization
    • Time reconstruction
      • non critical, medium frequency changes, medium short-term devel
        • optimization of ratio method
        • affected by trigger optimization

  • (Calibrated) Rec Hits
    • Application of calibration constants
      • critical, low frequency changes, low devel
        • propagation of reco flags
        • affected by trigger optimization
    • Laser transparency corrections
      • critical, low frequency changes, medium long-term devel
        • work on transparency correction algo

  • Clustering
    • Clustering Algorithms
      • critical, high frequency changes, high short-term devel
        • ES area to be fully included
        • refurbishing of the code would be good
        • possible room for performance improvement
    • Clustering Corrections (energy scale, uncertainty, gap/crack)
      • critical, high frequency changes, medium short-term devel
        • at each release needs re-computation of parameters + appropriate DB filling
        • may require code changes if algorithms get improved
        • gap/crack needs to tested and be included in the reco flow
        • error estimation still unders study
    • Cluster tools
      • non critical, medium frequency change, medium devel

  • Preshower
    • no real idea

  • Validation
    • each of the items to be validated should take care of its part for the validation (suggest histograms, eventually implement them etc.)
    • one person to supervise the process and look at the results/debug problems if any/contact relevant persons

  • Accessory topics (i.e. topics affecting/needed by ECAL reco)
    • Data Base (DB)
      • Objects
        • critical, high frequency changes, expected to become low
      • Payload filling (online/offline DB, trivial)
        • critical, high frequency changes
          • need a tag for each release
          • most of the time it is just a copy of old payloads
          • regular set of payload changes with time and has to be updated
      • Trivial condition retriever
      • DB technicalities (e.g. O2O etc.)
        • no real idea, but we don't need one
    • Geometry
      • critical, low frequency change, low long-term devel expected
        • mainly optimization, big changes should have been already done
    • Electronics Mapping
      • trigger
        • non critical, low frequency change
          • it works as it is, could be improved?
      • readout
        • non critical, low frequency change, medium short-term devel expected
          • optimization
          • possible redefinition of few mappings
          • should be worked on to improve ECAL conventions (e.g. have a tool to universally handle all mappings: now it is split into geometry, trigger stuff, detId's methods etc. and it is very complicated)


ECAL reconstruction

Trigger

Trigger Primitives (TP)

Selective Readout Process (SRP)

Trigger Emulators

Unpacker

Uncalibrated Rec Hits

Amplitude reconstruction

Time reconstruction

(Calibrated) Rec Hits

Application of calibration constants

Laser transparency corrections

Clustering

Clustering Algorithms

Clustering Corrections

Preshower

Accessory topics

Data Base (DB)

Objects
Payload filling (online/offline DB, trivial)

Geometry

Detector Geometrical Description
Electronics Mapping (trigger, readout)

-- FedericoFerri - 27 Apr 2009

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2009-04-28 - FedericoFerri
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback