HydroCAD® Stormwater Modeling - Since 1986
Dealing with Oscillations
What are oscillations?
Oscillations are rapid changes (fluctuations) in the outflow hydrograph. This occurs when the projected outflow overshoots the actual value, causing the flow to change rapidly back-and-forth (oscillate). HydroCAD automatically checks each routing calculation to see if oscillations are present, and generates a warning message when required. The presence of oscillations generally indicates that the routing results are not valid and should not be relied upon.
What causes oscillations?
Oscillations are generally caused by an abrupt change in the stage-storage or stage-discharge curve. If these changes are too abrupt, the routing procedure can not track the curve properly, causing an overshoot in the calculated outflow, which can oscillate back-and-forth around the correct value.
Why am I getting so many warning messages?
With a dynamic routing, an oscillation in one node will propagate downstream and upstream throughout the entire drainage network, often triggering additional warnings in other nodes. Therefore you should resolve all oscillation warnings before attending to other warnings or results. Correcting the source of the oscillations will often resolve many other warnings.
Having a closer look
How do I correct oscillations?
If you get an oscillation warning, click on the message for additional details. In many cases, oscillations are resolved by setting a smaller dt, or perhaps by setting the Finer Routing parameter to 2 or 3. This causes the program to update the routing calculations more frequently, thus preventing the overshoot that typically triggers the oscillations.
Oscillations can also be triggered by overfilled storage, or by other conditions that cause an abrupt change in any stage-storage or stage-discharge curve. Resolving the cause of the oscillations will produce better results than "masking" them with the Finer Routing parameter.
Oscillations can also occur when using an exfiltration velocity with a flat-bottomed pond, as shown on the example above. This situation can usually be corrected by setting the exfiltration Phase-in Depth to to a small non-zero value, such as 0.01 feet.
What if I still get oscillations?
If oscillations still occur after making several adjustments, try to determine where the oscillations are originating. This can be done by disconnecting parts of the drainage system to see if you can isolate the problem. Often you will find a particular node that is the source of the problem. You may then be able to devise an alternate way to model that part of the watershed, such as correcting an overfilled storage condition, or combing adjacent storage volumes into a single pond.
Always keep the model as simple as possible in order to meet your immediate modeling objectives. Test as you go and fix any problems ASAP. More tips here.
What if the hydrograph looks OK?
If you don't see a clear oscillation pattern (as discussed above), the results may be acceptable, in spite of the warning message. This can occur in systems with complex routing behavior, such as tailwater, where additional peaks can be introduced into the hydrograph during the routing process. If you cannot see the oscillations visually, or there are only a couple of additional peaks, the results may be acceptable, and the oscillation warning can be ignored.
If a finer routing value of 2 or 3 doesn't resolve the situation, set the finer routing back to 1 and pursue other remedies. Do no leave the finer routing at 2 or 3 unless this actually solves the problem. Setting the finer routing above 4 is rarely effective, and can actually compromise the results.
Reducing the time step (dt) is usually the first approach to addressing oscillations. This will generally increase the accuracy of the calculations, without any adverse effects other than a longer calculation time. The minimum dt of 0.01 hours can be used for most situations. The minimum value can be reduced further by customizing the TimeInc parameter on the Settings|Units screen. However, smaller values rarely offer any benefit over the default minimum, and will significantly increase calculation time and memory requirements.
Copyright © 2013 HydroCAD Software Solutions LLC (privacy) (legal notices)