Operational Modelling menu in MOHID Studio allows the user to configure his own MOHID and other models to run operationally (gathering initial and boundary conditons at each run and storing results in database without human interaction) or to mport and export hdf's to database and check hdf and timeseries results from database.
Here the user can check what model domains exist (or add/remove), the hdf files indexed in database and hdf datasets present.
Here the user can import and export hdf to database and extract timeseries from database (from hdf).
Top impor files into database on "File" box select the files from disk (may select several).
On Model Domain select the model domain that the hdf belong to. If importing fiels from a new model domain, please go first to "Model Results" and press "Domain" button and add the new model domai first.
On Options select if the results have a spin-up period (the results on this period will not be stored in database)
Click on "Import" to start importing files.
To Export hdf files to disk on "Source" select the model domain and the dates to export.
On "Target" select the output file in "Output File" box.
If want to interpolate results to a different grid use the checkbox "intepolate to new grid" and choose a target grid and an interpolation method.
In "Exporr" press the button to start the process.
To Export timeseries files to disk from hdf results on "Select model domain" select the model domain and the dates to export.
On "Location" select the locaton to export either by providing coordinates in WGS84 or by picking in the Map.
On "Process" may select to save the time series to file by selecting the checkbox "Create ASCII file" and providing the output filename or/and see the timeseries in a graph by selecting the checkbox "Create Time Serie GRaph" and the graph will open in Studio "XY Graph"
In file watcher the user can import timeseries and hdf automatically from a folder to database as soon as new files arrive (e.g. in external operational models that write results in a defined older), by specifying the folder, the file filter expression, and what to do with the file after import (delete, copy to a folder, move to a folder).
In Operational Models the user may convert their MOHID Studio projects into operational ones. For external models (e.g. WRF not yet integrated inside MOHID Studio) the model can be configured to run inside a specified working folder.
In case of MOHID models, the operational model can run in same project as existing in Studio where user works day-by-day, but the operational model will automatically create simulations at the end of the project (after a few days of user work adding new simulations, they will be in the middle) and may run at the same time as user simulations (and compete to access to some files) so it is advised to create a new project just for operationalization.
1) The user needs to have installed ActionServer (windows sevice) so that the model configured to run are launched at the specified hour(s) every day without any human interaction (the only condition is that the computer is ON, no login is required).
Check the page on Action Server Install to install the ActionServer.
2) In case of MOHID models, the standard for a project to be accepted to operationalization is to have two or more simulations, but needs to have exactly two template simulations, and one needs to be a parent and the other child (continuation run). This two runs define the cold start and hot start simulations, respectively, and the user can prepare them as needed.
See Figure 1) for operational model simulation definition.
In "Local Model Domain" window the user may add/edit/remove an operational domain that will run in his machine.
The user may choose the new Domain Name and type (MOHID Water, MOHID Land and other types of models) and if type is MOHID the user can choose the MOHID Studio project where to work. This project needs to have the pre-requisite nº2 or the interface will warn the user when trying to save the model domain.
See Figure 2).
The user may also choose to clean the project by selecting checkbox "Clean Up at End". If this is checked, after each simulation finish the process deletes the simulation created, the result files from res folder (hdf and timeseries) and stores hdf files in a storage folder defined by user. If this is not checked, nothing is done and MOHID runs are not touched, meaning that simulation folders and files will pile up in windows explorer and MOHID Studio inside the project and the results will remain in res folder. The latter can be used for first simulations to check results inside MOHID Studio but it is advised to chek the clean up option after.
For nested domains, create a model domain per MOHID domain and select the checkbox "Parent Domain" and select the parent domain in the child domains. For running, only the father domain should be checked "Enable Scheduling". All sons domains will run from father.
The next step after Model Domain Configuration is to define initial or boundary conditions (that change in time and are dynamic (e.g. results from other models as meteorological)). Constant and climatological conditions are not defined here but in the two template simulations datafiles since they will be immutable trough all the simulation period.
Each boundary condition will write to one file ("Target File") and this file will be updated every run with the most updated results in database for the simulation dates. This file needs to be used in template simulations (e.g. referenced in Atmosphere data file or Discharge data file) so that it has any impact on the operational simulations!!
See Figure 3) for configuring boundary condition type.
By Pressing "Edit Providers" the providers available for the selected type of file and property will be loaded.
The boundary conditions may be fetched from providers where the providers are all model domains in the database. These model providers can be user operational models (e.g. MOHID Land providing flow for MOHID Water or MOHD Water providing level for MOHID Land, MOHID Land watershed providing flow for MOHID Land inundation areas, etc.) or by using ActionServer download capabilities, these providers can be other external models (e.g. GFS, MeteoGalizia, Maretec Models) that are stored in database.
Check the page on Action Server Download Guide to configure model results downloads from external sources with ActionServer.
The user may choose to force the model with timeseries, hdf with only one property, or hdf with all model domain properties available. In all cases, the user can define several variable source providers and his priority (e.g. different meteorological models). If the first fails to give data to the complete simulation duration, than it goes to the next and so on.
Both TimeSeries and hdf with only one property can also have failback providers, meaning that if all the variable source providers do not have data to the complete simulation duration, than the user can choose:
See Figure 4) for configuring boundary condition providers.
For the operational models to run they need to have sceduling ON ("Enable Scheduling) and ActionServer service needs to be running (as a windows service).
See Figure 5) for searching Services.msc in Start Menu (in Windows 8, is similar in previous versions).
Press the services.msc to see all windows services. Action Server should be at the start (if ActionServer was installed).
See Figure 6) for Starting ActionServer service.
Whenever a model domain is changed need to restart ActionServer service.
Here are the configuration with the executables to use with operational models.
In Layers is possible to load grid based and vector properties from database to the map. Just need to select which model domain, property and mapping to use and the layer is added to the map.