CivilStorm

Question

I have a catchment connected to an outfall node. After running the model the report option outputs N/A for all results. I was specifically checking to see if the catchment peak flow out matched the outfall node peak flow in. The graph and data table options work as expected for the same outfall node, so it appears the model is working. 
 Other outfall nodes connected to a conduit from a pond outfall do not seem to have the problem and report data as expected. 
 Is there a solution to make the report function not output N/A for catchments connected directly to nodes?

Craig Calvin · Answer

The user notification "Storage Multiplier must be greater than zero" is referring to the property below. In CONNECT Edition you can get to this dialog by going to the Components tab, select Stormwater Controls, then click Storage Chambers. Another way to access this dialog is to double-click on the pond, click the dropdown arrow in the Storage Chamber input field, then select <Edit Storage Chambers>.

Jesse Dringoli · Answer

Hello David, Regarding the maximum flow field in the outfall - you'll need to add a channel and cross section like in the below screenshot. You may still see some difference between the peak flow at the outfall vs. the catchment, due to attenuation in the channel, or differences between the calculation timestep and output increment. Try setting them equal in the calculation options. 
 Regarding the storage chamber issue - it does look like there is an issue there. It appears to be validating on a field that does not apply for that type of chamber. We will look into this and get back to you shortly.

Jesse Dringoli · Answer

Hello Tony, 
 I looked into the history of this and the issue (reference # 716231) was fixed in a patch for versions 10.00.00.45 and 10.01.00.70. 
 Please check which version you are using, by going to File > Help > About. Patches for previous versions are included in newer releases, and there is a later release available: 10.02.00.55. If you're on 10.01.00.70 or earlier, upgrading to fix the problem. If you are on 10.01.00.70 or earlier and cannot upgrade, please let us know and we'll contact you regarding a patch.