WRM web version: Scenario Editors

The scenario editor top level shows all available scenarios for WaterWare/WRM, together with their author/owner and last modification date. The list can be sorted by name, user, and modification date with the appropriate column headers. There is also a simple full text search function to identify a specific scenario.

Please note that while any user can view and copy all scenario in the list, only scenarios owned by a user can be modified.

The basic SCENARIO LIST offers the following functions:

1. select and view a scenario: click on the view button;
2. copy a scenario: select copy; the display (same as view) will be started ; please note that the scenario copy will have been given an automatically generated name, by prepending the original name with the user name - edit as required.

1. scenario list   shows the list of scenarios described above;
2. new scenario  opens a new, empty scenario;
3. node type   shows a list of all supported node types, their descriptions, symbols, and link to the on-line manual pages - please note that for external users, this listing is READ ONLY.
4. new type   editor template for new node types (not accessible for external users);
5. user info   shows information about the curent user, includes a password editor.
6. help   hypertext help pages;
7. exit   should be obvious.

Editing a Scenario

The main editor page summarizes the scenario and offers another BUTTON MENU:

1. current scenario (reloads the page, but returns to it from other pages triggered !)
2. nodes produces a list of nodes used in the scenario for selection/viewing/editing;
3. reaches produces a list of reaches and reach editor;
4. view network generates an enlarged network diagram;
5. back returns to the calling page.

• A HEADER, that includes
• number of Nodes and Reaches used (read only)
• number of Start nodes, Demand nodes, Reservoirs (as indications for the complexity of the scenario);
• Scenario name
• Description free text describing the scenario, assumptions, data sources, etc.
• StartNode (byname) for the network.
• start date (only year and month should be selected. Please note that currently, the user is responsible to keep this selection consistent with the time series used !),
• project and location (for organizational reasons mainly),
• and the creation date and last update together with the user/author (read only).
• A set of global scaling factors
  • for all DEMAND NODE demand time series (generic);
  • for each SECTORAL demand (municipal; touristic; industrial; light industry; commercial; services; irrigation) if this is not explicitly specified, the global value is inherited; SECTORAL specification overload the global specification.
  • for all INPUT (Start node) time series (generic);
  • for each TYPE of START NODE (sping, GWater, subcatchment, transfer) - if this is not explicitly specified, the global value is inherited; TYPE specific specification overload the global specification. Please note that this ALSO includes the precipitation time series that can be specified for any reservoir
• Network diagram with a link to the locations GIS data;
• A final set of BUTTONS for:
  • SAVE
  • DELETE
  • BACK
  complete the interface functionality.