If you're experiencing a problem with HEC-ResSim that you believe may be an error in the computations or the user interface, please follow the instructions below. See a good example.

Please include the following information in an e-mail, and send it to hec.ressim@usace.army.mil:

1. Contact Information: Name, Phone Number (optional), and E-mail Address.
   
   
2. Program Version: What version of the software are you using?
   
   
3. Operating System: What operating system are you using?
   
   
4. Problem Descrption: Please give a detailed description of the problem. include screen shots, text of error messages, or other information produced by the program that illustrates the problem. Sometimes, a picture really is worth a thousand words. Alt-PrtScn will copy the active window to the “clipboard”. You can then paste the graphic into your email.
   
   
5. Steps to Reproduce: If the problem is reproducible, please list the steps required to re-create the problem. If it is not reproducible (only happened once, or occasionally for no apparent reason), please describe the circumstances in which it occurred and the symptoms observed. Because it is much harder for us to fix problems that don’t seem to have consistent, reproducible behavior, a detailed explanation of the situation and program behavior is key.
   
   
6. The Watershed: If the problem occurs in only one of your watersheds and not in another, we may need a copy of the watershed in order to track down the bug. See the document “How to Backup HEC-ResSim Watersheds” for instructions on producing a zip file of the watershed. Create this zip file as soon after the problem occurs as possible (before you’ve had a chance to “fix it” or work around it). If the zip file is less than 5 Mbytes, you can attach it to your email. If it is larger than what can be sent via email, please indicate in your email that you have created the zip file. We will contact you with an ftp site where you can place it for us to retrieve. All model data submitted is considered confidential and is not used for any purpose other than program testing and debugging.

• Which module you were working in?
• Which network and/or alternative(s) exhibit the behavior?
• Which simulation you were working with (if relevant)?