You are currently reviewing an older revision of this page.
When looking at a Time History (graph) or animating a profile in the Transient Results Viewer, changes are seen (for example a change in HGL or flow) in the very beginning of the transient simulation, before the transient event occurs.
This is referred to as an "Initial Surge" or "Spurious surge" and is often an indication of a discrepency between the initial conditions (steady state) and the first transient timestep. Essentially, HAMMER see that a change in momentum has occured in the very first timestep, and graphs and profiles display the resulting transition (albeit typically small). In some cases this manifests itself as a small "wiggle" or "jumpiness" in the HGL before the real surge event occurs (such as a pump shutdown or valve closure), while in other cases you may see a noticeable drop or spike in HGL in the first timestep. Addressing this problem is important, to ensure that the starting conditions are in a true steady state condition.
1) First, to properly check for an initial surge, make sure that your "real" transient event is configured to begin a few seconds after the start of the simulation. For example if you are simulating an emergency pump shutdown, use a "time (delay until shutdown)" of five seconds. This way, you can check to make sure that the first five seconds of the transient simulation remains steady, before the pump shutdown occurs.
2) If you see an initial surge occur before your "real" transient event, check for any obvious problems with the model configuration, in the general area where you see the initial surge occur. For example pump status that does not match with the transient pump type, or any of the issues described in the articles in the "See also" at the bottom of this page. Also check your User Notifications list for any clues.
3) If the source of the initial surge is not clear, you should next utilize the Transient Output Log to identify any specific elements to focus on. Navigate to Report > Transient Reports > Analysis Output Log (referred to as the "Transient Analysis Output Log" in older versions). This will open a text-based report in WordPad. Press CTRL+F (Find) , type in "initial surge", and it will jump to the relevant section of the report, as seen in the example screenshot below:
Note: in the Transient Calculation Options, the Initial Flow Consistency and Initial head Consistency determine the thresholds for displaying an endpoint under the above section in the report. Meaning, a change in flow or head between the initial conditions and the first transient timestep, that is above the values entered in these calculation options, will cause the pipe endpoint to appear in the list as the cause of an initial surge. The reason is because there can sometimes be a small movement in the first timestep that is expected, such as from a change in tank level for a tank that was filling or draining in the initial conditions.
Initial surge or transient event after adding a surge tank to a model.
Problems with pump in transient simulation when the relative speed factor in the initial conditions is less than 1.0
Change in results before turbine load rejection occurs
Initial surge when using turbine load acceptance operating case