MohidWiki - User contributions [en]

Meteo

2008-09-05T09:57:59Z

193.136.128.7: /* Where are the HDF5 files? */

This chapter explains which meteorological data we have available.
Currently there are 2 meteorological models running operationally for Portugal ([http://www.mmm.ucar.edu/mm5/ MM5] and [http://www.wrf-model.org/ WRF]). The higher operational spatial resolution is 9 km but 3km are already being tested. MM5 3 day forecasts for Portugal are published on [http://meteo.ist.utl.pt/ http://meteo.ist.utl.pt/].
There is also available forecasts and analysis from the global model [http://en.wikipedia.org/wiki/Global_Forecast_System GFS] which are used for initial and boundary conditions for MM5, WRF and recently [http://www.maretec.mohid.com/ww3/ WWIII].
There is also a database of meteorological observations (surface and upperair).

==MM5==
MM5 meteorological surface forecasts are automatically being delivered to MARETEC in MOHID-HDF5 format. This section explains where are the HDF5 files. For other time periods and/or variables, or if you see that there is some file missing or has problems, please email me! (arosa@ist.utl.pt)

===System Operational Configuration===
[http://www.mmm.ucar.edu/mm5/ MM5] is running 4 time per day (00,06,12,18 h UTC) producing 3 days forecasts with 3 spatial nested domains: D1 with 81 km resolution, D2 with 27 km and D3 with 9 km ([http://meteo.ist.utl.pt/ http://meteo.ist.utl.pt/]). These simulation were using [http://en.wikipedia.org/wiki/Global_Forecast_System GFS] grib1 (1º resolution, which is ~80 km at our latitudes). Since August 2007, only 2 domains are simulated (D2 with 27 km and D3 with 9 km) because MM5 uses GFS grib2 output (0.5º resolution, which is ~40 km at our latitudes).
Also, since XXX 7 days forecasts are produced four times per day.

===Where are the HDF5 files?===

Recent files can be found in ftp://ftp.mohid.com/ (meteoIST:mm5) where:

#'''ftp://ftp.mohid.com/mm5_6h''' stored in '''\\alexandria\public\modelos\Meteo_IST\mm5_6h'''
#*Each file has the 2nd 6 hours of simulation. When glued, you can have a combination of the most recent available forecast.
#*simulation 00h : files have outputs from 7:00 to 12:00
#*simulation 06h : files have outputs from 13:00 to 18:00
#*simulation 12h : files have outputs from 19:00 to 00:00
#*simulation 18h : files have outputs from 1:00 to 6:00
#'''ftp://ftp.mohid.com/mm5_7d''' stored in '''\\alexandria\public\modelos\Meteo_IST\mm5_7d'''
#*Simulation 00h with 7 days forecasts. This is only delivered at Friday's to run MOHID Portuguese Coast Operational Model.
#'''ftp://ftp.mohid.com/SIGEL/mm5_3d''' (not being stored)
#*Four daily simulations with 3 days forecasts.

===References to MM5-IST configuration===

*Sousa, T., Domingos, J. (2002) Previsão Meteorológica em Portugal Continental utilizando o modelo operacional e de investigação MM5. Dissertação para obtenção do Grau de Mestre em Ecologia, Gestão e Modelação dos Recursos Marinhos, Instituto Superior Técnico, 150pp. [http://redibericamm5.uib.es/publicacions/any2002/g30_tesi_02.pdf]

*Rodrigo's Msc thesis has a chapter on validation of MM5 forecasts for Guia

*Riflet, G.; Leitão, P.C.; Trancoso, A.R.; Canas,A.; Fernandes, L.; Fernandes, R.; Garcia, A.C.; Mateus, M.; Neves, R.J. (2007). Assessing the quality of a pre-operational model for the portuguese coast. Geophysical Research Abstracts, Vol. 9, 09979, European Geosciences Union, 15 – 20 April, Vienna, Austria

==Maretec archive==

=== MM5 forecasts ===
Here's the unexhaustive list of MM5 data outputs in hdf5 at Maretec data servers. There are three type of domains: D1 (~90 km), D2 (~30 km) and D3 (~10 km). However the domains changed during 2006/2007 and so there are the new D1, D2, D3 and the old D1, D2, D3.

* 20060601 - 20061020:
** D1, D2, D3 \\alexandria\public\modelos\Meteo_IST\mm5_7d\7d_old

* 20061020 - 20061124:
** D1, D2, D3 \\alexandria\public\modelos\Meteo_IST\mm5_3d

* 20061124 - 20061201:
** D2 \\alexandria\public\modelos\Meteo_IST\mm5_7d

* 20061201 - 20070103:
** D2 \\alexandria\public\modelos\Meteo_IST\mm5_7d
** D3 \\alexandria\public\modelos\Meteo_IST\Dezembro2006

* 20070103 - 20070706:
** D2 \\alexandria\public\modelos\Meteo_IST\mm5_7d

* 20070706 - 20080509:
** D2, D3 \\alexandria\public\modelos\Meteo_IST\mm5_7d

=== GFS wind files ===
#'''\\alexandria\public\modelos\Meteo_IST\GFS\'''
#*Daily 1 day wind forecasts(from 0h00 to 21h00) from GFS model covering the North Atlantic
#'''\\alexandria\public\modelos\Meteo_IST\GFS\latest\'''
#*Daily 7 days wind forecasts from GFS model covering the North Atlantic

==Related Pages==

*[[Module_InterfaceWaterAir]]
*[[ConvertToHDF5]]

Module Atmosphere

2008-08-14T13:11:42Z

193.136.128.7:

== Overview ==
The atmosphere module is responsible for meteorological data needed to compute processes occurring at the water-air interface, such as computing wind shear stress, radiation balances, latent and sensible heat fluxes.

A user manual is available in the link at the bottom of the page. This user manual intends to help the user to couple atmosphere to water, activating in MOHID wind forcing, heat fluxes and mass fluxes between this interface.

== Concepts ==

== Main processes ==

=== Air temperature ===
Air temperature is used for latent heat, sensible heat and downward longwave radiation computation (in the atmoshphere-water interface).

=== Solar radiation ===
Heat flux with solar origin hitting the water surface.
In absence of field data it can be computed based on two approaches that depend both on Top Of Atmosphere Radiation, sun height and cloud cover:

i) MOHID (default method)

ii) CE-QUAL based method.

Solar radiation is used to compute radiation that enters the water surface (after reflection). One method for cloud cover computation also uses radiation as input.

=== Wind ===
Wind is described by its velocity decomposed on x and y components. If not available it can be computed from wind modulus and wind direction.

Wind is used to compute latent heat, sensible heat and wind stress (in the water-atmoshphere interface).

===Specific humidity===
Specific humidity is the ratio of water mass present in the atmosphere against the air mass. Moisture mixture is the ratio of water mass against that of dry air. Relative humidity can be computed from specific humidity, pressure and air temperature when not given.

=== Relative humidity ===
Relative humidity is a term used to describe the amount of water vapor that exists in a gaseous mixture of air and water.
The relative humidity of an air-water mixture is defined as the ratio of the partial pressure of water vapor in the mixture to the saturated vapor pressure of water at a given temperature.

Relative humidity is used for latent heat computation (in the water-atmoshphere interface).

=== Precipitation ===
Mass Flux from rain.

=== Sun hours ===

=== Cloud cover ===
Fraction of sky covered with clouds. Represents the radiation absorption in the atmosphere.
It can be computed from three approaches:

i) comparison between measured sun hours (if available) with potential sun hours;

ii) comparison between solar radiation (measured or computed) and top of atmosphere radiation;

iii) random solution (default method).

