...
The is a draft schedule. Hopefully, it captures all the sessions/topics we will need. Things will probably need to be moved around to accommodate people's schedules or due to discussion at sessions, i.e., pick up something later or work on something that came up, further discuss ideas that come up.
Friday has been left open in case we need it, and Joe, Alex, Tom, and Don will be around that day.
We can discuss scheduling changes on the #softwareweek channel.
Monday (2020-03-02)
Time | Almanor | Havasu |
---|
9am-9:30am | Kickoff- Discussion of goals and objectives
- Review accomplishments of previous software weeks.
| |
9:30am-11am | Current status updates- Fermitools
- Overview of current development and build process
- Upcoming releases
- Python 3 transition
- Break
- SLAC
- FT2 reprocessing & IGRF model update
- Batch farm
- Jenkins
| |
11am-noon | Current and Future StaffingWho is even there anymore and what is their availability? - Identify areas of shortfall.
- Identify people who can take over SLAC infrastructure and Fermitools/Fermipy tasks if current person leaves.
Difficulty for FSSC personnel to take over on infrastructure that we don't use regularly. How much can we rely on collaboration people? Where can external folk inject the most help? Can we create a list of who to contact for various issues?
| |
noon-2pm | Lunch | |
2pm-3pm | Fermitools future directions discussion - What development needs to be done. What's missing from the tools.
- Discuss and work on improving interface between Fermitools and Fermipy.
- Modularizing the Fermtiools?
- Effectively freeze the tools?
- Using other package managers?
- Who will be in charge of which packages, e.g., gtorbsim
- What does the C&A group need that isn’t being provided by the FSSC (and vice-versa)
- Switch to CMake instead of SCons?
- Support for RHEL6 and older Linux systems.
| |
3pm-4pm | Halfpipe & L1 pipeline future Go through current documentation to update (and remove old information). Get together to discuss and write document pipeline how-tos and fixes. Update re-piping documentation. Document database schema. Dealing with missing datagrams - Causes, handling, what to do if repiping fails? Data lifecycle from an ISOC perspective - where does the data go?
- what do the processing steps do?
- how does this interact with the infrastructure?
Data reprocessing documentation FT2 reprocessing & IGRF model update. Installing new pipeline.
| |
...