You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 42 Next »

The software week goal is to facilitate communication and collaboration between everyone as we move forward extended support for Fermi. FSSC members will be available at SLAC all week for group discussions and one-on-one meetings. In addition to targeted topics, we encourage attendees with broad or cross-cutting interests to join the various discussions. There will be plenty of work, so we'll need everyone to take part in this transition.

Previous Software Weeks: Fall 2017,  Winter 2017, Winter 2018

Dates: March 2, 2020 - March 5, 2020

Location: Two conference rooms in B53 at SLAC have been reserved for each day.

  • 3/2 - Almanor/Havasu
  • 3/3 - Toluca/ Tulara
  • 3/4 - Tulara /Toluca
  • 3/5 - Almanor/Tulara
  • 3/6 - Almanor/Havasu

Slack: The #softwareweek channel is available for discussion.

Attendees

We've narrowed the possible weeks to late February and early March 2020 at SLAC. If you are interested in attending, please use the table below to indicate which of the weeks works for you, and we'll try to pick the week that works best for the most people.  If you can't attend in person, hopefully we can work out remote attendance.

 

Name

Week of

Feb 17

Week of

Feb 24

Week of

March 2

Week of

March 9

Comments
Liz HayesYYYY 
Don HornerYYYYJoe says Happy Birthday Tom!
Alex ReustleIf neededYYYHappy Birthday Tom!
Joe AsercionYNIf neededYWill be in Denver 2/27-3/1. Could fly from Denver to San Jose on 3/2 though (but I'd prefer not to)
Tom StephensYYYYFeb 17th is President's Day (and the 19th is my birthday (smile))
Nicola OmodeiAfter the 18thYYY 
Tom GlanzmanYYYY 
Richard DuboisYYYY 
Brian Van KlaverenYYYYLater is possibly better.
Toby BurnettYYYY 
Eric CharlesYYYY 
Steve TetherNNYY 
Heather Kelly    will attend remotely
Judy Racusin  Y  

Schedule and Agenda

All times Pacific Standard.

One conference room is schedule each day and the other is open for breakout sessions, side meetings, or whatever else might be needed.  There is a lot of time for lunch, too, so we can use some of that time, if needed. 

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.

Monday (2020-03-02)

TimeAlmanorHavasu
9am-9:30amKickoff
  • Discussion of goals and objectives
  • Review accomplishments of previous software weeks.
 
9:30am-11amCurrent 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-noonCurrent and Future Staffing
  • Who 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-2pmLunch 
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.

    • Nicola knows about FT1 reprocessing.  Are the steps documented?
    • Document how to do FT2 reprocessing.
 

Tuesday (2020-03-03)

 

TimeTularaToluca
9am-10amOther SLAC infrastructure issues 
10am-11am
SLAC move to CentOS.
  • Create the containers and move pipeline to containers to run on Centos7.
  • Do the process together and test.
  • What else is affected? 
 
11am-noon
Fermitools documentation
  • Documentation status
    • Missing fhelp files
    • What is out of date?
  • What is needed?  New threads?  Who will do them?
  • Using Jupyter notebooks
  • Work together on documentation?
 
noon-2pmLunch 
2pm-3pmFermitools code development
  • Go over the process of using the new development paradigm
  • How to use Github, submit patches, etc
  • How to update, build locally etc.
 
3pm-4pm
Fermitools Azure pipeline
  • Maintenance and development
  • Training on design/development of the Azure pipeline
  • Joe will go in depth about how pipeline functions as Azure and how config file functions.
 

 

Wednesday (2020-03-04)

TimeTularaToluca
9am-10amFermitools testing
  • How to get the tools tested before release. C&A group role?
  • Improving unit tests.
  • Turn analysis thread Jupyter notebooks into scripts that can be run automatically
 
10am-11am
Fermitools user support and tracking tasks
  • JIRA vs. Github
  • github tracker and helpdesk staffing, response times etc. 
 
11am-noon
Pointlike
  • How long will Toby support it?  What should we do after that?
 
noon-2pmLunch 
2pm-3pmGLASTRelease and Jenkins
  • Heather, Brian, Alex, Joe, Joanne?
  • Make sure GR builds with Jenkins.  
  • Is Heather's knowledge about build and deployment documented?
 
3pm-4pmFermitools bug fix workshop
  • Get together to go through and maybe fix reported Fermitools bugs/issues.
  • Need Eric, Joe, Alex, Tom, Don others?
 

 

Thursday (2020-03-05)

TimeTularaAlmanor
9am-10amChange in SLAC batch system.
  • Have Tom, Brian and ?
  • Work on moving to the new batch system.
  • Have Tom develop contacts with infrastructure staff.
 
10am-11amAdding capabilities to the FSSC data server
  • The FSSC data server is being moved to new, better hardware, including NVMe SSDs.
  • How this will affect the data server.
  • Do we want to add new capabilities? New filtering? Allow all sky searches?
  • Any new data products to add to the server?
 
11am-noonCloseout
  • Review decisions
  • Assign action items
 
noon-2pmLunch 
2pm-3pm  
3pm-4pm  

Friday (2020-03-06)

TimeAlmanorHavasu
9am-10am  
10am-11am  
11am-noon  
noon-1pmLunch 
1pm-2pm  
2pm-3pm  
3pm-4pm  



 

  • No labels