HydroWeb - Hints/Assessments
General Remarks - Assessment first week - Tasks for the next days - Mike11
Welcome everybody in HydroWeb !
You might need some days
to establish a suitable working method for your
collaboration in your team.
Learning new tools and discuss a first suitable team interaction
agreement in a online team meeting will take some time.
The collaboration approach might differ in the four
teams in respect to the heterogeneity of the team composition
and time shift working.
So please find your way in
this 'Learning by Doing' experiment.
All the different tools applied in HydroWeb
(GoogleSite, GoogleGroups, GoogleCalendar, GoogleDocs/Drive,
Skype, BigBlueButton, Adobe Acrobat Connect Pro, Hangout,
Remote Desktop Connection, Mike11, ...)
requires some training by activities from your side.
HydroWeb is a self-learning course: learning by doing!!
In the next days/weeks you
will become well trained on them just by using them
in a flexible "try and error" way. You will develop new soft skills
and working methods for collaboration via the Web.
Whenever a problem is coming up, please do not hesitate to
ask your team mates and the supervisor (Frank) for support.
Please do not forget: HydroWeb is an educational game: No risk, no fun!
Don't worry if your team colleagues react not in the way you like,
the 'best' team work will happen if you find suitable compromises
for synergy effects in your team!
Everyone has set up the Google account and joint the platform to start
the HydroWeb team collaboration. This is indeed a big step forward.
Please continue using the Team Kickoff description
and the hints given below.
The team pages (Google Sites) has been edited by few team members only!
It is very important to start activities, please do not wait until a
final warning has to be send out to start your team work,
the idea of 1st week was to set-up the team work. As example:
I did not found for team 1, 3 and 4 any entry on the Team Member Page or in the Address Book (Kickoff Step 4).
I strongly recommend to finish kickoff step 1 to step 8 ASAP otherwise your team work might run ut of time!
Recommendation on next working steps:
Please use the page "Minutes" to report your activities (if not yet done).
Key idea of HydroWeb is to use a shared application server with shared file system
and installed Mike11 software. This approach is used since 20 years successfully.
As the open and free Internet is by time more and more corrupted by hackers, miss use and
criminal activities, the security level became more complex and important.
This has a deep impact to "Web-based Collaborative Engineering". This year all
universities has protected their servers by restrictive firewall rules leading
to complicated access procedures. The free Internet is transferred to protected Islands.
So we have to use VPN to connect to the different Intranet systems,
to access the RDP_Server in Nice with Mike11 we have to use the Nice VPN.
The access to the server in Nice (134.59.229.9) with Mike11 has been send to you on 14 October
to your @etu.univ-cotedazur.fr email account. Please check your emails on this account.
You can work on this server (e.g. with Mike11) using RemoteDesktopConncetion (via VPN connection to be in the Nice campus network).
The key idea of HydroWeb is to play a game, which contains
more or less typical situations in projects. One situation is to
run software, you never used before. As in the HydroWeb game
you have a tutorial and the Help functions of the software to become familiar with the tool
as well as in the background for larger problems a hotline (-> supervisor),
which is in HydroWeb for free :-)
However, this is contrary to other courses in universities,
when somebody explains to you, what to do step by step.
In HydroWeb you have to find the solution and working method
yourself as a team.
This kind of creative working is a huge challenge in engineering!
In case of problems on the platform or with Mike11:
Don't worry, this is normal. "Learning by Doing" and "Try and Error"
means always to run in troubles and problems:
Engineers should be able to find solutions for unforeseen
problems in a creative process :-)
The river Vidå Mike11 model consists of several different files. The most important files are:
Please always report the changes of the files related to your sub tasks. Most files are modified in more than one sub task. At the end of WP1, you (as team!) have to join all sub tasks modification in one file set by copying the different modifications in unique files.
Work package 1 is designed to set-up the model and to become familiar with Mike11 as editor for the river. When changing files please report always the changes you did. You should also check, whether the simulation runs well, but you have not to check the results against flooding and so on. This will be part of WP2 later :-)
WP1.2 to WP1.5 can be performed in parallel. Please create for each work package WP1.2 ... WP1.5 a new folder with a related name in which the whole Mike11 file set is copied. In this way you can work in parallel on the work packages on different files. When all locations are ready, you have to merge the files in one final file set. Create a new folder for this purpose and copy WP1.2 to it. Then step by step integrate the changes of the other work packages. Using the reports of the changes you will find out the overlapping files. This is mainly the boundary file, which was changed in WP1.3, 1.4 and 1.5. The cross section file is only changed in WP1.2, the network file in WP1.5. I deeply recommend to create always new time series files for changing/adding boundary conditions (WP1.3, WP1.4 and WP1.5). Just again: please REPORT all your changes in detail in the minutes and use the model list page of your team work space to report the progress in general.
For WP1.2 you have "only" to edit the cross section file:
Using the tabular editor you will find the cross sections
by the name of the branches and the chainages.
For the elevation of the cross section bottom level
you have to find the minimum z coordinate: zmin.
Add the elevation value to zmin which leads
to zelev. Please change all z coordinates
less than zelev to this value.
That's all :-)
In WP1.3 you have to edit the boundary file and the related time series file. Please create a new time series file for this purpose to avoid later overwriting when you have to merge the results with the other teams. Inside the time series file you can set-up two columns/items for the given discharge at both locations. When the time series file is ready, you have to link the time series file and related items inside the boundary file.
The original exercise data set consider only two of the
five pump stations by constant boundary conditions.
You have to add three boundary conditions for the other
three pump stations at the related river locations.
We recommend to create a new time series file for
the five discharge/inflow boundary conditions of the pump station.
The time window is September 1990 and you could use
e.g. a time step of one day.
The total amount of water for each pump station within this month
is given in the exercise, as well as the possible pump rate.
You are free to use the different pump rates within this month,
but we recommend to pump more water at the begin of the month
then at the end, when there will be some rain.
Please calculate the amount of pumped water by
sum pump rate * time. The result should be +-5% nearby the given total amount of water
in the exercise.
You could add for each
pump station one discharge item and link this in
the boundary condition file to the pump station location.
In this way WP1.3 and WP1.4 are considered in separated time series files
but in the same boundary condition file.
The Galgestrom in the North East of Tønder. The cross sections are given in the cross section file. You have to create new points along the Galgestrom from upstream to downstream. Please start at the connection to the "white" road (in the map nearby the "E" of Emmerske) and then go down the river to the connection to the given branch. Connect the points to a new branch and rename it to GALGESTROM. Topo-ID should be TOPO-96 as in the cross section file. The chainage should not exceed 2540 m downstream, as this is the last cross section defined in the cross section file for GALGESTROM. At the last downstream point you have to connect the Galgestrom branch to the VIDAA-OVR branch. Finally you have to add a new boundary condition at upstream with q=0.2 m3/s.