I am somewhat experienced using SWMM, but a new user of StormNet. I am having difficulties modeling intake bypasses. Specifically, I am working on a large basin with cascading bypasses all of which appear to be working as expected, but whenever I try to add a bypass to the uppermost intake in my model I repeatedly receive an "ERROR 600 : On grade Inlet Inlet-34 does not have two outlet links. At least one stormwater sewer pipe and a bypass gutter link must be defined."
This is not the case. It is set up just like the rest of the bypasses in the model. Is there something that I am missing? Also, there seems to be some variability to the order in which I have to enter the data. For example, if I have the intake chosen as at a sag when I create the bypass link and then change it to on grade the model appears to let me create the bypass, but the analysis fails and the Error 600 is displayed, but if I have the intake as on grade and then create the link it won't recognize it as a bypass link at all. In either case if I go through the connections everything is listed as connected properly, but then the "Error 600" reappears and halts the analysis. I am waisting a lot of time going through endless iterations and I'm tempted to go back to plain old SWMM.
Can't tell if you are running into a bug or not. Note that there have been a lot of improvements that have been added to the software, and there is always that "possibility" that a software developer should have "zigged" instead of "zagged". If so, I will "zap" them :).
If you can, please send me your StormNET model file for me to review. Also, make certain you have the latest release of StormNET. The current release is 4.11, but we are (hoping) to release an update next week (has HEC-1 implemented in it, and a bunch of other nice "goodies").
Chris,
I am using the newest release. I have tried several different variations in an effort to model the bypass. I sometimes receive an additional error: "ERROR 171 : Curve Inlet-34-BYPASS has its data out of sequence."
Where is a curve inlet defined, and what data is out of sequence? I am attaching my StormNET model file as it is now.
Note that I looked at your attached StormNET model. Note that the current release of StormNET cannot have storm drain inlets that have two separate outlet (downstream) drain pipes. If you look at Inlet-34, you have links Con-31 and Con-23 defined as downstream pipes that route the flow captured at Inlet-34. Con-47 is defined as the roadway by-pass link.
The way to get around this is to add a computational nodal point (i.e., Junction) just downstream of Inlet-34 and have links Con-31 and Con-23 connect to this computational point. Then, have a short pipe or direct connection between Inlet-34 and the computational point. The invert and the top of the computational point can be the same as the pipes it is connecting to.
We have planned for a future version of StormNET to handle multiple downstream outlet drain pipes from inlets. For the mean time, however, you need to model it as I have described.
If you continue to face problems, please let me know.
I've done as you suggested, but then I receive an error that says that you cannot have more than one direct link connected to a node. If I use a short length of pipe to my computational node it will perform the analysis, but I do not believe that it is accurately modeling the upwelling and overflow that I am after since it merely moves this flow to the computational node that is no longer connected to the overflow channel at Inlet 34.
I have been unable to locate in the product documentation these kinds of limitations. However, I do seem to recall some of these being mentioned in the SWMM documents.
Note that EPA SWMM does not have an equivalnet element that matches the hydraulic capabilities of the inlet elements that we have implemented. However, if you upload your model to me, I will look at it and see what is wrong with it.