Revision Level:   1.0

Editing and running client-server scenarios
The CREATE button of the scenario handler of the
client-server interface leads to a pop-up window that supports
editing and eventual execution of a client-server scenario.
Depending on the model, the dialog box may contain different
sets of variables and parameters, but in general they include:
- Simulation control like starting date, duration, time step;
- Input parameters such as emission and meteorological scenarios.
These parameter sets are described in the manual pages
for the individual client-server models:
- REGOZON
- MEMO/MUSE
- POM
- MODFLOW/MT3D
Once the scenario has been edited, the simulation run can be
triggered by the COMPUTE icon in the header bar of
the pop-up window.
Starting the model server
To start the model server dialog box, the name of the scenario must have
been modified to be different from the original template name,
since the system will NOT overwrite an existing scenario.
To edit the scenario name, use the Backspace or
Delete buttons and enter the new name on the keyboard.
Please make sure to create a valid UNIX file name that should not contain any
special characters (non alphanumeric) characters.
An attempt to start the server for the current scenario name will
generate a WARNING box message.
The model server dialog window includes:
- display of the (symbolic) model server name; the user can choose alternative servers
from a selector triggered by the name display, if such alternative backup servers have been
specified in the defaults.
- the server URL (see above)
- an icon menu, where again the COMPUTE icon is used to send
the http POST request to the specified server and start the computations.
The example below specifies two alternative server names and their respective URL
in the default file ./defaults/neco:.
*.cliser.sernames.name.3: MP1 Regozon
*.cliser.sernames.node.3: mp1:8080/cgi-bin/regozon
*.cliser.sernames.name.4: BERLIN Regozon
*.cliser.sernames.node.4: zeus.first.gmd.de/regozon
WARNING:
the client-server communication protocol is based on a parallel
client program that is started from the main ECOSIM server.
This process will wait for the completion of the simulation request,
which can take several hours depending on the model and the scenario.
The result file is visible in the file list of the LOAD command,
but there will be an error message when attempting to load that file
before the simulation run is completed.