=======================
------------------------
Build 5.0.021 (09/30/10)
------------------------
Engine Updates
1. A code refactoring error in build 5.0.019 that resulted in no
recovery of infiltration capacity during dry periods has been fixed.
See subcatch.c.
2. The pervious area adjustment used in 5.0.019 for evaporation and
infiltration to a subcatchment's groundwater zone was corrected.
See gwater.c.
3. The accounting of evaporation loss from just the pervious area of a
subcatchment has been corrected. See subcatch.c.
4. The rainfall + runon used to compute infiltration is no longer
pre-adjusted by subtracting any evaporation loss. See subcatch.c.
5. The rate for Green-Ampt infiltration is no longer allowed to be
less than the smaller of the saturated hydraulic conductivity and
the available surface moisture. See infil.c.
6. The available surface moisture for Green-Ampt infiltration is
considered 0 if its value is less than a small tolerance. See
infil.c.
7. Evaporation and infiltration losses from Storage nodes under
Kinematic Wave and Steady Flow routing are now accounted for
properly. See flowrout.c.
8. The Pollutant Loading summary tables in the Status Report now
lists results for all pollutants in a single table instead of
listing just 5 pollutants per table. See report.c.
GUI Updates
1. The anchoring of the components on either side of the splitter
bar on the Data Browser panel was changed to insure that the
main window is displayed correctly when SWMM is first launched.
2. The incorrect display of link slopes on the study area map under
the Elevation Offsets option was corrected.
------------------------
Build 5.0.020 (08/23/10)
------------------------
Engine Updates
1. A refactoring bug that prevented SWMM from reading rainfall data
from external rainfall files was fixed. See gage.c.
------------------------
Build 5.0.019 (07/30/10)
------------------------
Engine Updates
1. The ability to explicitly model five different types of Low Impact
Development (LID) practices at the subcatchment level has been
added. Consult the LID Controls topic in the Help file for details.
See lid.c, lid.h, infil.c, infil.h, input.c, inputrpt.c, project.c,
statsrpt.c, and subcatch.c.
2. Pollutant buildup over a given landuse can now be specified by a time
series instead of just a buildup function. Consult the Land Uses /
Buildup topic in the Help index for more details. See landuse.c and
keywords.c.
3. An option was added to allow evaporation of standing water to occur
only during periods with no precipitation (the default is the current
practice of allowing evaporation in both wet and dry periods). See
climate.c, enums.h, keywords.c, objects.h, project.c, subcatch.c,
and text.h.
4. Storage node losses from evaporation and infiltration are now computed
directly within the flow routing routines to produce better
conservation of mass. See objects.h, routing.c, dynwave.c and node.c.
5. The check to see if flow in a link should not exceed the normal flow
now uses just the upstream Froude number rather than both up and
downstream numbers. See dynwave.c.
6. The maximum trials used when evaluating the flow and head equations at
a given time period for dynamic wave routing was increased from 4 to 8.
See dynwave.c.
7. The Ponding calculation for dynamic wave flow routing was changed once
again to obtain better continuity results. The depth in a surcharged
node that can pond is not allowed to rise higher than just beyond full
depth in any single time step. After that, its change in depth is
determined by the node's ponded area. Similarly, the depth of a ponded
node is not allowed to drop more than just below full depth in any
single time step. See dynwave.c and node.c.
8. For Kinematic Wave and Steady Flow routing, a node's ponded area is
no longer used to infer a ponded depth when a node floods with Ponding
turned on. Instead, the water depth is simply set to the node's maximum
depth and the ponded area parameter is simply used as a indicator as
to whether the node can pond or not. (This differs from dynamic wave
routing where the ponded area directly influences ponded depth through
the solution of the momentum and flow conservation equations.) See
flowrout.c.
9. As a consequence of the preceeding update, the Node Flooding Summary
table in the Status Report no longer displays the maximum ponded volume
in acre-inches (or hectare-mm). Instead it displays the maximum ponded
depth (ft or m) for Dynamic Wave flow routing or the maximum ponded
volume (1000 ft3 or 1000 m3) for other forms of routing. See stats.c
and statsrpt.c.
10. The groundwater mass balance equations were returned to the form they
had in release 5.0.013 since they were not correctly accounting for
the water volume transferred between the saturated and unsaturated
zones due only to a change in the water table depth. See gwater.c.
11. Controls based on flow rates now properly account for the direction of
flow when they are evaluated. This may require users to add an extra
condition clause to a rule that only applies for flow in the positive
direction (e.g., AND Link XXX FLOW >= 0.0). See controls.c.
12. The Villemonte correction for downstream submergence is now also used
for partly filled orifices (instead of just for weirs). See link.c and
dynwave.c.
13. A missing term in the equation used to check for submerged inlet
control for Culvert conduits was fixed. See culvert.c.
14. If a non-conduit link is connected to a storage node then its
contribution to the node's surface area is now ignored. See
dynwave.c.
15. The automatic adjustment of the maximum depth of a link's end nodes
to be at least as high as the link's crown no longer applies when
the link is a bottom orifice. See link.c.
16. A fatal error message is now generated if a conduit's entrance,
exit, or average loss coefficient value is negative. See link.c.
17. Requests to do internal routing of runoff between impervious and
pervious sub-areas of a subcatchment when only one type of sub-area
exists are now ignored. See subcatch.c.
18. The check on the error condition of a node having both incoming and
outgoing dummy conduits was modified so as not to get fooled by
Outlet-type links. See toposort.c.
19. The Ignore Snowmelt switch is now internally set to true whenever
there are no snow pack objects defined, so that precipitation is not
mistakenly converted to snow for a project with temperature data.
See gage.c and project.c.
20. When reading min/max daily temperatures from a climate file, the
values are now swapped if the minimum is greater than the maximum.
See climate.c.
21. When the Hargreaves method is used to compute an evaporation rate
from daily temperature values, negative rates are no longer allowed.
See climate.c.
22. Several bugs that prevented SWMM from detecting and reading Canadian
DLY02/04 climate files correctly were fixed. See climate.c.
23. An error message is now generated if a time series used for rainfall
is also used for another purpose in a project (since it will cause
the two uses to be out of synch). See error.h, error.c, gage.c,
climate.c, control.c, and inflow.c.
24. An error message is now generated if two Rain Gages with files as
their data source use the same Station IDs but different names for
the data file. See rain.c, error.h, and error.c.
25. When zero rainfall values appear in a rain file or time series they
are now skipped over and treated as a dry period, the same as would
occur had they not been entered in the first place. See gage.c.
26. A bug that caused the data in an evaporation time series to be out
of synch with the simulation time clock has been fixed. This only
affected evaporation data supplied from time series and not monthly
average data or data from climate files. See climate.c.
27. The water quality mass balance now correctly accounts for any initial
mass in the system created by using a hot start file. See massbal.c.
28. For models that only compute runoff and have a reporting time step
less than the wet time step, the latter is internally set equal to
the former. See swmm5.c.
GUI Updates
1. The Data Browser was updated to include the newly added Low Impact
Development (LID) objects and new dialog forms were added to specify
LID design data and their placement within a project's subcatchments.
2. You can now open a project input file by dragging it from Windows
Explorer (or the Desktop) and dropping it anywhere in SWMM's main
window.
3. A new checkbox was added to the Evaporation page of the Climatology
Editor to include the option to evaporate only in dry periods.
4. The choices for Function type on the Buildup page of the Land Use
Editor were extended to include an external time series (EXT).
5. SWMM will now continue to use the period (".") as the decimal
separator even if the user or the system changes the Windows Regional
Settings while the program is running.
6. A new installer program is now used that places the example data sets
in the user's My Documents\EPA SWMM Projects folder.
7. The components below the horizonal splitter bar on the Data Browser
panel were placed in their own panel component so that the splitter
would work correctly under Windows 7.