2026-04-06
2026-04-06
Updating CDA + Gate Settings/Changes + Water Contracts (discussion)
Versions:
- 2026.04.03-develop
Topics:
- Updating CDA On District T7 (Use Mitch's new script, it takes release as an argument)
- Location Kind Sub tables correction -> ADR being formed. Kinds possibly set but the record not placed in (projects) table?
- Scott -> No Data in Dev, possibly not reading env file on build OR bad field in file
- Newest CDA requires Java11, ticket with IT to update your tomcat
Outlets / Gate-changes endpoints in CDA. "Is there anything out there that explains the benefit of using these vs sublocations and timeseries? We are all setup without using these and I'd like to know what the advantage there would be in switching at this point if any."[Peter M]
- Background comps for regi-headless to translate from TS based gate settings and the gate change/settings schema tables (CWMS)
- gate change/settings have more developed metadata, why you do the gate change, when GC is created all settings are recorded at the time of that change (flow/notes/etc)
- With timeseries, no enforcement of setting recorded for all the gates at that particular time. You rely on data acq / app behavior to ensure all settings are captured at that time
- Carrying Forward -> Changes/settings/turbine settings/water supply (pumpages) all changes are BoP (Beginning of Period) set gate to setting, flow continues until you make next change in future. (Current effort, make container of regi comps)
- MVP -> If you use /projects/office/project-id/gate-changes does not make a TS. OpenDCS thoughts Backfill Irregular Timeseries Comp 1280 FillForward Algorithm 349
- Peter -> Identical schema for turbine settings/changes and water supply (Getters/Setters)
Water Contracts (Discussion) : [Peter M] -> Contracts are related to "Pump-Accounting". Water Contracts are pertinent data.
- Water user can have 0 to Many contracts, must start with water
Issues:
- water-user endpoint for swagger does not have {project-id} linked to input