Meeting Update after Chama Meeting

Notes from meeting on 12/13/2022

• Clarification on Plume. Should rename to make clearer? Multi plume vs plume with gradient.
  • There should be 1 plume with gradient in it.
  • The Plume should be diagonally across the network.
• Clarification on scenarios. Our scenarios vs the Chama keyword “scenario”.
  • The clarification of Chama terms will get into the paper.
• Using specific subset of junctions. For example, Banklick would take too long to run with all junctions as possible sensor placement locations.
  • It would be nice to get more involvement from SD1, but they are fairly busy.
  • Next time we talk with someone from SD1 we will be asking if they have a list of places they monitor.
• Working with utilities in general could be useful. Find the practical applications as opposed to the purely scientific/theoretical we’re seeing at this stage.
• Change some of the titles in the Chama Runs table/matrix. Contaminant type to measurement of the contaminant.
• Avoid using multiple “large” rain events at once. I.e. don’t combine 2 yr, 10 yr, 100 yr rain events in a single run.
  • Look at the current rainfall time-series for the following:
    • Volume
    • Time
    • Peak
    • Intensity
  • For example6 we will likely need to make new rainfall similar to inch rainfalls not to the year rainfalls.

Tasks Based on meeting

1. Talk with Sudhir about formulas for finding Volume, Peak, and Intensity from flow.
2. Start creating a large gradient plume diagonal over the network.
   1. Start with Example6_Final
   2. Google selecting in a shape in QGIS to see if there is an easy way to get subcatchment names. This will work for rain gages as well.
      1. https://freegistutorial.com/how-to-use-select-features-by-area-in-qgis/
3. Start documenting what Chama calls things as well as what we call things in preperation for the report.
4. Create new rainfall for Example6 Final that is closer to the inch time-series than the year time-series.