CWMS-Vue Known Issues Moved

Please note that with the release of CWMS-Vue 4.0, CWMS-Vue Known Issues can now be found at CWMS-Vue Release Notes & Known Issues v4.2.0



Below is a list of Known Issues identified in HEC-RTS 3.6 and their current status. Issues with a status of Resolved have been addressed and will be included in the next version of CWMS.


SummaryComponent/sPublic DescriptionKeyPublic Status
Forecast Results not Visible in HEC-FIA for a Grids-Only ComputeHEC-FIAThe result reports of a successful HEC-FIA Grid Only Alternative simulation are only available to view from the CAVI, and not within HEC-FIA.

Work-around is to make sure to view the reports from within the CAVI.		CWMS-1235Future Version
When run from RTS, HMS will "compute" when outside of stage-discharge curveHEC-HMSIssue:
If the flow exceeds the elevation-discharge curve in HEC-HMS, HEC-HMS messaging will generate an Error but in HEC-RTS, it will note that the compute was successful (even though the HEC-HMS compute does not truly finish). If there are models following HEC-HMS, they will try to compute.
The stage that gets passed is old stage data in the model (either in the forecast.dss or in the base HEC-HMS model results).

Workaround: To ensure that no wrong results are provided: delete prior model results in your base HEC-HMS model. This workaround assumes there are no results in the forecast.dss file.		CWMS-2380In Progress
Missing Observed Stage Causes HEC-HMS Model Compute to FailHEC-HMSHEC-HMS is failing to compute when missing stage data that is not necessary for the compute.

Temporary workaround: Remove stage data that is linked to the compute that is not present in the forecast.dss.

Resolved in HEC-HMS 4.14		CWMS-2314Resolved
HEC-HMS holding onto .dss files during Teaming uploadHEC-HMS, Team ForecastingHEC-HMS is locking dss files associated with the models. This stops HEC-RTS from pushing the dss files to the master location.

Temporary workaround:
Upload all can be used to force all HEC-HMS. Select the HEC-HMS folder in the model sync and select the Upload All Files.		CWMS-2185Future Version
HEC-MetVue Computed Output Temperature Dataset doesn't cover entire extents of the clipping polygonHEC-MetvueIssue: Handling of SHG gridded output dataset clipping sometime clips just inside the input basin shapefile and results with a few missing grid cell values along the basin perimeter.

Workaround: Use ArcGIS to create a buffered version of the basin shapefile. Use a buffer of 5000 meters.		CWMS-2227Future Version
HEC-MetVue data display only (not computation) do not use non-GMT watershed settingsHEC-Metvue, MetVuePluginIssue: For non-GMT CWMS watersheds (i.e. watersheds built with a local time zone), HEC-MetVue data displays do not currently apply the local time zone by default unless the user sets Time Zone read overrides in the input data Map Windows.

For Computation on the other hand, HEC-MetVue does use the CWMS watershed's Time Zone setting by default, so HEC-MetVue and HEC-HMS computations handle the local time zone appropriately. This issue only affect the display in the CAVI but the not the computations

Workaround: To fix the display issue in the CAVI Forecast Map Window, the user would have to set time zone overrides for the HEC-MetVue Output Map Window(s).

The user can also apply the time zone overrides in the setup module especially so that they carry over to new forecasts. The user would have to create the results Map Windows manually in the setup Module to match the output dataset's name from the alternative editor and append the alternative's key. For example if the output dataset name in the HEC-MetVue Alternative Editor is called "Precip" and the alternative key is "N", the user should name the results Map Window "Precip (N)".		CWMS-2057Future Version
HEC-MetVue Preprocessing not Triggering for some forecast runsHEC-Metvue, MetVuePluginIssue: Having the very first Forecast Run with no HEC-MetVue alternative throws off preprocessing for HEC-MetVue alternatives down the list of Forecast Runs.

