1 / 6

HCAL Upgrade TP software status

HCAL Upgrade TP software status. Jane Nachtman (Iowa) for the HCAL group Calorimeter Trigger Upgrade Workshop July 23, 2008. List of questions from Dave.

ashelton
Download Presentation

HCAL Upgrade TP software status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. HCAL Upgrade TP software status Jane Nachtman (Iowa) for the HCAL group Calorimeter Trigger Upgrade Workshop July 23, 2008

  2. List of questions from Dave • What functionality currently exists?   - What has been introduced beyond the baseline detector / trigger simulation?   - To what extent is the code tested / validated?- What is planned for the coming months?   - Are there substantial changes or additions to functionality still required?   - Are you working to a formal task list, or are things still informal?- Who has responsibility for the code?   - Is it a team effort? How are code changes discussed and coordinated in your group?   - How is this foreseen to evolve?- Is the code 'public' (in CVS, documented) or private?   - What / how large is the 'user base'? Experts only?- Is more work required in performance?   - If so, what are the bottlenecks?   - Will fundamental changes (perhaps to components not touched so far) be required in the future?   - What are the interfaces to other components of upgrade simulations?- What will be the issues with a transition to 3_1?- What would be the issues with a convergence with mainstream CMS releases?   - Such that upgrade code could co-exist with mainstream CMS software   - Is this a desirable goal?

  3. Existing Functionality, status • Several private codes in the hands of individuals, mostly shared privately among experts, various levels of documentation (internal notes, talks) • SiPM modeling (Fermilab) • QIE simulation (Princeton) • Longitudinal segmentation, digi-level (Minnesota) • Longitudinal segmentation, RecHit level (DESY) • CaloTower from HLT (Princeton) • Code is all very new, so at a preliminary stage with respect to integration in mainstream CMSSW

  4. Plans for coming months • Validation/Development ongoing, expected to continue for short-term future • Still at preliminary stage • For example, TPG code is waiting for ongoing studies/code to stabilize • Task list • Mostly informal • Working from guidelines for initial goals for studies, code developed to do the studies

  5. More questions • Responsibility for the code • Mainly individuals • Changes suggested by experts • Goal – put into cvs, in CMSSW 3_x • Interfaces • This is an area where much work is needed in the near future • Code is mainly being used for individual studies /validation so far, needs to be put together • Some software works within cmssw to some degree, others will need more work to be incorporated

  6. Dave’s questions that I can’t answer right now • Performance bottlenecks – as we don’t have a full upgrade simulation package, not easy to understand this • At this point we are generating small samples, main issue is generating pileup events • Issues with transition to cmssw 3_x • Code is in various stages, versions • Issues not yet known

More Related