SDC Sphy Manual
  • 📚Readme
  • manual
    • SPHY Manual
      • 1. Introduction
      • 2. Theory
        • 2.1 Background
        • Modules
        • Reference and potential evaporation
        • Dynamic vegetation processes
        • Snow processes
        • Glacier processes
        • Soil water processes
        • Soil erosion processes
        • Routing
      • 3. Applications
        • Irrigation management in lowland areas
        • Snow- and glacier-fed river basins
        • Flow forecasting
      • 4. Installation of SPHY
      • 5. SPHY model GUI
        • 5.1 Map canvas layers and GUI interactions
        • 5.2 Top menu buttons
        • 5.3 General settings
        • 5.4 Climate
        • 5.5 Soils
        • 5.6 Groundwater
        • 5.7 Land use
        • 5.8 Glaciers
        • 5.9 Snow
        • 5.10 Routing
        • 5.11 Report options
        • 5.12 Running the model
        • 5.13 Visualizing model output
      • 6. SPHY model preprocessor v1.0
        • 6.1 Overview
        • 6.2 General settings
        • 6.3 Area selection
        • 6.4 Modules
        • 6.5 Basin delineation
        • 6.6 Stations
        • 5.7 Meteorological forcing
      • 7. Build your own SPHY-model
        • Select projection extent and resolution
        • Clone map
        • DEM and Slope
        • Delineate catchment and create local drain direction map
        • Preparing stations map and sub-basins map
        • Glacier fraction map
        • Soil hydraulic properties
        • Other static input maps
        • Meteorological forcing map series
        • Open water evaporation
        • Soil erosion model input
        • Sediment transport
        • Reporting
      • Appendix 1: Input and Output
      • Appendix 2: Hindu Kush-Himalaya database
      • References
      • Copyright
Powered by GitBook
On this page
  1. manual
  2. SPHY Manual
  3. 5. SPHY model GUI

5.12 Running the model

Previous5.11 Report optionsNext5.13 Visualizing model output

Last updated 1 year ago

Figure 47 provides an overview of the Run Model tab. Before running the model you need to specify your environmental settings, which are setting the PATH of the PCRaster bin folder and selecting the python executable (python.exe).

The PCRaster bin PATH can be found under the PCRaster installation folder (see Section 3.1.3). This folder can be selected by clicking the Select path button.

The python executable can be found under the Python installation folder (see Section 3.1.1), and can be selected by clicking the Select python.exe button.

After setting these environmental settings you can run the model by pressing the Run model button. During model execution the command line output will be reported in the log screen as is shown in Figure 48. Model run can be cancelled anytime by pressing the Cancel model run button. If this is done, then previous model output will NOT be overwritten. Figure 49 shows an example of the log screen output of a cancelled model run.

If an error occurs after the Run model button has been clicked, then a screen similar to that of Figure 49 will be shown. In that case you need to check your model input/parameters, environmental settings, or a combination of these.

If your model run was successful, then a screen similar (without red line) to Figure 50 will be shown. The text “Model run was successfully!” indicates that model execution was successfully.

At this stage you still can click the Cancel model run to prevent previous model output to be overwritten. Otherwise the GUI continues with converting model output (part below red line) to a suitable output format. Converting the model output may take a long time, depending on the length of the model simulation period and the settings in the Report options tab. The line with the three dots (…) indicates that the GUI is still working to convert the output.

After the line “Converting model output maps completed!” is shown, you can continue to the Visualize results tab in order to analyze model output.

Figure 47: Overview of the Run Model tab.
Figure 48: Example of log screen output during model run.
Figure 49: Example log screen output of cancelled model run.
Figure 50: Example log screen output of successful model run.