Ideas Lab

Information in the River Cross Section Unit

Published on 02/02/2010 at 15:05 by bailesm

In the River Cross Section unit, could we have another field - to store information about the surveyed points.

This information often comes in with the topo survey - but is lost when the model is created.

e.g. If points are in channel/on the flood plain
or material across the flood plain

e.g. Start / End of Bridge opening

e.g. If the sections are extended in ISIS Mapper - we could record which points are from Topo Survey and which are from LiDAR (and the name of the Lidar Grid used)

e.g. If survey points are manually adjusted (for whatever reason)

The same idea could be used with Spill Units.

Mark

Actions:

Planar animation of ISIS 1D time series results

Published on 27/01/2010 at 16:38 by jiym

Currently the ISIS time series results are viewed via the time series, cross section and the long section plot, which gives a relatively localised and detailed view of what the modelled results are. However there are often occasions the viewer/modeller would like to look at the general hydraulic behaviour of the model before diving into the investigation of the details. The general view could be when and where the water in the channel starts to overflow or confined by the artificial glass wall, when the bridges get surcharged, or when the gates start to operate according to the operational rule.

To achieve this, I am thinking of a planar animation of the 1D time series results in GIS visualiser which gives an overall and holistic view of the model behaviour. The value (could be anything) associated to the hydraulic unit shown throughout the animation could be displayed more visually (using different colour or size of symbol) rather than the actual numbers.

I got some crude ideas for the functionalities:
1. For structures in general, colour codes the Mode or State.
2. For the bridges behaviour regarding surcharging, green colour shows no surcharging, and use yellow to red denoting different degrees of surcharging.
3. For spills, use two colours to represent the positive and negative flow, and use different saturation of each colour to indicate the discharge rate.
4. For river section, use different colours to indicating the glass wall placed, e.g. 0.15m, 0.5m, 1m
5. For reservoir unit, depth could be colour coded as well.
6. On top of this, the user can place the detailed time series plot for the units of particular interest aside to view the interactions.
7....

Actions:

4	Allow Global Edit of out of bank Roughness Published on 13/01/2010 at 15:09 by Conor Galvin Could there be an addition to the global edit function which would allow both the in-bank and out-bank roughness to be defined? Actions: » View Idea Details » Comment on this idea

Permit manual change of defualt run parameters

Published on 18/11/2009 at 12:29 by Claire

It'd be useful if the default settings in ifrf.exe could be manually changed, so 'supress windows output' could be on by default for example.

Particularly useful when working on a big project where all the runs are unsteady, have the same start and end times, initial conditions in the .DAT file etc, etc. Being presented with the same blank steady direct run after iterating a model then having to either change all the settings or load an old .ief and change the .DAT and results references can be a bit tiresom...

Actions:

Automated visualiser file building

Published on 16/11/2009 at 11:27 by kostya

Have an automated gxy/ixy schematic layout, rather than placing the units in a long line (save for the token offsetting of QTBDYs) determined by the dat file ordering. This could potentially re-use the algorithm used in reordering the initial conditions (which determines the natural ordering of the model nodes).

Actions:

Model file comparison tool

Published on 16/11/2009 at 11:25 by kostya

Have a compare models function. Using a typical text-based comparison tool (such as Vdiff) is adequate for small changes, but when the differences become numerous, or when the differences are not really differences (0.000 is different from 0 in a text file, but not numerically), this breaks down.

Actions:

Manually prescribed varying timestep

Published on 16/11/2009 at 11:24 by kostya

As opposed to automatic adaptive timestepping, to allow the timestep to change over a pre-defined period the run (e.g. 60s for first hour, then 360s). This would reduce differences in results for similar models, observed due to time-dependency (e.g. with reservoir volumes).

Comments:

» PHA commented: I tend to think models shouldn't be timestep dependent! Are there rules in the model which operate at funny times? Those ...

Actions:

» View full comments

2D Adaptive timestep

Published on 16/11/2009 at 11:18 by kostya

Add adaptive timestep to ISIS 2D this should help speed up the models through its easier times

Comments:

» PHA commented: It should be noted that there really wouldn't be much room to move on this though! Maybe down to quarter of the 'normal' ...

Actions:

» View full comments

Close animation plot from simulation

Published on 16/11/2009 at 11:17 by kostya

If a long section animation is open, and you start a new run, it will fail due to the conflict of trying to write to an open results file. Rather than having to find the plot, close it and start the run again, how about an option to say "Close plot file and overwrite" this could be interactive or automatic.

Actions: