HydroWeb - Hints/Assessments
General Remarks - Reporting - Hints on WP2
HydroWeb is running!
All teams and most team members are active and communicating on different levels.
I observed progress in the Mike11 exercise; most teams are finishing the sub-tasks of WP1
at least I found some related reports.
I have the feeling, that
most of you became more and more familiar with Mike11 and the shared team platform.
Congratulation, this is indeed a great step within
just two weeks besides all the other lectures!
HydroWeb is on Web based Collaborative Engineering - not on Mike11 or editing Word documents. The focus is given to the communication, coordination and documentation within your teams using modern SHARED Web technology. Please feel free to contact me whenever you have a question or problem (email, Skype, BigBlueButton, ...), I'm online as specified in the HydroWeb supervisor calendar.
Please have a look on the Team Photos Page. Six team photos are still missing.
Today I had a view to the few reports on the team web sites.
Most teams were using GoogleDocs documents integrated in the GoogleSite pages.
These shared documents will help you soon to finalize
the project in the near future as team work by sharing
and editing in parallel Web documents ...
Team1: I did not found any report on your Web-Site ;-(
The number of reports will increase by time.
A table of report might help not to loose the overview
and to have a quick access to all reports.
Please use also the ModelList pages to list all
model versions on the RDP server with the related semantic short description.
I found reports for some few parts of work package 1 on the team web sites. I assume the teams will finalize them ASAP, if not yet done. I strongly recommend write the reports in parallel to your modelling activities. It would be helpful to write the reports about WP1.2 to WP1.5 before merging the files in WP1.6 towards the final model file set as part of WP1. Then to write the report about this merging before starting WP2 and so on. The report of WP1.6 should also include information about the simulation results. Please finalize the reports of each sub task before starting the next following working step based on this sub task.
Work package 2 deals with the optimization of the model file set of work package 1
towards navigation, flood management and water level management in Tønder park lake.
When work package 1 has been finished (all sub tasks and the merging towards a final
file set has been performed and reported),
you can start with work package 2 maybe by three steps:
Besides weirs you can also model other engineering investigations, examples are:
The impact of your changes can be checked with the MikeView tool for the result file. We recommend using the longitudal profile and the water level visualization. The red and green lines (min/max water level) can be compared with the lowest point in the crossection and the left/right embankment to check for minimum water level and for overtopping for the river banks (flooding).
The easiest way of creating an artificial infrastructure is a broad crested weir. Please do not use any other type of structure. Weirs are part of the network file; you can add them in the map by the graphical editor or in the tabular editor (Structure -> Weir). Please use the type "Broad Crested Weir". With the valve you can simulate the storm gate. A valve set to "only positive flow" will let the water flow out (q positive) of the river but not from the sea into (negative flow) the river. The geometry can be defined by level/width combination, which defines the free cross section for discharge. We recommend using a rectangle cross section (two level with same width). Have a look to the cross sections nearby the weir to find suitable levels.
A hint for the storm gate: the width of the three gates in reality is 7.07 m each from the level -2,75 to 4,00.