I am working on project which includes 50 models. where we have to give runs for different return periods and durations for each model. It is a time taking process, which unnecessarily create chances of error by creating run setup every time. is it possible to include a run set up template, which can be changed as per the user requirement and saved for the further use.?23 votes
Is there a matrix type tool in ICM that allows you to easily set up complicated run set ups? i.e. for this 1 Model Network, these runs with use these rainfall files, inflow files, WWG, etc are needed.
Rainfall Inflow WWG Tradeflows
M5-30 Inf-M5-30 WWG1 Trade1
M5-240 Inf-M5-240 WWG1 Trade1
M5-960 Inf-M5-960 WWG1 Trade1
M10-30 Inf-M10-30 WWG1 Trade1
M10-240 Inf-M10-240 WWG1 Trade1
M10-960Inf-M10-960 WWG1 Trade1
With same timesteps and 2D parameters?24 votes
Would like to be able to work across multiple screens - plan view on one screen and long section/grid/graph on another.67 votes
Sometime a TSR running for few weeks throws up convergence hence these sims need to be rerun with shorter timestep which is both inefficient and a lot of time is wasted. It would be good if somehow the simulations dialog allowed to run the model with Max and Min timestep so that when it encounters convergence there after the model runs with shorter timestep. (I understand the model does timestep halving but even then it fails to converge)1 vote
Thank you for this, there is already a mechanism available for achieving something very similar to this. If you have a network and then go to the simulation parameters for this network via Model > Model parameters > Simulation parameters then within these there is an entry for “Max number of timestep halvings”. Depending on the timestep in the run dialog and the entry in the simulation parameters here you will be able to determine the minimum computational timestep that the engine goes to before failing a simulation.
Hope this helps.
Validation as a background task so UI isn't locked.35 votes
We have spent quite a bit of time investigating how validation improvements might be achieved, whether that be through validation as a background task or whether it be with improvements on the speed of validation in the first place.
There is no silver bullet which has been identified so far, the validation is already very efficient with minimal potential for speed improvements and there are issues with it as a background task as previously mentioned which we haven’t got fully fledged solutions to yet.
- Don't see your idea?