Code Sprints

EPIC Code Sprints Banner

Welcome to EPIC Code Sprints!

A code sprint is a “sprint-like” event in which cross-functional team members get together and collaborate intensively on software projects. The goal is to leave with actionable tasks or a consensus on how best to address a specific topic. EPIC offers code sprints on a quarterly basis; check back regularly to register!

Current Code Sprint

Short-Range Weather Application Training 2022: Porting Over SRW/MRW Tools to the UW Toolkit 

December 16, 2022, 11:00 AM EST

Hosted on Google Meet. Limited to 100 attendees.

Interested in learning more about using the applications EPIC is developing? The Unified Workflow (UW) Toolkit provides the mechanism for moving data, submitting jobs, and generating and managing configuration files for the SRW Application. Join the EPIC Team on Friday, December 16, 2022, for a virtual day-long training designed to demonstrate how best to use the new application tools that the UW Team is creating and how to apply tools in the UW Toolkit repository to the SRW Application code. 

Hosted via Google Meet. Limited to 100 attendees.

Past Code Sprints

Outcomes and Value

The CodeSprint was aligned very well around teaching new community members how to run SRW locally on a MacBook.  You could show up to the event with a blank canvas, and leave with evertyhing that was needed to run a forecast. It is a great way to look at cost savings and be able to run the model locally instead of incurring large HPC costs. Liga who co-chairs the release group was also in attendance.

Why I think this was a powerful event:

  1. It is a challenge to setup this work to run SRW from nothing. When you log onto Tier-1 machines, HPC-Stack (Spack-stack), tools, packages are all available to you already, so setting those up yourself takes time and it very meticulous.
  2. Being able to run SRW locally for college students will save them a lot of money. Running SRW in the cloud can add up costs, but being able to run it on local hardware is an important step in allowing more members to have access.

Outcomes and Value

The code sprint participants emerged with both the ability to run the SRW App in the cloud and an understanding of how they can use this knowledge to assist the UFS community by building the infrastructure required to quickly test research. Three code sprint postdoc participants partook in a session on building the AWS cloud infrastructure for the SRW App. The event included a slide deck presentation on the code architecture followed by a hands-on process where each user built the SRW App in their own environment. Participants provided helpful feedback as UFS SRW App users and community members. They would like expanded documentation on how to utilize their own test case data and model configurations, and they would like more transparency about upcoming releases and what features—particularly physics implementations—will be included in releases. They would like to see documentation and roadmaps expand in these areas.

New ideas: Participants would like to see a code sprint like this with all CSPs and would like another event that walks through running and configuring the SRW application after the infrastructure is built out. They would like more information on how can they run local research in the cloud and stage appropriate data for their experiments. 

Outcomes and Value

The code sprint participants developed their knowledge of the SRW App, the infrastructure suite used to support it, and ways that they can assist the UFS community using this knowledge to quickly test research. Seven code sprint participants partook in a session on building the AWS cloud infrastructure for the SRW App and ran the SRW App after building the infrastructure to support the application.

New Ideas: The users communicated that they would like to see a follow-up event that walks through building out the infrastructure in AWS without the first portion of the event included. Rather than providing them with IAM, S3, and other baseline configurations, participants would set up these elements themselves.