Cloud cover is used for downward long wave radiation computation (in the atmoshphere-water interface). One method in solar radiation computation (if no data available) uses cloud cover as input.

'''Remarks''':

* Random solution is default method but it shoud not.

* Cloud cover should never be computed from computed radiation. This latter situation returns always zero cloud cover and zero radiation in the results (*).

* Cloud cover computation from measured radiation has the advantage that is not a random calculation but has the disadvantage that returns the same trend as radiation data: meaning that every day at night sky is completely covered with clouds and reaches minimum cloud cover at solar mid day. It may not be realistic for heat budgets at night.

(*)This appens because the model is initialized with zero radiation; then, if cloud cover is computed from radiation it returns zero cloud cover (**) in next time step which in turn results in zero transmissivity and zero radiation, going on cycle.

(**) in MOHID code for cloud cover computation from radiation, cloud cover units are different than standard, being value 1 the situation with no clouds and zero the opposite.

=== Irrigation ===
Mass flux from water added by anthropogenic sources.

== Other features ==

=== Random components ===
Cloud cover computation has as it default method a random method. This method was adapted from CE-Qual formulation.
See cloud cover for further information.

== User Manual ==
[[Coupling_Water-Atmosphere_User_Manual]]

== Links ==

*[[Module_InterfaceWaterAir]]
*[[ConvertToHDF5]]

