Duties of ISS-cream data analysis manager (DM) the DM is in charge of the overall analysis of data from the isscream instrument. S/he manages the process of processing and analyzing level 0 data to…

Duties of ISS-cream data analysis manager (DM) the DM is in charge of the overall analysis of data from the isscream instrument. S/he manages the process of processing and analyzing level 0 data to level 1 and level 2 data, is responsible for the analysis code repository, define the standards and processes used in analyzing the data and verifies the integrity of the level 1 and level 2 data. S/he reports to the project scientist (as opposed to experiment PI). Specific tasks 1. Coordinate defining analysis standards (EG version of root to be used in processing). 2. Coordinate defining standardized format and distributions of all code and data, including levels 1 and 2. 3. Maintain documentation on all programs and datafile structures. 4. Establish and maintain a documentation repository for analysis available to collaborators. 5. Establish and maintain an analysis code repository, providing access to collaborators. 6. Coordinate institutional efforts (through weekly/biweekly/monthly phone calls, wiki) towards reaching level 1 data. 7. Ensure the consolidation of multiple data streams (flight data & HK, ISS conditions such as SAA) into one root stream and providing this to collaborators (requires storage accessible to all collaborators and to the DM for processing). 8. Verify and maintain quality of calibration and levels 1 and 2 analyzed data. 9. Create and maintain a common code set that accesses consolidated root data, disseminated through code repository. 10. Create and maintain a common set of code tools (EG pedestal subtraction, track finding, energy determination), disseminated through code repository. 11. Participate in determining instrument response and efficiencies using simulations and data. 12. Participate in efforts to finalize science through ensuring proper calculations of live time, efficiencies, energy binning corrections. 13. Facilitate comparison of flight data with simulated data. 14. Analysis code BUG tracking. 15. Create process for approval of analysis results for presentation or publication. 16. Establish monthly high-level meeting to discuss analysis status issues. Attendees: DM, project scientist, PI, one instrument representative, OPS, instrument manager, others as needed 17. Collects code from analysts that produces level 2 data and publishable data. 18. Ensure compatibility between analysis code and product and simulations code and product. NKU is providing a server with up to 10TB of storage space accessible to collaborators. The server will also provide a documentation wiki and code repository.