HEC-DSS and HEC-DSSVue Planned Activities
| Activity | Funded (Y/N) | Cost | Delivery Date |
|---|
| Tech Support - Assistance with Migration to HEC-DSS 7 | Y | $50,000 (HEC labor) | |
| Maintenance of Shared Code - including SHEF import/export | Y | $45,000 (HEC labor) | |
| Planning and Prototyping the Future of HEC-DSS with Java | Y | $50,000 (HEC labor) | |
| Improving the Future of HEC-DSS with Python | Y | $30,000 (HEC labor) | |
Assistance with Migration to HEC-DSS 7
A major effort will wrap up this year as the team retires HEC-DSS 6 and finishes the migration to HEC-DSS 7. This effort will help migrate all software packages within CWMS 3.4 to HEC-DSS 7, as the CAVI now defaults to using version 7 files. The core work is completed, and during CWMS 3.4 testing we will make additional updates as necessary. This effort completes a 10+ year effort of developing HEC-DSS 7, which added features and removed size limitations of HEC-DSS 6 while also removing dependency on legacy Fortran code. Field support will be provided with this effort to ensure all offices transition to using HEC-DSS 7 files as they migrate to CWMS 3.4 after the release.
Maintenance of Shared Code
The team will continue working on improving the SHEF import and export functionality in HEC-DSSVue this year. SHEF import and export functionality is being converted from Fortran to Python. Using Python for SHEF allows both HEC-DSSVue and CWMS cloud services to use the same code. The legacy Fortran code was not practical to maintain.
Planning and Prototyping the Future of HEC-DSS with Java
We are planning on updating both the API and back-end technology for HEC-DSS. The current Java design has a circular dependency; the java code must know the DSS data structure, and the C code (HEC-DSS) must know the Java data structures. The new API is compatible with all languages. Additional API's will be language specific, building upon the new API (RAS 2025 is using a .net specific API for C#). The team will create a Java and python specific APIs as well. Another benefit of the new prototype is the ability to use off-the-shelf technology for data storage instead of the current custom HEC-DSS storage.
Improving the Future of HEC-DSS with Python
The team will work on developing a Python API for HEC-DSS, which will allow users to write scripts using Python once the work is complete. Users have been asking for the ability to use Python instead of Jython, as Python has many libraries that allow plotting, math, etc. beyond the limited Java tools available in Jython.
CWMS-Vue Planned Activities
| Activity | Funded (Y/N) | Cost | Delivery Date |
|---|
| Maintenance Contract | Y | $20,000 (HEC labor) $75,000 (contract) | |
| Standalone Release of CWMS-Vue | Y | $20,000 (HEC labor) $75,000 (contract) | |
| Improve the DevOps Environment for CWMS-Vue | Y | $50,000 (HEC labor) | |
| Technology Transfer - Webinars and Tutorials | Y | $20,000 (HEC labor) | |
| Technology Transfer - User's Manual Updates | Y | $15,000 (HEC labor) $10,000 (Field labor) | |
Maintenance Contract
The planned maintenance work for CWMS-Vue includes continued performance improvements to load data more quickly.
Standalone Release of CWMS-Vue
The team is planning a standalone release of CWMS-Vue in FY25 after CWMS 3.4 is released. This will allow the team to release new versions of the software quicker to the field to provide new features on a more timely schedule.
Improve the DevOps Environment for CWMS-Vue
The team will continue to build out manual tests and investigate an automated testing framework.
Webinars and Tutorials
Webinars are targeted to cover new capabilities released in CWMS-Vue for CWMS 3.4. Topics might include read/write capabilities using CDA and enhancements to the Graphical Editor.
User's Manual Updates
The team is currently working on a new, standalone version of the CWMS-Vue User's Manual. As new features are added to CWMS-Vue, the team will work on updating the User's Manual and other documentation.