Login/Accounts 

No significant modifications or issues from previous CWMS version.

Scripting 

Wild card imports are generally not allowed.  See details here:  Scripting.

Team Modeling 

In CWMS 3.2.2 and 3.2.3, sometimes files will not get uploaded (seems to be mostly around locked dss files associated with HMS model). If you encounter this, wait a few minutes (the lock on the file should release) and then force upload the watershed again and the files should be uploaded.

In all versions, check the storage on /var/tmp if experiencing problems uploading to master watersheds hosted on CWMS servers.    During initial upload the watershed files are staged in a scratch folder under /var/tmp, which has only 10G total space in standard T7 configuration.    The files are cleared out of /var/tmp before the synchronization process finishes, but the upload will fail if available space runs out while staging.  Avoid performing simultaneous uploads among users sharing the server, especially of large watersheds.     

Watersheds upgraded to CWMS 3.2.3 and synchronized to the master watersheds will no longer be usable by colleagues running CWMS 3.2.2.  Please coordinate with teammates regarding updating master watersheds.  Note that master watersheds saved on "Windows Network" servers could be saved with the same watershed name in separate folders for CWMS 3.2.3.  Master watersheds saved on the CWMS server must be renamed to be saved separately from the CWMS 3.2.2 version of the watershed.  Also, discuss the team plan for master forecasts.  For offices that continue from day to day using "rolling" forecasts, note that opening an existing master forecast will cause the individual models to be upgraded (as they were with the watershed).  Some offices may prefer to simply create a new forecast.  

If you desire to use the CAVI dashboard with a team modeling watershed, you will need to delete some files on the master watershed to ensure the dashboard can be used amongst several computers (issue HEC is looking into and is denoted in the Dashboard area).

If the watershed properties CWMS server differs from the CWMS server connected to (prompted when initially opening CWMS), this can cause some issues with the team modeling if using a Master Watershed location to the CWMS server. Please ensure that both the server logged into and the server in watershed properties are the same.

There have been instances of watersheds that utilize team modeling that take additional time to open (reported upwards of 30-minutes) while teleworking.

When setting the path for a "Windows Network" Master Watershed Folder, utilize the ellipses on the right hand side of the dialog. If you copy and paste the path and it uses the network path drive letter, this can cause some slowdown compared to having the actual path. In the example below, if the user denoted the path starting "M" instead of "hec-netapp2...", this could cause a slowdown in communicating to the drive. If you use the ellipses, this will use the proper notation.

 CAVI

  1. When the CAVI freezes or becomes unresponsive and the user wishes to close CWMS, make sure to use the HEC-RTSTaskList.exe that is found within the CAVI folder of CWMS.  This program ensures that all programs associated with CWMS are closed.  Using Window's Task Manager does not always catch all the programs, and "zombie" processes can lead to errors such as "HMS: ERROR 10013: Another instance of HEC-HMS is currently using project…”.   Similar issues might arise if the user closes the console window of CAVI.
  2. Deleting/archiving a forecast sometimes does not occur as anticipated. This can be caused by the dss files still connected to the CAVI. If you wish to delete a forecast, try moving away form the forecast and then delete the forecast (https://discourse.hecdev.net/t/deleting-a-forecast-file-structure-still-exists/1933/4 [You have to be logged in to see this post]).
  3. Contact Joan Klipsch or Shannon Larson if you wish to use the CAVI Ensemble Compute (functionality included in CWMS 3.2.3 but not final).
  4. Having Program orders with both MFP and MetVue can cause issues.  It is recommend to avoid program orders with both, and use separate CWMS watersheds for MetVue and MFP. 
  5. Multiple CAVI instances are supported in this version of CWMS; however, both instance write to the same log location, this can cause issues if you desire to view the log files once the watershed is closed.
    1. There is a CAVI.config modification to create a unique log per each CAVI instance (this will cause for a large amount of log files, so you might need to go to log location to cleanup periodically)
      Add vmparam -DLogFileHasPid=true to the CAVI.config file.