Workaround: Until a new version of CWMS with a fix, the workaround is to ensure that the first Forecast Run contains a HEC-MetVue Alternative. One can also use the Forecast Run Editor to Save the non-HEC-MetVue Forecast Run as a new Run, which will put the copy at the bottom of the list. So when it comes to adding the forecast runs in a new or existing forecast simulation, that would guarantee that a HEC-MetVue Forecast run is at the top of the list.		CWMS-2115Future Version
Improve HEC-MetVue Preprocessing messages for INST-VAL data fillingHEC-MetvueMetVue Preprocessing messages need improvement to list out all filling methods used for INST-VAL gridded records that have missing data a the start and/or end of the time window as well as other instances of missing data in the middle of the time window.CWMS-2068Future Version
CWMS - HEC-RAS geometry overwritten when selecting second planHEC-RASIssue: When a CWMS Forecast Run has two HEC-RAS alternatives in the program order that contain different geometries, the second geometry can be overwritten by the first if the user does not wait until the geometry completely loads.

Workaround: When switching between the two HEC-RAS Geometries, the user must wait to open the geometry until the second HEC-RAS Plan finishes loading (The spinning loading icon disappears). If the user tries to open the HEC-RAS geometry before loading is finished the overwrite may occur.		CWMS-2249Future Version
Closing some HEC-RAS forms with File > Exit option returns "Run-time error '5': Invalid procedure call or argumentHEC-RASIssue: When launching the Geometric Data editor or Steady Flow Data editor in the Setup or Modeling tabs, then closing the form using the File > Exit option, HEC-RAS returns the following error: "Run-time error '5': Invalid procedure call or argument".

Workaround: Close the dialog using the X in the top right corner.		CWMS-786Future Version
When using the Workflow Buttons - HEC-RAS Geometry Overridden when two HEC-RAS Alternatives are included HEC-RASUsing the Workflow Buttons with multiple HEC-RAS Alternatives in a single forecast can cause the first HEC-RAS geometry to overwrite the other.

Workaround - Recommended to not use the workflow buttons in these forecasts. Ensure that the correct HEC-RAS alternative is selected by launching HEC-RAS and starting the compute directly from HEC-RAS.		CWMS-326Future Version
Map Elements Fail to Draw on Creation of a New ForecastMapping and LayersIssue: When creating a new forecast, map elements for HEC-HMS and HEC-ResSim will sometimes fail to draw. When this occurs, there will also be an error message: HMS command: "getGraphicElements": Command failed: No HEC-HMS Project.
If this occurs, you can get the map elements to appear by either changing the map window size, zooming in/out, or panning. A second option is to right-click on the forecast and select "Display in Map"		CWMS-2520In Progress
Model Linking does not update when an HMS gage pathname part is editedModel LinkingIssue: Currently, HEC-RTS does not update the DSS pathname list in the Model Linking Editor if a change is made to the DSS Pathname in the HEC-HMS project. This will be improved with the combination of HEC-RTS 3.6 and HEC-HMS 4.14. when HEC-HMS 4.14 is released.

Workaround: From the Model Linking Editor, the user can browse to select the DSS Pathname desired. However if the user clicks on the modified entry again in the Model Linking Editor the DSS pathname will reset to the original linking. (the resetting issue has been resolved in HEC-RTS 3.6).		CWMS-2444Future Version
Master Watershed download failing being connected to CDATeam ForecastingDownloading a master watershed while connected to CDA in HEC-RTS/CWMS will result in an error.
A workaround is to be connected to local or a CWMS database before downloading a master watershed.
Target Version to have this resolved is 3.7		CWMS-2581Future Version


Below is a list of HEC-ResSim specific Known Issues identified in HEC-RTS 3.6 and their current status. Issues with a status of Resolved have been addressed and will be included in the next version of RTS. While this list has been updated to only cover Known Issues in ResSim that a Water Manager is likely to come across, a full list of known issues in the latest release of ResSim can be found here.

SummaryPublic DescriptionKeyPublic Status
Flow Computation Method - Program Determined Not Always Working

Issue: HEC-ResSim compute in the OSI can occasionally fail when period average data is used by variables but was found to run after second compute attempt.

