Some short notes

- save wizard options
- update processed data based on locked/unlocked flag
- batch run
- scenario(s)
- changing boundary conditions in a batch mode is the highest priority
- statistical analysis features (min, max, ... of the n runs)

They will send a feedback and suggestions about most wanted features.

The main feedback is: "Brilliant!", "I'm impressed!" (smile)

Hi Edward and Gennadii,
Herewith a short explanation of how we are doing batch runs.
At the moment we use hydrologic models like WBNM or RAFTS.
We have tools that convert the hydrologic output (hydrographs) into .prn files.
(results in hundreds of -prn files):

For example (below) BU01c and PU04b are 2 cases: a Base case and a Proposed case.
For every case we have hydrographs for storms with different recurrence intervals, like BU01c002 (1 in 2 year event), BU01c005 (1 in 5 year event). Within each event we have different durations (120 minutes, 15 minutes, etc) for different location nodes (A12, A16, etc).

Attached are the 1 in 100 and 1 in 50 year batch files for the proposed case.
When you open them in a text editor, you'll see it's very easy to assign the .prn file locations to different SOBEK nodes and run different durations.
When you have set up one .sbf file you just copy them and do a "find and replace" for 100 to 50 or PU04 to BU01c.

What we would like to see in the new Sobek version is something similar.
The boundary conditions (inflow, Q-H, H-T or initial water level) sitting at one location and within DelftShell being able to assign different boundary conditions to different SOBEK runs.
And also being able to do change a whole series of links (like in the advanced batch tool, changing all the links from BU01c to PU04b).

I hope this makes it a bit clear. If not than I am happy to give you a call and explain this in more detail.

Cheers,

Christian Huising
Project Engineer
Phone:07 3100 2455
Fax:07 3369 9722
Direct:07 3139 2976
Email:christian.huising@cardno.com.au
Web:www.cardno.com.au

  • No labels