|
|
Similar to the functionality available InfoWSWMM where you are able to define a start date and time for the simulation and a start date and time for results. This allows initial phases of the model simulation to be ignored by the results without needing to set up individual hotstarts for every network and scenario (saving a lot of time!)
My team is running a lot of TSR simulations at the moment for annual CSO spill counts, with model verification runs to get the model to match EDM spill counts, then baseline and options models to try to reduce spill counts. Since EDM spill numbers are given per calendar year, this means ideally the model run would start on 1st Jan, but this is right in the middle of the wet winter period, so to get winter infiltration right in the model, we normally start the run on 1st Dec the previous year, to get the build up. But trying to exclude any predicted spills in this initial month can be tricky when processing the results through a statistical report - normally requiring processing the results externally in Excel. So I agree it would streamline the approach a lot if the software could be told to not save results from the initial build-up month. And I also agree that with the number of different scenarios being simulated, and the complexity of GIM flows, trying to make use of initial conditions files or initial state sims for this kind of thing is more of a hassle than the current work-around of longer sims and post processing in Excel.
I understand why you might vote for this approach, as it seems popular among many users. However, I want to point out that not using a hot start file in SWMM5, ICM SWMM, or InfoSWMM may not necessarily save you any time. I've observed that numerous users run their large models for an additional simulation day, which could be easily avoided by employing a hot start file. This would eliminate the need for that extra simulation run. So, in my opinion, it's worth considering the use of a hot start file to potentially improve efficiency.