I am running a Storm model without Long Term Continuous Simulation, the model has 20 scenarios (exclude rational and 50 years storm), each scenario run takes around 15 min. when I did batch run the model took around 4 hours! and the model size reaches to around 11 GB. that is unusual, I am running the model on my laptop which is i9 processor with a 64 gm ram and a very good graphics card.
I am looking for a solution; that kills my time if I would do change and re-run the model. I am running epa swmm which required by the client. the model has gullies and gutters.
Is that a reasonable time for a run? how can solve that? is that due to the program capabilities?
Modelling gullies are required by the client for this development and his thought that would customize the pipe sizes and would give the design the real prediction of what will happen during the storm.
I uploaded the model for your kind review in the secured link.
Regards,
Mohamad
It would be interesting to know how long it took to run 1/4 of the scenarios in batch in comparison with how long it took to run each of those scenarios individually. In thinking more about this it sounds like there may be one or two scenarios, maybe more, in the model you have that might not be running efficiently, but again that is just a guess without being able to see anything.
Dear Mark,
I run those scenarios which have different rainfall (each one has rainfall), it is to evaluate the peak of FEH and check the higher runoff. it is logical to have them run all. the batch run made for such tasks. please check the model (have fun :) ).
it is running but took 4 hours and the folder size after run all became 11 GB. it is the first time happen like that and not logic for each change I will make and run to wait 4 hours. it is really important to investigate and feed us back.
you are so appreciated.
Thank you,
Mohamad.
I noticed that the scenarios run significantly faster (I ran all 20 in batch in 30 minutes) if the engine compatibility calculation option is set to EPA 5.1.12 (instead of the Bentley Enhanced version).
On-grade HEC-22 inlet calculations are not supported in this case (as seen in the user notification and in this article) so this is likely not an option. But, it may point to the culprit; those inlet calculations may be taking up significant time when using the traditional Bentley-enhanced SWMM solver version, which supports my colleague Scott's findings that the issue may be related to the large number of inlets and the complex arrangement. Here is an example to illustrate, showing a manhole with 14 pipes connected to it, most connected to individual, on-grade inlets. Is the real system set up this way with a ? If simplification here is possible, it will likely help speed up model runs.
The output files for each scenario are about 500 MB (even in my faster test run). This size does not appear out of the ordinary given the number of elements and timesteps. While not extremely large individually, these do add up to a large model size for 20+ scenarios.
Here are some other things to consider to reduce the size and duration of the model runs::
Jesse DringoliTechnical Support Manager, OpenFlowsBentley Communities Site AdministratorBentley Systems, Inc.
Dear Jesse,
In spite, we have an active subscription, but for this model we are running the model with version (08.11.05.113) because the client has a similar version, we do not have the option to change the EPA or using bentley EPA.
for the gullies, I know in the new version we can connect the gullies to pipes, here we do not, so we placed the gullies as it should be with respect to surface slopes, and we connect them where they should be, the gullies are "side entry gully". I guess that is the best to reflect real life in the model (where the client insists to connect the catchments to the gullies to have advantages of using the road surface for spread and kind of delay flow entry which that will be during runoff.