30 likes | 174 Vues
This document outlines our decision to conduct a detailed evaluation of two observation simulation tools: O1 (Livetime/pointing simulator) and O2 (High-level observation simulator). With over 2 Full-Time Equivalents (FTEs) involved, it emphasizes the need for timely enhancements to existing tools. Key objectives include validating the Gaudi structure, refining requirements, and utilizing existing simulation elements. Collaboration among team members is crucial for implementing improvements by summer's end, with priorities set for developing various outputs, verifying models, and addressing testing requirements.
E N D
Observation simulation: What we decided • Study O1 (Livetime/pointing simulator) and O2 (High-level observation simulator) • Decide to evaluate in detail by building a trial example: between U. Washington and Perugia, we have >2 FTE. • Something is needed soon for other tools • Validate use of Gaudi structure • Allow refinement of requirements • Many elements already exist in the current simulation • Gino already has a model, code for several elements • We think it can be implemented in the Gaudi framework by the end of summer.
Work to do • FITS service: wrapper around the FITSIO package – Sandhia and Heather • Orbit model: verify current model, perhaps enhance • easy to maintain independent versions if implement as service • Pointing mode: need to separate from orbit. Also SAA. • Sources: current scheme is adequate to stand in for U7. New sources to put into library • Galactic diffuse (Perugia, from FITS table) • EGRET catalog + extensibility • Pointing history • Generate output summary like D2 table (UW) • Fast simulation • use PSF, Aeff model to adjust energy, direction. (Perugia has) • create D1-like table
Observation Simulation Breakout Session • Review use cases and requirements summaries • Deficiencies in the analysis environment? • Discuss open issues, assess existing software • Testing requirements • Estimate development requirements • FTEs & time, including for evaluating open issues, testing, documentation, by tool or database • factor in software that can be reused • Development support available • Development order, or priorities anyway • Deliverables from conveners • At wrapup session on Friday: Verbal summary of deliberations – the highlights • Shortly thereafter (next week, to SSC-LAT working group): Written version with details