General Configuration

Action Server can be customized by editing the Action.Server.exe.config that lives in the same directory as the program:

  • 32 bits CPU: C:\Program Files\Action Modulers\Action Server
  • 64 bits CPU: C:\Program Files (x86)\Action Modulers\ Action Server

Among other things, this file specifies the database and the directory for plugin's configuration files.


By default, the database and plugin's configuration directory is C:\ProgramData\Action Modulers\<CustomApplicationName>

where CustomApplicationName is "MOHID Studio" if MOHID Studio is installed, or "Action.Server" if not. This option can be customized with:

 <add key="CustomApplicationName" value="MOHID Studio"/>

Start Database

Default database is of Sqlite format, named TestingUrbanWater.db as specified with the following code block in Action.Server.exe.config file:

     <property name="dialect">NHibernate.Dialect.SQLiteDialect</property>
     <property name="connection.connection_string">Data Source=TestingUrbanWater.db;Version=3;New=True;</property>
     <property name="connection.driver_class">NHibernate.Driver.SQLite20Driver</property>

Without MOHID Studio installed, a database must be created:

  1. Open command line prompt (start+r, write cmd)
  2. "C:\Program Files (x86)\Action Modulers\Action.Serve.exe" -checkdb
  3. Specify database name according to Action.Server.config
  4. Database should be in C:\ProgramData\Action Modulers\<CustomApplicationName>\Configurations\TestingUrbanWater.db

Running Action Server

Action Server can be run as a Windows service for operational usage, as explained earlier, or as a console program for testing purposes:

  1. Open command line prompt (start+r, write cmd)
  2. "C:\Program Files (x86)\Action Modulers\Action.Serve.exe" -console


Plugins

Installed plugins are present as dll like C:\Program Files (x86)\Action Modulers\Action Server 2015\ActionSoft.Plugins.Server.<PluginName>.dll, where <PluginName> is to be replaced by each plugin name.

MOHID Operational Modelling

GFS Downloader

GFS Downloader is a service that downloads GFS forecast data at specified times, making them available in MOHID Studio as grid or time series at specified sites. This plugin is also necessary to run WRF Runner plugin.

The corresponding dll name is ActionSoft.Plugins.Server.GfsDownloader.dll.

GFS Downloader can be customized by editing the configuration file C:\ProgramData\Action Modulers\<CostumApplicationName>\Configurations\GfsDownloader.config .


GFSDownload.config.png
Figure 1 : Block of Configuration from file GfsDownload.config.


Where:

CronExpression - Sec Min Days Month Weekday User. Example: "0 30 5/6 * * ?" means "At 30 minutes past the hour, every 6 hours after 05:00, any user" [1]
StorageDirectoryHdf - Directory to store converted HDF5 files
StorageDirectoryBin - Directory to store converted original grib2 files (needed by WRF model)
ConvertToHDF5 - Flag to convert original files into HDF5
InsertIntoDataBase - Register files in the database
ExtractTimeSeries - Flag to export time series from HDF5 file. Sites are specified in the database and configured with MOHID Studio
TimeOutMinutes - Time (in minutes) after which the download stops waiting for files
ForecastDays - Number of forecast days to download
Download3D - Download full atmosphere (needed to force WRF)
DownloadSurface - Download only surface files
PathToWgribTool - Path to wgrib2 program
MaxParallelThreads - Maximum number of simultaneous downloads

Each download is retried 5 times by default.

A status.log file is written in the target directory (StorageDirectoryBin\yyyyMMDDHH\status.log) for WRF Runner plugin.

Conversion to HFD5 is for the following variables:

ConvertToHDF5 Variables
GFS Name MOHID Name
TMP:2 m above air temperature
UGRD:10 m above wind velocity X
VGRD:10 m above wind velocity Y
wind modulus
RH:2 m above relative humidity
SOILW:0-0.1 m below ground relative water content (ThetaF)
TCDC:convective cloud layer cloud cover
DSWRF solar radiation

WRF Runner

WRF Runner is a service that runs the regional meteorological model WRF at specified times, making forecasts for a pre-configured domain. Results are available in MOHID Studio as grid or time series at specified sites. This plugin needs GFS Downloader plugin.

The corresponding dll name is ActionSoft.Plugins.Server.WrfRunner.dll.

WRF Runner can be customized by editing the configuration file C:\ProgramData\Action Modulers\<CostumApplicationName>\Configurations\WrfRunner.config.


WrfRunner.config.png
Figure 2 : Block of Configuration from file WrfRunner.config.


Where:

CronExpression - Sec Min Days Month Weekday User. Example: "0 30 7/6 * * ?" means "At 30 minutes past the hour, every 6 hours after 07:00, any user" [2]
StorageDirectory - Directory to store output files
WorkingDirectory - Path to WRF pre-compiled executables, input files and namelists [1]
ConvertToHDF5 - Flag to convert original files into HDF5
InsertIntoDataBase - Register files in the database
ExtractTimeSeries - Flag to export time series from HDF5 file. Sites are specified in the database and configured with MOHID Studio
ForecastDays - Number of forecast days to download
PathToExecutables - Path to wgrib2 program
MaxParallelThreads - XXXX
ModelDomainName - Name of domain
GfsStorageDirectory - path to GFS original 3D files (grib2 format)
SpinUpHours - Number of hours to consider as spin-up period (will be removed from final HDF5 file)
UseMpi - Flag to run WRF in parallel mode wit MPI
NumberOfCores - Number of parallelized threads
PathToMpiExec - Path to MPICH2 libraries


See how to configure a new WRF domain.

Vessel Tracking

Result & Publishing

WMS Server

Rest API

Coastal Risk

Coastal Risk - User Guide



References

  1. Cron expression descriptor tool : http://cronexpressiondescriptor.azurewebsites.net.
  2. Cron expression descriptor tool : http://cronexpressiondescriptor.azurewebsites.net.

Links

User Guides

Coastal Risk