[[Category:Modules]]
[[Category:MOHID Base 2]]

Jabber

2008-05-22T18:02:37Z

193.136.128.7: /* jabber bot */

[[Jabber]] is xmpp-based free instant messenger. [[Twitter]] also uses jabberbots to send twitters.

==accounts==
* damnthug: damnthug42@xmpp.us
* pointpt: pointpt@jabber-fr.net

==jabber bot==

> ./echo_threaded.rb damnthug42@xmpp.us secretpass

> ./my_jabber_bot.rb damnthug42@xmpp.us secretpass

[[Category:Internet]]
[[Category:Linux]]
[[Category:Ruby]]

Gems

2008-05-22T15:00:38Z

193.136.128.7: /* xmpp4r */

[[gems|Rubygems]] is the extension manager for [[ruby]]. Much like cpan is the extension manager for [[Perl]]. [[Gems]] is more than a packaging manager: it's a library versioning manager too! [http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/132899 That is also it's achille's heel].

==Install==
Requires [[ruby]] to be installed prior.

Install [http://rubygems.org/ rubygems]
> wget http://rubyforge.org/frs/download.php/35283/rubygems-1.1.1.tgz
> tar -xvf rubygems-1.1.1.tgz
> cd rubygems-1.1.1
> ruby setup.rb

Install extra-packages for gems to work correctly
> sudo apt-get install ruby1.8-dev

To configure gems on your system you need to set the environment variable RUBYOPT. This will preload "require gems" to every ruby script you run.
>vim ~/.bashrc
.bashrc> export RUBYOPT=rubygems

==Popular gems==
===xmpp4r===
[[xmpp]] is the open protocol behind the [[jabber]] service.

> sudo apt-get install libopenssl-ruby
> sudo gem install xmpp4r -y

Testing
> irb
irb> require 'xmpp4r/client'

====xmpp4r-simple====
> sudo gem install xmpp4r-simple -y

===twitter===
> sudo gem install twitter -y

==External references==
*[[Ruby]],
*[http://rubygems.org/ gems homepage]

[[Category:Programming]]
[[Category:Ruby]]
[[Category:Linux]]

Regexp

2008-05-11T10:01:42Z

193.136.128.7: /* See also */

[[Regexp]] stands for regular expressions. Regular expressions are what made languages like [[Awk]] and [[Perl]] notorious. Regular expressions are expressions equating a pattern string. To write a regular expression in [[Perl]] on must insert it between slashes (''/regexp/'')For example:
/[a-z]/
means all the alphabet lowercase letters.
/[0-4]/
stands for all the digits from 0 to 4 inclusive.
/\d{2,5,7}/
stands for all the sequences of 2, 5 or 7 digits.

The interesting thing is that you can compose regexps into complex patterns. For example the regexp
/[A-Z]:[0-3]\.\S{1,8}/
describes a pattern that will match, for example, the strings ''B:1.HelloSir'' or '''A:0.Good''. But it will not match ''a:2.darn'' because the first letter must be uppercase.

==See also==
*[[Perl]]
*[[Bash]]
*[[Sed]]
*[[Awk]]
*[[Python]]
*[[Ruby]]

[[Category:Perl]]
[[Category:Linux]]
[[Category:Windows]]
[[Category:Programming]]

Model setup methodology

2007-06-28T18:29:15Z

193.136.128.7:

NOTE: This article has been discontinued and is no longer maintained.

This is the log of the current best-practice methodology for setting up hydrodynamic nested models.

== Build the General Data ==
=== Bathymetries ===

*'''[[Grid]]''': First of all, define your domain(s) and build the grid(s). We use [[Mohid GIS]] for that matter. For nested models, remember to keep a maximum downscaling factor ratio of ''1:3''. In the end, you should have a bunch of [[Grid|''.grd'']] files.

*'''Baseline data''': Next, you need to define/obtain your baseline topographic/bathymetric data as well as your landline data. For example, in regional oceanography, one could choose the ETOPO or GEBCO datasets (available in intranet at ''\\kepler\DataCenter\DadosBase\Oceanografia\Batimetria'') for the bathymetry.

*'''[[ConvertToXYZ]]''': However, before interpolation of the datasets to your grid, you need to convert the dataset into a readable file for [[Mohid GIS]]. [[ConvertToXYZ]] is a little program used for that effect. It will create a [[XYZ points| ''.xyz'']] file.

*'''[[Digital Terrain Creator]]''': Create land line and save it as a [[Polygons|''.xy'']] file. Interpolate the bathymetry data [[XYZ points| ''.xyz'']] file to your grid by using the [[Digital Terrain Creator]] software.

*'''[[SmoothBatimNesting]]''': Optionally, if you created a son grid, then you'll want to smooth it near the boundaries relatively to the father grid. We use the [[SmoothBatimNesting]] software for that matter.

*'''Retouch''' manually the bathymetry [[Grid Data|''.dat'']] file(s) under [[Mohid GIS]] in order to remove all awkward looking cells, as they tend to be a nuisance for stability issues later on.

That's it, your bathymetries should be ready to go!

=== Tidal gauges ===
To simulate tide, [[MOHID]] generates the tide water level at the boundaries by interpolation of
predicted levels between points defined near the open boundaries of the domain. The predicted levels are calculated by the [[TidePrev]] software embedded in [[MOHID]]. [[TidePrev]] calculates the water level from the tidal harmonic components. The harmonic components are given by the [[Fes95]] or the [[Fes2004]] solution, and tidal gauges can be extracted for points near the boundary. Thus [[MOHID]] requires the tidal gauges. The tidal gauges are obtained by the [[Fes95]] or [[Fes2004]] software. The input for the [[Fes2004]] software is an [[XYZ points| ''.xyz'']] file.

=== Initial S and T fields ===
S and T fields are waterproperties. Mohid allows several ways to initialize S and T.
*PROFILE
*LAYERS
*ASCII_FILE
*etc...
You should refer to [[waterproperties.dat]] to learn how to initialize S and T.

[[Category:MOHID Water]]

FillMatrix

2007-06-22T15:40:33Z

193.136.128.7: /* Input file (FillMatrix.dat) */

The '''FillMatrix''' application creates a [[Grid Data|grid data]] file or [[HDF5]] file from data interpolated from [[XYZ points|XYZ]] or [[Time Series]] files.

It should not be confused with [[Module FillMatrix]] which is responsible in MOHID for handling data input to 2D or/and 3D arrays.

Running options for this application are specified by the user in a input file named [[FillMatrix#Input file (FillMatrix.dat)|FillMatrix.dat]].

==Introduction==

This application considers georeferenced data in an interpolation process to obtain one or a time series of 2D fields usable in the MOHID framework. The interpolation process involves spatial interpolation, in the case of a time invariant 2D field, and spatial and time interpolation, in the case of a time series of 2D fields.

The georeferenced data can be of two types:

- time invariant: XYZ data, defined in a XYZ file or directly by the user in the input file;

- time variant: time series data, defined in a time series file.

The data location defined individually by the user in the input file is called a '''station'''.

The output field is obtained for the desired property and can also be time invariant or time variant:

- a '''time invariant field (grid data file)''' is obtained from spatial interpolation and time interpolation for a time instant specified by the user;

- a '''time variant field (HDF5 file)''' is determined taking into account user-defined time window, a maximum time span and output times; the maximum time span is used in case of data lacking to control the process of interpolation: if a source of time variant data has data more distant in time from the desired output time than the maximum time span then this source is not considered in the interpolation.

The interpolation in space can be accomplished using triangulation or [[inverse-distance weighted method]]. In this second method the user can specify the inverse-distance weighting power and the maximum distance between the intended grid location and a data station for that station to be considered in the spatial interpolation.

The interpolation in time is linear.

'''Typical use:'''

Generate, from measurement networks data, initial or forcing data for MOHID Water models.

'''Data input requirements:'''

A [[Grid Data|grid data]] file containing grid and mapping information for the intended output file. This is commonly a bathymetry file.

One or more files containing data to use as the interpolation basis, which can consist in:

- one [[XYZ points|XYZ]] file, if the intended output data field is not time variable;

- one or more [[Time Series]] files, each representing a station, usable both in cases of time variable or non variable fields.

Alternatively the use of data files can be ignored, being the data values for each station supplied by the user in the input file.

The coordinate system must be the same in all files.

'''Ouput:'''

An grid data or a HDF5 file, respectively in case a time invariant and a time variant field is generated.

==Input file (FillMatrix.dat)==

PROPERTY_NAME : ... (name of the property whose values are being interpolated)
PROPERTY_UNITS : ... (units of property whose values are being interpolated)

OUTPUT_FILE : ... (path/name of output data file)

VARIABLE_IN_TIME : 0/1 (states if fields to be created are variable in time:
0 = not variable (default), 1 = variable)
(if they are variable in time a HDF5 file is created)

GRID_DATA_FILE : ... (path/name of input grid data file, a bathymetry/topography file)

INTERPOLATION_METHOD : 1/2 (spatial interpolation method: 1 = triangulation, 2 = IWD)

XYZ_FILE : ... (path/name of input XYZ file, in Mohid GIS format)

(if XYZ_FILE not provided:)
(block for each station containing data to be considered; may be several)
<begin_station>
NAME : ... (name of station)
X : ... (XX coordinate of the station)
Y : ... (YY coordinate of the station)
VALUE_TYPE : ... (type of information: "SINGLE_VALUE" (default), "TIMESERIE")
(if VALUE_TYPE : SINGLE_VALUE:)
VALUE : ... (property value of the station)
(if VALUE_TYPE : TIMESERIE:)
FILENAME : ... (path/name of station time series file)
DATA_COLUMN : ... (column where data is stored)
<end_station>

(if VARIABLE_IN_TIME : 1:)
START : ... (start time: yyyy mm dd hh mm ss)
END : ... (end time: yyyy mm dd hh mm ss)
MAX_TIME_SPAN : ... (maximum span in seconds for a time serie value to be
considered valid as data source)
OUTPUT_TIME : ... (output time in seconds, may be provided several values)
SKIP_NULLVALUES : 0/1 (option to do not output null values: 0 = no (default), 1 = yes)

(if VARIABLE_IN_TIME : 0:)
TIME_INSTANT : ... (time instant in which to extract data from time series:
yyyy mm dd hh mm ss)

(if INTERPOLATION_METHOD : 1:)
FILL_OUTSIDE_POINTS : 0/1 (option to perform extrapolation in triangulation: 0 = no
(default), 1 = yes)
WRITE_TRIANGLES : 0/1 (option to write a polygon file with created triangles in
triangulation: 0 = no (default), 1 = yes)
TRIANGLES_FILE : ... (path/name of triangles file to create)

(if INTERPOLATION_METHOD : 2:)
MAX_DISTANCE : ... (maximum allowed distance between a data source location and
the output grid location)
IWD_N : ... (inverse-distance weighting power; 2.0 = default)

''Remarks:''

- output field can only be obtained for one property/parameter per FillMatrix application run;

- although not required it is advisable that the attributed property/parameter name is
consistent with the MOHID naming convention, so that the produced output file is readily used
in other MOHID applications;

- FillMatrix application assumes that the input georeferenced data is in the same coordinate
system and property units requested for the output field;

- in OUTPUT_TIME keyword (case VARIABLE_IN_TIME : 1) at least two values in seconds must be
provided: the first value indicates the time in seconds after the start time when is made
first output, the last value is the afterwards time step of the outputs; when more than two
values are provided (maximum of 240 values) the values between the first and the last are
considered the time, from the start time, of specific outputs, after which the time step value
is considered for output: e.g. OUTPUT_TIME : 0 7200 21600 3600 means outputs at the start
time, after 7200 seconds from start, after 21600 seconds from start and after every 3600
seconds;

- the default value for the IWD_N keyword is considered by N.O.A.A. 1972, ''National Weather''
''Service River Forecast System forecast procedures'', TM NWS HYDRO-14, US Department of
Commerce, Washington DC. adequate for interpolation of rainfall data.

==Sample==
PROPERTY_NAME : batim
PROPERTY_UNITS : m
VARIABLE_IN_TIME : 0
TIME_INSTANT : 2005 1 1 0 0 0

OUTPUT_FILE : PolygonBatimIWN.dat

GRID_DATA_FILE : PolygonBatim.dat
XYZ_FILE : vigo.xyz

INTERPOLATION_METHOD : 2
MAX_DISTANCE : 0.005
IWD_N : 2

[[Category:Tools]]

Inverse-distance weighted method

2007-06-22T15:14:08Z

193.136.128.7:

In this method of interpolation the value of a property at a target location is determined as the weighted sum of the property value at the sampled locations, being the weight of each sample value a power of the inverse of the distance between the target location and the sample location.

The value of the inverse-distance weighting power controls the region of influence of each sampled location: as its value increase the region of influence decreases until it becomes the area which is closer to the target location than to any other location, a null value causes the method of interpolation to be equivalent to averaging the sample values.

References:

Lam, N. S., 1983, "Spatial interpolation methods review", ''The American
Cartographer'', 10, pp. 129-149.

Mohid Statistics Analyser

2007-06-22T14:46:00Z

193.136.128.7: /* Graphic output */

The '''Mohid Statistics Analyser''' application calculates statistics and obtains graphs of comparison between two time series data.

Running options for this application are specified in an [[Mohid Statistics Analyser#User interface|interface]].

==Introduction==

For model validation or model comparison studies it is usefull to calculate comparison statistics and graphs. The Mohid Statistics Analyser allows the creation of such information for one or more properties with two site specific [[Time Series|time series]] files in a user-friendly way.

The properties which can be object of such analysis are the properties present in the time series. It is not required by the Mohid Statistics Analyser that the comparison is made for the same property in both time series, i.e., interproperties comparisons are possible. Per application run only one pair of time series can be analysed.

The information is obtained based on data located on a time window. That time window is defined as the time period for which data exist in both time series and any further constrain indicated by the user in the interface. If time instants in the two time series are different then the second time series data is linearly interpolated for the first time series data time instants.

The instant data in the time window is considered to obtain the all data information: "Statistics (All)" and "Graph (All)". This data is also preprocessed to derive the daily and monthly information: daily information ("Statistic (Daily)" and "Graph (Daily)") is obtained from the daily averages of the data and monthly information ("Statistic (Monthly)" and "Graph (Monthly)") is obtained from the monthly averages of the data.

The statistics which are calculated for each application run consist in:

- average of time series 1 data ("Observed Average");

- average of time series 2 data ("Modeled Average");

- bias;

- root mean square error (RMSE);

- Pearson product-moment correlation coefficient (R<sup>2</sup>);

- Nash-Sutcliffe coefficient of model efficiency.

The graphs are representations of the second time series data as a function of the first time series data - XY graphs. Several graph types and appearances can be selected.

'''Typical use:'''

Calculate statistics and graphics comparing the MOHID results with observed data.

'''Data input requirements:'''

Two [[Time Series|time series]] files containing data from different sources, generally one having observed data and another having model results.

'''Ouput:'''

Statistics and XY graphs, presenting the second time series data as a function of the first time series data, considering all data values for the time instants of the first time series, daily averages and monthly averages.

==User interface==

The user interface is generally installed in the personal computer together with MOHID GIS and MOHID GUI and other applications, in the MOHID package.

The access to the interface executable file can be done through the Programs section of the Start Menu of the Desktop.

After access to the interface a '''window''' appears with '''7 selectable tabs:'''

- '''Geral''': tab where the user makes the '''input''' of information required to run the Mohid Statistics Analyser application;

- '''Statistic (All)''': tab presenting '''output''' statistics obtained considering all data values;

- '''Statistic (Daily)''': tab presenting '''output''' statistics obtained from daily averages values;

- '''Statistic (Monthly)''': tab presenting '''output''' statistics obtained from monthly averages values;

- '''Graph (All)''': tab presenting the '''output''' XY graph of all data values;

- '''Graph (Daily)''': tab presenting the '''output''' XY graph of daily averages values;

- '''Graph (Monthly)''': tab presenting the '''output''' XY graph of monthly averages values.

In the next sections are presented the details about [[Mohid Statistics Analyser#User interface#Data input|Data input]], [[Mohid Statistics Analyser#User interface#Statistics output|Statistics output]] and [[Mohid Statistics Analyser#User interface#Graph output|Graph output]].

===Data input===

The data input information is inserted by the user in the '''Geral''' tab, through the following steps:

- select the first time series, which will be considered the observed data and will define the time instants of both time series data, by writing the correspondent path in '''Geral --> Observed Data --> Filename''' or by clicking the respective '''Browse''' button and finding in the file in the computer folders; if the specified path does not exist then a window with an error message is generated;

- in the '''Geral --> Observed Data''' area appears the list of variables with data available in the selected time series; the user must then select the intended variable for the comparison;

- select the second time series, which will be considered the model data, by writing the correspondent path in '''Geral --> Model Data --> Filename''' or by clicking the respective '''Browse''' button and finding in the file in the computer folders; if the specified path does not exist then a window with an error message is generated;

- in the '''Geral --> Model Data''' area appears the list of variables with data available in the selected time series; the user must then select the intended variable for the comparison; this choice must be done carefully since the application does not require that the same variable must be selected in both time series;

- in the '''Geral --> Parameter''' area appears the time window where data is available for comparison; the user can restrict this time window to the desirable comparison interval using the available buttons; the time window can be reset at any time to the original one by clicking the '''Parameter --> Reset Dates''' button;

- click the '''Geral --> Process...''' button for input data processing.

During input data processing some messages for the user are generated and those appear together with a progress bar in the area bellow the '''Process...''' button. Error or warning messages can appear in separate windows during the processing, namely if the time window is badly specified (error message) or if a specific type of average data (daily or monthly) is not available.

The sucessfull processing terminates with a "Done!" message. In this case in the '''Geral --> Show Time Series''' presents for selection three buttons each causing the appearance of an individual window ('''Time Serie Graph''') where the actual time series considered for comparison is presented in graph form:

- '''All Values''': time series of values considered for Statistic (All) and Graph (All) tabs results;

- '''Daily Values''': time series of values considered for Statistic (Daily) and Graph (Daily) tabs results (daily averages);

- '''Monthly Values''': time series of values considered for Statistic (Monthly) and Graph (Monthly) tabs results (monthly averages).

In each time series graph window it is possible to change the features of the graph using the available buttons in the menu located above the graph, namely:

- '''Chart Type''': opens a '''Command and Options''' window allowing the selection of several actions: '''General''', '''Border/Fill''', '''Data Sheet''', '''Type''', '''Series Groups''', '''Show/Hide''';

- '''Undo''': undoes any graph change operation;

- '''Show/Hide Legend''': selecting the button causes the appearance of the legend, clicking on it again makes the legend disapear;

- '''Commands and Options''': opens a '''Command and Options''' window allowing the selection of several actions: '''General''', '''Border/Fill''', '''Data Sheet''', '''Type''', '''Series Groups''', '''Show/Hide''';

- '''Chart Wizard''': opens a '''Command and Options''' window allowing the selection of actions concerning '''Data Source''', '''Data Sheet''' and '''Type''';

- '''Help''': opens a help window where can be found information on how to change the graph features using the buttons referred before.

Four additional buttons, located beneath the graph, command the following actions:

- '''CheckBox1''': checking it allows the selection in '''Window Width [days]''' the number of days to appear in the graph and in the ruler the location in the time interval of that number of days;

- '''Save XML''': saves the graph in XML code in the path provided by the user;

- '''Save Image''': saves the graph as a GIF or JPEG file in the path provided by the user;

- '''Exit''': causes the closing of the '''Time Serie Graph''' window.

Back to the Mohid Statistics Analyser Geral tab, the lower-right button '''Exit''' exits the Mohid Statistics Analyser window.

===Statistics output===

The Mohid Statistics Analyser statistics output is organized in the '''Statistic (All)''', '''Statistic (Daily)''' and '''Statistic (Monthly)''' tabs, for statistics considering all data, daily averages and monthly averages, respectively.

This output is only produced after the data input by the user in the '''Geral''' tab and the successful data processing.

In each of the statistics tabs the information content is similar:

- '''Observed Average''' (average of the first time series);

- '''Modeled Average''' (average of the second time series);

- '''Bias''';

- '''RMSE''' (root mean square error);

- '''R<sup>2</sup>''' (Pearson product-moment correlation coefficient);

- '''Model Efficiency''' (Nash-Sutcliffe coefficient).

For each of these statistic parameters is presented the calculated value, in the grey area, and a small description of the meaning and the interpretation of the parameter, in the blue area.

Beneath the parameters information are presented some notes on the approach used to calculate the statistics.

The lower-right button '''Exit''' in each Statistics tab exits the Mohid Statistics Analyser window.

===Graphic output===

The Mohid Statistics Analyser graphic output is organized in the '''Graph (All)''', '''Graph (Daily)''' and '''Graph (Monthly)''' tabs, for graphs considering all data, daily averages and monthly averages, respectively.

This output is only produced after the data input by the user in the '''Geral''' tab and the successful data processing.

In each of the graphs tabs the information content is similar: a XY point graph of second time series data ('''Model Data''') as a function of the first time series data ('''Observed Data''').

It is possible to change the features of the graph using the available buttons in the menu located above the graph, namely:

- '''Chart Type''': opens a '''Command and Options''' window allowing the selection of several actions: '''General''', '''Border/Fill''', '''Data Sheet''', '''Type''', '''Series Groups''', '''Show/Hide''';

- '''Undo''': undoes any graph change operation;

- '''Show/Hide Legend''': selecting the button causes the appearance of the legend, clicking on it again makes the legend disapear;

- '''Commands and Options''': opens a '''Command and Options''' window allowing the selection of several actions: '''General''', '''Border/Fill''', '''Data Sheet''', '''Type''', '''Series Groups''', '''Show/Hide''';

- '''Chart Wizard''': opens a '''Command and Options''' window allowing the selection of actions concerning '''Data Source''', '''Data Sheet''' and '''Type''';

- '''Help''': opens a help window where can be found information on how to change the graph features using the buttons referred before.

The lower-right button '''Exit''' in each Graph tab exits the Mohid Statistics Analyser window.

The Mohid Statistics Analyser application does not allow the saving of the Graph tabs images.

[[Category:Tools]]
[[Category:Graphical User Interfaces]]