Ideas Lab

Would it be possible to add panel markers simply by clicking on the point in the cross-section plot by selecting the appropriate icon in the edit series menu? Instead of clicking on the point exiting the cross-section plot and then selecting the panel marker, it would be a great time saver for large models.

Additionally would it be possible to copy mannings n values between cells by clicking and dragging the cell to the desired row, similar to the procedure for copying cell values in excel?

Comments:

» ian commented: excel-type functionality for other purposes would be good too - such as editting node labels

» Andrewc commented: It would also be really helpful if the panel/roughness status was stored in memory and/or formsed.ini so that when it is ...

Could we have some automation to ordering the initial conditions in the data file. During model build and stabilisation, we often revisit units in the data file. This results in a re-ordering of the initial conditions in the data file. When post-processing results, the order at which these are in is vital, especially if the model is large and you are only interested in particular reaches. Thanks. TJ

Comments:

adamsk commented on behalf of the ISIS team: Agree. If it's a graphical view within ISIS, e.g. Time Series output, one can use the "Alphabetical Order" option in the ...

robh commented on behalf of the ISIS team: This is now being actively developed for a future release of ISIS. This will allow you to sort your initial conditions ...

» robh commented: This functionality is now available in 3.3.

» chasward commented: Functionality does not appear to work in 3.3.0.88 Can you advise?

Today's modern computers tend to have more than 1 processing core. I would like ISIS to make better use of multi-core processing to speed up ISIS model runs. This could be done either by parallelising the code (speed up a single model run) or by modifying the batch simulation interface to allow multiples runs to occur at the same time.

Comments:

» Tony_Green commented: I would have thought the batch idea would be easy to implement and potentially useful - ie just have a field saying how ...

» chrisw commented: Anything that makes ISIS run faster is a good thing but I'm not sure than parallelising is the most cost-effective ...

Judging from the amount of people who have discovered the formatting error in the Culvert Inlet input values table in the Help file within one day or so of release, I realise many people must regularly refer to this table for the input values.
How useful would it be to have a "Culvert Inlet wizard" that takes you through the culvert types and enters the values for you? Should minimise transcription errors and make input easier.
konrad

Comments:

» hfielding commented: This is an excellent idea.

robh commented on behalf of the ISIS team: This is currently in development for a future release.

» robh commented: This has now been implemented in version 3.3.

I often find it difficult with large geo-referenced models to located nodes in the GXY visualiser. It would be great to have a simple "zoom to selection" button where the visualiser will zoom and centre on nodes selected in the network.

Comments:

» hinxmana commented: This would be really useful

robh commented on behalf of the ISIS team: This has now been developed for a future version of ISIS. The functionality will mean single selected nodes will be ...

» robh commented: This has now been implemented in version 3.3.

When applying a global roughness change in ISIS it only applies this to river sections.

Given that the bed under a bridge is nearly always composed of the same material as the bed u/s and d/s of the structure, could the global change be altered to allow manipulation of Manning's under the structure?

Comments:

» PHA commented: A nice additional tick-box to include structures, or not, would seem good to me.

» Tony_Green commented: Whilst looking at this, it would be good to stop ISIS writing at the beginning of a run the warning about changing N in ...

At the moment, if you are viewing cross sections and scroll through a model, the panel markers and Manning's values are removed every time you cross a structure.

I think it would be helpful if panel markers and Manning's values re-appeared when you got to the next river section unit, rather than having to be re-selected each time.

Actions:

» View Idea Details

» Comment on this idea

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:

» View Idea Details

» Comment on this idea

In many cases we need a spill to represent the flow over a bridge or banks and need to add spill units and junctions into the model. This takes time (especially in an urban situation) and adds to model size and schematic complexity.

This could be readily built in and would be useful to see in the graphics when checking.

Perhaps output something on the flow through the bridge and over the spill in the ustate as well as velocity through the bridge opening.

Comments:

» PHA commented: Sounds good, so long as you're still allowed to have bridges without the built in spill. If linking with a 2d scheme, it ...

As I understand things, .IEDs currently only work for boundary units. It would be nice if this restriction could be lifted, and any unit could be substituted.
This would mean (for example) you could setup different orifices being blocked in different .IEDs; then combining blockage options is as simple as loading in a few .IEDs into an .IEF.
Altering bridges (for proposed designs), reservoir volumes (new mitigation measures), sluice sizes/rules, etc, etc, is all then easy to play with in a nice modular manner.

Actions:

» View Idea Details

» Comment on this idea