Workaround: Use INST-VAL for input time series

RSS-1048Future Version
API Elev-Zone Model Variable in State Variable being added wrong

Issue: When you add Elev-Zone model Variables to a State Variable, it adds "reg" which causes the State Variable to fail at compute.

Workaround: When adding Elev-Zone, remove the "reg"

RSS-1495In Progress
System Downstream Control Operations fail to work correctly when one reservoir surcharges

Issue: If a dam is surcharging and the DS control rule is not in that dam's surcharge zone, the other dams in the system don't see it's release and act as if it's releasing zero.

Workaround: Two steps need to be taken:

  1. Add system operations rule to the "surcharge zone" 
  2. Reservoirs operate in a level 1 or level 2 condition (different downstream control flow) based on if any reservoir enters their upper flood control zone.  A state variable computes this "level" and sets draft rates.  Logic was added to the state variable for a "level 3" condition, which forces the other reservoirs to shut off releases via the addition of a 'level 3 shutoff' rule in the level 1 and level 2 zones at the other dams.
RSS-1275Future Version
Missing model variables in API

Issue: After transitioning from ResSim v3.5.1 to v4.1.2, may notice that a variety of model variables are missing in the State Variable API

Workaround: Open the Alternative Editor and select an Alternative for that Network. Reopen the State Variable Editor and the missing model variables will be present in the API.

RSS-1472In Progress
ResSim Model Linking in Default is wrong

Issue: When opening the Model Linking editor, the Location/Parameter pathnames could show incorrect time series in the Setup Module. Creating new forecasts while these are outdated, will carry the old pathnames into your forecast. HEC-RTS 3.6 includes HEC-ResSim 4.1.2. There was an update to how Variants are being handled by ResSim in v4.0. For some watersheds, the .linkages files were not updated to reflect changes in the base watershed. When these watersheds are opened in HEC-RTS 3.6, the Model linking editor defaults to using ResSim-default pathnames. 

Before Migrating to HEC-RTS 3.6

  1. Open your watershed in CWMS 3.5 and verify that there are no blank fields in the Default ResSim variant. If there are, update them to match the most used ResSim RTS alternative. 
  2. Confirm model linking before migrating to HEC-RTS 3.6. 
    1. Open your model in CWMS v3.5
    2. Make sure that you are on the Setup tab and then launch the MLE.
    3. In the MLE, select the Forecast Run and the ResSim model.
    4. Scroll down to the bottom of the MLE and select one of the time series that is a Lookback parameter and toggle one of the "Input From" drop downs.
    5. This will make the Apply button go live. Select Apply.
    6. This will update the .linkages

If already migrated to HEC-RTS 3.6:

  1. Select the Forecast and then "Get Linkages From". Select another forecast run from the list that has the correct pathnames
    or
  2. Remap the model linking from the Setup Module. 

RSS-1519


Missing Reservoir Guide Curves

In ResSim versions prior to 4.0, it was possible to have no Guide Curve set, but in 4.1, a check was added to ensure a Guide Curve had been set at all reservoirs. For the 4.1.1 release it was identified that this check was unnecessary and it was turned back off. In one model that was failing to compute, adding a guide curve resolved the compute issue. Was unable to reproduce that error in other models. Recommended best practice is to add a guide curve to all reservoirs even it it's just above the inactive zone.

RSS-1506

In Progress
API - Elev-Zone Model Variable in State Variable being added wrong

Issue: When you add Elev-Zone model Variables to a SV, it adds "reg" which causes the SV to fail at compute.

Workaround: When adding elev-zone, delete the "reg" after it is added.

RSS-1495

In Progress


 

1 RESOLVED  -  Issues are fixed and will be available in the next release of their applicable software.

2 IN PROGRESS  -  Issues are currently being worked on.          

3 IMPROVED  -  The next version includes an incremental improvement but not a total fix

4 FUTURE VERSION  -  This requires a structural change or major development. The team will add it to a future version if funding permits.