Notes about ISOC and the italian contributions

1. Gamma-ray Large Area Space Telescope Notes about ISOC and the italian contributions

2. Publication Review Board Membership and collaboration policies Group 1 Group 2 Flight Operations Group 3 Group 4 Science Operations Group 5 Group 6 Science Analysis Systems Group 7 …Group N ISOC in the LAT Collaboration This entire slide is taken from Rob Cameron’s presentation at the ISOC Technical Review, August 2006 • The ISOC is the core of the LAT support activities at SLAC after the LAT project delivers the instrument • ISOC provides LAT data to the collaboration during the first year of the mission, and beyond • ISOC has close connections to LAT Science Groups • ISOC science staff participate in all Science Groups • Calibration and Analysis Methods • Event reconstruction • Filter configuration • AGN & GRB Science groups • Automated science processing definition • The LAT collaboration participates in the ISOC • Principal areas: science analysis software; science operations • e.g. software tool development by the collaboration coordinated through SAS • LAT Operations Steering Committee guides interaction between ISOC and broader LAT collaboration • Principally for issue resolution • e.g. compute resources • Members: Johnson, Ritz, Atwood, Cameron, Dubois, Michelson, Analysis Coordinator (McEnery)

3. Science Operations inside ISOC SO main responsibilities • Data processing (L1 and some higher-level) • Data monitoring (LAT, sources and background) • LAT Calibration • LAT performance parameterization (IRF) • Anomaly detection and resolution • Optimize configuration (register settings, on-board filter) • Interact with SWG for definition of observing strategies • Interact with SAS and LAT collaboration for exchange of tools and data monitoring results • Implement observing strategies • Transient automated detection and alert (ASP) • Provide coverage for above tasks through LAT collaboration SO does not (this is Flight Operations matter) • Control and command the LAT • Monitor health & safety • Modify flight software • Develop processing infrastructure

4. Official chart presented october 27

5. Notes on the Organization of SO • Yes, that is a lot of boxes • Every major area has someone as designated lead • Might strike you as SLAC-centric in a “We’re from SLAC and we are here to help” way • In terms of the actual tasks, the expectation is not at all that everything gets done at SLAC • And of course this would not work anyway in terms of the broad distribution of expertise and person-power • Think of the leads as coordinating the efforts in SO within the collaboration and the ISOC • The Daily Operations Group (DOG) will have an overall coordinating role that is not obvious in the functional diagram • The ISOC is at SLAC but the success of SO will rely on the collaboration functioning as, well, a collaboration Seth and Eduardo at SCI • There was a need to present all boxes with lead at SCI • Collaboration from us is not only welcome by NEEDED • Responsibility roles will be aknowledged • Most tools, functions, roles to be implemented still • current chart does NOT reflect current implementations unofficially

6. Existing working groups • Daily Operations • Define roles of shift takers, shift coordinators, control-room operating mode, anomaly resolution escalation process • Overview functions and tools, identify weak areas, suggest required development • Organize training and test of tools • non-official: interface to national communities to search for qualified to address SO needs (1 rep/country) • Data Servers • Identify data types to be served, access mode and interface • Pipeline • Shape-up pipeline 2 and provide support for SC • IRF • Develop official computation/visualization tool for IRFs • Elogbook • Identify/develop elogbook • Monitoring • Identify/develop data monitoring tools

7. Areas of collaboration • Existing collaborations • Luca Latronico in DOG • Francesco Longo in Pipeline group • Claudia Cecchi, Carlotta Pittori in Data Servers group • Riccardo Rando in IRF group • INFN-PI in data monitoring group • Proposal for new collaborations • Substantially contribute to ASP development • Require strong interaction with SWG • ASP group not existing yet, software framework TBD • Candidates: Nicola (GRB), Gino (AGN), Aldo (DM), Max+Andrea (pulsar) • INFN-Bari for data monitoring • In particular offline, following I&T work • Study of IRF optimization for GRB science • Nicola • Nothing on optimization yet – need to think about it

8. Proposal • Create a national Steering Committee with representatives from all collaborating institutions • Define areas of collaboration • Define project (task, people, schedule) • Propose project to SO and make sure responsibilities are aknowledged • Note: there is currently no official mode for the above proposal

9. Reference material • ISOC HOME • http://confluence.slac.stanford.edu/display/ISOC/Home • Overview of science operations (Seth/Eduardo) • http://confluence.slac.stanford.edu/download/attachments/21021/SO_overview_v2.pdf?version=1 • Daily Operations group • https://confluence.slac.stanford.edu/display/ISOC/Operations • Working groups for tools development • https://confluence.slac.stanford.edu/display/ISOC/Operations+tools