How a Pool Computes the Overflow

The Overflow output of a Pool has meaning (and is computed) only if you have specified an Upper Bound. GoldSim computes the Overflow such that the flowing material (e.g., water, widgets, people, rocks) is conserved. To understand how it does so, recall the key assumption regarding the Euler integration method: The specified Rates (Inflows and Outflow Requests) represent constant rates over the next timestep.

Hence, at the beginning of a timestep, GoldSim can project what the Quantity will be at the end of timestep, compare it to the Upper Bound, and easily compute an Overflow for that timestep. To illustrate this, consider the following simple example. Assume we are modeling a pond with an Upper Bound of 3000 m³, and that at time = 10 days, the pond contains 2700 m³ of water. Let’s further assume that our model has a 2 day timestep. Assume that for times greater than 10 days, the Inflows and the Outflow Requests are constant and equal to 500 m³/day and 100 m³/day, respectively, so that the pond will fill up and start to overflow at 10.75 days.

In order to compute overflow rates accurately, by default GoldSim inserts an “unscheduled update” when the Pool reaches an Upper Bound. Unscheduled updates are timesteps that are automatically inserted by GoldSim during the simulation in order to more accurately simulate the system.

In particular, the Overflow for the example described above is treated as follows. At 10 days, GoldSim would report an (instantaneous) Overflow of zero. A new timestep (an “unscheduled update”) would then be inserted at 10.75 days when the pond would start to overflow. The Overflow at this time would actually be internally calculated as 400 m³/day. However, because by default GoldSim only reports values at scheduled timesteps (e.g., 10 days, 12 days), the Overflow will not be displayed as 400 m³/day until 12 days.

Hence, it is important to understand that the Overflow represents the instantaneous overflow rate at the reported time. You cannot assume that this rate is constant over the next scheduled timestep. That is, it would be incorrect to assume that the Overflow was zero between 10 and 12 days. In fact, at 10 days, the Overflow was indeed 0 m³/day, but it changed to 400 m³/day at 10.75 days (between the scheduled updates). Because 10.75 days is an unscheduled timestep, you would not see this in a time history plot. However, if the Overflow was integrated (e.g., using an Integrator or a Reservoir that represented the total amount of water that has overflowed), the following results would be obtained:

Note that the amount of water is properly conserved. At 12 days, the pond has been overflowing for 1.25 days (at a rate of 400 m³/day), so that a total volume of 500 m3 has overflowed. At 14 days, the pond as been overflowing for 3.25 days, so a total volume of 1300 m³ has overflowed.

Note: In some cases, it may be of interest to see the output values (such as the Overflow) that were computed at unscheduled updates. To facilitate this, GoldSim provides an option to do so (under a specified set of conditions) in the Advanced Time settings.

Note: Most spreadsheet models implicitly compute average values (e.g., flows) over a step (or the change from one step to the next). You can compute average values such as these (e.g., in order to compare GoldSim with a spreadsheet model) by using Goldsim’s Reporting Periods feature.

Note: As noted above, by default, GoldSim inserts an unscheduled update when the Pool reaches an Upper Bound. However, if desired, you can disable unscheduled updates (although it is generally not recommended). If you do so, the reported Overflow is the average rate over the next scheduled timestep and can be assumed to be constant. (This option is accessed via the Advanced… button in the Time tab of the Simulation Setting dialog).

Note: You can record when Pools hit or depart from their Upper and Lower Bounds in the model’s Run Log. This logging can be activated via the General tab of the Options dialog (accessed via Model|Options from the main menu).

The calculation of the Overflow is further complicated because the Upper Bound can be specified to change with time (i.e., you could specify this input as being time-variable). If you do so, GoldSim makes the following assumption: like the Inflows and Outflow Requests, the Upper Bound is assumed to remain constant over a timestep.

For example, if you specify that the Upper Bound varies linearly from 3000 m³ to 2000 m³ over 100 days, and simulate the system with a 10 day timestep, GoldSim will approximate the Upper Bound curve internally as a stair-step function:

The dashed line represents the Specified Upper Bound
The solid line represents the Upper Bound as simulated by GoldSim, assuming a 10 day timestep

Hence, within a given timestep, GoldSim follows the same logic outlined in the previous example to compute the Overflow for that timestep.

Note that an Overflow can be generated even if there is no net inflow of material into the Pool. This can happen if the Upper Bound decreases below the value of the Quantity. To illustrate this, consider the following simple example. Assume we are modeling a pond with an Upper Bound of 3000 m³. Further assume that at the beginning of a timestep, the pond contains 2700 m³ of water. There are no further inflows or outflows from the pond. However, assume that over the next timestep, the Upper Bound decreases from 3000 m³ to 2500 m³ (e.g., it fills up with silt).

How would GoldSim handle this? During the timestep the Upper Bound would be assumed to remain at 3000 m³. At the beginning of the following timestep, however, it would instantaneously decrease to 2500 m³. This would result in 2700 – 2500 = 200 m³ of water that would instantaneously have to overflow. GoldSim actually spreads this out over the following timestep, such that with a 2 day timestep, the Overflow over the following timestep would be 200/2 = 100 m³/day.

Note: If the Upper Bound is constant, the Quantity in the Pool will never exceed the Upper Bound. However, if the Upper Bound is changing with time, under some circumstances, it is possible for the Quantity of the Pool to exceed the Upper Bound. If the Upper Bound is exceeded (because it has changed during a timestep), GoldSim will overflow the excess uniformly over the next timestep.

Note: Although GoldSim conserves mass in these situations, this does not imply that the result is perfectly accurate. In fact, the accuracy of the result is a function of the timestep, since GoldSim is approximating continuously varying functions (i.e., rates and bounds) using stair-step functions. This approximation is discussed further in Appendix F of the GoldSim User’s Guide.

Time (days)	Reported Overflow Rate (m³/day)	Total Water Overflowed (m³)
8	0	0
10	0	0
12	400	500
14	400	1300