Skip to main content

Week

4/24/2023 Monday​

  • Get Benz and MTW working
  • What is going on with Hydraulic.c there might be and error here.
    • Fixed the error with Jake. Wrote up and email but Jake requested I test it on MTW before I get Steve and Sudhir into it.
  • Started working on MTW.
    • Documenting as I go.
    • What tables will I need for EX.
  • Benz Scada data is not showing up. But the rest of EPANET Console Core seems to be working after Jake and I made that change.
  • In office on Tuesdays and Fridays.

4/25/2023 Tuesday​

  • Benz Scada Data was not showing up because I had the wrong dates.
  • Filled the database with MTW CSV's
  • HT-EX needs to have a Scada Tag table. It only needs 2 columns ScadaTagId and DataSource ID.
  • Start Date in MTW should be 1391403600
  • End Date in MTW should be 1391403600
  • Call with Sudhir
    • Update tasklist
    • Check to make sure I have the OWA Latest Pull.
      • Last time it was updated was "
    • I do not need to read the EPANET file from Lew! Sudhir might send it to me later anyway for me to put it on google drive. (DDA, PDA stuff)
    1. EPANET OWA
      1. Write up an email on how the OWA changes were made.
        1. 3 copies clearly labeled of the file where Steve need to verify the modification.
        2. Make sure no new changes have been made since last week to the OWA code.
        3. Point Sudhir and Steve to the Latest OWA code.
        4. Attach the GQC c file to the email. Has the code been back factored into the new OWA code. Will we need to make modifications to our code.
        5. Send Email to Jake for verification and clarity before I send it off to Steve.
    2. DDA vs PDA in EPANET
      1. Export an INP file that uses PDA instead of DDA. Use one of the files that Vannary used last week.
        1. Find out where we can make the change for that in the INP file.
      2. 64 DLL redo PDA in console core are we repeating our good results?

4/26/2023 Wednesday​

4/27/2023 Thursday​

  • Update tasklist based on what Sudhir and Jake assigned yesterday.
  • Read Email and run EPA Standard EPANET DLL.
    • Send out the results.
  • Get Doxygen on my computer
    • Run Doxygen on C code for EPANET.
      • Make sure that the recursive is checked it is easy to miss.
  • Look over tasks gotten yesterday from Sudhir.
    • How can I tell warnings from errors in EPANET.
      • Start with the Doxygen documentation.
      • Look for flags, warnings, and errors.
  • Grafana Start PDA VS DDA page.
    • Start with Leak at 244
    • Why did it not stop.
  • Talk to Sudhir and Jake about how to do the Grafana Tables.
    • I can have as many dashboards as I need.
    • I need to stop overthinking.

4/28/2023 Friday​

  • Combo of No scada data and error to reproduce the error.
  • Made a copy of the MTW database that had Scada data
  • Ran all the DDA and PDA runs for No leak, Leak at 224, and Zero balance.
  • Update the Grafana.
  • Debugging the Never ending simulation error.
    • In app settings.json
      • I don't think that ScadaEndUnixtime is ever used in EPANET Console Core.
      • I don't think the ScadaTimestepSeconds is ever used in EPANET Console Core.
      • The Database = false still inserts into the database.
    • Why does the time to Next Hydraulic Event vary.
      • it should be 300 seconds aka 5 min and it starts out like that but noticed that during the error it is 141 so I put a watch on it and a break with condition on it and there are weird numbers on it.
        • 233
        • 69
        • 87
        • 211
        • 108
        • 192
        • 261
        • 39
        • 159
        • 141...
      • Not all of the numbers being off cause an error. in fact these numbers were in order and the only error is at 141.

TODO​

  1. Get Benz and MTW working on HydroTrek.
    1. Follow Jake's Lucid Chart diagram.
    2. Benz
    3. MTW
  2. HydroTrek Documentation
    1. Organize Documentation From Dropbox.
    2. Put Documentation on Google Drive.
    3. Create a document Overview.md for each project in HydroTrek Suite.
    4. Create documentation for standard inputs and outputs for each network.
      1. INP Files
      2. Start and end dates in correct formats
      3. Where do I need to change the database so that the programs work.
      4. What type of file is modified to change the configs.
    5. Database
      1. What needs to exist where to find the data for the networks... Everything about the databases. There are 3 per network.
    6. Create Github issues for each project that reflect the Jira tickets that are available for each project.
  3. EPANET OWA
    1. Write up an email on how the OWA changes were made.
      1. 3 copies clearly labeled of the file where Steve need to verify the modification.
      2. Make sure no new changes have been made since last week to the OWA code.
      3. Point Sudhir and Steve to the Latest OWA code.
      4. Attach the GQC c file to the email. Has the code been back factored into the new OWA code. Will we need to make modifications to our code.
      5. Send Email to Jake for verification and clarity before I send it off to Steve.
      6. Run Doxygen on EPANET.
      7. C code linting look into this.
      8. Create ERD for Database
      9. What's the input file you're running that's throwing the imbalance warning? (exact name)
      10. Can you run the same input file in the 32bit GUI and see if the same imbalance warnings occur?
      11. Can you look into OWA error codes vs warning codes? Sudhir thinks that "error code 1" doesn't make sense and that maybe <100 are warning codes and >100 are error codes. This would help us with our logging.
        1. We need to discuss how to handle Warnings vs Errors.
        2. I need to write up issue I found where error stopped simulation from finishing. (This was warning code. It was pressure related error code 6. The same happened with error code 1. )
          1. Should be noted that the error code 6 was expected. DDA vs PDA test.
  4. DDA vs PDA in EPANET
    1. Export an INP file that uses PDA instead of DDA. Use one of the files that Vannary used last week.
      1. Find out where we can make the change for that in the INP file.
    2. 64 DLL redo PDA in console core are we repeating our good results?
    3. Run With leak for DDA and PDA and Graph in Grafana.
  5. SWC and SWMM upload to Google drive
    1. I think this is done but make sure.
    2. Mark the locations in dropbox when I am done.
  6. Review SWC Pollutant Functional and Design Specs.
    1. These are old but we have some experience with SWMMOPT and Chama at this point. So that needs to be leveraged.
  7. Look into Security for React Frontend. Authentication. SWC
    1. Chat GPT?
  1. EPANET OWA
  2. Pull a copy of the latest EPANET code from OWA.
  3. Compare with our version of EPANET code.
  4. Potentially merge their/our changes, or document if there might be any conflicts.
  5. After merging, test the code, verify that it still runs, and validate results.
  6. Make sure current EPANET Console Core and Network Model Run before I start making Code changes.
Last updated on by Melissa