Fall 2025 - period from 9/2/2025 to 10/7/2025

[rburghol]

• Topics for 9/30/2025 meeting:
  • Project tracking HARP project: Shenandoah Drought Baseflow analysis baseflow_storage#36
    • This is the original list from our kickoff meeting, separated into its own issue for better tracking.
    • Drought report items have been added, though majority of drought report was employig components that we currently have.
    • All 1st level items (and some 2nd level) should have a link to a separate issue
    • As a team we need to add links to our various issue pages on the relevant bullet point
    • Add bullet points if we have created an new issue to further explore a given point.
  • Curating / finalizing issues
    • Majority of our issues have significant comments, which is great way to track chronological evolution of our problem solving approach, but we need to go back and curate these.
• Topic for 9/23/2025 meeting: Code-sharing and data-sharing:
  • Asynchronous/ephemeral work requires aggressive code-sharing.
  • Many of us will have 10-15 minutes max to take a look at code/results, and being able to access your current development code and/or a snippet of draft code is essential to getting feedback.
  • Also, a teammate may find themselves with time on their hands and if your code is readily available (and up to date), they can hop in at a moments notice.
  • Best Practices:
    • At minimum, push code to github after every work session
    • Link the branch/script(s) in the very top of your sub-project issue
    • Summarize work in comment on your sub-project issue after each session (this helps communicate to the team, as well as potentially assisting you in recalling the state of your work when you resume).
    • Periodically merging branches with main branch to make sure that no branches fall too far behind the main branch.
      • When doing pull requests, give notification so team members are aware of changes.
• Review results of drought report Drought Status Assessment Report baseflow_storage#10
• Sample Projection script:
  • Project and Plot: https://github.com/HARPgroup/baseflow_storage/blob/main/R/examples/plot_projection.R
  • The projection function: https://github.com/HARPgroup/baseflow_storage/blob/main/R/bfd_agwrc_project.R
  • What is computed model recharge during our historical projection? What does this recharge amount to in terms of increased cfs?
• Modeling (@ilonah22 ):
  • Recharge data harvesting (post CSV locations, and develop code)
    • Begin with single landuse/landseg analysis (forest, maybe pasture also)
    • Later, we may move on to full model data harvesting.
    • Add this recharge data to event analytics
  • ET data harvesting and impact on flows:
    • How much does it matter?
    • Can we incorporate these "add-backs" to the fall/winter projections?
• Event post-processing (@benhdye )
  • Trim from the front until slope of computed AGWRC goes to zero
  • Determine impact on computed AGWR
• Run event identification script against model outputs. (@willprokopik ) Baseflow Event Identification Against Modeled Stream Flow baseflow_storage#29
  • The model calibration assessment begins here.
  • What is computed model recharge during out event?
• Meteorological Data (first come first served):
  • Add precip data to our event analysis (see daily values here: http://deq1.bse.vt.edu:81/met/PRISM/precip/)
• Events (list ones that warrant focus):
  • 2002 February (why is the R^2 lower when it looks so darn good?)
  • Baseflow gets carried away... (Shenandoah examples?)
  • What is computed model recharge during our event?
  • 2023
  • 1931
  • other?
• Overview/summary:
  • Chart of $Qout = f (AGWS)$ ; AGWS = storage
• Characterizing/identifying flow-dependent AGWRC
• check in next week on whether/when/where for a group in person meeting (or 2nd group virtual meeting)
  @COBrogan @julieshortridge