<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://www.wiki.mohid.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Guillaume</id>
		<title>MohidWiki - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://www.wiki.mohid.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Guillaume"/>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Special:Contributions/Guillaume"/>
		<updated>2026-04-04T14:37:00Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.28.0</generator>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nb-vf-cf&amp;diff=6750</id>
		<title>Nb-vf-cf</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nb-vf-cf&amp;diff=6750"/>
				<updated>2013-07-02T17:57:09Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: Created page with &amp;quot;Quick tips for work.  Launch ''routes.bat'' written by Gustavo in order to allow both wifi to access extranet and cable ethernet to access intranet (twice).  Disable IPV6 from yo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Quick tips for work.&lt;br /&gt;
&lt;br /&gt;
Launch ''routes.bat'' written by Gustavo in order to allow both wifi to access extranet and cable ethernet to access intranet (twice).&lt;br /&gt;
&lt;br /&gt;
Disable IPV6 from your wireless configuration because otherwise google's ipv6 enforcing will generate a conflict between intranet access and extranet access.&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6749</id>
		<title>Nagios</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6749"/>
				<updated>2013-07-02T17:43:58Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Useful links and commmands for the OMD package */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...&lt;br /&gt;
&lt;br /&gt;
==Useful links and commmands for the OMD package==&lt;br /&gt;
&lt;br /&gt;
* http://[nagios-server]:8888/[site]/thruk --&amp;gt; identifies the nagios plugin (script in perl, python, bash...)&lt;br /&gt;
* http://[nagios-server]:8888/[site]/nagios --&amp;gt; nagios basic frontend&lt;br /&gt;
* http://[nagios-server]:8888/[site]/check_mk --&amp;gt; check_mk frontend&lt;br /&gt;
&lt;br /&gt;
Sites: ppv, teste&lt;br /&gt;
&lt;br /&gt;
Nagios server: 10.15.228.34:8888&lt;br /&gt;
&lt;br /&gt;
Ssh server to nagios vm: 10.15.228.34:2222&lt;br /&gt;
&lt;br /&gt;
==How to add a new service to a site and host==&lt;br /&gt;
 &lt;br /&gt;
 &amp;gt; sudo su - [site]&lt;br /&gt;
 &amp;gt; vim /opt/omd/sites/[site]/etc/nagios/conf.d/ngpp.cfg&lt;br /&gt;
&lt;br /&gt;
'''ngpp.cfg''' is a specific configuration file of the services for the host ''ngpp''.&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://omdistro.org/doc/quickstart_debian_ubuntu OMD for debian ubuntu]&lt;br /&gt;
*[http://mathias-kettner.com/check_mk.html Check_mk]&lt;br /&gt;
&lt;br /&gt;
[Category:Linux]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6748</id>
		<title>Nagios</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6748"/>
				<updated>2013-07-02T17:33:50Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...&lt;br /&gt;
&lt;br /&gt;
==Useful links and commmands for the OMD package==&lt;br /&gt;
&lt;br /&gt;
* http://[nagios-server]:8888/[site]/thruk --&amp;gt; identifies the nagios plugin (script in perl, python, bash...)&lt;br /&gt;
* http://[nagios-server]:8888/[site]/nagios --&amp;gt; nagios basic frontend&lt;br /&gt;
* http://[nagios-server]:8888/[site]/check_mk --&amp;gt; check_mk frontend&lt;br /&gt;
&lt;br /&gt;
Sites: ppv, teste&lt;br /&gt;
&lt;br /&gt;
Nagios server: 10.15.228.34:8888&lt;br /&gt;
&lt;br /&gt;
Ssh server to nagios vm: 10.15.228.34:2222&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://omdistro.org/doc/quickstart_debian_ubuntu OMD for debian ubuntu]&lt;br /&gt;
*[http://mathias-kettner.com/check_mk.html Check_mk]&lt;br /&gt;
&lt;br /&gt;
[Category:Linux]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6747</id>
		<title>Nagios</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6747"/>
				<updated>2013-07-02T17:33:28Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...&lt;br /&gt;
&lt;br /&gt;
==Useful links and commmands for the OMD package==&lt;br /&gt;
&lt;br /&gt;
* http://[nagios-server]:8888/[site]/thruk --&amp;gt; identifies the nagios plugin (script in perl, python, bash...)&lt;br /&gt;
* http://[nagios-server]:8888/[site]/nagios --&amp;gt; nagios basic frontend&lt;br /&gt;
* http://[nagios-server]:8888/[site]/check_mk --&amp;gt; check_mk frontend&lt;br /&gt;
&lt;br /&gt;
Sites: ppv, teste&lt;br /&gt;
Nagios server: 10.15.228.34:8888&lt;br /&gt;
Ssh server to nagios vm: 10.15.228.34:2222&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://omdistro.org/doc/quickstart_debian_ubuntu OMD for debian ubuntu]&lt;br /&gt;
*[http://mathias-kettner.com/check_mk.html Check_mk]&lt;br /&gt;
&lt;br /&gt;
[Category:Linux]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6746</id>
		<title>Nagios</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6746"/>
				<updated>2013-07-02T17:32:01Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...&lt;br /&gt;
&lt;br /&gt;
==Useful links and commmands for the OMD package==&lt;br /&gt;
&lt;br /&gt;
* http://[nagios-server]:8888/[site]/thruk --&amp;gt; identifies the nagios plugin (script in perl, python, bash...)&lt;br /&gt;
* http://[nagios-server]:8888/[site]/nagios --&amp;gt; nagios basic frontend&lt;br /&gt;
* http://[nagios-server]:8888/[site]/check_mk --&amp;gt; check_mk frontend&lt;br /&gt;
&lt;br /&gt;
Sites: ppv, teste&lt;br /&gt;
Nagios server: 10.15.228.34:2222&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://omdistro.org/doc/quickstart_debian_ubuntu OMD for debian ubuntu]&lt;br /&gt;
*[http://mathias-kettner.com/check_mk.html Check_mk]&lt;br /&gt;
&lt;br /&gt;
[Category:Linux]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6745</id>
		<title>Nagios</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6745"/>
				<updated>2013-07-02T17:28:17Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* External References */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://omdistro.org/doc/quickstart_debian_ubuntu OMD for debian ubuntu]&lt;br /&gt;
*[http://mathias-kettner.com/check_mk.html Check_mk]&lt;br /&gt;
&lt;br /&gt;
[Category:Linux]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6744</id>
		<title>Nagios</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6744"/>
				<updated>2013-07-02T15:28:07Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://omdistro.org/doc/quickstart_debian_ubuntu OMD for debian ubuntu]&lt;br /&gt;
&lt;br /&gt;
[Category:Linux]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6743</id>
		<title>Nagios</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Nagios&amp;diff=6743"/>
				<updated>2013-07-02T15:27:27Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: Created page with &amp;quot;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...  ==External...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Nagios is a monitoring tool that mediates several plugins that find useful information to the user, such as cpu usage, ping time reply, disk usage, ram usage, etc ...&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://omdistro.org/doc/quickstart_debian_ubuntu OMD for debia ubuntu]&lt;br /&gt;
&lt;br /&gt;
[Category:Linux]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6738</id>
		<title>Svn faia</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6738"/>
				<updated>2013-06-24T14:02:27Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Checkout */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is the log of the instructions followed to install an svnserver in debian/ubuntu and to create a repository and add some code files. This tutorial follows closely on the following [http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ link].&lt;br /&gt;
&lt;br /&gt;
==Manual==&lt;br /&gt;
===svn server===&lt;br /&gt;
====installation====&lt;br /&gt;
 &amp;gt; sudo apt-get install subversion libapache2-svn&lt;br /&gt;
 &amp;gt; sudo mkdir /var/svnserver&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver&lt;br /&gt;
&lt;br /&gt;
====dav-svn configuration====&lt;br /&gt;
 &amp;gt; sudo vim /etc/apache2/mods-available/dav_svn.conf&lt;br /&gt;
 dav_svn.conf&amp;gt;&lt;br /&gt;
 # remove the # in front of the &amp;lt;location and &amp;lt;/location&lt;br /&gt;
 &amp;lt;Location /svn&amp;gt;&lt;br /&gt;
  DAV svn&lt;br /&gt;
  SVNParentPath /var/svnserver&lt;br /&gt;
  AuthType Basic&lt;br /&gt;
  AuthName &amp;quot;Subversion Repository&amp;quot;&lt;br /&gt;
  AuthUserFile /etc/apache2/dav_svn.passwd&lt;br /&gt;
  Require valid-user&lt;br /&gt;
  #SSLRequireSSL      # this line must be added if you want SSL enabled&lt;br /&gt;
 &amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====apache daemon restart====&lt;br /&gt;
 &amp;gt; sudo a2enmod dav_svn&lt;br /&gt;
 &amp;gt; sudo /etc/init.d/apache2 restart&lt;br /&gt;
&lt;br /&gt;
====add users====&lt;br /&gt;
 # First user with -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd -c /etc/apache2/dav_svn.passwd firstuser&lt;br /&gt;
 # Next users without -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd /etc/apache2/dav_svn.passwd nextuser&lt;br /&gt;
&lt;br /&gt;
===Repositories===&lt;br /&gt;
====New repo====&lt;br /&gt;
 &amp;gt; sudo svnadmin create /var/svnserver/repos&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver/repos&lt;br /&gt;
&lt;br /&gt;
====Test repo====&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
&lt;br /&gt;
====Add new project folder====&lt;br /&gt;
 &amp;gt; mkdir /path/to/localrepo&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
 &amp;gt; cp -R /path/to/project /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn add ./project&lt;br /&gt;
 &amp;gt; svn commit -m &amp;quot;Initial commit&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
===Regular user===&lt;br /&gt;
====Checkout====&lt;br /&gt;
 &amp;gt; mkdir /path/to/localrepo&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
&lt;br /&gt;
or&lt;br /&gt;
&lt;br /&gt;
 &amp;gt; svn co http://eibd.ist.utl.pt/svn/repos&lt;br /&gt;
&lt;br /&gt;
====Update====&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn update&lt;br /&gt;
&lt;br /&gt;
====Commit changes====&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn commit -m 'Commit description'&lt;br /&gt;
&lt;br /&gt;
==External references==&lt;br /&gt;
*[http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ debian svn server tutorial]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Linux]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6737</id>
		<title>Svn faia</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6737"/>
				<updated>2013-06-21T22:52:14Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is the log of the instructions followed to install an svnserver in debian/ubuntu and to create a repository and add some code files. This tutorial follows closely on the following [http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ link].&lt;br /&gt;
&lt;br /&gt;
==Manual==&lt;br /&gt;
===svn server===&lt;br /&gt;
====installation====&lt;br /&gt;
 &amp;gt; sudo apt-get install subversion libapache2-svn&lt;br /&gt;
 &amp;gt; sudo mkdir /var/svnserver&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver&lt;br /&gt;
&lt;br /&gt;
====dav-svn configuration====&lt;br /&gt;
 &amp;gt; sudo vim /etc/apache2/mods-available/dav_svn.conf&lt;br /&gt;
 dav_svn.conf&amp;gt;&lt;br /&gt;
 # remove the # in front of the &amp;lt;location and &amp;lt;/location&lt;br /&gt;
 &amp;lt;Location /svn&amp;gt;&lt;br /&gt;
  DAV svn&lt;br /&gt;
  SVNParentPath /var/svnserver&lt;br /&gt;
  AuthType Basic&lt;br /&gt;
  AuthName &amp;quot;Subversion Repository&amp;quot;&lt;br /&gt;
  AuthUserFile /etc/apache2/dav_svn.passwd&lt;br /&gt;
  Require valid-user&lt;br /&gt;
  #SSLRequireSSL      # this line must be added if you want SSL enabled&lt;br /&gt;
 &amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====apache daemon restart====&lt;br /&gt;
 &amp;gt; sudo a2enmod dav_svn&lt;br /&gt;
 &amp;gt; sudo /etc/init.d/apache2 restart&lt;br /&gt;
&lt;br /&gt;
====add users====&lt;br /&gt;
 # First user with -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd -c /etc/apache2/dav_svn.passwd firstuser&lt;br /&gt;
 # Next users without -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd /etc/apache2/dav_svn.passwd nextuser&lt;br /&gt;
&lt;br /&gt;
===Repositories===&lt;br /&gt;
====New repo====&lt;br /&gt;
 &amp;gt; sudo svnadmin create /var/svnserver/repos&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver/repos&lt;br /&gt;
&lt;br /&gt;
====Test repo====&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
&lt;br /&gt;
====Add new project folder====&lt;br /&gt;
 &amp;gt; mkdir /path/to/localrepo&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
 &amp;gt; cp -R /path/to/project /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn add ./project&lt;br /&gt;
 &amp;gt; svn commit -m &amp;quot;Initial commit&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
===Regular user===&lt;br /&gt;
====Checkout====&lt;br /&gt;
 &amp;gt; mkdir /path/to/localrepo&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
&lt;br /&gt;
====Update====&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn update&lt;br /&gt;
&lt;br /&gt;
====Commit changes====&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn commit -m 'Commit description'&lt;br /&gt;
&lt;br /&gt;
==External references==&lt;br /&gt;
*[http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ debian svn server tutorial]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Linux]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6736</id>
		<title>Svn faia</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6736"/>
				<updated>2013-06-21T22:51:28Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is the log of the instructions followed to install an svnserver in debian/ubuntu and to create a repository and add some code files. This tutorial follows closely on the following [http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ link].&lt;br /&gt;
&lt;br /&gt;
==Manual==&lt;br /&gt;
===svn server===&lt;br /&gt;
====installation====&lt;br /&gt;
 &amp;gt; sudo apt-get install subversion libapache2-svn&lt;br /&gt;
 &amp;gt; sudo mkdir /var/svnserver&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver&lt;br /&gt;
&lt;br /&gt;
====dav-svn configuration====&lt;br /&gt;
 &amp;gt; sudo vim /etc/apache2/mods-available/dav_svn.conf&lt;br /&gt;
 dav_svn.conf&amp;gt;&lt;br /&gt;
 # remove the # in front of the &amp;lt;location and &amp;lt;/location&lt;br /&gt;
 &amp;lt;Location /svn&amp;gt;&lt;br /&gt;
  DAV svn&lt;br /&gt;
  SVNParentPath /var/svnserver&lt;br /&gt;
  AuthType Basic&lt;br /&gt;
  AuthName &amp;quot;Subversion Repository&amp;quot;&lt;br /&gt;
  AuthUserFile /etc/apache2/dav_svn.passwd&lt;br /&gt;
  Require valid-user&lt;br /&gt;
  #SSLRequireSSL      # this line must be added if you want SSL enabled&lt;br /&gt;
 &amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====apache daemon restart====&lt;br /&gt;
 &amp;gt; sudo a2enmod dav_svn&lt;br /&gt;
 &amp;gt; sudo /etc/init.d/apache2 restart&lt;br /&gt;
&lt;br /&gt;
====add users====&lt;br /&gt;
 # First user with -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd -c /etc/apache2/dav_svn.passwd firstuser&lt;br /&gt;
 # Next users without -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd /etc/apache2/dav_svn.passwd nextuser&lt;br /&gt;
&lt;br /&gt;
===Repositories===&lt;br /&gt;
====New repo====&lt;br /&gt;
 &amp;gt; sudo svnadmin create /var/svnserver/repos&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver/repos&lt;br /&gt;
&lt;br /&gt;
====Test repo====&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
&lt;br /&gt;
====Add new project folder====&lt;br /&gt;
 &amp;gt; mkdir /path/to/localrepo&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
 &amp;gt; cp -R /path/to/project /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn add ./project&lt;br /&gt;
 &amp;gt; svn commit -m &amp;quot;Initial commit&amp;quot;&lt;br /&gt;
 &lt;br /&gt;
===Regular user===&lt;br /&gt;
====Checkout====&lt;br /&gt;
 &amp;gt; mkdir /path/to/localrepo&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
&lt;br /&gt;
====Update====&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn update&lt;br /&gt;
&lt;br /&gt;
====Commit====&lt;br /&gt;
 &amp;gt; cd /path/to/localrepo&lt;br /&gt;
 &amp;gt; svn commit -m 'Commit description'&lt;br /&gt;
&lt;br /&gt;
==External references==&lt;br /&gt;
*[http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ debian svn server tutorial]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Linux]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6735</id>
		<title>Svn faia</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Svn_faia&amp;diff=6735"/>
				<updated>2013-06-21T22:41:19Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: Created page with &amp;quot;This is the log of the instructions followed to install an svnserver in debian/ubuntu and to create a repository and add some code files. This tutorial follows closely on the fol...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is the log of the instructions followed to install an svnserver in debian/ubuntu and to create a repository and add some code files. This tutorial follows closely on the following [http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ link].&lt;br /&gt;
&lt;br /&gt;
==Manual==&lt;br /&gt;
===svn server===&lt;br /&gt;
====installation====&lt;br /&gt;
 &amp;gt; sudo apt-get install subversion libapache2-svn&lt;br /&gt;
 &amp;gt; sudo mkdir /var/svnserver&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver&lt;br /&gt;
&lt;br /&gt;
====dav-svn configuration====&lt;br /&gt;
 &amp;gt; sudo vim /etc/apache2/mods-available/dav_svn.conf&lt;br /&gt;
 dav_svn.conf&amp;gt;&lt;br /&gt;
 # remove the # in front of the &amp;lt;location and &amp;lt;/location&lt;br /&gt;
 &amp;lt;Location /svn&amp;gt;&lt;br /&gt;
  DAV svn&lt;br /&gt;
  SVNParentPath /var/svnserver&lt;br /&gt;
  AuthType Basic&lt;br /&gt;
  AuthName &amp;quot;Subversion Repository&amp;quot;&lt;br /&gt;
  AuthUserFile /etc/apache2/dav_svn.passwd&lt;br /&gt;
  Require valid-user&lt;br /&gt;
  #SSLRequireSSL      # this line must be added if you want SSL enabled&lt;br /&gt;
 &amp;lt;/Location&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====apache daemon restart====&lt;br /&gt;
 &amp;gt; sudo a2enmod dav_svn&lt;br /&gt;
 &amp;gt; sudo /etc/init.d/apache2 restart&lt;br /&gt;
&lt;br /&gt;
====add users====&lt;br /&gt;
 # First user with -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd -c /etc/apache2/dav_svn.passwd firstuser&lt;br /&gt;
 # Next users without -c option&lt;br /&gt;
 &amp;gt; sudo htpasswd /etc/apache2/dav_svn.passwd nextuser&lt;br /&gt;
&lt;br /&gt;
===New repository===&lt;br /&gt;
 &amp;gt; sudo svnadmin create /var/svnserver/repos&lt;br /&gt;
 &amp;gt; sudo chown -R www-data:www-data /var/svnserver/repos&lt;br /&gt;
&lt;br /&gt;
====Test svn server====&lt;br /&gt;
 &amp;gt; svn co http://localhost/svn/repos&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Regular user===&lt;br /&gt;
&lt;br /&gt;
==External references==&lt;br /&gt;
*[http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ debian svn server tutorial]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Linux]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Svn&amp;diff=6734</id>
		<title>Svn</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Svn&amp;diff=6734"/>
				<updated>2013-06-21T14:48:57Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://subversion.tigris.org/ Subversion] is the hottest version control system available in the free world.&lt;br /&gt;
&lt;br /&gt;
==The Mohid subversion repositories==&lt;br /&gt;
===Intranet repositories addresses===&lt;br /&gt;
&lt;br /&gt;
The intranet repository is deprecated and should not be used anymore...&lt;br /&gt;
See instead [[codeplex]].&lt;br /&gt;
&lt;br /&gt;
===Internet (read-only) repositories addresses===&lt;br /&gt;
The official repository is at the [[Codeplex]].&lt;br /&gt;
&lt;br /&gt;
==GUI clients==&lt;br /&gt;
To quickly download the code please install a gui client. Choose your flavour:&lt;br /&gt;
&lt;br /&gt;
*[[RapidSvn]], very similar environment to source-safe, for windows, linux and mac.&lt;br /&gt;
*[[TortoiseSvn]], elegantly inserts itself into your windows explorer environment (windows only).&lt;br /&gt;
&lt;br /&gt;
==Syntax==&lt;br /&gt;
to get the code from the command line. Useful when building scripts...&lt;br /&gt;
&lt;br /&gt;
===Importing new tree===&lt;br /&gt;
Do this when you want to kick-start a new google code project ...&lt;br /&gt;
 &amp;gt; svn import https://myproject.googlecode.com/svn/trunk/ --username USER -m &amp;quot;Initial import&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===Checkout project===&lt;br /&gt;
 &amp;gt; svn checkout https://myproject.googlecode.com/svn/trunk/ myproject --username USER&lt;br /&gt;
&lt;br /&gt;
===Get latest version===&lt;br /&gt;
First retrieval:&lt;br /&gt;
 &amp;gt; svn checkout http://someproject.googlecode.com/svn/trunk/ someproject&lt;br /&gt;
Routine retrieval:&lt;br /&gt;
 &amp;gt; svn update someproject&lt;br /&gt;
&lt;br /&gt;
===Commiting project===&lt;br /&gt;
 &amp;gt; svn commit -m &amp;quot;Some comment&amp;quot; --force-log someproject&lt;br /&gt;
&lt;br /&gt;
===Listing files in project===&lt;br /&gt;
 &amp;gt; svn ls -R http://someproject.googlecode.com/svn/trunk/&lt;br /&gt;
&lt;br /&gt;
===More commands===&lt;br /&gt;
*[http://articles.slicehost.com/2007/9/5/introduction-to-subversion An introduction to subversion.]&lt;br /&gt;
&lt;br /&gt;
==Syncing method==&lt;br /&gt;
[[Svn]] can be used in very inventive ways. One of them is to use [http://code.google.com google code] hosting services to keep your favorite tools' configuration files. Here below we give an example of how to keep in-sync your [[Opera]] profile.&lt;br /&gt;
&lt;br /&gt;
Pre-requisites:&lt;br /&gt;
*An [[svn]] client,&lt;br /&gt;
*A web-based [[svn]] repository.&lt;br /&gt;
&lt;br /&gt;
===windows===&lt;br /&gt;
Here's a batch file that allows to sync your opera profile. The same batch file is a little bit more detailed in the [[Opera]] article in this wiki.&lt;br /&gt;
 &lt;br /&gt;
 REM OperaSync2.bat&lt;br /&gt;
 @echo off&lt;br /&gt;
 &lt;br /&gt;
 set TARGET=C:\Documents and Settings\Guillaume\Application Data\Opera\Opera\profile&lt;br /&gt;
 set PROG=Opera&lt;br /&gt;
 set EXEC=C:\Programas\Opera\%PROG%.exe&lt;br /&gt;
 set REPO=https://preopmodel.googlecode.com/svn/trunk/%PROG%Sync&lt;br /&gt;
 set USER=&lt;br /&gt;
 &lt;br /&gt;
 echo Checking out from %REPO% ...&lt;br /&gt;
 svn checkout %REPO% &amp;quot;%TARGET%&amp;quot; --username %USER%&lt;br /&gt;
 echo %PROG% running ...&lt;br /&gt;
 %EXEC%&lt;br /&gt;
 echo Commiting to %REPO% ...&lt;br /&gt;
 svn commit -m --force-log &amp;quot;%TARGET%&amp;quot;&lt;br /&gt;
 echo Done.&lt;br /&gt;
 &lt;br /&gt;
 @echo on&lt;br /&gt;
&lt;br /&gt;
NOTE: The first time you run the file, you'll be prompted for a password.&lt;br /&gt;
&lt;br /&gt;
==Installing svn server in linux==&lt;br /&gt;
&lt;br /&gt;
 &amp;gt; sudo yum install subversion tracd&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://svnbook.red-bean.com/nightly/en/index.html Great book on Subversion]&lt;br /&gt;
*[http://subversion.tigris.org/ Subversion homepage],&lt;br /&gt;
*[http://tortoisesvn.tigris.org/ Tortoise svn].&lt;br /&gt;
*[http://code.google.com Google code]. Good for hosting svn repos.&lt;br /&gt;
*[http://trikks.wordpress.com/2010/06/15/setup-a-subversion-svn-server-in-debian/ Great document on how to install a svn server.]&lt;br /&gt;
&lt;br /&gt;
===Mohid subversion workshop documents===&lt;br /&gt;
*[http://docs.google.com/Doc?id=ddc79s84_573dxd57vg2 Workshop program and notes].&lt;br /&gt;
&lt;br /&gt;
[[Category:Windows]]&lt;br /&gt;
[[Category:Linux]]&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Svn]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6730</id>
		<title>SPH</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6730"/>
				<updated>2013-06-14T23:00:53Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[SPH|Smoothed-Particle Hydrodynamics]] is a computational technique to simulate fluid dynamics using a mesh-free lagrangian-tracer approach. The mesh-free lagrangian tracers can represent any property, from granulate to continuum in nature, from sand particles, to density, to fluid momentum and vorticity. [[SPH]] estimates any property value on any point of the domain based on the lagrangian tracers in the vicinity, weighted by a kernel function. The lagrangian tracers, in turn, are transported by the very same velocity field they generate. They are also subjected to any physical process whose continuum field they previously generated. This allows SPH to generate highly non-linear continuum fields, most unlike the traditional structured-mesh algorithms, and it can realistically simulate, for example, wave breaking, flooding, two-phasic flow interaction.&lt;br /&gt;
&lt;br /&gt;
Because of the lagrangian-tracer nature of SPH, it has been successfully parallelized in both MPI and GPU architectures, with performance increases in the order of 100 for the latter; thus making this technique more and more interesting for realistic fluid simulation scenarios.&lt;br /&gt;
&lt;br /&gt;
The mesh-free nature of SPH allows it simulate extremely turbulent and non-linear flow, filling and emptying extremely complex volumes.&lt;br /&gt;
&lt;br /&gt;
Both of these interesting features, many million particle simulation at competitive performance thanks to GPU computind and non-linear flow filling and emptying very complex volumes, makes SPH very attractive as a service to maritime industry. Some companies, such as HydrOcean, estimate an increase of its use, at the request of clients in the industry, in the forthcoming years.&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==State-of-the-art==&lt;br /&gt;
&lt;br /&gt;
== External references ==&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Particle Hydrodynamics on Wikipedia]&lt;br /&gt;
&lt;br /&gt;
==Major publications on SPH==&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6729</id>
		<title>SPH</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6729"/>
				<updated>2013-06-14T23:00:06Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[SPH|Smoothed-Particle Hydrodynamics]] is a computational technique to simulate fluid dynamics using a mesh-free lagrangian-tracer approach. The mesh-free lagrangian tracers can represent any property, from granulate to continuum in nature, from sand particles, to density, to fluid momentum and vorticity. [[SPH]] estimates any property value on any point of the domain based on the lagrangian tracers in the vicinity, weighted by a kernel function. The lagrangian tracers, in turn, are transported by the very same velocity field they generate. They are also subjected to any physical process whose continuum field they previously generated. This allows SPH to generate highly non-linear continuum fields, most unlike the traditional structured-mesh algorithms, and it can realistically simulate, for example, wave breaking, flooding, two-phasic flow interaction.&lt;br /&gt;
&lt;br /&gt;
Because of the lagrangian-tracer nature of SPH, it has been successfully parallelized in both MPI and GPU architectures, with performance increases in the order of 100 for the latter; thus making this technique more and more interesting for realistic fluid simulation scenarios.&lt;br /&gt;
&lt;br /&gt;
The mesh-free nature of SPH allows it simulate extremely turbulent and non-linear flow, filling and emptying extremely complex volumes.&lt;br /&gt;
&lt;br /&gt;
Both of these interesting features, many million particle simulation at competitive performance thanks to GPU computind and non-linear flow filling and emptying very complex volumes, makes SPH very attractive as a service to maritime industry and some companies, such as HydrOcean, estimate an increase of its use, at the request of clients in the industry, in the forthcoming years.&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==State-of-the-art==&lt;br /&gt;
&lt;br /&gt;
== External references ==&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Particle Hydrodynamics on Wikipedia]&lt;br /&gt;
&lt;br /&gt;
==Major publications on SPH==&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6728</id>
		<title>SPH</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6728"/>
				<updated>2013-06-14T22:58:41Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[SPH|Smoothed-Particle Hydrodynamics]] is a computational technique to simulate fluid dynamics using a mesh-free lagrangian-tracer approach. The mesh-free lagrangian tracers can represent any property, from granulate to continuum in nature, from sand particles, to density, to fluid momentum and vorticity. [[SPH]] estimates any property value on any point of the domain based on the lagrangian tracers in the vicinity, weighted by a kernel function. The lagrangian tracers, in turn, are transported by the very same velocity field they generate. They are also subjected to any physical process whose continuum field they previously generated. This allows to generate highly non-linear continuum fields, most unlike the traditional structured-mesh algorithms, which can realistically simulate, for example, wave breaking, flooding, two-phasic flow interaction.&lt;br /&gt;
&lt;br /&gt;
Because of the lagrangian-tracer nature of SPH, it has been successfully parallelized in both MPI and GPU architectures, with performance increases in the order of 100 for the latter; thus making this technique more and more interesting for realistic fluid simulation scenarios.&lt;br /&gt;
&lt;br /&gt;
The mesh-free nature of SPH allows it simulate extremely turbulent and non-linear flow, filling and emptying extremely complex volumes.&lt;br /&gt;
&lt;br /&gt;
Both of these interesting features, many million particle simulation at competitive performance thanks to GPU computind and non-linear flow filling and emptying very complex volumes, makes SPH very attractive as a service to maritime industry and some companies, such as HydrOcean, estimate an increase of its use, at the request of clients in the industry, in the forthcoming years.&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==State-of-the-art==&lt;br /&gt;
&lt;br /&gt;
== External references ==&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Particle Hydrodynamics on Wikipedia]&lt;br /&gt;
&lt;br /&gt;
==Major publications on SPH==&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6727</id>
		<title>SPH</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6727"/>
				<updated>2013-06-14T22:45:03Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[SPH|Smoothed-Particle Hydrodynamics]] is a computational technique to simulate fluid dynamics using a mesh-free lagrangian-tracer approach. The mesh-free lagrangian tracers can represent any property, from granulate to continuum in nature, from sand particles, to density, to fluid momentum and vorticity. [[SPH]] estimates any property value on any point of the domain based on the lagrangian tracers in the vicinity, weighted by a kernel function.&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==State-of-the-art==&lt;br /&gt;
&lt;br /&gt;
== External references ==&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Particle Hydrodynamics on Wikipedia]&lt;br /&gt;
&lt;br /&gt;
==Major publications on SPH==&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6726</id>
		<title>SPH</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6726"/>
				<updated>2013-06-14T22:44:43Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[SPH|Smoothed-Particle Hydrodynamics]] is a computational technique to simulate fluid dynamics using a mesh-free lagrangian-tracer approach. The mesh-free lagrangian tracers can represent any property, from granulate to continuum in nature, from sand particles, to density, to fluid momentum and vorticity. [[SPH]] estimates any property value on any point of the domain based on the lagrangian tracers in the vicinity, weighted by a kernel function.&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==State-of-the-art==&lt;br /&gt;
&lt;br /&gt;
== External References ==&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Particle Hydrodynamics on Wikipedia]&lt;br /&gt;
&lt;br /&gt;
==Major publications on SPH==&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6725</id>
		<title>SPH</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6725"/>
				<updated>2013-06-14T22:34:17Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[SPH|Smoothed-Particle Hydrodynamics]]&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==State-of-the-art==&lt;br /&gt;
&lt;br /&gt;
== External References ==&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Particle Hydrodynamics on Wikipedia]&lt;br /&gt;
&lt;br /&gt;
==Publications on SPH==&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6724</id>
		<title>SPH</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=SPH&amp;diff=6724"/>
				<updated>2013-06-14T22:33:53Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: Created page with &amp;quot;Smoothed-Particle Hydrodynamics  ==History==  ==State-of-the-art==  == External References == *[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Part...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[SPH|Smoothed-Particle Hydrodynamics]]&lt;br /&gt;
&lt;br /&gt;
==History==&lt;br /&gt;
&lt;br /&gt;
==State-of-the-art==&lt;br /&gt;
&lt;br /&gt;
== External References ==&lt;br /&gt;
*[http://en.wikipedia.org/wiki/Smoothed-particle_hydrodynamics Smoothed-Particle Hydrodynamics on Wikipedia]&lt;br /&gt;
&lt;br /&gt;
==Publications on SPH??&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6303</id>
		<title>*NIX platforms</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6303"/>
				<updated>2012-07-02T13:50:20Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a tutorial on how to install MOHID in linux and derived other platforms. To complement this tutorial, you can also check out some [[Codeplex#Video%20tutorials|video tutorials]] in the [[Codeplex]] article.&lt;br /&gt;
&lt;br /&gt;
== Installing ==&lt;br /&gt;
&lt;br /&gt;
=== Prerequisites ===&lt;br /&gt;
# gcc, g++ and make-tools for linux&lt;br /&gt;
# Subversion&lt;br /&gt;
# Intel Fortran 9 or greater&lt;br /&gt;
&lt;br /&gt;
''NOTE'': this article was written assuming the fortran compiler is ''Intel''. If this is not the case then change where there is written &amp;quot;ifort&amp;quot; with the fortran compiler in use (ex: openf95, pgf90, g90, etc...). In particular, the MOHID code is found to build well with the [[open64]] fortran.&lt;br /&gt;
&lt;br /&gt;
==== HDF5 libraries ====&lt;br /&gt;
To compile Mohid it is mandatory to have the HDF5 [http://hdf.ncsa.uiuc.edu/HDF5/] libraries compiled. In HDF5's web page it is possible to obtain both binary distribuitions and the source code. Most of the times it is necessary to build from source; so download the source code, e. g. hdf5-1.6.5.tar.gz;&lt;br /&gt;
 &amp;gt; tar -zxvf hdf5-1.6.5.tar.gz&amp;lt;/code&amp;gt;&lt;br /&gt;
 &amp;gt; cd hdf5-1.6.5&amp;lt;/code&amp;gt;&lt;br /&gt;
 &amp;gt; F9X=ifort ./configure --enable-fortran (--prefix=$HDF5ROOTDIR --enable-parallel)&amp;lt;/code&amp;gt;&lt;br /&gt;
 &amp;gt; make&amp;lt;/code&amp;gt;&lt;br /&gt;
 &amp;gt; make check&amp;lt;/code&amp;gt;&lt;br /&gt;
 &amp;gt; make install&amp;lt;/code&amp;gt;&lt;br /&gt;
Detailed information may be found in file ./release_docs/INSTALL.&lt;br /&gt;
&lt;br /&gt;
==== Zlib libraries ====&lt;br /&gt;
To use the HDF5 libraries it is mandatory to have installed the zlib libraries. So install the zlib package for your linux distro. Also, keep a record of where the libz.a library is installed (it might come in handy later on).&lt;br /&gt;
&lt;br /&gt;
==== Netcdf libraries ====&lt;br /&gt;
The netcdf libraries are optional since they are not required to run [[MohidWater]]. However they are useful for other modules of the Mohid Suite such as [[ConvertToHDF5]]. You can get them from the [http://www.unidata.ucar.edu/software/netcdf/ official site]. Here's the [[netcdf|report]] on how to build them for windows.&lt;br /&gt;
&lt;br /&gt;
=== Checking out the MOHID code ===&lt;br /&gt;
Use [[subversion]] to checkout the latest version of the code stored at [[codeplex]].&lt;br /&gt;
 &amp;gt; mkdir [mohidpath]&lt;br /&gt;
 &amp;gt; svn co https://mohid.svn.codeplex.com/svn [mohidpath]&lt;br /&gt;
&lt;br /&gt;
Or update to the latest version of the code&lt;br /&gt;
 &amp;gt; svn update&lt;br /&gt;
&lt;br /&gt;
=== Building MohidWater ===&lt;br /&gt;
Make sure that you have intel Fortran installed (any version later than 9.x should do). Follow instructions in the README file that is in the codeplex distribution, under the Linux folder (you are required to create the Editme.mk file from a template and edit your hdf5 library paths).&lt;br /&gt;
&lt;br /&gt;
To build the Linux makefile solution, just type&lt;br /&gt;
 &amp;gt; make Nix&lt;br /&gt;
&lt;br /&gt;
To clean the distribution, type:&lt;br /&gt;
 &amp;gt; make Nix.clean&lt;br /&gt;
&lt;br /&gt;
Make sure you also check our [[codeplex|videos]].&lt;br /&gt;
&lt;br /&gt;
== Running Mohid projects in linux ==&lt;br /&gt;
&lt;br /&gt;
===General guidelines that change from windows===&lt;br /&gt;
# There are no graphical interfaces available. No GUI, no PostProcessor and no GIS.&lt;br /&gt;
# Linux is case-sensitive. This is very important.&lt;br /&gt;
# Linux reads paths to files and folders using the slash '/' instead of the backslash '\'.&lt;br /&gt;
&lt;br /&gt;
Required files for mohidwater to run (preserve letters capitalization!). You must copy (and edit) the files manually:&lt;br /&gt;
 exe/nomfich.dat&lt;br /&gt;
 exe/tree.dat&lt;br /&gt;
&lt;br /&gt;
== TroubleShooting ==&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile keeps giving me errors :('''&lt;br /&gt;
&lt;br /&gt;
A:Here's a list of what could be causing these errors:&lt;br /&gt;
#Open the makefiles and check that fields are properly filled.&lt;br /&gt;
#Make sure that '''mod''' and '''bin''' directories exist in the module's folder. Otherwise simply make them with the mkdir command.&lt;br /&gt;
#Make sure that &amp;quot;ifort&amp;quot; is a valid command. If it isn't then you probably didn't loaded its environment variables. Type &amp;quot;source /opt/intel/fc/9.0/bin/ifortvars.sh&amp;quot; for that.&lt;br /&gt;
#Make sure that the intel fortran compiler was properly installed.&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile complains when compiling ModuleGOTM.f90'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you have to rename &lt;br /&gt;
: GOTM'''V'''ariables_in.'''f90''' ---&amp;gt; GOTM'''v'''ariables_in.'''f90'''&lt;br /&gt;
: GOTM'''V'''ariables_out.'''f90''' ---&amp;gt; GOTM'''v'''ariables_out.'''f90'''. &lt;br /&gt;
This error shows up in linux because it's case-sensitive whereas windows isn't. Also, make sure that the extension is written in lower case.&lt;br /&gt;
&lt;br /&gt;
'''Q: By the time i'm linking the final MohidWater binary I get some error about&lt;br /&gt;
unreferenced functions &amp;quot;compress2&amp;quot; and others in HDF5 files...'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you need to specify  to link against the libz.a library. Identify the exactly&lt;br /&gt;
the location of libz.a (ex: in my system it can be found at /opt/zlib/lib/libz.a)&lt;br /&gt;
then add edit accordingly the ''Solutions/Linux/Editme.mk'' file.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Makefile]]&lt;br /&gt;
*[[Mohid Makefile]]&lt;br /&gt;
*[[ifort]]&lt;br /&gt;
*[[open64]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technology]]&lt;br /&gt;
[[Category:Linux]]&lt;br /&gt;
[[Category:Makefile]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6302</id>
		<title>*NIX platforms</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6302"/>
				<updated>2012-07-02T13:49:32Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a tutorial on how to install MOHID in linux and derived other platforms. To complement this tutorial, you can also check out some [[Codeplex#Video%20tutorials|video tutorials]] in the [[Codeplex]] article.&lt;br /&gt;
&lt;br /&gt;
== Installing ==&lt;br /&gt;
&lt;br /&gt;
=== Prerequisites ===&lt;br /&gt;
# gcc, g++ and make-tools for linux&lt;br /&gt;
# Subversion&lt;br /&gt;
# Intel Fortran 9 or greater&lt;br /&gt;
&lt;br /&gt;
''NOTE'': this article was written assuming the fortran compiler is ''Intel''. If this is not the case then change where there is written &amp;quot;ifort&amp;quot; with the fortran compiler in use (ex: openf95, pgf90, g90, etc...). In particular, the MOHID code is found to build well with the [[open64]] fortran.&lt;br /&gt;
&lt;br /&gt;
==== HDF5 libraries ====&lt;br /&gt;
To compile Mohid it is mandatory to have the HDF5 [http://hdf.ncsa.uiuc.edu/HDF5/] libraries compiled. In HDF5's web page it is possible to obtain both binary distribuitions and the source code. Most of the times it is necessary to build from source:&lt;br /&gt;
# download the source code, e. g. hdf5-1.6.5.tar.gz;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; tar -zxvf hdf5-1.6.5.tar.gz&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; cd hdf5-1.6.5&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; F9X=ifort ./configure --enable-fortran (--prefix=$HDF5ROOTDIR --enable-parallel)&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make check&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make install&amp;lt;/code&amp;gt;&lt;br /&gt;
Detailed information may be found in file ./release_docs/INSTALL.&lt;br /&gt;
&lt;br /&gt;
==== Zlib libraries ====&lt;br /&gt;
To use the HDF5 libraries it is mandatory to have installed the zlib libraries. So install the zlib package for your linux distro. Also, keep a record of where the libz.a library is installed (it might come in handy later on).&lt;br /&gt;
&lt;br /&gt;
==== Netcdf libraries ====&lt;br /&gt;
The netcdf libraries are optional since they are not required to run [[MohidWater]]. However they are useful for other modules of the Mohid Suite such as [[ConvertToHDF5]]. You can get them from the [http://www.unidata.ucar.edu/software/netcdf/ official site]. Here's the [[netcdf|report]] on how to build them for windows.&lt;br /&gt;
&lt;br /&gt;
=== Checking out the MOHID code ===&lt;br /&gt;
Use [[subversion]] to checkout the latest version of the code stored at [[codeplex]].&lt;br /&gt;
 &amp;gt; mkdir [mohidpath]&lt;br /&gt;
 &amp;gt; svn co https://mohid.svn.codeplex.com/svn [mohidpath]&lt;br /&gt;
&lt;br /&gt;
Or update to the latest version of the code&lt;br /&gt;
 &amp;gt; svn update&lt;br /&gt;
&lt;br /&gt;
=== Building MohidWater ===&lt;br /&gt;
Make sure that you have intel Fortran installed (any version later than 9.x should do). Follow instructions in the README file that is in the codeplex distribution, under the Linux folder (you are required to create the Editme.mk file from a template and edit your hdf5 library paths).&lt;br /&gt;
&lt;br /&gt;
To build the Linux makefile solution, just type&lt;br /&gt;
 &amp;gt; make Nix&lt;br /&gt;
&lt;br /&gt;
To clean the distribution, type:&lt;br /&gt;
 &amp;gt; make Nix.clean&lt;br /&gt;
&lt;br /&gt;
Make sure you also check our [[codeplex|videos]].&lt;br /&gt;
&lt;br /&gt;
== Running Mohid projects in linux ==&lt;br /&gt;
&lt;br /&gt;
===General guidelines that change from windows===&lt;br /&gt;
# There are no graphical interfaces available. No GUI, no PostProcessor and no GIS.&lt;br /&gt;
# Linux is case-sensitive. This is very important.&lt;br /&gt;
# Linux reads paths to files and folders using the slash '/' instead of the backslash '\'.&lt;br /&gt;
&lt;br /&gt;
Required files for mohidwater to run (preserve letters capitalization!). You must copy (and edit) the files manually:&lt;br /&gt;
 exe/nomfich.dat&lt;br /&gt;
 exe/tree.dat&lt;br /&gt;
&lt;br /&gt;
== TroubleShooting ==&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile keeps giving me errors :('''&lt;br /&gt;
&lt;br /&gt;
A:Here's a list of what could be causing these errors:&lt;br /&gt;
#Open the makefiles and check that fields are properly filled.&lt;br /&gt;
#Make sure that '''mod''' and '''bin''' directories exist in the module's folder. Otherwise simply make them with the mkdir command.&lt;br /&gt;
#Make sure that &amp;quot;ifort&amp;quot; is a valid command. If it isn't then you probably didn't loaded its environment variables. Type &amp;quot;source /opt/intel/fc/9.0/bin/ifortvars.sh&amp;quot; for that.&lt;br /&gt;
#Make sure that the intel fortran compiler was properly installed.&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile complains when compiling ModuleGOTM.f90'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you have to rename &lt;br /&gt;
: GOTM'''V'''ariables_in.'''f90''' ---&amp;gt; GOTM'''v'''ariables_in.'''f90'''&lt;br /&gt;
: GOTM'''V'''ariables_out.'''f90''' ---&amp;gt; GOTM'''v'''ariables_out.'''f90'''. &lt;br /&gt;
This error shows up in linux because it's case-sensitive whereas windows isn't. Also, make sure that the extension is written in lower case.&lt;br /&gt;
&lt;br /&gt;
'''Q: By the time i'm linking the final MohidWater binary I get some error about&lt;br /&gt;
unreferenced functions &amp;quot;compress2&amp;quot; and others in HDF5 files...'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you need to specify  to link against the libz.a library. Identify the exactly&lt;br /&gt;
the location of libz.a (ex: in my system it can be found at /opt/zlib/lib/libz.a)&lt;br /&gt;
then add edit accordingly the ''Solutions/Linux/Editme.mk'' file.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Makefile]]&lt;br /&gt;
*[[Mohid Makefile]]&lt;br /&gt;
*[[ifort]]&lt;br /&gt;
*[[open64]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technology]]&lt;br /&gt;
[[Category:Linux]]&lt;br /&gt;
[[Category:Makefile]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6301</id>
		<title>*NIX platforms</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6301"/>
				<updated>2012-07-02T13:48:52Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a tutorial on how to install MOHID in linux and derived other platforms. To complement this tutorial, you can also check out some [[Codeplex#Video%20tutorials|video tutorials]] in the [[Codeplex]] article.&lt;br /&gt;
&lt;br /&gt;
== Installing ==&lt;br /&gt;
&lt;br /&gt;
=== Prerequisites ===&lt;br /&gt;
# gcc, g++ and make-tools for linux&lt;br /&gt;
# Subversion&lt;br /&gt;
# Intel Fortran 9 or greater&lt;br /&gt;
&lt;br /&gt;
''NOTE'': this article was written assuming the fortran compiler is ''Intel''. If this is not the case then change where there is written &amp;quot;ifort&amp;quot; with the fortran compiler in use (ex: openf95, pgf90, g90, etc...). In particular, the MOHID code is found to build well with the [[open64]] fortran.&lt;br /&gt;
&lt;br /&gt;
==== HDF5 libraries ====&lt;br /&gt;
To compile Mohid it is mandatory to have the HDF5 [http://hdf.ncsa.uiuc.edu/HDF5/] libraries compiled. In HDF5's web page it is possible to obtain both binary distribuitions and the source code. Most of the times it is necessary to build from source:&lt;br /&gt;
# download the source code, e. g. hdf5-1.6.5.tar.gz;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; tar -zxvf hdf5-1.6.5.tar.gz&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; cd hdf5-1.6.5&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; F9X=ifort ./configure --enable-fortran (--prefix=$HDF5ROOTDIR --enable-parallel)&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make check&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make install&amp;lt;/code&amp;gt;&lt;br /&gt;
Detailed information may be found in file ./release_docs/INSTALL.&lt;br /&gt;
&lt;br /&gt;
==== Zlib libraries ====&lt;br /&gt;
To use the HDF5 libraries it is mandatory to have installed the zlib libraries. So install the zlib package for your linux distro. Also, keep a record of where the libz.a library is installed (it might come in handy later on).&lt;br /&gt;
&lt;br /&gt;
==== Netcdf libraries ====&lt;br /&gt;
The netcdf libraries are optional since they are not required to run [[MohidWater]]. However they are useful for other modules of the Mohid Suite such as [[ConvertToHDF5]]. You can get them from the [http://www.unidata.ucar.edu/software/netcdf/ official site]. Here's the [[netcdf|report]] on how to build them for windows.&lt;br /&gt;
&lt;br /&gt;
=== Checking out the MOHID code ===&lt;br /&gt;
Use [[subversion]] to checkout the latest version of the code stored at [[codeplex]].&lt;br /&gt;
 &amp;gt; mkdir [mohidpath]&lt;br /&gt;
 &amp;gt; svn co https://mohid.svn.codeplex.com/svn [mohidpath]&lt;br /&gt;
&lt;br /&gt;
Or update to the latest version of the code&lt;br /&gt;
 &amp;gt; svn update&lt;br /&gt;
&lt;br /&gt;
=== Building MohidWater ===&lt;br /&gt;
Make sure that you have intel Fortran installed (any version later than 9.x should do). Follow instructions in the README file that is in the codeplex distribution, under the Linux folder (you are required to create the Editme.mk file from a template and edit your hdf5 library paths).&lt;br /&gt;
&lt;br /&gt;
To build the Linux makefile solution, just type&lt;br /&gt;
&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make Nix&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To clean the distribution, type:&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make Nix.clean&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure you also check our [[codeplex|videos]].&lt;br /&gt;
&lt;br /&gt;
== Running Mohid projects in linux ==&lt;br /&gt;
&lt;br /&gt;
===General guidelines that change from windows===&lt;br /&gt;
# There are no graphical interfaces available. No GUI, no PostProcessor and no GIS.&lt;br /&gt;
# Linux is case-sensitive. This is very important.&lt;br /&gt;
# Linux reads paths to files and folders using the slash '/' instead of the backslash '\'.&lt;br /&gt;
&lt;br /&gt;
Required files for mohidwater to run (preserve letters capitalization!). You must copy (and edit) the files manually:&lt;br /&gt;
 exe/nomfich.dat&lt;br /&gt;
 exe/tree.dat&lt;br /&gt;
&lt;br /&gt;
== TroubleShooting ==&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile keeps giving me errors :('''&lt;br /&gt;
&lt;br /&gt;
A:Here's a list of what could be causing these errors:&lt;br /&gt;
#Open the makefiles and check that fields are properly filled.&lt;br /&gt;
#Make sure that '''mod''' and '''bin''' directories exist in the module's folder. Otherwise simply make them with the mkdir command.&lt;br /&gt;
#Make sure that &amp;quot;ifort&amp;quot; is a valid command. If it isn't then you probably didn't loaded its environment variables. Type &amp;quot;source /opt/intel/fc/9.0/bin/ifortvars.sh&amp;quot; for that.&lt;br /&gt;
#Make sure that the intel fortran compiler was properly installed.&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile complains when compiling ModuleGOTM.f90'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you have to rename &lt;br /&gt;
: GOTM'''V'''ariables_in.'''f90''' ---&amp;gt; GOTM'''v'''ariables_in.'''f90'''&lt;br /&gt;
: GOTM'''V'''ariables_out.'''f90''' ---&amp;gt; GOTM'''v'''ariables_out.'''f90'''. &lt;br /&gt;
This error shows up in linux because it's case-sensitive whereas windows isn't. Also, make sure that the extension is written in lower case.&lt;br /&gt;
&lt;br /&gt;
'''Q: By the time i'm linking the final MohidWater binary I get some error about&lt;br /&gt;
unreferenced functions &amp;quot;compress2&amp;quot; and others in HDF5 files...'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you need to specify  to link against the libz.a library. Identify the exactly&lt;br /&gt;
the location of libz.a (ex: in my system it can be found at /opt/zlib/lib/libz.a)&lt;br /&gt;
then add edit accordingly the ''Solutions/Linux/Editme.mk'' file.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Makefile]]&lt;br /&gt;
*[[Mohid Makefile]]&lt;br /&gt;
*[[ifort]]&lt;br /&gt;
*[[open64]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technology]]&lt;br /&gt;
[[Category:Linux]]&lt;br /&gt;
[[Category:Makefile]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6300</id>
		<title>*NIX platforms</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=*NIX_platforms&amp;diff=6300"/>
				<updated>2012-07-02T13:45:17Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This is a tutorial on how to install MOHID in linux and derived other platforms. To complement this tutorial, you can also check out some [[Codeplex#Video%20tutorials|video tutorials]] in the [[Codeplex]] article.&lt;br /&gt;
&lt;br /&gt;
== Installing ==&lt;br /&gt;
&lt;br /&gt;
=== Prerequisites ===&lt;br /&gt;
# gcc, g++ and make-tools for linux&lt;br /&gt;
# Subversion&lt;br /&gt;
# Intel Fortran 9 or greater&lt;br /&gt;
&lt;br /&gt;
''NOTE'': this article was written assuming the fortran compiler is ''Intel''. If this is not the case then change where there is written &amp;quot;ifort&amp;quot; with the fortran compiler in use (ex: openf95, pgf90, g90, etc...). In particular, the MOHID code is found to build well with the [[open64]] fortran.&lt;br /&gt;
&lt;br /&gt;
==== HDF5 libraries ====&lt;br /&gt;
To compile Mohid it is mandatory to have the HDF5 [http://hdf.ncsa.uiuc.edu/HDF5/] libraries compiled. In HDF5's web page it is possible to obtain both binary distribuitions and the source code. Most of the times it is necessary to build from source:&lt;br /&gt;
# download the source code, e. g. hdf5-1.6.5.tar.gz;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; tar -zxvf hdf5-1.6.5.tar.gz&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; cd hdf5-1.6.5&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; F9X=ifort ./configure --enable-fortran (--prefix=$HDF5ROOTDIR --enable-parallel)&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make check&amp;lt;/code&amp;gt;&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make install&amp;lt;/code&amp;gt;&lt;br /&gt;
Detailed information may be found in file ./release_docs/INSTALL.&lt;br /&gt;
&lt;br /&gt;
==== Zlib libraries ====&lt;br /&gt;
To use the HDF5 libraries it is mandatory to have installed the zlib libraries. So install the zlib package for your linux distro. Also, keep a record of where the libz.a library is installed (it might come in handy later on).&lt;br /&gt;
&lt;br /&gt;
==== Netcdf libraries ====&lt;br /&gt;
The netcdf libraries are optional since they are not required to run [[MohidWater]]. However they are useful for other modules of the Mohid Suite such as [[ConvertToHDF5]]. You can get them from the [http://www.unidata.ucar.edu/software/netcdf/ official site]. Here's the [[netcdf|report]] on how to build them for windows.&lt;br /&gt;
&lt;br /&gt;
=== Building MohidWater ===&lt;br /&gt;
Make sure that you have intel Fortran installed (any version later than 9.x should do). Follow instructions in the README file that is in the codeplex distribution, under the Linux folder (you are required to create the Editme.mk file from a template and edit your hdf5 library paths).&lt;br /&gt;
&lt;br /&gt;
To build the Linux makefile solution, just type&lt;br /&gt;
&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make Nix&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To clean the distribution, type:&lt;br /&gt;
# &amp;lt;code&amp;gt; &amp;gt; make Nix.clean&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Make sure you also check our [[codeplex|videos]].&lt;br /&gt;
&lt;br /&gt;
== Running Mohid projects in linux ==&lt;br /&gt;
&lt;br /&gt;
===General guidelines that change from windows===&lt;br /&gt;
# There are no graphical interfaces available. No GUI, no PostProcessor and no GIS.&lt;br /&gt;
# Linux is case-sensitive. This is very important.&lt;br /&gt;
# Linux reads paths to files and folders using the slash '/' instead of the backslash '\'.&lt;br /&gt;
&lt;br /&gt;
Required files for mohidwater to run (preserve letters capitalization!). You must copy (and edit) the files manually:&lt;br /&gt;
 exe/nomfich.dat&lt;br /&gt;
 exe/tree.dat&lt;br /&gt;
&lt;br /&gt;
== TroubleShooting ==&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile keeps giving me errors :('''&lt;br /&gt;
&lt;br /&gt;
A:Here's a list of what could be causing these errors:&lt;br /&gt;
#Open the makefiles and check that fields are properly filled.&lt;br /&gt;
#Make sure that '''mod''' and '''bin''' directories exist in the module's folder. Otherwise simply make them with the mkdir command.&lt;br /&gt;
#Make sure that &amp;quot;ifort&amp;quot; is a valid command. If it isn't then you probably didn't loaded its environment variables. Type &amp;quot;source /opt/intel/fc/9.0/bin/ifortvars.sh&amp;quot; for that.&lt;br /&gt;
#Make sure that the intel fortran compiler was properly installed.&lt;br /&gt;
&lt;br /&gt;
'''Q: the makefile complains when compiling ModuleGOTM.f90'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you have to rename &lt;br /&gt;
: GOTM'''V'''ariables_in.'''f90''' ---&amp;gt; GOTM'''v'''ariables_in.'''f90'''&lt;br /&gt;
: GOTM'''V'''ariables_out.'''f90''' ---&amp;gt; GOTM'''v'''ariables_out.'''f90'''. &lt;br /&gt;
This error shows up in linux because it's case-sensitive whereas windows isn't. Also, make sure that the extension is written in lower case.&lt;br /&gt;
&lt;br /&gt;
'''Q: By the time i'm linking the final MohidWater binary I get some error about&lt;br /&gt;
unreferenced functions &amp;quot;compress2&amp;quot; and others in HDF5 files...'''&lt;br /&gt;
&lt;br /&gt;
A: Probably you need to specify  to link against the libz.a library. Identify the exactly&lt;br /&gt;
the location of libz.a (ex: in my system it can be found at /opt/zlib/lib/libz.a)&lt;br /&gt;
then add edit accordingly the ''Solutions/Linux/Editme.mk'' file.&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[Makefile]]&lt;br /&gt;
*[[Mohid Makefile]]&lt;br /&gt;
*[[ifort]]&lt;br /&gt;
*[[open64]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Technology]]&lt;br /&gt;
[[Category:Linux]]&lt;br /&gt;
[[Category:Makefile]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6294</id>
		<title>ConvertToHDF5</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6294"/>
				<updated>2012-06-14T16:57:12Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Convert Seasonde RADAR data sample configuration file */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''ConvertToHDF5''' is an application which allows the making of several operations, called '''actions''', involving HDF5 files: conversion of data in other formats (e.g. NETCDF) to HDF5, grid interpolation, concatenation of several files.&lt;br /&gt;
&lt;br /&gt;
Running options for this application are specified by the user in a input file named [[ConvertToHDF5#Input file (ConvertToHDF5Action.dat)|'''ConvertToHDF5Action.dat''']]. Several actions can be specified in the same input file, being processed sequentially by the ConvertToHDF5 application.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
The operations involving HDF5 files performed by ConvertToHDF5, specified individually by an action, can be organized in:&lt;br /&gt;
&lt;br /&gt;
* [[#file management|file management]]&lt;br /&gt;
* [[#grid interpolation|grid interpolation]] and &lt;br /&gt;
* [[#format conversion|format conversion]]. &lt;br /&gt;
&lt;br /&gt;
These types and the respective actions are detailed in the next sections. &lt;br /&gt;
&lt;br /&gt;
The input file specification for each action can be found bellow in the [[#Input file (ConvertToHDF5Action.dat)|Input file (ConvertToHDF5Action.dat)]] section.&lt;br /&gt;
&lt;br /&gt;
==File management==&lt;br /&gt;
&lt;br /&gt;
===Glue files===&lt;br /&gt;
This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 files to be glued. &amp;quot;Grid&amp;quot; and &amp;quot;Results&amp;quot; data groups should be equal in all these files.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with glued &amp;quot;Results&amp;quot; data. &amp;quot;Residual&amp;quot; and &amp;quot;Statistics&amp;quot; HDF5 data groups are not copied to the output file since they are time period specific (different values potentially occour in each file). General statistics can be calculated for the glued HDF5 file data using tool [[HDF5Statistics]].&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Grid interpolation==&lt;br /&gt;
&lt;br /&gt;
===Interpolate files===&lt;br /&gt;
This action performs the conversion of one HDF5 file data existing in one 2D or 3D spatial grid to another 2D or 3D spatial grid, creating a new HDF5 file. The interpolation is performed only for the data located a time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
The HDF5 file containing data to be interpolated is called the '''father file'''.&lt;br /&gt;
&lt;br /&gt;
In case of 3D interpolation the application conducts first the horizontal grid interpolation&lt;br /&gt;
(keeping father geometry) and only after it conducts the vertical interpolation (from father geometry to new geometry).&lt;br /&gt;
&lt;br /&gt;
Several types of 2D interpolation are available for use: bilinear, spline 2D and triangulation.&lt;br /&gt;
For vertical interpolation (used in 3D interpolation) can be supplied several polinomial degrees for interpolation.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data for forcing or providing initial conditions for a MOHID Water model, e.g. a meteorological forcing file.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
For 2D/3D interpolation:&lt;br /&gt;
&lt;br /&gt;
- father HDF5 file;&lt;br /&gt;
&lt;br /&gt;
- father horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
For 3D interpolation also needed:&lt;br /&gt;
&lt;br /&gt;
- father vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- auxiliary horizontal data grid, in a grid data file in the format supported by MOHID; this file is used for horizontal grid interpolation in 3D interpolation operations.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with interpolated data. In case of 3D interpolation also produced an auxiliary HDF5 file with the result of the horizontal grid interpolation, which can be inspected to check if this operation is well performed.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].&lt;br /&gt;
&lt;br /&gt;
===Patch files===&lt;br /&gt;
This action consists in performing an interpolation of HDF5 data between grids, as in action [[#Interpolate files|Interpolate files]], but considering more than one HDF5 file as containing data to be interpolated to the new grid and a priority scale. The interpolation is performed only for the data located in the time window specified by the user. The present version of this action operates only on 2D data.&lt;br /&gt;
&lt;br /&gt;
Each HDF5 file containing data to be interpolated is called a '''father file''' and has an user-attributed '''priority level''' to be respected in the interpolation process: for each new grid cell the ConvertToHDF5 application will look for data first on the Level 1 father file and only in the case this data is inexistent will it look for data in Level 2 file, proceeding in looking for higher level files if no data is found subsequentely.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
To obtain an HDF5 file with data from several HDF5 files each containing data with different spatial resolution and only for a specific part of the new grid. This is, for instance, the case when one is preparing a best resolution meteorological HDF5 file for forcing MOHID Water from several meteorological model domains, having different spatial resolution and span, since the best resolution data is not available for all new grid cells.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
The new horizontal data grid, in a grid data file in the format supported by MOHID, and for each father file:&lt;br /&gt;
&lt;br /&gt;
- level of priority: 1 = maximum priority, priority decreases with increasing level value;&lt;br /&gt;
&lt;br /&gt;
- data grid, in the form of a grid data file in the format supported by MOHID.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with patched data.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#PATCH HDF5 FILES|PATCH HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Format conversion==&lt;br /&gt;
&lt;br /&gt;
===Meteorological model data===&lt;br /&gt;
Mohid does not simulate explicitly the atmosphere, but needs information about atmospheric properties in time and space. This requires that atmospheric properties are supplied to MOHID Water in supported formats. These formats can be derived from meteorological data in HDF5 format. Because the results of meteorological models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the MM5 and the ERA40. These are succintly detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''ERA40''====&lt;br /&gt;
This format refers to the European Centre for Medium-Range Weather Forecasts (ECMWF) 40 years re-analysises results, acessed by site http://data.ecmwf.int/data/d/era40_daily/. This data is available for several meteorological variables with maximum 6 hour periodicity for days in the period from 1957-09-01 to 2002-08-31. &lt;br /&gt;
&lt;br /&gt;
ERA40 data files are supplied by ECMWF in a NetCDF format and with an user-costumized time window, periodicity (time step range from 6 hours to a day) and meteorological properties set. The ERA40 meteorological properties which are recognized by MOHID are presented bellow together with the correspondent MOHID name: &lt;br /&gt;
&lt;br /&gt;
 ---ERA40 NAME---         ---MOHID NAME---&lt;br /&gt;
   sshf                     sensible heat                &lt;br /&gt;
   slhf                     latent heat                  &lt;br /&gt;
   msl                      atmospheric pressure &lt;br /&gt;
   tcc                      cloud cover &lt;br /&gt;
   p10u                     wind velocity X&lt;br /&gt;
   p10v                     wind velocity Y&lt;br /&gt;
   p2t                      air temperature&lt;br /&gt;
   ewss                     wind stress X&lt;br /&gt;
   nsss                     wind stress Y&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to all MOHID Water recognized property available in the ERA40 file, producing an individual HDF5 file for each property. The name of each HDF5 file generated includes the ERA40 meteorological property identificator correspondent to the data contained.&lt;br /&gt;
&lt;br /&gt;
Alternatively, ConvertToHDF5 can copy to a single ASCII file the heading information concerning each meteorological variable considered in the original ERA40 file.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data suitable for being used for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ERA40 NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file for each meteorological property contained in the original NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ERA40 FORMAT|CONVERT ERA40 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Aladin''====&lt;br /&gt;
This format relates to Aladin meteorological model results. Some of the atmospheric property needed by MOHID Water is present in Aladin output files, enabling to run prediction simulations with MOHID Water when access to Aladin prevision files is available.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts Aladin results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Aladin netcdf results file to convert.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with Aladin results and a grid data file in MOHID format with the Aladin grid pseudo-information: a fake orography is created of 100 m depth.&lt;br /&gt;
This last file can be used to interpolate the Aladin data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ALADIN FORMAT|CONVERT ALADIN FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MM5''====&lt;br /&gt;
This format relates to the Fifth-Generation NCAR / Penn State Mesoscale Model (MM5) output files format. Almost every atmospheric property needed by MOHID Water is present in MM5 output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts MM5 results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the MM5 files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
For conversion to be completed it is required the horizontal grid information of MM5 results which is available in special TERRAIN files.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
MM5 results file to convert and MM5 TERRAIN file. The TERRAIN file supplies the MM5 results grid information. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
A HDF5 file with MM5 results and a grid data file in MOHID format with the MM5 grid information.&lt;br /&gt;
This last file can be used to interpolate the MM5 data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MM5 FORMAT|CONVERT MM5 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''WRF''====&lt;br /&gt;
This format relates to the Weather Research and Forecast model (WRF) output files format. Almost every atmospheric property needed by MOHID Water is present in WRF output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts WRF results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the WRF properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the WRF files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
WRF direct output file.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with WRF results and a grid data file in MOHID format with the WRF grid information.&lt;br /&gt;
This last file can be used to interpolate the WRF data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! [[PROJ4 | PROJ4]] library is needed! See [[#Compile_ModuleWRFFormat |  Compile_ModuleWRFFormat]]&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT WRF FORMAT|CONVERT WRF FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Wave model data===&lt;br /&gt;
Mohid does not simulate explicitly the wave dynamics, but needs information about wave properties in time and space. This requires that wave properties are supplied to MOHID Water in supported formats. These formats can be derived from wave data in HDF5 format. Because the results of wave models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the table format of SWAN. This is succintly detailed in the next section.&lt;br /&gt;
&lt;br /&gt;
====''SWAN''====&lt;br /&gt;
SWAN data files are supplied in a ASCII format. The data is organized by time instant. For each time instant there is a table of data. Each column represents one property. &lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to gradients of wave stresses X and Y, mean amplitude, mean period and mean direction.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 SWAN data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ASCII (table type) SWAN results data files and bathymetry in MOHID grid data foramt. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (wave stresses X and Y, mean amplitude, mean period and mean direction). &lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT TO AND FROM SWAN|CONVERT TO AND FROM SWAN]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Ocean model data===&lt;br /&gt;
Ocean model data, available in diverse formats, can be used by MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation. These uses require that the model data is in HDF5 format and conversion is therefore needed.&lt;br /&gt;
&lt;br /&gt;
Currently the large scale ocean models formats convertible into HDF5 by ConvertToHDF5 includes MERCATOR.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MERCATOR''====&lt;br /&gt;
MERCATOR data files are supplied in a NetCDF format and with an user-costumized spatial window and periodicity. Water level and water properties (temperature and salinity) data is available in type T files, velocity component u data is available in type U files and velocity component v data is available in type V files. The type of data of a specific MERCATOR file is generally indicated in the file name.&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to temperature, salinity, water level, component u of velocity and component v of velocity.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 MERCATOR data usable for forcing or validation of MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
NetCDF MERCATOR results data files and NetCDF MERCATOR grid data files. It should be provided one grid data file of each type: T, U and V. These are generally provided by the MERCATOR services together with the results files.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (temperature, salinity, water level, velocity u and velocity v) and the correspondent grid data and geometry files, containing respectively the horizontal grid and the vertical discretization of the HDF5 file. The grid data and geometry files can be used afterwards to interpolate the MERCATOR data to another grid and geometry (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MERCATOR FORMAT|CONVERT MERCATOR FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Climatological data===&lt;br /&gt;
Climatological data can be used in MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation, in case more realistic data (measurements or model) data is unavailable. This data is generally supplied by producers in formats not readly usable by MOHID Water which justifies the existence of a conversion tool.&lt;br /&gt;
&lt;br /&gt;
Two climatological data format conversions are implemented in ConvertToHDF5: Levitus ocean data and Hellerman Rosenstein meteorological data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''Levitus''====&lt;br /&gt;
The Levitus climatology provides results for water temperature and salinity.&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window requested by the user. &lt;br /&gt;
Typically, it requires 3 steps to complete the task:&lt;br /&gt;
&lt;br /&gt;
- convert levitus format &lt;br /&gt;
&lt;br /&gt;
- extrapolate the data to the whole levitus domain(required to avoid uncoincidental coastlines) &lt;br /&gt;
&lt;br /&gt;
- interpolate with the model grid(bathymetry)&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as boundary forcing and/or initial condition specification in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Levitus climatological data files, one per property and per time period (e.g a month).&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Levitus climatological data, grid data file with the horizontal&lt;br /&gt;
grid of the data and a geometry file with vertical discretization of the data (MOHID formats).&lt;br /&gt;
The grid data and the geometry files can be used to interpolate the climatological data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT LEVITUS FORMAT|CONVERT LEVITUS FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Hellerman Rosenstein''====&lt;br /&gt;
This is a meteorological climatology providing wind stress. There is a file per wind stress component. Since the data refer to surface values it is a 2D field.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window provided by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as meteorological forcing in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Hellerman Rosenstein climatological data ASCII files, one per wind stress component.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Hellerman Rosenstein climatological data and grid data file with the horizontal&lt;br /&gt;
grid of the climatological data. This grid data file can be used to interpolate the climatological data from the original horizontal grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT HELLERMAN ROSENSTEIN ASCII|CONVERT HELLERMAN ROSENSTEIN ASCII]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''World Ocean Atlas 2005''====&lt;br /&gt;
The World Ocean Atlas (WOA) 2005 climatology provides results for water temperature, salinity and several water quality and biology properties.&lt;br /&gt;
&lt;br /&gt;
Description, Action and Input Files are described in a separate page: [[ConvertToHDF5 WOA2005]].&lt;br /&gt;
&lt;br /&gt;
===Generic NETCDF CF FILES===&lt;br /&gt;
&lt;br /&gt;
Converts any netcdf file following the CF convention into Mohid HDF5 files. Check the [[ConvertToHDF5#CONVERT_GENERIC_NETCDF_CF | Input File]] and [[ConvertToHDF5#Convert_generic_Netcdf_CF_to_MOHID.28.hdf5.29 | Sample File]].&lt;br /&gt;
&lt;br /&gt;
===Radar data===&lt;br /&gt;
====Seasonde RADAR Data====&lt;br /&gt;
Converts a list of ascii files from the Seasonde radar data, which measures currents over a given region of space, into an hdf5 file with the MOHID format. Useful to validate coastal and estuarine models where radars are located. ConvertToHDF5 tool must be compiled with the preprocessor variable definition _SCANLINE_UNSAFE set in the Mohid Base 1.&lt;br /&gt;
&lt;br /&gt;
==Input file (ConvertToHDF5Action.dat)==&lt;br /&gt;
===General structure===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt; (block containing instructions for running a specific action) &lt;br /&gt;
 ACTION                    : ... (intended action)&lt;br /&gt;
 ... (action specific instructions)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : ...&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GLUES HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 3D_FILE                   : 0/1 (0 = 2D file, 1 = 3D file)&lt;br /&gt;
 &lt;br /&gt;
 TIME_GROUP                : ... (Default=&amp;quot;Time&amp;quot;. Other option: &amp;quot;SurfaceTime&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (Default=&amp;quot;Results&amp;quot;. Other options: &amp;quot;Residual&amp;quot;, &amp;quot;SurfaceResults&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 &lt;br /&gt;
 (block of HDF5 data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of HDF5 file with data to be included in glue, one per line, at least two files)&lt;br /&gt;
 ...                      &lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===INTERPOLATE GRIDS===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of horizontal interpolation: 1 = Bilinear, 2 = Spline2D,&lt;br /&gt;
                                  3 = Triangulation)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION_WINDOW      : ... ... ... ... (2D spatial window to consider for interpolation: &lt;br /&gt;
                                              Xmin Ymin Xmax Ymax; default = all domain)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D           : 0/1 (0 = 2D interpolation, 1 = 3D interpolation)&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_2D            : 0/1/2/3/4/5 (2D extrapolation: 0=no extrapolation, 1=medium&lt;br /&gt;
                                      triangulation, 2=high triangulation, &lt;br /&gt;
                                      3=nearest neighbour, 4=nearest cell, &lt;br /&gt;
                                      5=constant value)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_VALUE         : ... (name of the value to extrapolate to when EXTRAPOLATE_2D is&lt;br /&gt;
                                  set to constant value (5))&lt;br /&gt;
 &lt;br /&gt;
 DO_NOT_BELIEVE_MAP        : 0/1 (0=consider input HDF5 file map, 1=do not consider input HDF5&lt;br /&gt;
                                  file map)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (name of base group of HDF5 variables containing data to be &lt;br /&gt;
                                  interpolated; default is &amp;quot;/Results&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (if INTERPOLATION3D : 1 also required:)&lt;br /&gt;
 FATHER_GEOMETRY           : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  of input HDF5 file)&lt;br /&gt;
 NEW_GEOMETRY              : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  intended for output HDF5 file)&lt;br /&gt;
 POLI_DEGREE               : 1/... (degree of vertical interpolation: 1=linear, ...)&lt;br /&gt;
 &lt;br /&gt;
 AUX_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for auxiliar output HDF5 file;&lt;br /&gt;
                                  default is file provided in NEW_GRID_FILENAME)&lt;br /&gt;
 &lt;br /&gt;
 AUX_OUTPUTFILENAME        : ... (path/name of auxiliar output HDF5 file to contain result&lt;br /&gt;
                                  of horizontal grid interpolation)   &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the file indicated in AUX_GRID_FILENAME can be different from the one indicated in&lt;br /&gt;
   NEW_GRID_FILENAME in terms of bathymetry, while the horizontal grid should be, commonly, the&lt;br /&gt;
   same: this altered bathymetry can be used to extend the water column in the original data so&lt;br /&gt;
   that the process of vertical interpolation is done easily;&lt;br /&gt;
 &lt;br /&gt;
 - in case of INTERPOLATION3D : 1, ConvertToHDF5 can generate new versions of bathymetry which &lt;br /&gt;
   are consistent with the geometry definition (extension is '.new'); there are possibly three&lt;br /&gt;
   bathymetry changes referring to father grid, new grid and aux grid (the same bathymetry is&lt;br /&gt;
   not altered twice); although initially new and aux grid are the same they can result &lt;br /&gt;
   different because of bathymetry changes;&lt;br /&gt;
 &lt;br /&gt;
 - in case the new geometry is 2D and father geometry is 3D then POLI_DEGREE : 1 &lt;br /&gt;
   (linear interpolation) should be used;&lt;br /&gt;
 &lt;br /&gt;
 - EXTRAPOLATE_2D : 1/2/3/4/5 should be considered if it is expected that the coast line is not&lt;br /&gt;
   coincidental in the father and new grids, to avoid lack of data in the interpolation&lt;br /&gt;
   process; extrapolation is performed for all cells even the land cells; &lt;br /&gt;
 &lt;br /&gt;
 - in case of DO_NOT_BELIEVE_MAP : 1 the application generates a map based on cells where&lt;br /&gt;
   interpolation results are available; this causes that if EXTRAPOLATE_2D : 1/2/3/4/5 is used&lt;br /&gt;
   the AUX_GRID_FILENAME should not have land cells in order for the new map to be concurrent&lt;br /&gt;
   with the result of extrapolation and avoid errors generation, specially if INTERPOLATION3D :&lt;br /&gt;
   1 is considered.&lt;br /&gt;
&lt;br /&gt;
===PATCH HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of interpolation: 3 = Triangulation, default and only&lt;br /&gt;
                                  one implemented)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 (block for each father HDF5 file, should be at least two)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                     : ... (integer priority level: 1 = highest, increase for lower&lt;br /&gt;
                                  priority)&lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 N_REMOVE_FRAME            : 0   (width, in number of cells, of frame to remove)&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT ERA40 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of ERA40 NetCDF file)&lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
                                 (root of name for all files produced)&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII          : 0/1 (1 = convert variable heading info for ASCII file; 0 = default)&lt;br /&gt;
 CONVERT_TO_HDF5           : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 GRIDTO180                 : 0/1 (1 = convert grid from [0 360] to [-180 180], 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 YY_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 TIME_VARIABLE             : ... (name of time variable in the input file: usual name is&lt;br /&gt;
                                  &amp;quot;time&amp;quot;)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - either CONVERT_TO_ASCII : 1 or CONVERT_TO_HDF5 : 1 must be chosen for any action to be&lt;br /&gt;
 performed by ConvertToHDF5;&lt;br /&gt;
 &lt;br /&gt;
 - when CONVERT_TO_HDF5 : 1 an HDF5 file is produced for every variable contained in the&lt;br /&gt;
 original ERA40 file; the name of each file is composed of the name indicated on FILENAME&lt;br /&gt;
 concatenated with the ERA40 variable identifier;&lt;br /&gt;
 &lt;br /&gt;
 - to the XX_VARIABLE, YY_VARIABLE and TIME_VARIABLE keywords should generally be  &lt;br /&gt;
 specified &amp;quot;longitude&amp;quot;, &amp;quot;latitude&amp;quot; and &amp;quot;time&amp;quot;, respectively; the option to&lt;br /&gt;
 include as keywords was made only to make the application robust to future variable name&lt;br /&gt;
 changes.&lt;br /&gt;
&lt;br /&gt;
===CONVERT ALADIN FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 (path to aladin netcdf file)\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each Aladin property to convert in &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;...&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt; block must conform to the following variables&lt;br /&gt;
 &lt;br /&gt;
           ---ALADIN NAME---    ---MOHID NAME---&lt;br /&gt;
             soclotot            CloudCover_&lt;br /&gt;
             sohumrel            RelativeHumidity_&lt;br /&gt;
             sofluxir            NonSolarFlux_&lt;br /&gt;
             sosspres            AtmosphericPressure_&lt;br /&gt;
             sosolarf            SolarRadiation_&lt;br /&gt;
             sotemair            AirTemperature_&lt;br /&gt;
             sowinmod            WindModulus_&lt;br /&gt;
             sowaprec            Precipitation_&lt;br /&gt;
             sozotaux            WindStressX_&lt;br /&gt;
             sometauy            WindStressY_&lt;br /&gt;
             sowindu10           WindVelocityX_&lt;br /&gt;
             sowindv10           WindVelocityY_&lt;br /&gt;
&lt;br /&gt;
===CONVERT MM5 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MM5 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of MM5 file)&lt;br /&gt;
 TERRAIN_FILENAME          : ... (path/name of MM5 TERRAIN file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of MM5 data to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP                 : 0/1 (1 = compute and write mean sea level pressure field; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of MM5 properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of MM5 property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each MM5 property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must&lt;br /&gt;
 conform to the MOHID designation specified in code of ModuleGlobalData; the correspondence is &lt;br /&gt;
 the following (see [[Module_InterfaceWaterAir]] for a more detailed explanation).&lt;br /&gt;
 &lt;br /&gt;
           ---MM5 NAME---    ---MOHID NAME---&lt;br /&gt;
             T2             air temperature&lt;br /&gt;
             PSTARCRS       atmospheric pressure&lt;br /&gt;
             U10            wind velocity X&lt;br /&gt;
             V10            wind velocity Y&lt;br /&gt;
             UST            wind shear velocity&lt;br /&gt;
             LHFLUX         latent heat&lt;br /&gt;
             SWDOWN         sensible heat&lt;br /&gt;
             SWDOWN         solar radiation&lt;br /&gt;
             LWDOWN         infrared radiation&lt;br /&gt;
             SWOUT          top outgoing shortwave radiation&lt;br /&gt;
             LWOUT          top outgoing longwave radiation&lt;br /&gt;
             SOIL T 1       soil temperature layer 1&lt;br /&gt;
             SOIL T 1       soil temperature layer 2&lt;br /&gt;
             SOIL T 1       soil temperature layer 3&lt;br /&gt;
             SOIL T 1       soil temperature layer 4&lt;br /&gt;
             SOIL T 1       soil temperature layer 5&lt;br /&gt;
             SOIL T 1       soil temperature layer 6&lt;br /&gt;
             Q2             2-meter mixing ratio&lt;br /&gt;
             TSEASFC        sea water temperature&lt;br /&gt;
             PBL HGT        PBL height&lt;br /&gt;
             PBL REGIME     PBL regime&lt;br /&gt;
             RAIN CON       accumulated convective precipitation        (cm)&lt;br /&gt;
             RAIN NON       accumulated non-convective precipitation    (cm)&lt;br /&gt;
             GROUND T       ground temperature&lt;br /&gt;
             RES TEMP       infinite reservoir slab temperature&lt;br /&gt;
             U              wind velocity X_3D&lt;br /&gt;
             V              wind velocity Y_3D&lt;br /&gt;
             W              wind velocity Z_3D&lt;br /&gt;
             T              air temperature_3D&lt;br /&gt;
             PP             atmospheric pressure_3D&lt;br /&gt;
             Q              mixing ratio_3D&lt;br /&gt;
             CLW            cloud water mixing ratio_3D&lt;br /&gt;
             RNW            rain water mixing ratio_3D&lt;br /&gt;
             ICE            cloud ice mixing ratio_3D&lt;br /&gt;
             SNOW           snow mixing ratio_3D&lt;br /&gt;
             RAD TEND       atmospheric radiation tendency_3D&lt;br /&gt;
&lt;br /&gt;
===CONVERT WRF FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                       : CONVERT WRF FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                     : ... (path/name of WRF file)&lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of WRF data&lt;br /&gt;
                                     to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP_MM5             : 0/1 (1 = compute mean sea level pressure with MM5toGrads algorithm; 1 = default)&lt;br /&gt;
 COMPUTE_MSLP_WRF             : 0/1 (1 = compute mean sea level pressure with ARWPost algorithm; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 OUTPUT_DT                    : real (DT interval in seconds between each output; default = 0.0)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
  &lt;br /&gt;
 - the name of each property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must conform to the MOHID &lt;br /&gt;
   designation specified in code of ModuleGlobalData; the correspondence to WRF is in function &lt;br /&gt;
   VariableIsToRead in ModuleWRFFormat. Conversion is not direct since WRF outputs tendencies and not  &lt;br /&gt;
   total values. &lt;br /&gt;
 &lt;br /&gt;
 - Caution: This action is not extensively tested.&lt;br /&gt;
&lt;br /&gt;
===CONVERT MERCATOR FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION               : 1/2/3/4 (version of MERCATOR files)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 1:)&lt;br /&gt;
 BASE_BULLETIN             : ...&lt;br /&gt;
 DATES_FILE                : ...&lt;br /&gt;
 NUM_DATES                 : ... &lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 2/3:)&lt;br /&gt;
 INPUT_GRID_FILENAME       : ... (path/name of file with horizontal discretization of water&lt;br /&gt;
                                  properties and water level data)&lt;br /&gt;
 (if READ_OPTION : 2:)&lt;br /&gt;
 INPUT_GRID_FILENAME_U     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component U data)&lt;br /&gt;
 INPUT_GRID_FILENAME_V     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component V data)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 3:)&lt;br /&gt;
 INPUT_BATHY_FILENAME      : ... (path/name of file with bathymetry)&lt;br /&gt;
     &lt;br /&gt;
 (if READ_OPTION : 3/4:)&lt;br /&gt;
 CALC_BAROTROPIC_VEL       : 0/1 (1 = calculate barotropic velocity, 0 = not calculate; &lt;br /&gt;
                                  default = 0)&lt;br /&gt;
 &lt;br /&gt;
 (if CALC_BAROTROPIC_VEL : 1 and READ_OPTION : 3:)&lt;br /&gt;
 INPUT_MESH_ZGRID_FILENAME : ... (path/name of file with information about layers ticknesses)&lt;br /&gt;
 &lt;br /&gt;
 (block of MERCATOR data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of MERCATOR NetCDF data file, one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT LEVITUS FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT LEVITUS FORMAT&lt;br /&gt;
  &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Levitus data: &amp;quot;monthly&amp;quot;/&amp;quot;annual&amp;quot;; default is&lt;br /&gt;
                                  &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Levitus grid)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
 &lt;br /&gt;
 (block for each water property to be present in output HDF5 file, can be several)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property)&lt;br /&gt;
 ANNUAL_FILE               : ... (path/name of Levitus annual file)&lt;br /&gt;
 &lt;br /&gt;
 (block of Levitus data files)&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of Levitus data file (e.g. a monthly data file), one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT HELLERMAN ROSENSTEIN ASCII===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
  &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Hellerman Rosenstein data: &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Hellerman&lt;br /&gt;
                                  Rosenstein grid: default and only allowed value is &amp;quot;2.&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
   &lt;br /&gt;
 (block for each Hellerman Rosenstein data file)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property: &amp;quot;wind stress X&amp;quot;/&amp;quot;wind stress Y&amp;quot;)&lt;br /&gt;
 FILE                      : ... (path/name Hellerman Rosenstein file)&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CONVERT GENERIC NETCDF CF===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION              : CONVERT NETCDF CF TO HDF5 MOHID       &lt;br /&gt;
 HDF5_OUT            : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 OUTPUTFILENAME      : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)&lt;br /&gt;
 OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property for time, generally &amp;quot;time&amp;quot;&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT     : ... (name of the netcdf property for latitude, generally &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_LONG    : ... (name of the netcdf property for longitude, generally &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_MAPPING : ... (name of the netcdf field where is located the mapping 0 water 1 land)&lt;br /&gt;
                           (It can also be used any field, i.e. temperature)&lt;br /&gt;
 MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus &amp;gt;0.5 water)&lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER   : real (number of netcdf properties) &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property&lt;br /&gt;
 NAME                : name of the HDF5 Mohid property&lt;br /&gt;
 UNITS               : property units&lt;br /&gt;
 DESCRIPTION         : property description&lt;br /&gt;
 DIM                 : 2/3 Number of property dimensions &lt;br /&gt;
 VECTOR_INTENSITY    : 0/1 If property corresponds to a vector intensity&lt;br /&gt;
 VECTOR_X            : Decomposition of Vector Intensity X&lt;br /&gt;
 VECTOR_Y            : Decomposition of Vector Intensity Y&lt;br /&gt;
 BEAUFORT_SCALE      : 0/1 If property correspond to the beaufort scale&lt;br /&gt;
 ADD_FACTOR          : To add the property a fixed value&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 path to netcdf cf file&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT SEASONDE RADAR FORMAT ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 !HDF5 path and filename that will contain the results&lt;br /&gt;
 OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
 &lt;br /&gt;
 !griddata path and filename that will contain a griddata of the proxy bathymetry used in the hdf5 output file.&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Path and filename to the grid that maps the radar data. This grid must be constructed with the [[GIS]]&lt;br /&gt;
 !or MOHID Studio and must &amp;quot;fit&amp;quot; well where the points stand.&lt;br /&gt;
 INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
 &lt;br /&gt;
 !This is the version of the grid used by the seasonde radar system.&lt;br /&gt;
 !If the grid version of the seasonde radar changes, then most likely a new input grid must be&lt;br /&gt;
 !constructed with the GIS or MOHID Studio.&lt;br /&gt;
 IH_GRID_VERSION           : 4&lt;br /&gt;
 &lt;br /&gt;
 !This is a list with the Seasonde radar ascii data files. One file per instant.&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Samples==&lt;br /&gt;
All sample files are named ''ConvertToHDF5Action.dat''.&lt;br /&gt;
&lt;br /&gt;
===Glue several MOHID(.hdf5) files===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : SurfaceHydro_OP.hdf5&lt;br /&gt;
  &lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_21.hdf5&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_22.hdf5&lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 2D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME           : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
  &lt;br /&gt;
 START                    : 2006 6 21 17 22 30&lt;br /&gt;
 END                      : 2006 6 22 17 22 0&lt;br /&gt;
  &lt;br /&gt;
 FATHER_GRID_FILENAME     : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME        : TagusConstSpacing.dat&lt;br /&gt;
  &lt;br /&gt;
 BASE_GROUP               : /Results/Oil/Data_2D&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 3D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 1&lt;br /&gt;
 FATHER_FILENAME         : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME          : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2006 6 21 17 22 30&lt;br /&gt;
 END                     : 2006 6 22 17 22 0&lt;br /&gt;
 &lt;br /&gt;
 FATHER_GRID_FILENAME    : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP              : /Results/Oil/Data_2D&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D         : 1&lt;br /&gt;
 FATHER_GEOMETRY         : D:\Projectos\MohidRun\test\data\Geometry_1.dat&lt;br /&gt;
 NEW_GEOMETRY            : TagusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME      : Aux_GridRegular.hdf5&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Patch several MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 3&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2005 2 28 13 0 0&lt;br /&gt;
 END                     : 2005 3 1 13 0 0&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 3&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D1.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid1.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 2&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D2.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid2.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 1&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D3.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid3.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME          : MM5Forcing.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME       : K:\Simula\GeneralData\Batim\CostaPortuguesa.dat&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert an ERA40 file to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                  : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                : D:\Aplica\ERA40\1971ERA1973.nc&lt;br /&gt;
 OUTPUTFILENAME          : D:\Aplica\ERA40\1971ERA1973T2&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII        : 0&lt;br /&gt;
 CONVERT_TO_HDF5         : 1&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE             : longitude&lt;br /&gt;
 YY_VARIABLE             : latitude&lt;br /&gt;
 TIME_VARIABLE           : time&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a MM5 file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : MMOUT_DOMAIN2&lt;br /&gt;
 TERRAIN_FILENAME          : TERRAIN_DOMAIN2&lt;br /&gt;
 OUTPUTFILENAME            : D2.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : D2.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 !START                     : 2010 02 15 00 00 00&lt;br /&gt;
 !END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a WRF file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : wrfout_d01_2010-02-15_00.nc&lt;br /&gt;
 OUTPUTFILENAME            : wrfout_d01.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : wrfout_d01.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 START                     : 2010 02 15 00 00 00&lt;br /&gt;
 END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Mercator-Ocean(.nc) to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION              : 2&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Psy2v2r1v_R20060628/MercatorR20060628.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : Psy2v2r1v_R20060628/MercatorGridR20060628.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : Psy2v2r1v_R20060628/MercatorGeometryR20060628.dat&lt;br /&gt;
 &lt;br /&gt;
 INPUT_GRID_FILENAME      : GridFiles/ist_meteog-gridT.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_U    : GridFiles/ist_meteog-gridU.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_V    : GridFiles/ist_meteog-gridV.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060621_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060622_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060623_R20060628.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Levitus format to MOHID(.hdf5) and interpolate grid===&lt;br /&gt;
==== Convert ====&lt;br /&gt;
First convert the Levitus ASCII format to a raw HDF5 format:&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT LEVITUS FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Levitus.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : LevitusGeometry.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 0.25&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -16.0  31&lt;br /&gt;
 UPPER_RIGHT_CORNER       :   1.   40&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : salinity&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : temperature&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Temp\t000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Extrapolate ====&lt;br /&gt;
Then extrapolate the data (still in the raw HDF5 format):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME          : Levitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : LevitusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxLeviTusAllPointsWithData.hdf5&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 EXTRAPOLATE_2D           : 2&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Interpolate ====&lt;br /&gt;
Finally, interpolate to the final grid and geometry (same as the [[#Interpolate 3D MOHID(.hdf5) files to a new grid| Interpolate 3D sample]]):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 OUTPUTFILENAME           : CadizMonthlyLevitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 NEW_GRID_FILENAME        : Algarve0.02SigmaSmooth_V3_CartMoreLayers.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : Geometry_1.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxCadizMonthlyLevitus.hdf5&lt;br /&gt;
 AUX_GRID_FILENAME        : Aux12km.dat&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the programme may construct a new bathymetry twice. Use this bathymetry only on the AUX_GRID_FILENAME keyword.&lt;br /&gt;
&lt;br /&gt;
===Convert Hellerman Rosenstein ASCII format to MOHID(.hdf5)  ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : ClimatologicWindStress.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : ClimatologicWindStressGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 2.&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -180  -90&lt;br /&gt;
 UPPER_RIGHT_CORNER       : 180  90&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress X&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUXX.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress Y&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUYY.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert ALADIN(.nc) format to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKPRES_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKSOLAR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKTAIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKWIND_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_FLUXPRE_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSU_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSV_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_U10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_V10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKHUMI_OPASYMP_19723_20088.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Convert generic Netcdf CF to MOHID(.hdf5)  ===&lt;br /&gt;
&lt;br /&gt;
This sample is for converting a typical GFS file&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION : CONVERT NETCDF CF TO HDF5 MOHID&lt;br /&gt;
 HDF5_OUT : 1&lt;br /&gt;
 OUTPUTFILENAME : ..\..\data\hdf5\GFS.hdf5&lt;br /&gt;
 NETCDF_OUT : 1&lt;br /&gt;
 OUTPUT_NETCDF_FILE : ..\..\data\netcdf\GFS.nc&lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : time&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT : latitude&lt;br /&gt;
 NETCDF_NAME_LONG : longitude&lt;br /&gt;
 NETCDF_NAME_MAPPING : TMP_10mb&lt;br /&gt;
 MAPPING_LIMIT : -10000&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER : 6 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : PRMSL_meansealevel&lt;br /&gt;
 NAME : atmospheric pressure&lt;br /&gt;
 UNITS : Pa&lt;br /&gt;
 DESCRIPTION : GFS&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : UGRD_10mb&lt;br /&gt;
 NAME : wind velocity X&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : VGRD_10mb&lt;br /&gt;
 NAME : wind velocity Y&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus&lt;br /&gt;
 NAME                     : wind modulus &lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 VECTOR_INTENSITY         : 1&lt;br /&gt;
 VECTOR_X                 : wind velocity X&lt;br /&gt;
 VECTOR_Y                 : wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus_beaufort &lt;br /&gt;
 NAME                     : wind modulus beaufort &lt;br /&gt;
 UNITS : beaufort scale&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 BEAUFORT_SCALE           : 1&lt;br /&gt;
 VECTOR_X                 : wind modulus&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : TMP_2maboveground&lt;br /&gt;
 NAME : air temperature&lt;br /&gt;
 UNITS : oC&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 ADD_FACTOR  : -273&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ..\..\data\netcdf\gfs_4_20111115.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
=== Convert Seasonde RADAR data sample configuration file===&lt;br /&gt;
The input grid file must be created to be the recipient of the data in the ascii files.&lt;br /&gt;
To create this grid, it is recommended to convert manually, resorting to a good text editor, such as Notepad++, a few radar ascii files into the [[xyz]] Mohid format, then load them in the [[GIS]] or [[Mohid Studio]], and from there create and save a regular grid that fits the points. Use that grid to convert the data into one hdf5 file.&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
 INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
 IH_GRID_VERSION           : 4&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
 ../RadarFiles/TOTL_IHOC_2012_05_30_1400.tuv.txt&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
Compile the ConvertToHDF5 tool with the preprocessor variable _SCANLINE_UNSAFE defined in Mohid Base 1.&lt;br /&gt;
&lt;br /&gt;
== OceanColor modules compilation ==&lt;br /&gt;
Compiling the [[ConvertToHDF5]] tool with the OceanColor modules is more complicated than one might expect. A solution is proposed here for a release version using the Compaq Visual Fortran 6.6c. The difficulties rise because C code is embedded with a fortran interface and also, extra libraries such as hdf4 are required.&lt;br /&gt;
&lt;br /&gt;
=== Pre-requisites ===&lt;br /&gt;
&lt;br /&gt;
This is a list of prerequisites to successfully compile the tool:&lt;br /&gt;
*Compaq Visual Fortran 6.5 with patch 6.6c,&lt;br /&gt;
*VS .NET 2003 (Vc7 in particular),&lt;br /&gt;
*Hdf5 libraries ('''hdf5.lib''' '''hdf5_fortran.lib''' '''hdf5_hl.lib'''),&lt;br /&gt;
*Netcdf libraries ('''netcdf.lib''' '''netcdf_.lib'''),&lt;br /&gt;
*Hdf4 libraries ('''hd421.lib''', '''hm421.lib'''),&lt;br /&gt;
*szlib, zlib and jpeg libraries ('''szlib.lib''', '''zlib.lib''' and '''libjpeg.lib'''),&lt;br /&gt;
*the fortran source files ('''ModuleConvertModisL2.F90 ModuleConvertModisL3.F90 ModuleConvertOceanColorL2.F90'''),&lt;br /&gt;
*the C source files and their fortran interface files ('''readL2scan.c readL2Seadas.c''' and '''cdata.f crossp.f fgeonav.f''').&lt;br /&gt;
&lt;br /&gt;
=== CVF IDE configuration ===&lt;br /&gt;
# Configure everything as specified in [[Compiling with CVF]].&lt;br /&gt;
# Add the source files listed in the prerequisites above to the source files listing.&lt;br /&gt;
# Go to '''Tools--&amp;gt;Options...--&amp;gt;Directories'''. There, add the '''$DOTNET2K3/Vc7/bin''' to the '''Executable files''''; the '''$DOTNET2K3/Vc7/include''' and '''$DOTNET2K3/Vc7/PlatformSDK/include''' to the '''Include files'''; and finally, the '''$DOTNET2K3/Vc7/lib''', '''$DOTNET2K3/Vc7/PlatformSDK/lib''' and  '''$DOTNET2K3/Vc7/PlatformSDK/bin''' to the '''Library files'''.&lt;br /&gt;
# Go to '''Projects--&amp;gt;Settings--&amp;gt;Release--&amp;gt;Link--&amp;gt;Input'''. There, add the following libraries: '''netcdf.lib netcdf_.lib hd421.lib hm421.lib libjpeg.lib'''. (Make sure the hdf5 libraries as well as the szlib and zlib libraries are already mentioned).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshoots ===&lt;br /&gt;
'''Q: I get unresolved external references during linkage, but I have all the libraries mentioned above included. What should I do?'''&lt;br /&gt;
&lt;br /&gt;
A: Unresolved external references can come out for two reasons:&lt;br /&gt;
#you didn't specified all the libraries required or all the paths for the default libraries or,&lt;br /&gt;
#[http://en.wikipedia.org/wiki/Name_decoration name mangling] problems. Use the [[dumpbin]] utility to the libraries to checkout which language convention they are using. If that's the problem then you need to try to get new libraries with the correct naming convention.&lt;br /&gt;
&lt;br /&gt;
That's it, you should now be able to build the [[ConvertToHdf5]] project successfully.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Q: I got a message saying the entry point _NF_PUT_ATT_REAL@28 could not be located in netcdf.dll'''&lt;br /&gt;
&lt;br /&gt;
A: copy the file netcdf.dll to the exe folder&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF5 Homepage]&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF4 Homepage]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
*[[Module_Atmosphere]]&lt;br /&gt;
*[[Module_InterfaceWaterAir]]&lt;br /&gt;
*[[Coupling_Water-Atmosphere_User_Manual]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Hdf5]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6293</id>
		<title>ConvertToHDF5</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6293"/>
				<updated>2012-06-14T16:55:36Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Radar data */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''ConvertToHDF5''' is an application which allows the making of several operations, called '''actions''', involving HDF5 files: conversion of data in other formats (e.g. NETCDF) to HDF5, grid interpolation, concatenation of several files.&lt;br /&gt;
&lt;br /&gt;
Running options for this application are specified by the user in a input file named [[ConvertToHDF5#Input file (ConvertToHDF5Action.dat)|'''ConvertToHDF5Action.dat''']]. Several actions can be specified in the same input file, being processed sequentially by the ConvertToHDF5 application.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
The operations involving HDF5 files performed by ConvertToHDF5, specified individually by an action, can be organized in:&lt;br /&gt;
&lt;br /&gt;
* [[#file management|file management]]&lt;br /&gt;
* [[#grid interpolation|grid interpolation]] and &lt;br /&gt;
* [[#format conversion|format conversion]]. &lt;br /&gt;
&lt;br /&gt;
These types and the respective actions are detailed in the next sections. &lt;br /&gt;
&lt;br /&gt;
The input file specification for each action can be found bellow in the [[#Input file (ConvertToHDF5Action.dat)|Input file (ConvertToHDF5Action.dat)]] section.&lt;br /&gt;
&lt;br /&gt;
==File management==&lt;br /&gt;
&lt;br /&gt;
===Glue files===&lt;br /&gt;
This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 files to be glued. &amp;quot;Grid&amp;quot; and &amp;quot;Results&amp;quot; data groups should be equal in all these files.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with glued &amp;quot;Results&amp;quot; data. &amp;quot;Residual&amp;quot; and &amp;quot;Statistics&amp;quot; HDF5 data groups are not copied to the output file since they are time period specific (different values potentially occour in each file). General statistics can be calculated for the glued HDF5 file data using tool [[HDF5Statistics]].&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Grid interpolation==&lt;br /&gt;
&lt;br /&gt;
===Interpolate files===&lt;br /&gt;
This action performs the conversion of one HDF5 file data existing in one 2D or 3D spatial grid to another 2D or 3D spatial grid, creating a new HDF5 file. The interpolation is performed only for the data located a time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
The HDF5 file containing data to be interpolated is called the '''father file'''.&lt;br /&gt;
&lt;br /&gt;
In case of 3D interpolation the application conducts first the horizontal grid interpolation&lt;br /&gt;
(keeping father geometry) and only after it conducts the vertical interpolation (from father geometry to new geometry).&lt;br /&gt;
&lt;br /&gt;
Several types of 2D interpolation are available for use: bilinear, spline 2D and triangulation.&lt;br /&gt;
For vertical interpolation (used in 3D interpolation) can be supplied several polinomial degrees for interpolation.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data for forcing or providing initial conditions for a MOHID Water model, e.g. a meteorological forcing file.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
For 2D/3D interpolation:&lt;br /&gt;
&lt;br /&gt;
- father HDF5 file;&lt;br /&gt;
&lt;br /&gt;
- father horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
For 3D interpolation also needed:&lt;br /&gt;
&lt;br /&gt;
- father vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- auxiliary horizontal data grid, in a grid data file in the format supported by MOHID; this file is used for horizontal grid interpolation in 3D interpolation operations.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with interpolated data. In case of 3D interpolation also produced an auxiliary HDF5 file with the result of the horizontal grid interpolation, which can be inspected to check if this operation is well performed.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].&lt;br /&gt;
&lt;br /&gt;
===Patch files===&lt;br /&gt;
This action consists in performing an interpolation of HDF5 data between grids, as in action [[#Interpolate files|Interpolate files]], but considering more than one HDF5 file as containing data to be interpolated to the new grid and a priority scale. The interpolation is performed only for the data located in the time window specified by the user. The present version of this action operates only on 2D data.&lt;br /&gt;
&lt;br /&gt;
Each HDF5 file containing data to be interpolated is called a '''father file''' and has an user-attributed '''priority level''' to be respected in the interpolation process: for each new grid cell the ConvertToHDF5 application will look for data first on the Level 1 father file and only in the case this data is inexistent will it look for data in Level 2 file, proceeding in looking for higher level files if no data is found subsequentely.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
To obtain an HDF5 file with data from several HDF5 files each containing data with different spatial resolution and only for a specific part of the new grid. This is, for instance, the case when one is preparing a best resolution meteorological HDF5 file for forcing MOHID Water from several meteorological model domains, having different spatial resolution and span, since the best resolution data is not available for all new grid cells.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
The new horizontal data grid, in a grid data file in the format supported by MOHID, and for each father file:&lt;br /&gt;
&lt;br /&gt;
- level of priority: 1 = maximum priority, priority decreases with increasing level value;&lt;br /&gt;
&lt;br /&gt;
- data grid, in the form of a grid data file in the format supported by MOHID.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with patched data.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#PATCH HDF5 FILES|PATCH HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Format conversion==&lt;br /&gt;
&lt;br /&gt;
===Meteorological model data===&lt;br /&gt;
Mohid does not simulate explicitly the atmosphere, but needs information about atmospheric properties in time and space. This requires that atmospheric properties are supplied to MOHID Water in supported formats. These formats can be derived from meteorological data in HDF5 format. Because the results of meteorological models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the MM5 and the ERA40. These are succintly detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''ERA40''====&lt;br /&gt;
This format refers to the European Centre for Medium-Range Weather Forecasts (ECMWF) 40 years re-analysises results, acessed by site http://data.ecmwf.int/data/d/era40_daily/. This data is available for several meteorological variables with maximum 6 hour periodicity for days in the period from 1957-09-01 to 2002-08-31. &lt;br /&gt;
&lt;br /&gt;
ERA40 data files are supplied by ECMWF in a NetCDF format and with an user-costumized time window, periodicity (time step range from 6 hours to a day) and meteorological properties set. The ERA40 meteorological properties which are recognized by MOHID are presented bellow together with the correspondent MOHID name: &lt;br /&gt;
&lt;br /&gt;
 ---ERA40 NAME---         ---MOHID NAME---&lt;br /&gt;
   sshf                     sensible heat                &lt;br /&gt;
   slhf                     latent heat                  &lt;br /&gt;
   msl                      atmospheric pressure &lt;br /&gt;
   tcc                      cloud cover &lt;br /&gt;
   p10u                     wind velocity X&lt;br /&gt;
   p10v                     wind velocity Y&lt;br /&gt;
   p2t                      air temperature&lt;br /&gt;
   ewss                     wind stress X&lt;br /&gt;
   nsss                     wind stress Y&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to all MOHID Water recognized property available in the ERA40 file, producing an individual HDF5 file for each property. The name of each HDF5 file generated includes the ERA40 meteorological property identificator correspondent to the data contained.&lt;br /&gt;
&lt;br /&gt;
Alternatively, ConvertToHDF5 can copy to a single ASCII file the heading information concerning each meteorological variable considered in the original ERA40 file.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data suitable for being used for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ERA40 NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file for each meteorological property contained in the original NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ERA40 FORMAT|CONVERT ERA40 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Aladin''====&lt;br /&gt;
This format relates to Aladin meteorological model results. Some of the atmospheric property needed by MOHID Water is present in Aladin output files, enabling to run prediction simulations with MOHID Water when access to Aladin prevision files is available.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts Aladin results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Aladin netcdf results file to convert.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with Aladin results and a grid data file in MOHID format with the Aladin grid pseudo-information: a fake orography is created of 100 m depth.&lt;br /&gt;
This last file can be used to interpolate the Aladin data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ALADIN FORMAT|CONVERT ALADIN FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MM5''====&lt;br /&gt;
This format relates to the Fifth-Generation NCAR / Penn State Mesoscale Model (MM5) output files format. Almost every atmospheric property needed by MOHID Water is present in MM5 output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts MM5 results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the MM5 files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
For conversion to be completed it is required the horizontal grid information of MM5 results which is available in special TERRAIN files.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
MM5 results file to convert and MM5 TERRAIN file. The TERRAIN file supplies the MM5 results grid information. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
A HDF5 file with MM5 results and a grid data file in MOHID format with the MM5 grid information.&lt;br /&gt;
This last file can be used to interpolate the MM5 data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MM5 FORMAT|CONVERT MM5 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''WRF''====&lt;br /&gt;
This format relates to the Weather Research and Forecast model (WRF) output files format. Almost every atmospheric property needed by MOHID Water is present in WRF output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts WRF results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the WRF properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the WRF files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
WRF direct output file.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with WRF results and a grid data file in MOHID format with the WRF grid information.&lt;br /&gt;
This last file can be used to interpolate the WRF data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! [[PROJ4 | PROJ4]] library is needed! See [[#Compile_ModuleWRFFormat |  Compile_ModuleWRFFormat]]&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT WRF FORMAT|CONVERT WRF FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Wave model data===&lt;br /&gt;
Mohid does not simulate explicitly the wave dynamics, but needs information about wave properties in time and space. This requires that wave properties are supplied to MOHID Water in supported formats. These formats can be derived from wave data in HDF5 format. Because the results of wave models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the table format of SWAN. This is succintly detailed in the next section.&lt;br /&gt;
&lt;br /&gt;
====''SWAN''====&lt;br /&gt;
SWAN data files are supplied in a ASCII format. The data is organized by time instant. For each time instant there is a table of data. Each column represents one property. &lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to gradients of wave stresses X and Y, mean amplitude, mean period and mean direction.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 SWAN data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ASCII (table type) SWAN results data files and bathymetry in MOHID grid data foramt. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (wave stresses X and Y, mean amplitude, mean period and mean direction). &lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT TO AND FROM SWAN|CONVERT TO AND FROM SWAN]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Ocean model data===&lt;br /&gt;
Ocean model data, available in diverse formats, can be used by MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation. These uses require that the model data is in HDF5 format and conversion is therefore needed.&lt;br /&gt;
&lt;br /&gt;
Currently the large scale ocean models formats convertible into HDF5 by ConvertToHDF5 includes MERCATOR.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MERCATOR''====&lt;br /&gt;
MERCATOR data files are supplied in a NetCDF format and with an user-costumized spatial window and periodicity. Water level and water properties (temperature and salinity) data is available in type T files, velocity component u data is available in type U files and velocity component v data is available in type V files. The type of data of a specific MERCATOR file is generally indicated in the file name.&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to temperature, salinity, water level, component u of velocity and component v of velocity.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 MERCATOR data usable for forcing or validation of MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
NetCDF MERCATOR results data files and NetCDF MERCATOR grid data files. It should be provided one grid data file of each type: T, U and V. These are generally provided by the MERCATOR services together with the results files.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (temperature, salinity, water level, velocity u and velocity v) and the correspondent grid data and geometry files, containing respectively the horizontal grid and the vertical discretization of the HDF5 file. The grid data and geometry files can be used afterwards to interpolate the MERCATOR data to another grid and geometry (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MERCATOR FORMAT|CONVERT MERCATOR FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Climatological data===&lt;br /&gt;
Climatological data can be used in MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation, in case more realistic data (measurements or model) data is unavailable. This data is generally supplied by producers in formats not readly usable by MOHID Water which justifies the existence of a conversion tool.&lt;br /&gt;
&lt;br /&gt;
Two climatological data format conversions are implemented in ConvertToHDF5: Levitus ocean data and Hellerman Rosenstein meteorological data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''Levitus''====&lt;br /&gt;
The Levitus climatology provides results for water temperature and salinity.&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window requested by the user. &lt;br /&gt;
Typically, it requires 3 steps to complete the task:&lt;br /&gt;
&lt;br /&gt;
- convert levitus format &lt;br /&gt;
&lt;br /&gt;
- extrapolate the data to the whole levitus domain(required to avoid uncoincidental coastlines) &lt;br /&gt;
&lt;br /&gt;
- interpolate with the model grid(bathymetry)&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as boundary forcing and/or initial condition specification in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Levitus climatological data files, one per property and per time period (e.g a month).&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Levitus climatological data, grid data file with the horizontal&lt;br /&gt;
grid of the data and a geometry file with vertical discretization of the data (MOHID formats).&lt;br /&gt;
The grid data and the geometry files can be used to interpolate the climatological data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT LEVITUS FORMAT|CONVERT LEVITUS FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Hellerman Rosenstein''====&lt;br /&gt;
This is a meteorological climatology providing wind stress. There is a file per wind stress component. Since the data refer to surface values it is a 2D field.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window provided by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as meteorological forcing in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Hellerman Rosenstein climatological data ASCII files, one per wind stress component.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Hellerman Rosenstein climatological data and grid data file with the horizontal&lt;br /&gt;
grid of the climatological data. This grid data file can be used to interpolate the climatological data from the original horizontal grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT HELLERMAN ROSENSTEIN ASCII|CONVERT HELLERMAN ROSENSTEIN ASCII]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''World Ocean Atlas 2005''====&lt;br /&gt;
The World Ocean Atlas (WOA) 2005 climatology provides results for water temperature, salinity and several water quality and biology properties.&lt;br /&gt;
&lt;br /&gt;
Description, Action and Input Files are described in a separate page: [[ConvertToHDF5 WOA2005]].&lt;br /&gt;
&lt;br /&gt;
===Generic NETCDF CF FILES===&lt;br /&gt;
&lt;br /&gt;
Converts any netcdf file following the CF convention into Mohid HDF5 files. Check the [[ConvertToHDF5#CONVERT_GENERIC_NETCDF_CF | Input File]] and [[ConvertToHDF5#Convert_generic_Netcdf_CF_to_MOHID.28.hdf5.29 | Sample File]].&lt;br /&gt;
&lt;br /&gt;
===Radar data===&lt;br /&gt;
====Seasonde RADAR Data====&lt;br /&gt;
Converts a list of ascii files from the Seasonde radar data, which measures currents over a given region of space, into an hdf5 file with the MOHID format. Useful to validate coastal and estuarine models where radars are located. ConvertToHDF5 tool must be compiled with the preprocessor variable definition _SCANLINE_UNSAFE set in the Mohid Base 1.&lt;br /&gt;
&lt;br /&gt;
==Input file (ConvertToHDF5Action.dat)==&lt;br /&gt;
===General structure===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt; (block containing instructions for running a specific action) &lt;br /&gt;
 ACTION                    : ... (intended action)&lt;br /&gt;
 ... (action specific instructions)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : ...&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GLUES HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 3D_FILE                   : 0/1 (0 = 2D file, 1 = 3D file)&lt;br /&gt;
 &lt;br /&gt;
 TIME_GROUP                : ... (Default=&amp;quot;Time&amp;quot;. Other option: &amp;quot;SurfaceTime&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (Default=&amp;quot;Results&amp;quot;. Other options: &amp;quot;Residual&amp;quot;, &amp;quot;SurfaceResults&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 &lt;br /&gt;
 (block of HDF5 data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of HDF5 file with data to be included in glue, one per line, at least two files)&lt;br /&gt;
 ...                      &lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===INTERPOLATE GRIDS===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of horizontal interpolation: 1 = Bilinear, 2 = Spline2D,&lt;br /&gt;
                                  3 = Triangulation)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION_WINDOW      : ... ... ... ... (2D spatial window to consider for interpolation: &lt;br /&gt;
                                              Xmin Ymin Xmax Ymax; default = all domain)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D           : 0/1 (0 = 2D interpolation, 1 = 3D interpolation)&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_2D            : 0/1/2/3/4/5 (2D extrapolation: 0=no extrapolation, 1=medium&lt;br /&gt;
                                      triangulation, 2=high triangulation, &lt;br /&gt;
                                      3=nearest neighbour, 4=nearest cell, &lt;br /&gt;
                                      5=constant value)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_VALUE         : ... (name of the value to extrapolate to when EXTRAPOLATE_2D is&lt;br /&gt;
                                  set to constant value (5))&lt;br /&gt;
 &lt;br /&gt;
 DO_NOT_BELIEVE_MAP        : 0/1 (0=consider input HDF5 file map, 1=do not consider input HDF5&lt;br /&gt;
                                  file map)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (name of base group of HDF5 variables containing data to be &lt;br /&gt;
                                  interpolated; default is &amp;quot;/Results&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (if INTERPOLATION3D : 1 also required:)&lt;br /&gt;
 FATHER_GEOMETRY           : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  of input HDF5 file)&lt;br /&gt;
 NEW_GEOMETRY              : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  intended for output HDF5 file)&lt;br /&gt;
 POLI_DEGREE               : 1/... (degree of vertical interpolation: 1=linear, ...)&lt;br /&gt;
 &lt;br /&gt;
 AUX_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for auxiliar output HDF5 file;&lt;br /&gt;
                                  default is file provided in NEW_GRID_FILENAME)&lt;br /&gt;
 &lt;br /&gt;
 AUX_OUTPUTFILENAME        : ... (path/name of auxiliar output HDF5 file to contain result&lt;br /&gt;
                                  of horizontal grid interpolation)   &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the file indicated in AUX_GRID_FILENAME can be different from the one indicated in&lt;br /&gt;
   NEW_GRID_FILENAME in terms of bathymetry, while the horizontal grid should be, commonly, the&lt;br /&gt;
   same: this altered bathymetry can be used to extend the water column in the original data so&lt;br /&gt;
   that the process of vertical interpolation is done easily;&lt;br /&gt;
 &lt;br /&gt;
 - in case of INTERPOLATION3D : 1, ConvertToHDF5 can generate new versions of bathymetry which &lt;br /&gt;
   are consistent with the geometry definition (extension is '.new'); there are possibly three&lt;br /&gt;
   bathymetry changes referring to father grid, new grid and aux grid (the same bathymetry is&lt;br /&gt;
   not altered twice); although initially new and aux grid are the same they can result &lt;br /&gt;
   different because of bathymetry changes;&lt;br /&gt;
 &lt;br /&gt;
 - in case the new geometry is 2D and father geometry is 3D then POLI_DEGREE : 1 &lt;br /&gt;
   (linear interpolation) should be used;&lt;br /&gt;
 &lt;br /&gt;
 - EXTRAPOLATE_2D : 1/2/3/4/5 should be considered if it is expected that the coast line is not&lt;br /&gt;
   coincidental in the father and new grids, to avoid lack of data in the interpolation&lt;br /&gt;
   process; extrapolation is performed for all cells even the land cells; &lt;br /&gt;
 &lt;br /&gt;
 - in case of DO_NOT_BELIEVE_MAP : 1 the application generates a map based on cells where&lt;br /&gt;
   interpolation results are available; this causes that if EXTRAPOLATE_2D : 1/2/3/4/5 is used&lt;br /&gt;
   the AUX_GRID_FILENAME should not have land cells in order for the new map to be concurrent&lt;br /&gt;
   with the result of extrapolation and avoid errors generation, specially if INTERPOLATION3D :&lt;br /&gt;
   1 is considered.&lt;br /&gt;
&lt;br /&gt;
===PATCH HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of interpolation: 3 = Triangulation, default and only&lt;br /&gt;
                                  one implemented)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 (block for each father HDF5 file, should be at least two)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                     : ... (integer priority level: 1 = highest, increase for lower&lt;br /&gt;
                                  priority)&lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 N_REMOVE_FRAME            : 0   (width, in number of cells, of frame to remove)&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT ERA40 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of ERA40 NetCDF file)&lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
                                 (root of name for all files produced)&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII          : 0/1 (1 = convert variable heading info for ASCII file; 0 = default)&lt;br /&gt;
 CONVERT_TO_HDF5           : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 GRIDTO180                 : 0/1 (1 = convert grid from [0 360] to [-180 180], 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 YY_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 TIME_VARIABLE             : ... (name of time variable in the input file: usual name is&lt;br /&gt;
                                  &amp;quot;time&amp;quot;)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - either CONVERT_TO_ASCII : 1 or CONVERT_TO_HDF5 : 1 must be chosen for any action to be&lt;br /&gt;
 performed by ConvertToHDF5;&lt;br /&gt;
 &lt;br /&gt;
 - when CONVERT_TO_HDF5 : 1 an HDF5 file is produced for every variable contained in the&lt;br /&gt;
 original ERA40 file; the name of each file is composed of the name indicated on FILENAME&lt;br /&gt;
 concatenated with the ERA40 variable identifier;&lt;br /&gt;
 &lt;br /&gt;
 - to the XX_VARIABLE, YY_VARIABLE and TIME_VARIABLE keywords should generally be  &lt;br /&gt;
 specified &amp;quot;longitude&amp;quot;, &amp;quot;latitude&amp;quot; and &amp;quot;time&amp;quot;, respectively; the option to&lt;br /&gt;
 include as keywords was made only to make the application robust to future variable name&lt;br /&gt;
 changes.&lt;br /&gt;
&lt;br /&gt;
===CONVERT ALADIN FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 (path to aladin netcdf file)\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each Aladin property to convert in &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;...&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt; block must conform to the following variables&lt;br /&gt;
 &lt;br /&gt;
           ---ALADIN NAME---    ---MOHID NAME---&lt;br /&gt;
             soclotot            CloudCover_&lt;br /&gt;
             sohumrel            RelativeHumidity_&lt;br /&gt;
             sofluxir            NonSolarFlux_&lt;br /&gt;
             sosspres            AtmosphericPressure_&lt;br /&gt;
             sosolarf            SolarRadiation_&lt;br /&gt;
             sotemair            AirTemperature_&lt;br /&gt;
             sowinmod            WindModulus_&lt;br /&gt;
             sowaprec            Precipitation_&lt;br /&gt;
             sozotaux            WindStressX_&lt;br /&gt;
             sometauy            WindStressY_&lt;br /&gt;
             sowindu10           WindVelocityX_&lt;br /&gt;
             sowindv10           WindVelocityY_&lt;br /&gt;
&lt;br /&gt;
===CONVERT MM5 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MM5 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of MM5 file)&lt;br /&gt;
 TERRAIN_FILENAME          : ... (path/name of MM5 TERRAIN file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of MM5 data to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP                 : 0/1 (1 = compute and write mean sea level pressure field; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of MM5 properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of MM5 property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each MM5 property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must&lt;br /&gt;
 conform to the MOHID designation specified in code of ModuleGlobalData; the correspondence is &lt;br /&gt;
 the following (see [[Module_InterfaceWaterAir]] for a more detailed explanation).&lt;br /&gt;
 &lt;br /&gt;
           ---MM5 NAME---    ---MOHID NAME---&lt;br /&gt;
             T2             air temperature&lt;br /&gt;
             PSTARCRS       atmospheric pressure&lt;br /&gt;
             U10            wind velocity X&lt;br /&gt;
             V10            wind velocity Y&lt;br /&gt;
             UST            wind shear velocity&lt;br /&gt;
             LHFLUX         latent heat&lt;br /&gt;
             SWDOWN         sensible heat&lt;br /&gt;
             SWDOWN         solar radiation&lt;br /&gt;
             LWDOWN         infrared radiation&lt;br /&gt;
             SWOUT          top outgoing shortwave radiation&lt;br /&gt;
             LWOUT          top outgoing longwave radiation&lt;br /&gt;
             SOIL T 1       soil temperature layer 1&lt;br /&gt;
             SOIL T 1       soil temperature layer 2&lt;br /&gt;
             SOIL T 1       soil temperature layer 3&lt;br /&gt;
             SOIL T 1       soil temperature layer 4&lt;br /&gt;
             SOIL T 1       soil temperature layer 5&lt;br /&gt;
             SOIL T 1       soil temperature layer 6&lt;br /&gt;
             Q2             2-meter mixing ratio&lt;br /&gt;
             TSEASFC        sea water temperature&lt;br /&gt;
             PBL HGT        PBL height&lt;br /&gt;
             PBL REGIME     PBL regime&lt;br /&gt;
             RAIN CON       accumulated convective precipitation        (cm)&lt;br /&gt;
             RAIN NON       accumulated non-convective precipitation    (cm)&lt;br /&gt;
             GROUND T       ground temperature&lt;br /&gt;
             RES TEMP       infinite reservoir slab temperature&lt;br /&gt;
             U              wind velocity X_3D&lt;br /&gt;
             V              wind velocity Y_3D&lt;br /&gt;
             W              wind velocity Z_3D&lt;br /&gt;
             T              air temperature_3D&lt;br /&gt;
             PP             atmospheric pressure_3D&lt;br /&gt;
             Q              mixing ratio_3D&lt;br /&gt;
             CLW            cloud water mixing ratio_3D&lt;br /&gt;
             RNW            rain water mixing ratio_3D&lt;br /&gt;
             ICE            cloud ice mixing ratio_3D&lt;br /&gt;
             SNOW           snow mixing ratio_3D&lt;br /&gt;
             RAD TEND       atmospheric radiation tendency_3D&lt;br /&gt;
&lt;br /&gt;
===CONVERT WRF FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                       : CONVERT WRF FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                     : ... (path/name of WRF file)&lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of WRF data&lt;br /&gt;
                                     to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP_MM5             : 0/1 (1 = compute mean sea level pressure with MM5toGrads algorithm; 1 = default)&lt;br /&gt;
 COMPUTE_MSLP_WRF             : 0/1 (1 = compute mean sea level pressure with ARWPost algorithm; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 OUTPUT_DT                    : real (DT interval in seconds between each output; default = 0.0)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
  &lt;br /&gt;
 - the name of each property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must conform to the MOHID &lt;br /&gt;
   designation specified in code of ModuleGlobalData; the correspondence to WRF is in function &lt;br /&gt;
   VariableIsToRead in ModuleWRFFormat. Conversion is not direct since WRF outputs tendencies and not  &lt;br /&gt;
   total values. &lt;br /&gt;
 &lt;br /&gt;
 - Caution: This action is not extensively tested.&lt;br /&gt;
&lt;br /&gt;
===CONVERT MERCATOR FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION               : 1/2/3/4 (version of MERCATOR files)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 1:)&lt;br /&gt;
 BASE_BULLETIN             : ...&lt;br /&gt;
 DATES_FILE                : ...&lt;br /&gt;
 NUM_DATES                 : ... &lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 2/3:)&lt;br /&gt;
 INPUT_GRID_FILENAME       : ... (path/name of file with horizontal discretization of water&lt;br /&gt;
                                  properties and water level data)&lt;br /&gt;
 (if READ_OPTION : 2:)&lt;br /&gt;
 INPUT_GRID_FILENAME_U     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component U data)&lt;br /&gt;
 INPUT_GRID_FILENAME_V     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component V data)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 3:)&lt;br /&gt;
 INPUT_BATHY_FILENAME      : ... (path/name of file with bathymetry)&lt;br /&gt;
     &lt;br /&gt;
 (if READ_OPTION : 3/4:)&lt;br /&gt;
 CALC_BAROTROPIC_VEL       : 0/1 (1 = calculate barotropic velocity, 0 = not calculate; &lt;br /&gt;
                                  default = 0)&lt;br /&gt;
 &lt;br /&gt;
 (if CALC_BAROTROPIC_VEL : 1 and READ_OPTION : 3:)&lt;br /&gt;
 INPUT_MESH_ZGRID_FILENAME : ... (path/name of file with information about layers ticknesses)&lt;br /&gt;
 &lt;br /&gt;
 (block of MERCATOR data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of MERCATOR NetCDF data file, one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT LEVITUS FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT LEVITUS FORMAT&lt;br /&gt;
  &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Levitus data: &amp;quot;monthly&amp;quot;/&amp;quot;annual&amp;quot;; default is&lt;br /&gt;
                                  &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Levitus grid)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
 &lt;br /&gt;
 (block for each water property to be present in output HDF5 file, can be several)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property)&lt;br /&gt;
 ANNUAL_FILE               : ... (path/name of Levitus annual file)&lt;br /&gt;
 &lt;br /&gt;
 (block of Levitus data files)&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of Levitus data file (e.g. a monthly data file), one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT HELLERMAN ROSENSTEIN ASCII===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
  &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Hellerman Rosenstein data: &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Hellerman&lt;br /&gt;
                                  Rosenstein grid: default and only allowed value is &amp;quot;2.&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
   &lt;br /&gt;
 (block for each Hellerman Rosenstein data file)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property: &amp;quot;wind stress X&amp;quot;/&amp;quot;wind stress Y&amp;quot;)&lt;br /&gt;
 FILE                      : ... (path/name Hellerman Rosenstein file)&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CONVERT GENERIC NETCDF CF===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION              : CONVERT NETCDF CF TO HDF5 MOHID       &lt;br /&gt;
 HDF5_OUT            : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 OUTPUTFILENAME      : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)&lt;br /&gt;
 OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property for time, generally &amp;quot;time&amp;quot;&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT     : ... (name of the netcdf property for latitude, generally &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_LONG    : ... (name of the netcdf property for longitude, generally &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_MAPPING : ... (name of the netcdf field where is located the mapping 0 water 1 land)&lt;br /&gt;
                           (It can also be used any field, i.e. temperature)&lt;br /&gt;
 MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus &amp;gt;0.5 water)&lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER   : real (number of netcdf properties) &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property&lt;br /&gt;
 NAME                : name of the HDF5 Mohid property&lt;br /&gt;
 UNITS               : property units&lt;br /&gt;
 DESCRIPTION         : property description&lt;br /&gt;
 DIM                 : 2/3 Number of property dimensions &lt;br /&gt;
 VECTOR_INTENSITY    : 0/1 If property corresponds to a vector intensity&lt;br /&gt;
 VECTOR_X            : Decomposition of Vector Intensity X&lt;br /&gt;
 VECTOR_Y            : Decomposition of Vector Intensity Y&lt;br /&gt;
 BEAUFORT_SCALE      : 0/1 If property correspond to the beaufort scale&lt;br /&gt;
 ADD_FACTOR          : To add the property a fixed value&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 path to netcdf cf file&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT SEASONDE RADAR FORMAT ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 !HDF5 path and filename that will contain the results&lt;br /&gt;
 OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
 &lt;br /&gt;
 !griddata path and filename that will contain a griddata of the proxy bathymetry used in the hdf5 output file.&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Path and filename to the grid that maps the radar data. This grid must be constructed with the [[GIS]]&lt;br /&gt;
 !or MOHID Studio and must &amp;quot;fit&amp;quot; well where the points stand.&lt;br /&gt;
 INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
 &lt;br /&gt;
 !This is the version of the grid used by the seasonde radar system.&lt;br /&gt;
 !If the grid version of the seasonde radar changes, then most likely a new input grid must be&lt;br /&gt;
 !constructed with the GIS or MOHID Studio.&lt;br /&gt;
 IH_GRID_VERSION           : 4&lt;br /&gt;
 &lt;br /&gt;
 !This is a list with the Seasonde radar ascii data files. One file per instant.&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Samples==&lt;br /&gt;
All sample files are named ''ConvertToHDF5Action.dat''.&lt;br /&gt;
&lt;br /&gt;
===Glue several MOHID(.hdf5) files===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : SurfaceHydro_OP.hdf5&lt;br /&gt;
  &lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_21.hdf5&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_22.hdf5&lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 2D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME           : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
  &lt;br /&gt;
 START                    : 2006 6 21 17 22 30&lt;br /&gt;
 END                      : 2006 6 22 17 22 0&lt;br /&gt;
  &lt;br /&gt;
 FATHER_GRID_FILENAME     : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME        : TagusConstSpacing.dat&lt;br /&gt;
  &lt;br /&gt;
 BASE_GROUP               : /Results/Oil/Data_2D&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 3D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 1&lt;br /&gt;
 FATHER_FILENAME         : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME          : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2006 6 21 17 22 30&lt;br /&gt;
 END                     : 2006 6 22 17 22 0&lt;br /&gt;
 &lt;br /&gt;
 FATHER_GRID_FILENAME    : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP              : /Results/Oil/Data_2D&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D         : 1&lt;br /&gt;
 FATHER_GEOMETRY         : D:\Projectos\MohidRun\test\data\Geometry_1.dat&lt;br /&gt;
 NEW_GEOMETRY            : TagusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME      : Aux_GridRegular.hdf5&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Patch several MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 3&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2005 2 28 13 0 0&lt;br /&gt;
 END                     : 2005 3 1 13 0 0&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 3&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D1.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid1.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 2&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D2.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid2.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 1&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D3.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid3.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME          : MM5Forcing.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME       : K:\Simula\GeneralData\Batim\CostaPortuguesa.dat&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert an ERA40 file to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                  : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                : D:\Aplica\ERA40\1971ERA1973.nc&lt;br /&gt;
 OUTPUTFILENAME          : D:\Aplica\ERA40\1971ERA1973T2&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII        : 0&lt;br /&gt;
 CONVERT_TO_HDF5         : 1&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE             : longitude&lt;br /&gt;
 YY_VARIABLE             : latitude&lt;br /&gt;
 TIME_VARIABLE           : time&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a MM5 file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : MMOUT_DOMAIN2&lt;br /&gt;
 TERRAIN_FILENAME          : TERRAIN_DOMAIN2&lt;br /&gt;
 OUTPUTFILENAME            : D2.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : D2.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 !START                     : 2010 02 15 00 00 00&lt;br /&gt;
 !END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a WRF file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : wrfout_d01_2010-02-15_00.nc&lt;br /&gt;
 OUTPUTFILENAME            : wrfout_d01.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : wrfout_d01.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 START                     : 2010 02 15 00 00 00&lt;br /&gt;
 END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Mercator-Ocean(.nc) to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION              : 2&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Psy2v2r1v_R20060628/MercatorR20060628.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : Psy2v2r1v_R20060628/MercatorGridR20060628.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : Psy2v2r1v_R20060628/MercatorGeometryR20060628.dat&lt;br /&gt;
 &lt;br /&gt;
 INPUT_GRID_FILENAME      : GridFiles/ist_meteog-gridT.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_U    : GridFiles/ist_meteog-gridU.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_V    : GridFiles/ist_meteog-gridV.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060621_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060622_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060623_R20060628.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Levitus format to MOHID(.hdf5) and interpolate grid===&lt;br /&gt;
==== Convert ====&lt;br /&gt;
First convert the Levitus ASCII format to a raw HDF5 format:&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT LEVITUS FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Levitus.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : LevitusGeometry.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 0.25&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -16.0  31&lt;br /&gt;
 UPPER_RIGHT_CORNER       :   1.   40&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : salinity&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : temperature&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Temp\t000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Extrapolate ====&lt;br /&gt;
Then extrapolate the data (still in the raw HDF5 format):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME          : Levitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : LevitusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxLeviTusAllPointsWithData.hdf5&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 EXTRAPOLATE_2D           : 2&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Interpolate ====&lt;br /&gt;
Finally, interpolate to the final grid and geometry (same as the [[#Interpolate 3D MOHID(.hdf5) files to a new grid| Interpolate 3D sample]]):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 OUTPUTFILENAME           : CadizMonthlyLevitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 NEW_GRID_FILENAME        : Algarve0.02SigmaSmooth_V3_CartMoreLayers.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : Geometry_1.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxCadizMonthlyLevitus.hdf5&lt;br /&gt;
 AUX_GRID_FILENAME        : Aux12km.dat&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the programme may construct a new bathymetry twice. Use this bathymetry only on the AUX_GRID_FILENAME keyword.&lt;br /&gt;
&lt;br /&gt;
===Convert Hellerman Rosenstein ASCII format to MOHID(.hdf5)  ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : ClimatologicWindStress.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : ClimatologicWindStressGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 2.&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -180  -90&lt;br /&gt;
 UPPER_RIGHT_CORNER       : 180  90&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress X&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUXX.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress Y&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUYY.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert ALADIN(.nc) format to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKPRES_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKSOLAR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKTAIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKWIND_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_FLUXPRE_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSU_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSV_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_U10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_V10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKHUMI_OPASYMP_19723_20088.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Convert generic Netcdf CF to MOHID(.hdf5)  ===&lt;br /&gt;
&lt;br /&gt;
This sample is for converting a typical GFS file&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION : CONVERT NETCDF CF TO HDF5 MOHID&lt;br /&gt;
 HDF5_OUT : 1&lt;br /&gt;
 OUTPUTFILENAME : ..\..\data\hdf5\GFS.hdf5&lt;br /&gt;
 NETCDF_OUT : 1&lt;br /&gt;
 OUTPUT_NETCDF_FILE : ..\..\data\netcdf\GFS.nc&lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : time&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT : latitude&lt;br /&gt;
 NETCDF_NAME_LONG : longitude&lt;br /&gt;
 NETCDF_NAME_MAPPING : TMP_10mb&lt;br /&gt;
 MAPPING_LIMIT : -10000&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER : 6 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : PRMSL_meansealevel&lt;br /&gt;
 NAME : atmospheric pressure&lt;br /&gt;
 UNITS : Pa&lt;br /&gt;
 DESCRIPTION : GFS&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : UGRD_10mb&lt;br /&gt;
 NAME : wind velocity X&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : VGRD_10mb&lt;br /&gt;
 NAME : wind velocity Y&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus&lt;br /&gt;
 NAME                     : wind modulus &lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 VECTOR_INTENSITY         : 1&lt;br /&gt;
 VECTOR_X                 : wind velocity X&lt;br /&gt;
 VECTOR_Y                 : wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus_beaufort &lt;br /&gt;
 NAME                     : wind modulus beaufort &lt;br /&gt;
 UNITS : beaufort scale&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 BEAUFORT_SCALE           : 1&lt;br /&gt;
 VECTOR_X                 : wind modulus&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : TMP_2maboveground&lt;br /&gt;
 NAME : air temperature&lt;br /&gt;
 UNITS : oC&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 ADD_FACTOR  : -273&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ..\..\data\netcdf\gfs_4_20111115.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
=== Convert Seasonde RADAR data sample configuration file===&lt;br /&gt;
The input grid file must be created to be the recipient of the data in the ascii files.&lt;br /&gt;
To create this grid, it is recommended to convert manually, resorting to a good text editor, such as Notepad++, a few radar ascii files into the [[xyz]] Mohid format, then load them in the [[GIS]] or [[Mohid Studio]], and from there create and save a regular grid that fits the points. Use that grid to convert the data into one hdf5 file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;begin_file&amp;gt;&lt;br /&gt;
ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
&lt;br /&gt;
OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
IH_GRID_VERSION           : 4&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_30_1400.tuv.txt&lt;br /&gt;
&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
&amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OceanColor modules compilation ==&lt;br /&gt;
Compiling the [[ConvertToHDF5]] tool with the OceanColor modules is more complicated than one might expect. A solution is proposed here for a release version using the Compaq Visual Fortran 6.6c. The difficulties rise because C code is embedded with a fortran interface and also, extra libraries such as hdf4 are required.&lt;br /&gt;
&lt;br /&gt;
=== Pre-requisites ===&lt;br /&gt;
&lt;br /&gt;
This is a list of prerequisites to successfully compile the tool:&lt;br /&gt;
*Compaq Visual Fortran 6.5 with patch 6.6c,&lt;br /&gt;
*VS .NET 2003 (Vc7 in particular),&lt;br /&gt;
*Hdf5 libraries ('''hdf5.lib''' '''hdf5_fortran.lib''' '''hdf5_hl.lib'''),&lt;br /&gt;
*Netcdf libraries ('''netcdf.lib''' '''netcdf_.lib'''),&lt;br /&gt;
*Hdf4 libraries ('''hd421.lib''', '''hm421.lib'''),&lt;br /&gt;
*szlib, zlib and jpeg libraries ('''szlib.lib''', '''zlib.lib''' and '''libjpeg.lib'''),&lt;br /&gt;
*the fortran source files ('''ModuleConvertModisL2.F90 ModuleConvertModisL3.F90 ModuleConvertOceanColorL2.F90'''),&lt;br /&gt;
*the C source files and their fortran interface files ('''readL2scan.c readL2Seadas.c''' and '''cdata.f crossp.f fgeonav.f''').&lt;br /&gt;
&lt;br /&gt;
=== CVF IDE configuration ===&lt;br /&gt;
# Configure everything as specified in [[Compiling with CVF]].&lt;br /&gt;
# Add the source files listed in the prerequisites above to the source files listing.&lt;br /&gt;
# Go to '''Tools--&amp;gt;Options...--&amp;gt;Directories'''. There, add the '''$DOTNET2K3/Vc7/bin''' to the '''Executable files''''; the '''$DOTNET2K3/Vc7/include''' and '''$DOTNET2K3/Vc7/PlatformSDK/include''' to the '''Include files'''; and finally, the '''$DOTNET2K3/Vc7/lib''', '''$DOTNET2K3/Vc7/PlatformSDK/lib''' and  '''$DOTNET2K3/Vc7/PlatformSDK/bin''' to the '''Library files'''.&lt;br /&gt;
# Go to '''Projects--&amp;gt;Settings--&amp;gt;Release--&amp;gt;Link--&amp;gt;Input'''. There, add the following libraries: '''netcdf.lib netcdf_.lib hd421.lib hm421.lib libjpeg.lib'''. (Make sure the hdf5 libraries as well as the szlib and zlib libraries are already mentioned).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshoots ===&lt;br /&gt;
'''Q: I get unresolved external references during linkage, but I have all the libraries mentioned above included. What should I do?'''&lt;br /&gt;
&lt;br /&gt;
A: Unresolved external references can come out for two reasons:&lt;br /&gt;
#you didn't specified all the libraries required or all the paths for the default libraries or,&lt;br /&gt;
#[http://en.wikipedia.org/wiki/Name_decoration name mangling] problems. Use the [[dumpbin]] utility to the libraries to checkout which language convention they are using. If that's the problem then you need to try to get new libraries with the correct naming convention.&lt;br /&gt;
&lt;br /&gt;
That's it, you should now be able to build the [[ConvertToHdf5]] project successfully.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Q: I got a message saying the entry point _NF_PUT_ATT_REAL@28 could not be located in netcdf.dll'''&lt;br /&gt;
&lt;br /&gt;
A: copy the file netcdf.dll to the exe folder&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF5 Homepage]&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF4 Homepage]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
*[[Module_Atmosphere]]&lt;br /&gt;
*[[Module_InterfaceWaterAir]]&lt;br /&gt;
*[[Coupling_Water-Atmosphere_User_Manual]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Hdf5]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6291</id>
		<title>ConvertToHDF5</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6291"/>
				<updated>2012-06-05T15:37:18Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* CONVERT SEASONDE RADAR FORMAT */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''ConvertToHDF5''' is an application which allows the making of several operations, called '''actions''', involving HDF5 files: conversion of data in other formats (e.g. NETCDF) to HDF5, grid interpolation, concatenation of several files.&lt;br /&gt;
&lt;br /&gt;
Running options for this application are specified by the user in a input file named [[ConvertToHDF5#Input file (ConvertToHDF5Action.dat)|'''ConvertToHDF5Action.dat''']]. Several actions can be specified in the same input file, being processed sequentially by the ConvertToHDF5 application.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
The operations involving HDF5 files performed by ConvertToHDF5, specified individually by an action, can be organized in:&lt;br /&gt;
&lt;br /&gt;
* [[#file management|file management]]&lt;br /&gt;
* [[#grid interpolation|grid interpolation]] and &lt;br /&gt;
* [[#format conversion|format conversion]]. &lt;br /&gt;
&lt;br /&gt;
These types and the respective actions are detailed in the next sections. &lt;br /&gt;
&lt;br /&gt;
The input file specification for each action can be found bellow in the [[#Input file (ConvertToHDF5Action.dat)|Input file (ConvertToHDF5Action.dat)]] section.&lt;br /&gt;
&lt;br /&gt;
==File management==&lt;br /&gt;
&lt;br /&gt;
===Glue files===&lt;br /&gt;
This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 files to be glued. &amp;quot;Grid&amp;quot; and &amp;quot;Results&amp;quot; data groups should be equal in all these files.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with glued &amp;quot;Results&amp;quot; data. &amp;quot;Residual&amp;quot; and &amp;quot;Statistics&amp;quot; HDF5 data groups are not copied to the output file since they are time period specific (different values potentially occour in each file). General statistics can be calculated for the glued HDF5 file data using tool [[HDF5Statistics]].&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Grid interpolation==&lt;br /&gt;
&lt;br /&gt;
===Interpolate files===&lt;br /&gt;
This action performs the conversion of one HDF5 file data existing in one 2D or 3D spatial grid to another 2D or 3D spatial grid, creating a new HDF5 file. The interpolation is performed only for the data located a time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
The HDF5 file containing data to be interpolated is called the '''father file'''.&lt;br /&gt;
&lt;br /&gt;
In case of 3D interpolation the application conducts first the horizontal grid interpolation&lt;br /&gt;
(keeping father geometry) and only after it conducts the vertical interpolation (from father geometry to new geometry).&lt;br /&gt;
&lt;br /&gt;
Several types of 2D interpolation are available for use: bilinear, spline 2D and triangulation.&lt;br /&gt;
For vertical interpolation (used in 3D interpolation) can be supplied several polinomial degrees for interpolation.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data for forcing or providing initial conditions for a MOHID Water model, e.g. a meteorological forcing file.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
For 2D/3D interpolation:&lt;br /&gt;
&lt;br /&gt;
- father HDF5 file;&lt;br /&gt;
&lt;br /&gt;
- father horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
For 3D interpolation also needed:&lt;br /&gt;
&lt;br /&gt;
- father vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- auxiliary horizontal data grid, in a grid data file in the format supported by MOHID; this file is used for horizontal grid interpolation in 3D interpolation operations.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with interpolated data. In case of 3D interpolation also produced an auxiliary HDF5 file with the result of the horizontal grid interpolation, which can be inspected to check if this operation is well performed.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].&lt;br /&gt;
&lt;br /&gt;
===Patch files===&lt;br /&gt;
This action consists in performing an interpolation of HDF5 data between grids, as in action [[#Interpolate files|Interpolate files]], but considering more than one HDF5 file as containing data to be interpolated to the new grid and a priority scale. The interpolation is performed only for the data located in the time window specified by the user. The present version of this action operates only on 2D data.&lt;br /&gt;
&lt;br /&gt;
Each HDF5 file containing data to be interpolated is called a '''father file''' and has an user-attributed '''priority level''' to be respected in the interpolation process: for each new grid cell the ConvertToHDF5 application will look for data first on the Level 1 father file and only in the case this data is inexistent will it look for data in Level 2 file, proceeding in looking for higher level files if no data is found subsequentely.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
To obtain an HDF5 file with data from several HDF5 files each containing data with different spatial resolution and only for a specific part of the new grid. This is, for instance, the case when one is preparing a best resolution meteorological HDF5 file for forcing MOHID Water from several meteorological model domains, having different spatial resolution and span, since the best resolution data is not available for all new grid cells.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
The new horizontal data grid, in a grid data file in the format supported by MOHID, and for each father file:&lt;br /&gt;
&lt;br /&gt;
- level of priority: 1 = maximum priority, priority decreases with increasing level value;&lt;br /&gt;
&lt;br /&gt;
- data grid, in the form of a grid data file in the format supported by MOHID.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with patched data.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#PATCH HDF5 FILES|PATCH HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Format conversion==&lt;br /&gt;
&lt;br /&gt;
===Meteorological model data===&lt;br /&gt;
Mohid does not simulate explicitly the atmosphere, but needs information about atmospheric properties in time and space. This requires that atmospheric properties are supplied to MOHID Water in supported formats. These formats can be derived from meteorological data in HDF5 format. Because the results of meteorological models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the MM5 and the ERA40. These are succintly detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''ERA40''====&lt;br /&gt;
This format refers to the European Centre for Medium-Range Weather Forecasts (ECMWF) 40 years re-analysises results, acessed by site http://data.ecmwf.int/data/d/era40_daily/. This data is available for several meteorological variables with maximum 6 hour periodicity for days in the period from 1957-09-01 to 2002-08-31. &lt;br /&gt;
&lt;br /&gt;
ERA40 data files are supplied by ECMWF in a NetCDF format and with an user-costumized time window, periodicity (time step range from 6 hours to a day) and meteorological properties set. The ERA40 meteorological properties which are recognized by MOHID are presented bellow together with the correspondent MOHID name: &lt;br /&gt;
&lt;br /&gt;
 ---ERA40 NAME---         ---MOHID NAME---&lt;br /&gt;
   sshf                     sensible heat                &lt;br /&gt;
   slhf                     latent heat                  &lt;br /&gt;
   msl                      atmospheric pressure &lt;br /&gt;
   tcc                      cloud cover &lt;br /&gt;
   p10u                     wind velocity X&lt;br /&gt;
   p10v                     wind velocity Y&lt;br /&gt;
   p2t                      air temperature&lt;br /&gt;
   ewss                     wind stress X&lt;br /&gt;
   nsss                     wind stress Y&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to all MOHID Water recognized property available in the ERA40 file, producing an individual HDF5 file for each property. The name of each HDF5 file generated includes the ERA40 meteorological property identificator correspondent to the data contained.&lt;br /&gt;
&lt;br /&gt;
Alternatively, ConvertToHDF5 can copy to a single ASCII file the heading information concerning each meteorological variable considered in the original ERA40 file.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data suitable for being used for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ERA40 NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file for each meteorological property contained in the original NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ERA40 FORMAT|CONVERT ERA40 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Aladin''====&lt;br /&gt;
This format relates to Aladin meteorological model results. Some of the atmospheric property needed by MOHID Water is present in Aladin output files, enabling to run prediction simulations with MOHID Water when access to Aladin prevision files is available.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts Aladin results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Aladin netcdf results file to convert.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with Aladin results and a grid data file in MOHID format with the Aladin grid pseudo-information: a fake orography is created of 100 m depth.&lt;br /&gt;
This last file can be used to interpolate the Aladin data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ALADIN FORMAT|CONVERT ALADIN FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MM5''====&lt;br /&gt;
This format relates to the Fifth-Generation NCAR / Penn State Mesoscale Model (MM5) output files format. Almost every atmospheric property needed by MOHID Water is present in MM5 output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts MM5 results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the MM5 files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
For conversion to be completed it is required the horizontal grid information of MM5 results which is available in special TERRAIN files.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
MM5 results file to convert and MM5 TERRAIN file. The TERRAIN file supplies the MM5 results grid information. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
A HDF5 file with MM5 results and a grid data file in MOHID format with the MM5 grid information.&lt;br /&gt;
This last file can be used to interpolate the MM5 data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MM5 FORMAT|CONVERT MM5 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''WRF''====&lt;br /&gt;
This format relates to the Weather Research and Forecast model (WRF) output files format. Almost every atmospheric property needed by MOHID Water is present in WRF output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts WRF results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the WRF properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the WRF files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
WRF direct output file.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with WRF results and a grid data file in MOHID format with the WRF grid information.&lt;br /&gt;
This last file can be used to interpolate the WRF data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! [[PROJ4 | PROJ4]] library is needed! See [[#Compile_ModuleWRFFormat |  Compile_ModuleWRFFormat]]&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT WRF FORMAT|CONVERT WRF FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Wave model data===&lt;br /&gt;
Mohid does not simulate explicitly the wave dynamics, but needs information about wave properties in time and space. This requires that wave properties are supplied to MOHID Water in supported formats. These formats can be derived from wave data in HDF5 format. Because the results of wave models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the table format of SWAN. This is succintly detailed in the next section.&lt;br /&gt;
&lt;br /&gt;
====''SWAN''====&lt;br /&gt;
SWAN data files are supplied in a ASCII format. The data is organized by time instant. For each time instant there is a table of data. Each column represents one property. &lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to gradients of wave stresses X and Y, mean amplitude, mean period and mean direction.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 SWAN data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ASCII (table type) SWAN results data files and bathymetry in MOHID grid data foramt. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (wave stresses X and Y, mean amplitude, mean period and mean direction). &lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT TO AND FROM SWAN|CONVERT TO AND FROM SWAN]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Ocean model data===&lt;br /&gt;
Ocean model data, available in diverse formats, can be used by MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation. These uses require that the model data is in HDF5 format and conversion is therefore needed.&lt;br /&gt;
&lt;br /&gt;
Currently the large scale ocean models formats convertible into HDF5 by ConvertToHDF5 includes MERCATOR.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MERCATOR''====&lt;br /&gt;
MERCATOR data files are supplied in a NetCDF format and with an user-costumized spatial window and periodicity. Water level and water properties (temperature and salinity) data is available in type T files, velocity component u data is available in type U files and velocity component v data is available in type V files. The type of data of a specific MERCATOR file is generally indicated in the file name.&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to temperature, salinity, water level, component u of velocity and component v of velocity.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 MERCATOR data usable for forcing or validation of MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
NetCDF MERCATOR results data files and NetCDF MERCATOR grid data files. It should be provided one grid data file of each type: T, U and V. These are generally provided by the MERCATOR services together with the results files.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (temperature, salinity, water level, velocity u and velocity v) and the correspondent grid data and geometry files, containing respectively the horizontal grid and the vertical discretization of the HDF5 file. The grid data and geometry files can be used afterwards to interpolate the MERCATOR data to another grid and geometry (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MERCATOR FORMAT|CONVERT MERCATOR FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Climatological data===&lt;br /&gt;
Climatological data can be used in MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation, in case more realistic data (measurements or model) data is unavailable. This data is generally supplied by producers in formats not readly usable by MOHID Water which justifies the existence of a conversion tool.&lt;br /&gt;
&lt;br /&gt;
Two climatological data format conversions are implemented in ConvertToHDF5: Levitus ocean data and Hellerman Rosenstein meteorological data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''Levitus''====&lt;br /&gt;
The Levitus climatology provides results for water temperature and salinity.&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window requested by the user. &lt;br /&gt;
Typically, it requires 3 steps to complete the task:&lt;br /&gt;
&lt;br /&gt;
- convert levitus format &lt;br /&gt;
&lt;br /&gt;
- extrapolate the data to the whole levitus domain(required to avoid uncoincidental coastlines) &lt;br /&gt;
&lt;br /&gt;
- interpolate with the model grid(bathymetry)&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as boundary forcing and/or initial condition specification in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Levitus climatological data files, one per property and per time period (e.g a month).&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Levitus climatological data, grid data file with the horizontal&lt;br /&gt;
grid of the data and a geometry file with vertical discretization of the data (MOHID formats).&lt;br /&gt;
The grid data and the geometry files can be used to interpolate the climatological data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT LEVITUS FORMAT|CONVERT LEVITUS FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Hellerman Rosenstein''====&lt;br /&gt;
This is a meteorological climatology providing wind stress. There is a file per wind stress component. Since the data refer to surface values it is a 2D field.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window provided by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as meteorological forcing in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Hellerman Rosenstein climatological data ASCII files, one per wind stress component.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Hellerman Rosenstein climatological data and grid data file with the horizontal&lt;br /&gt;
grid of the climatological data. This grid data file can be used to interpolate the climatological data from the original horizontal grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT HELLERMAN ROSENSTEIN ASCII|CONVERT HELLERMAN ROSENSTEIN ASCII]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''World Ocean Atlas 2005''====&lt;br /&gt;
The World Ocean Atlas (WOA) 2005 climatology provides results for water temperature, salinity and several water quality and biology properties.&lt;br /&gt;
&lt;br /&gt;
Description, Action and Input Files are described in a separate page: [[ConvertToHDF5 WOA2005]].&lt;br /&gt;
&lt;br /&gt;
===Generic NETCDF CF FILES===&lt;br /&gt;
&lt;br /&gt;
Converts any netcdf file following the CF convention into Mohid HDF5 files. Check the [[ConvertToHDF5#CONVERT_GENERIC_NETCDF_CF | Input File]] and [[ConvertToHDF5#Convert_generic_Netcdf_CF_to_MOHID.28.hdf5.29 | Sample File]].&lt;br /&gt;
&lt;br /&gt;
===Radar data===&lt;br /&gt;
====Seasonde RADAR Data====&lt;br /&gt;
Converts a list of ascii files from the Seasonde radar data, which measures currents over a given region of space, into an hdf5 file with the MOHID format. Useful to validate coastal and estuarine models where radars are located.&lt;br /&gt;
&lt;br /&gt;
==Input file (ConvertToHDF5Action.dat)==&lt;br /&gt;
===General structure===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt; (block containing instructions for running a specific action) &lt;br /&gt;
 ACTION                    : ... (intended action)&lt;br /&gt;
 ... (action specific instructions)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : ...&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GLUES HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 3D_FILE                   : 0/1 (0 = 2D file, 1 = 3D file)&lt;br /&gt;
 &lt;br /&gt;
 TIME_GROUP                : ... (Default=&amp;quot;Time&amp;quot;. Other option: &amp;quot;SurfaceTime&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (Default=&amp;quot;Results&amp;quot;. Other options: &amp;quot;Residual&amp;quot;, &amp;quot;SurfaceResults&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 &lt;br /&gt;
 (block of HDF5 data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of HDF5 file with data to be included in glue, one per line, at least two files)&lt;br /&gt;
 ...                      &lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===INTERPOLATE GRIDS===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of horizontal interpolation: 1 = Bilinear, 2 = Spline2D,&lt;br /&gt;
                                  3 = Triangulation)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION_WINDOW      : ... ... ... ... (2D spatial window to consider for interpolation: &lt;br /&gt;
                                              Xmin Ymin Xmax Ymax; default = all domain)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D           : 0/1 (0 = 2D interpolation, 1 = 3D interpolation)&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_2D            : 0/1/2/3/4/5 (2D extrapolation: 0=no extrapolation, 1=medium&lt;br /&gt;
                                      triangulation, 2=high triangulation, &lt;br /&gt;
                                      3=nearest neighbour, 4=nearest cell, &lt;br /&gt;
                                      5=constant value)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_VALUE         : ... (name of the value to extrapolate to when EXTRAPOLATE_2D is&lt;br /&gt;
                                  set to constant value (5))&lt;br /&gt;
 &lt;br /&gt;
 DO_NOT_BELIEVE_MAP        : 0/1 (0=consider input HDF5 file map, 1=do not consider input HDF5&lt;br /&gt;
                                  file map)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (name of base group of HDF5 variables containing data to be &lt;br /&gt;
                                  interpolated; default is &amp;quot;/Results&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (if INTERPOLATION3D : 1 also required:)&lt;br /&gt;
 FATHER_GEOMETRY           : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  of input HDF5 file)&lt;br /&gt;
 NEW_GEOMETRY              : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  intended for output HDF5 file)&lt;br /&gt;
 POLI_DEGREE               : 1/... (degree of vertical interpolation: 1=linear, ...)&lt;br /&gt;
 &lt;br /&gt;
 AUX_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for auxiliar output HDF5 file;&lt;br /&gt;
                                  default is file provided in NEW_GRID_FILENAME)&lt;br /&gt;
 &lt;br /&gt;
 AUX_OUTPUTFILENAME        : ... (path/name of auxiliar output HDF5 file to contain result&lt;br /&gt;
                                  of horizontal grid interpolation)   &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the file indicated in AUX_GRID_FILENAME can be different from the one indicated in&lt;br /&gt;
   NEW_GRID_FILENAME in terms of bathymetry, while the horizontal grid should be, commonly, the&lt;br /&gt;
   same: this altered bathymetry can be used to extend the water column in the original data so&lt;br /&gt;
   that the process of vertical interpolation is done easily;&lt;br /&gt;
 &lt;br /&gt;
 - in case of INTERPOLATION3D : 1, ConvertToHDF5 can generate new versions of bathymetry which &lt;br /&gt;
   are consistent with the geometry definition (extension is '.new'); there are possibly three&lt;br /&gt;
   bathymetry changes referring to father grid, new grid and aux grid (the same bathymetry is&lt;br /&gt;
   not altered twice); although initially new and aux grid are the same they can result &lt;br /&gt;
   different because of bathymetry changes;&lt;br /&gt;
 &lt;br /&gt;
 - in case the new geometry is 2D and father geometry is 3D then POLI_DEGREE : 1 &lt;br /&gt;
   (linear interpolation) should be used;&lt;br /&gt;
 &lt;br /&gt;
 - EXTRAPOLATE_2D : 1/2/3/4/5 should be considered if it is expected that the coast line is not&lt;br /&gt;
   coincidental in the father and new grids, to avoid lack of data in the interpolation&lt;br /&gt;
   process; extrapolation is performed for all cells even the land cells; &lt;br /&gt;
 &lt;br /&gt;
 - in case of DO_NOT_BELIEVE_MAP : 1 the application generates a map based on cells where&lt;br /&gt;
   interpolation results are available; this causes that if EXTRAPOLATE_2D : 1/2/3/4/5 is used&lt;br /&gt;
   the AUX_GRID_FILENAME should not have land cells in order for the new map to be concurrent&lt;br /&gt;
   with the result of extrapolation and avoid errors generation, specially if INTERPOLATION3D :&lt;br /&gt;
   1 is considered.&lt;br /&gt;
&lt;br /&gt;
===PATCH HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of interpolation: 3 = Triangulation, default and only&lt;br /&gt;
                                  one implemented)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 (block for each father HDF5 file, should be at least two)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                     : ... (integer priority level: 1 = highest, increase for lower&lt;br /&gt;
                                  priority)&lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 N_REMOVE_FRAME            : 0   (width, in number of cells, of frame to remove)&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT ERA40 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of ERA40 NetCDF file)&lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
                                 (root of name for all files produced)&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII          : 0/1 (1 = convert variable heading info for ASCII file; 0 = default)&lt;br /&gt;
 CONVERT_TO_HDF5           : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 GRIDTO180                 : 0/1 (1 = convert grid from [0 360] to [-180 180], 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 YY_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 TIME_VARIABLE             : ... (name of time variable in the input file: usual name is&lt;br /&gt;
                                  &amp;quot;time&amp;quot;)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - either CONVERT_TO_ASCII : 1 or CONVERT_TO_HDF5 : 1 must be chosen for any action to be&lt;br /&gt;
 performed by ConvertToHDF5;&lt;br /&gt;
 &lt;br /&gt;
 - when CONVERT_TO_HDF5 : 1 an HDF5 file is produced for every variable contained in the&lt;br /&gt;
 original ERA40 file; the name of each file is composed of the name indicated on FILENAME&lt;br /&gt;
 concatenated with the ERA40 variable identifier;&lt;br /&gt;
 &lt;br /&gt;
 - to the XX_VARIABLE, YY_VARIABLE and TIME_VARIABLE keywords should generally be  &lt;br /&gt;
 specified &amp;quot;longitude&amp;quot;, &amp;quot;latitude&amp;quot; and &amp;quot;time&amp;quot;, respectively; the option to&lt;br /&gt;
 include as keywords was made only to make the application robust to future variable name&lt;br /&gt;
 changes.&lt;br /&gt;
&lt;br /&gt;
===CONVERT ALADIN FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 (path to aladin netcdf file)\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each Aladin property to convert in &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;...&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt; block must conform to the following variables&lt;br /&gt;
 &lt;br /&gt;
           ---ALADIN NAME---    ---MOHID NAME---&lt;br /&gt;
             soclotot            CloudCover_&lt;br /&gt;
             sohumrel            RelativeHumidity_&lt;br /&gt;
             sofluxir            NonSolarFlux_&lt;br /&gt;
             sosspres            AtmosphericPressure_&lt;br /&gt;
             sosolarf            SolarRadiation_&lt;br /&gt;
             sotemair            AirTemperature_&lt;br /&gt;
             sowinmod            WindModulus_&lt;br /&gt;
             sowaprec            Precipitation_&lt;br /&gt;
             sozotaux            WindStressX_&lt;br /&gt;
             sometauy            WindStressY_&lt;br /&gt;
             sowindu10           WindVelocityX_&lt;br /&gt;
             sowindv10           WindVelocityY_&lt;br /&gt;
&lt;br /&gt;
===CONVERT MM5 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MM5 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of MM5 file)&lt;br /&gt;
 TERRAIN_FILENAME          : ... (path/name of MM5 TERRAIN file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of MM5 data to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP                 : 0/1 (1 = compute and write mean sea level pressure field; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of MM5 properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of MM5 property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each MM5 property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must&lt;br /&gt;
 conform to the MOHID designation specified in code of ModuleGlobalData; the correspondence is &lt;br /&gt;
 the following (see [[Module_InterfaceWaterAir]] for a more detailed explanation).&lt;br /&gt;
 &lt;br /&gt;
           ---MM5 NAME---    ---MOHID NAME---&lt;br /&gt;
             T2             air temperature&lt;br /&gt;
             PSTARCRS       atmospheric pressure&lt;br /&gt;
             U10            wind velocity X&lt;br /&gt;
             V10            wind velocity Y&lt;br /&gt;
             UST            wind shear velocity&lt;br /&gt;
             LHFLUX         latent heat&lt;br /&gt;
             SWDOWN         sensible heat&lt;br /&gt;
             SWDOWN         solar radiation&lt;br /&gt;
             LWDOWN         infrared radiation&lt;br /&gt;
             SWOUT          top outgoing shortwave radiation&lt;br /&gt;
             LWOUT          top outgoing longwave radiation&lt;br /&gt;
             SOIL T 1       soil temperature layer 1&lt;br /&gt;
             SOIL T 1       soil temperature layer 2&lt;br /&gt;
             SOIL T 1       soil temperature layer 3&lt;br /&gt;
             SOIL T 1       soil temperature layer 4&lt;br /&gt;
             SOIL T 1       soil temperature layer 5&lt;br /&gt;
             SOIL T 1       soil temperature layer 6&lt;br /&gt;
             Q2             2-meter mixing ratio&lt;br /&gt;
             TSEASFC        sea water temperature&lt;br /&gt;
             PBL HGT        PBL height&lt;br /&gt;
             PBL REGIME     PBL regime&lt;br /&gt;
             RAIN CON       accumulated convective precipitation        (cm)&lt;br /&gt;
             RAIN NON       accumulated non-convective precipitation    (cm)&lt;br /&gt;
             GROUND T       ground temperature&lt;br /&gt;
             RES TEMP       infinite reservoir slab temperature&lt;br /&gt;
             U              wind velocity X_3D&lt;br /&gt;
             V              wind velocity Y_3D&lt;br /&gt;
             W              wind velocity Z_3D&lt;br /&gt;
             T              air temperature_3D&lt;br /&gt;
             PP             atmospheric pressure_3D&lt;br /&gt;
             Q              mixing ratio_3D&lt;br /&gt;
             CLW            cloud water mixing ratio_3D&lt;br /&gt;
             RNW            rain water mixing ratio_3D&lt;br /&gt;
             ICE            cloud ice mixing ratio_3D&lt;br /&gt;
             SNOW           snow mixing ratio_3D&lt;br /&gt;
             RAD TEND       atmospheric radiation tendency_3D&lt;br /&gt;
&lt;br /&gt;
===CONVERT WRF FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                       : CONVERT WRF FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                     : ... (path/name of WRF file)&lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of WRF data&lt;br /&gt;
                                     to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP_MM5             : 0/1 (1 = compute mean sea level pressure with MM5toGrads algorithm; 1 = default)&lt;br /&gt;
 COMPUTE_MSLP_WRF             : 0/1 (1 = compute mean sea level pressure with ARWPost algorithm; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 OUTPUT_DT                    : real (DT interval in seconds between each output; default = 0.0)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
  &lt;br /&gt;
 - the name of each property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must conform to the MOHID &lt;br /&gt;
   designation specified in code of ModuleGlobalData; the correspondence to WRF is in function &lt;br /&gt;
   VariableIsToRead in ModuleWRFFormat. Conversion is not direct since WRF outputs tendencies and not  &lt;br /&gt;
   total values. &lt;br /&gt;
 &lt;br /&gt;
 - Caution: This action is not extensively tested.&lt;br /&gt;
&lt;br /&gt;
===CONVERT MERCATOR FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION               : 1/2/3/4 (version of MERCATOR files)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 1:)&lt;br /&gt;
 BASE_BULLETIN             : ...&lt;br /&gt;
 DATES_FILE                : ...&lt;br /&gt;
 NUM_DATES                 : ... &lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 2/3:)&lt;br /&gt;
 INPUT_GRID_FILENAME       : ... (path/name of file with horizontal discretization of water&lt;br /&gt;
                                  properties and water level data)&lt;br /&gt;
 (if READ_OPTION : 2:)&lt;br /&gt;
 INPUT_GRID_FILENAME_U     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component U data)&lt;br /&gt;
 INPUT_GRID_FILENAME_V     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component V data)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 3:)&lt;br /&gt;
 INPUT_BATHY_FILENAME      : ... (path/name of file with bathymetry)&lt;br /&gt;
     &lt;br /&gt;
 (if READ_OPTION : 3/4:)&lt;br /&gt;
 CALC_BAROTROPIC_VEL       : 0/1 (1 = calculate barotropic velocity, 0 = not calculate; &lt;br /&gt;
                                  default = 0)&lt;br /&gt;
 &lt;br /&gt;
 (if CALC_BAROTROPIC_VEL : 1 and READ_OPTION : 3:)&lt;br /&gt;
 INPUT_MESH_ZGRID_FILENAME : ... (path/name of file with information about layers ticknesses)&lt;br /&gt;
 &lt;br /&gt;
 (block of MERCATOR data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of MERCATOR NetCDF data file, one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT LEVITUS FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT LEVITUS FORMAT&lt;br /&gt;
  &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Levitus data: &amp;quot;monthly&amp;quot;/&amp;quot;annual&amp;quot;; default is&lt;br /&gt;
                                  &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Levitus grid)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
 &lt;br /&gt;
 (block for each water property to be present in output HDF5 file, can be several)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property)&lt;br /&gt;
 ANNUAL_FILE               : ... (path/name of Levitus annual file)&lt;br /&gt;
 &lt;br /&gt;
 (block of Levitus data files)&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of Levitus data file (e.g. a monthly data file), one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT HELLERMAN ROSENSTEIN ASCII===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
  &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Hellerman Rosenstein data: &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Hellerman&lt;br /&gt;
                                  Rosenstein grid: default and only allowed value is &amp;quot;2.&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
   &lt;br /&gt;
 (block for each Hellerman Rosenstein data file)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property: &amp;quot;wind stress X&amp;quot;/&amp;quot;wind stress Y&amp;quot;)&lt;br /&gt;
 FILE                      : ... (path/name Hellerman Rosenstein file)&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CONVERT GENERIC NETCDF CF===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION              : CONVERT NETCDF CF TO HDF5 MOHID       &lt;br /&gt;
 HDF5_OUT            : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 OUTPUTFILENAME      : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)&lt;br /&gt;
 OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property for time, generally &amp;quot;time&amp;quot;&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT     : ... (name of the netcdf property for latitude, generally &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_LONG    : ... (name of the netcdf property for longitude, generally &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_MAPPING : ... (name of the netcdf field where is located the mapping 0 water 1 land)&lt;br /&gt;
                           (It can also be used any field, i.e. temperature)&lt;br /&gt;
 MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus &amp;gt;0.5 water)&lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER   : real (number of netcdf properties) &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property&lt;br /&gt;
 NAME                : name of the HDF5 Mohid property&lt;br /&gt;
 UNITS               : property units&lt;br /&gt;
 DESCRIPTION         : property description&lt;br /&gt;
 DIM                 : 2/3 Number of property dimensions &lt;br /&gt;
 VECTOR_INTENSITY    : 0/1 If property corresponds to a vector intensity&lt;br /&gt;
 VECTOR_X            : Decomposition of Vector Intensity X&lt;br /&gt;
 VECTOR_Y            : Decomposition of Vector Intensity Y&lt;br /&gt;
 BEAUFORT_SCALE      : 0/1 If property correspond to the beaufort scale&lt;br /&gt;
 ADD_FACTOR          : To add the property a fixed value&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 path to netcdf cf file&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT SEASONDE RADAR FORMAT ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 !HDF5 path and filename that will contain the results&lt;br /&gt;
 OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
 &lt;br /&gt;
 !griddata path and filename that will contain a griddata of the proxy bathymetry used in the hdf5 output file.&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Path and filename to the grid that maps the radar data. This grid must be constructed with the [[GIS]]&lt;br /&gt;
 !or MOHID Studio and must &amp;quot;fit&amp;quot; well where the points stand.&lt;br /&gt;
 INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
 &lt;br /&gt;
 !This is the version of the grid used by the seasonde radar system.&lt;br /&gt;
 !If the grid version of the seasonde radar changes, then most likely a new input grid must be&lt;br /&gt;
 !constructed with the GIS or MOHID Studio.&lt;br /&gt;
 IH_GRID_VERSION           : 4&lt;br /&gt;
 &lt;br /&gt;
 !This is a list with the Seasonde radar ascii data files. One file per instant.&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Samples==&lt;br /&gt;
All sample files are named ''ConvertToHDF5Action.dat''.&lt;br /&gt;
&lt;br /&gt;
===Glue several MOHID(.hdf5) files===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : SurfaceHydro_OP.hdf5&lt;br /&gt;
  &lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_21.hdf5&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_22.hdf5&lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 2D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME           : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
  &lt;br /&gt;
 START                    : 2006 6 21 17 22 30&lt;br /&gt;
 END                      : 2006 6 22 17 22 0&lt;br /&gt;
  &lt;br /&gt;
 FATHER_GRID_FILENAME     : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME        : TagusConstSpacing.dat&lt;br /&gt;
  &lt;br /&gt;
 BASE_GROUP               : /Results/Oil/Data_2D&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 3D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 1&lt;br /&gt;
 FATHER_FILENAME         : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME          : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2006 6 21 17 22 30&lt;br /&gt;
 END                     : 2006 6 22 17 22 0&lt;br /&gt;
 &lt;br /&gt;
 FATHER_GRID_FILENAME    : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP              : /Results/Oil/Data_2D&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D         : 1&lt;br /&gt;
 FATHER_GEOMETRY         : D:\Projectos\MohidRun\test\data\Geometry_1.dat&lt;br /&gt;
 NEW_GEOMETRY            : TagusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME      : Aux_GridRegular.hdf5&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Patch several MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 3&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2005 2 28 13 0 0&lt;br /&gt;
 END                     : 2005 3 1 13 0 0&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 3&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D1.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid1.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 2&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D2.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid2.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 1&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D3.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid3.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME          : MM5Forcing.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME       : K:\Simula\GeneralData\Batim\CostaPortuguesa.dat&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert an ERA40 file to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                  : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                : D:\Aplica\ERA40\1971ERA1973.nc&lt;br /&gt;
 OUTPUTFILENAME          : D:\Aplica\ERA40\1971ERA1973T2&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII        : 0&lt;br /&gt;
 CONVERT_TO_HDF5         : 1&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE             : longitude&lt;br /&gt;
 YY_VARIABLE             : latitude&lt;br /&gt;
 TIME_VARIABLE           : time&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a MM5 file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : MMOUT_DOMAIN2&lt;br /&gt;
 TERRAIN_FILENAME          : TERRAIN_DOMAIN2&lt;br /&gt;
 OUTPUTFILENAME            : D2.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : D2.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 !START                     : 2010 02 15 00 00 00&lt;br /&gt;
 !END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a WRF file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : wrfout_d01_2010-02-15_00.nc&lt;br /&gt;
 OUTPUTFILENAME            : wrfout_d01.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : wrfout_d01.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 START                     : 2010 02 15 00 00 00&lt;br /&gt;
 END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Mercator-Ocean(.nc) to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION              : 2&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Psy2v2r1v_R20060628/MercatorR20060628.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : Psy2v2r1v_R20060628/MercatorGridR20060628.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : Psy2v2r1v_R20060628/MercatorGeometryR20060628.dat&lt;br /&gt;
 &lt;br /&gt;
 INPUT_GRID_FILENAME      : GridFiles/ist_meteog-gridT.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_U    : GridFiles/ist_meteog-gridU.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_V    : GridFiles/ist_meteog-gridV.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060621_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060622_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060623_R20060628.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Levitus format to MOHID(.hdf5) and interpolate grid===&lt;br /&gt;
==== Convert ====&lt;br /&gt;
First convert the Levitus ASCII format to a raw HDF5 format:&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT LEVITUS FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Levitus.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : LevitusGeometry.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 0.25&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -16.0  31&lt;br /&gt;
 UPPER_RIGHT_CORNER       :   1.   40&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : salinity&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : temperature&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Temp\t000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Extrapolate ====&lt;br /&gt;
Then extrapolate the data (still in the raw HDF5 format):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME          : Levitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : LevitusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxLeviTusAllPointsWithData.hdf5&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 EXTRAPOLATE_2D           : 2&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Interpolate ====&lt;br /&gt;
Finally, interpolate to the final grid and geometry (same as the [[#Interpolate 3D MOHID(.hdf5) files to a new grid| Interpolate 3D sample]]):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 OUTPUTFILENAME           : CadizMonthlyLevitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 NEW_GRID_FILENAME        : Algarve0.02SigmaSmooth_V3_CartMoreLayers.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : Geometry_1.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxCadizMonthlyLevitus.hdf5&lt;br /&gt;
 AUX_GRID_FILENAME        : Aux12km.dat&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the programme may construct a new bathymetry twice. Use this bathymetry only on the AUX_GRID_FILENAME keyword.&lt;br /&gt;
&lt;br /&gt;
===Convert Hellerman Rosenstein ASCII format to MOHID(.hdf5)  ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : ClimatologicWindStress.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : ClimatologicWindStressGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 2.&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -180  -90&lt;br /&gt;
 UPPER_RIGHT_CORNER       : 180  90&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress X&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUXX.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress Y&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUYY.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert ALADIN(.nc) format to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKPRES_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKSOLAR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKTAIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKWIND_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_FLUXPRE_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSU_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSV_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_U10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_V10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKHUMI_OPASYMP_19723_20088.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Convert generic Netcdf CF to MOHID(.hdf5)  ===&lt;br /&gt;
&lt;br /&gt;
This sample is for converting a typical GFS file&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION : CONVERT NETCDF CF TO HDF5 MOHID&lt;br /&gt;
 HDF5_OUT : 1&lt;br /&gt;
 OUTPUTFILENAME : ..\..\data\hdf5\GFS.hdf5&lt;br /&gt;
 NETCDF_OUT : 1&lt;br /&gt;
 OUTPUT_NETCDF_FILE : ..\..\data\netcdf\GFS.nc&lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : time&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT : latitude&lt;br /&gt;
 NETCDF_NAME_LONG : longitude&lt;br /&gt;
 NETCDF_NAME_MAPPING : TMP_10mb&lt;br /&gt;
 MAPPING_LIMIT : -10000&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER : 6 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : PRMSL_meansealevel&lt;br /&gt;
 NAME : atmospheric pressure&lt;br /&gt;
 UNITS : Pa&lt;br /&gt;
 DESCRIPTION : GFS&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : UGRD_10mb&lt;br /&gt;
 NAME : wind velocity X&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : VGRD_10mb&lt;br /&gt;
 NAME : wind velocity Y&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus&lt;br /&gt;
 NAME                     : wind modulus &lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 VECTOR_INTENSITY         : 1&lt;br /&gt;
 VECTOR_X                 : wind velocity X&lt;br /&gt;
 VECTOR_Y                 : wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus_beaufort &lt;br /&gt;
 NAME                     : wind modulus beaufort &lt;br /&gt;
 UNITS : beaufort scale&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 BEAUFORT_SCALE           : 1&lt;br /&gt;
 VECTOR_X                 : wind modulus&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : TMP_2maboveground&lt;br /&gt;
 NAME : air temperature&lt;br /&gt;
 UNITS : oC&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 ADD_FACTOR  : -273&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ..\..\data\netcdf\gfs_4_20111115.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
=== Convert Seasonde RADAR data sample configuration file===&lt;br /&gt;
The input grid file must be created to be the recipient of the data in the ascii files.&lt;br /&gt;
To create this grid, it is recommended to convert manually, resorting to a good text editor, such as Notepad++, a few radar ascii files into the [[xyz]] Mohid format, then load them in the [[GIS]] or [[Mohid Studio]], and from there create and save a regular grid that fits the points. Use that grid to convert the data into one hdf5 file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;begin_file&amp;gt;&lt;br /&gt;
ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
&lt;br /&gt;
OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
IH_GRID_VERSION           : 4&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_30_1400.tuv.txt&lt;br /&gt;
&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
&amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OceanColor modules compilation ==&lt;br /&gt;
Compiling the [[ConvertToHDF5]] tool with the OceanColor modules is more complicated than one might expect. A solution is proposed here for a release version using the Compaq Visual Fortran 6.6c. The difficulties rise because C code is embedded with a fortran interface and also, extra libraries such as hdf4 are required.&lt;br /&gt;
&lt;br /&gt;
=== Pre-requisites ===&lt;br /&gt;
&lt;br /&gt;
This is a list of prerequisites to successfully compile the tool:&lt;br /&gt;
*Compaq Visual Fortran 6.5 with patch 6.6c,&lt;br /&gt;
*VS .NET 2003 (Vc7 in particular),&lt;br /&gt;
*Hdf5 libraries ('''hdf5.lib''' '''hdf5_fortran.lib''' '''hdf5_hl.lib'''),&lt;br /&gt;
*Netcdf libraries ('''netcdf.lib''' '''netcdf_.lib'''),&lt;br /&gt;
*Hdf4 libraries ('''hd421.lib''', '''hm421.lib'''),&lt;br /&gt;
*szlib, zlib and jpeg libraries ('''szlib.lib''', '''zlib.lib''' and '''libjpeg.lib'''),&lt;br /&gt;
*the fortran source files ('''ModuleConvertModisL2.F90 ModuleConvertModisL3.F90 ModuleConvertOceanColorL2.F90'''),&lt;br /&gt;
*the C source files and their fortran interface files ('''readL2scan.c readL2Seadas.c''' and '''cdata.f crossp.f fgeonav.f''').&lt;br /&gt;
&lt;br /&gt;
=== CVF IDE configuration ===&lt;br /&gt;
# Configure everything as specified in [[Compiling with CVF]].&lt;br /&gt;
# Add the source files listed in the prerequisites above to the source files listing.&lt;br /&gt;
# Go to '''Tools--&amp;gt;Options...--&amp;gt;Directories'''. There, add the '''$DOTNET2K3/Vc7/bin''' to the '''Executable files''''; the '''$DOTNET2K3/Vc7/include''' and '''$DOTNET2K3/Vc7/PlatformSDK/include''' to the '''Include files'''; and finally, the '''$DOTNET2K3/Vc7/lib''', '''$DOTNET2K3/Vc7/PlatformSDK/lib''' and  '''$DOTNET2K3/Vc7/PlatformSDK/bin''' to the '''Library files'''.&lt;br /&gt;
# Go to '''Projects--&amp;gt;Settings--&amp;gt;Release--&amp;gt;Link--&amp;gt;Input'''. There, add the following libraries: '''netcdf.lib netcdf_.lib hd421.lib hm421.lib libjpeg.lib'''. (Make sure the hdf5 libraries as well as the szlib and zlib libraries are already mentioned).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshoots ===&lt;br /&gt;
'''Q: I get unresolved external references during linkage, but I have all the libraries mentioned above included. What should I do?'''&lt;br /&gt;
&lt;br /&gt;
A: Unresolved external references can come out for two reasons:&lt;br /&gt;
#you didn't specified all the libraries required or all the paths for the default libraries or,&lt;br /&gt;
#[http://en.wikipedia.org/wiki/Name_decoration name mangling] problems. Use the [[dumpbin]] utility to the libraries to checkout which language convention they are using. If that's the problem then you need to try to get new libraries with the correct naming convention.&lt;br /&gt;
&lt;br /&gt;
That's it, you should now be able to build the [[ConvertToHdf5]] project successfully.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Q: I got a message saying the entry point _NF_PUT_ATT_REAL@28 could not be located in netcdf.dll'''&lt;br /&gt;
&lt;br /&gt;
A: copy the file netcdf.dll to the exe folder&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF5 Homepage]&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF4 Homepage]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
*[[Module_Atmosphere]]&lt;br /&gt;
*[[Module_InterfaceWaterAir]]&lt;br /&gt;
*[[Coupling_Water-Atmosphere_User_Manual]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Hdf5]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6290</id>
		<title>ConvertToHDF5</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6290"/>
				<updated>2012-06-05T15:36:20Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* CONVERT SEASONDE RADAR FORMAT */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''ConvertToHDF5''' is an application which allows the making of several operations, called '''actions''', involving HDF5 files: conversion of data in other formats (e.g. NETCDF) to HDF5, grid interpolation, concatenation of several files.&lt;br /&gt;
&lt;br /&gt;
Running options for this application are specified by the user in a input file named [[ConvertToHDF5#Input file (ConvertToHDF5Action.dat)|'''ConvertToHDF5Action.dat''']]. Several actions can be specified in the same input file, being processed sequentially by the ConvertToHDF5 application.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
The operations involving HDF5 files performed by ConvertToHDF5, specified individually by an action, can be organized in:&lt;br /&gt;
&lt;br /&gt;
* [[#file management|file management]]&lt;br /&gt;
* [[#grid interpolation|grid interpolation]] and &lt;br /&gt;
* [[#format conversion|format conversion]]. &lt;br /&gt;
&lt;br /&gt;
These types and the respective actions are detailed in the next sections. &lt;br /&gt;
&lt;br /&gt;
The input file specification for each action can be found bellow in the [[#Input file (ConvertToHDF5Action.dat)|Input file (ConvertToHDF5Action.dat)]] section.&lt;br /&gt;
&lt;br /&gt;
==File management==&lt;br /&gt;
&lt;br /&gt;
===Glue files===&lt;br /&gt;
This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 files to be glued. &amp;quot;Grid&amp;quot; and &amp;quot;Results&amp;quot; data groups should be equal in all these files.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with glued &amp;quot;Results&amp;quot; data. &amp;quot;Residual&amp;quot; and &amp;quot;Statistics&amp;quot; HDF5 data groups are not copied to the output file since they are time period specific (different values potentially occour in each file). General statistics can be calculated for the glued HDF5 file data using tool [[HDF5Statistics]].&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Grid interpolation==&lt;br /&gt;
&lt;br /&gt;
===Interpolate files===&lt;br /&gt;
This action performs the conversion of one HDF5 file data existing in one 2D or 3D spatial grid to another 2D or 3D spatial grid, creating a new HDF5 file. The interpolation is performed only for the data located a time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
The HDF5 file containing data to be interpolated is called the '''father file'''.&lt;br /&gt;
&lt;br /&gt;
In case of 3D interpolation the application conducts first the horizontal grid interpolation&lt;br /&gt;
(keeping father geometry) and only after it conducts the vertical interpolation (from father geometry to new geometry).&lt;br /&gt;
&lt;br /&gt;
Several types of 2D interpolation are available for use: bilinear, spline 2D and triangulation.&lt;br /&gt;
For vertical interpolation (used in 3D interpolation) can be supplied several polinomial degrees for interpolation.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data for forcing or providing initial conditions for a MOHID Water model, e.g. a meteorological forcing file.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
For 2D/3D interpolation:&lt;br /&gt;
&lt;br /&gt;
- father HDF5 file;&lt;br /&gt;
&lt;br /&gt;
- father horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
For 3D interpolation also needed:&lt;br /&gt;
&lt;br /&gt;
- father vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- auxiliary horizontal data grid, in a grid data file in the format supported by MOHID; this file is used for horizontal grid interpolation in 3D interpolation operations.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with interpolated data. In case of 3D interpolation also produced an auxiliary HDF5 file with the result of the horizontal grid interpolation, which can be inspected to check if this operation is well performed.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].&lt;br /&gt;
&lt;br /&gt;
===Patch files===&lt;br /&gt;
This action consists in performing an interpolation of HDF5 data between grids, as in action [[#Interpolate files|Interpolate files]], but considering more than one HDF5 file as containing data to be interpolated to the new grid and a priority scale. The interpolation is performed only for the data located in the time window specified by the user. The present version of this action operates only on 2D data.&lt;br /&gt;
&lt;br /&gt;
Each HDF5 file containing data to be interpolated is called a '''father file''' and has an user-attributed '''priority level''' to be respected in the interpolation process: for each new grid cell the ConvertToHDF5 application will look for data first on the Level 1 father file and only in the case this data is inexistent will it look for data in Level 2 file, proceeding in looking for higher level files if no data is found subsequentely.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
To obtain an HDF5 file with data from several HDF5 files each containing data with different spatial resolution and only for a specific part of the new grid. This is, for instance, the case when one is preparing a best resolution meteorological HDF5 file for forcing MOHID Water from several meteorological model domains, having different spatial resolution and span, since the best resolution data is not available for all new grid cells.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
The new horizontal data grid, in a grid data file in the format supported by MOHID, and for each father file:&lt;br /&gt;
&lt;br /&gt;
- level of priority: 1 = maximum priority, priority decreases with increasing level value;&lt;br /&gt;
&lt;br /&gt;
- data grid, in the form of a grid data file in the format supported by MOHID.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with patched data.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#PATCH HDF5 FILES|PATCH HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Format conversion==&lt;br /&gt;
&lt;br /&gt;
===Meteorological model data===&lt;br /&gt;
Mohid does not simulate explicitly the atmosphere, but needs information about atmospheric properties in time and space. This requires that atmospheric properties are supplied to MOHID Water in supported formats. These formats can be derived from meteorological data in HDF5 format. Because the results of meteorological models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the MM5 and the ERA40. These are succintly detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''ERA40''====&lt;br /&gt;
This format refers to the European Centre for Medium-Range Weather Forecasts (ECMWF) 40 years re-analysises results, acessed by site http://data.ecmwf.int/data/d/era40_daily/. This data is available for several meteorological variables with maximum 6 hour periodicity for days in the period from 1957-09-01 to 2002-08-31. &lt;br /&gt;
&lt;br /&gt;
ERA40 data files are supplied by ECMWF in a NetCDF format and with an user-costumized time window, periodicity (time step range from 6 hours to a day) and meteorological properties set. The ERA40 meteorological properties which are recognized by MOHID are presented bellow together with the correspondent MOHID name: &lt;br /&gt;
&lt;br /&gt;
 ---ERA40 NAME---         ---MOHID NAME---&lt;br /&gt;
   sshf                     sensible heat                &lt;br /&gt;
   slhf                     latent heat                  &lt;br /&gt;
   msl                      atmospheric pressure &lt;br /&gt;
   tcc                      cloud cover &lt;br /&gt;
   p10u                     wind velocity X&lt;br /&gt;
   p10v                     wind velocity Y&lt;br /&gt;
   p2t                      air temperature&lt;br /&gt;
   ewss                     wind stress X&lt;br /&gt;
   nsss                     wind stress Y&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to all MOHID Water recognized property available in the ERA40 file, producing an individual HDF5 file for each property. The name of each HDF5 file generated includes the ERA40 meteorological property identificator correspondent to the data contained.&lt;br /&gt;
&lt;br /&gt;
Alternatively, ConvertToHDF5 can copy to a single ASCII file the heading information concerning each meteorological variable considered in the original ERA40 file.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data suitable for being used for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ERA40 NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file for each meteorological property contained in the original NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ERA40 FORMAT|CONVERT ERA40 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Aladin''====&lt;br /&gt;
This format relates to Aladin meteorological model results. Some of the atmospheric property needed by MOHID Water is present in Aladin output files, enabling to run prediction simulations with MOHID Water when access to Aladin prevision files is available.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts Aladin results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Aladin netcdf results file to convert.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with Aladin results and a grid data file in MOHID format with the Aladin grid pseudo-information: a fake orography is created of 100 m depth.&lt;br /&gt;
This last file can be used to interpolate the Aladin data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ALADIN FORMAT|CONVERT ALADIN FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MM5''====&lt;br /&gt;
This format relates to the Fifth-Generation NCAR / Penn State Mesoscale Model (MM5) output files format. Almost every atmospheric property needed by MOHID Water is present in MM5 output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts MM5 results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the MM5 files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
For conversion to be completed it is required the horizontal grid information of MM5 results which is available in special TERRAIN files.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
MM5 results file to convert and MM5 TERRAIN file. The TERRAIN file supplies the MM5 results grid information. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
A HDF5 file with MM5 results and a grid data file in MOHID format with the MM5 grid information.&lt;br /&gt;
This last file can be used to interpolate the MM5 data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MM5 FORMAT|CONVERT MM5 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''WRF''====&lt;br /&gt;
This format relates to the Weather Research and Forecast model (WRF) output files format. Almost every atmospheric property needed by MOHID Water is present in WRF output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts WRF results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the WRF properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the WRF files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
WRF direct output file.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with WRF results and a grid data file in MOHID format with the WRF grid information.&lt;br /&gt;
This last file can be used to interpolate the WRF data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! [[PROJ4 | PROJ4]] library is needed! See [[#Compile_ModuleWRFFormat |  Compile_ModuleWRFFormat]]&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT WRF FORMAT|CONVERT WRF FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Wave model data===&lt;br /&gt;
Mohid does not simulate explicitly the wave dynamics, but needs information about wave properties in time and space. This requires that wave properties are supplied to MOHID Water in supported formats. These formats can be derived from wave data in HDF5 format. Because the results of wave models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the table format of SWAN. This is succintly detailed in the next section.&lt;br /&gt;
&lt;br /&gt;
====''SWAN''====&lt;br /&gt;
SWAN data files are supplied in a ASCII format. The data is organized by time instant. For each time instant there is a table of data. Each column represents one property. &lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to gradients of wave stresses X and Y, mean amplitude, mean period and mean direction.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 SWAN data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ASCII (table type) SWAN results data files and bathymetry in MOHID grid data foramt. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (wave stresses X and Y, mean amplitude, mean period and mean direction). &lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT TO AND FROM SWAN|CONVERT TO AND FROM SWAN]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Ocean model data===&lt;br /&gt;
Ocean model data, available in diverse formats, can be used by MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation. These uses require that the model data is in HDF5 format and conversion is therefore needed.&lt;br /&gt;
&lt;br /&gt;
Currently the large scale ocean models formats convertible into HDF5 by ConvertToHDF5 includes MERCATOR.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MERCATOR''====&lt;br /&gt;
MERCATOR data files are supplied in a NetCDF format and with an user-costumized spatial window and periodicity. Water level and water properties (temperature and salinity) data is available in type T files, velocity component u data is available in type U files and velocity component v data is available in type V files. The type of data of a specific MERCATOR file is generally indicated in the file name.&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to temperature, salinity, water level, component u of velocity and component v of velocity.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 MERCATOR data usable for forcing or validation of MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
NetCDF MERCATOR results data files and NetCDF MERCATOR grid data files. It should be provided one grid data file of each type: T, U and V. These are generally provided by the MERCATOR services together with the results files.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (temperature, salinity, water level, velocity u and velocity v) and the correspondent grid data and geometry files, containing respectively the horizontal grid and the vertical discretization of the HDF5 file. The grid data and geometry files can be used afterwards to interpolate the MERCATOR data to another grid and geometry (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MERCATOR FORMAT|CONVERT MERCATOR FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Climatological data===&lt;br /&gt;
Climatological data can be used in MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation, in case more realistic data (measurements or model) data is unavailable. This data is generally supplied by producers in formats not readly usable by MOHID Water which justifies the existence of a conversion tool.&lt;br /&gt;
&lt;br /&gt;
Two climatological data format conversions are implemented in ConvertToHDF5: Levitus ocean data and Hellerman Rosenstein meteorological data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''Levitus''====&lt;br /&gt;
The Levitus climatology provides results for water temperature and salinity.&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window requested by the user. &lt;br /&gt;
Typically, it requires 3 steps to complete the task:&lt;br /&gt;
&lt;br /&gt;
- convert levitus format &lt;br /&gt;
&lt;br /&gt;
- extrapolate the data to the whole levitus domain(required to avoid uncoincidental coastlines) &lt;br /&gt;
&lt;br /&gt;
- interpolate with the model grid(bathymetry)&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as boundary forcing and/or initial condition specification in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Levitus climatological data files, one per property and per time period (e.g a month).&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Levitus climatological data, grid data file with the horizontal&lt;br /&gt;
grid of the data and a geometry file with vertical discretization of the data (MOHID formats).&lt;br /&gt;
The grid data and the geometry files can be used to interpolate the climatological data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT LEVITUS FORMAT|CONVERT LEVITUS FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Hellerman Rosenstein''====&lt;br /&gt;
This is a meteorological climatology providing wind stress. There is a file per wind stress component. Since the data refer to surface values it is a 2D field.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window provided by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as meteorological forcing in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Hellerman Rosenstein climatological data ASCII files, one per wind stress component.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Hellerman Rosenstein climatological data and grid data file with the horizontal&lt;br /&gt;
grid of the climatological data. This grid data file can be used to interpolate the climatological data from the original horizontal grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT HELLERMAN ROSENSTEIN ASCII|CONVERT HELLERMAN ROSENSTEIN ASCII]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''World Ocean Atlas 2005''====&lt;br /&gt;
The World Ocean Atlas (WOA) 2005 climatology provides results for water temperature, salinity and several water quality and biology properties.&lt;br /&gt;
&lt;br /&gt;
Description, Action and Input Files are described in a separate page: [[ConvertToHDF5 WOA2005]].&lt;br /&gt;
&lt;br /&gt;
===Generic NETCDF CF FILES===&lt;br /&gt;
&lt;br /&gt;
Converts any netcdf file following the CF convention into Mohid HDF5 files. Check the [[ConvertToHDF5#CONVERT_GENERIC_NETCDF_CF | Input File]] and [[ConvertToHDF5#Convert_generic_Netcdf_CF_to_MOHID.28.hdf5.29 | Sample File]].&lt;br /&gt;
&lt;br /&gt;
===Radar data===&lt;br /&gt;
====Seasonde RADAR Data====&lt;br /&gt;
Converts a list of ascii files from the Seasonde radar data, which measures currents over a given region of space, into an hdf5 file with the MOHID format. Useful to validate coastal and estuarine models where radars are located.&lt;br /&gt;
&lt;br /&gt;
==Input file (ConvertToHDF5Action.dat)==&lt;br /&gt;
===General structure===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt; (block containing instructions for running a specific action) &lt;br /&gt;
 ACTION                    : ... (intended action)&lt;br /&gt;
 ... (action specific instructions)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : ...&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GLUES HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 3D_FILE                   : 0/1 (0 = 2D file, 1 = 3D file)&lt;br /&gt;
 &lt;br /&gt;
 TIME_GROUP                : ... (Default=&amp;quot;Time&amp;quot;. Other option: &amp;quot;SurfaceTime&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (Default=&amp;quot;Results&amp;quot;. Other options: &amp;quot;Residual&amp;quot;, &amp;quot;SurfaceResults&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 &lt;br /&gt;
 (block of HDF5 data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of HDF5 file with data to be included in glue, one per line, at least two files)&lt;br /&gt;
 ...                      &lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===INTERPOLATE GRIDS===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of horizontal interpolation: 1 = Bilinear, 2 = Spline2D,&lt;br /&gt;
                                  3 = Triangulation)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION_WINDOW      : ... ... ... ... (2D spatial window to consider for interpolation: &lt;br /&gt;
                                              Xmin Ymin Xmax Ymax; default = all domain)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D           : 0/1 (0 = 2D interpolation, 1 = 3D interpolation)&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_2D            : 0/1/2/3/4/5 (2D extrapolation: 0=no extrapolation, 1=medium&lt;br /&gt;
                                      triangulation, 2=high triangulation, &lt;br /&gt;
                                      3=nearest neighbour, 4=nearest cell, &lt;br /&gt;
                                      5=constant value)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_VALUE         : ... (name of the value to extrapolate to when EXTRAPOLATE_2D is&lt;br /&gt;
                                  set to constant value (5))&lt;br /&gt;
 &lt;br /&gt;
 DO_NOT_BELIEVE_MAP        : 0/1 (0=consider input HDF5 file map, 1=do not consider input HDF5&lt;br /&gt;
                                  file map)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (name of base group of HDF5 variables containing data to be &lt;br /&gt;
                                  interpolated; default is &amp;quot;/Results&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (if INTERPOLATION3D : 1 also required:)&lt;br /&gt;
 FATHER_GEOMETRY           : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  of input HDF5 file)&lt;br /&gt;
 NEW_GEOMETRY              : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  intended for output HDF5 file)&lt;br /&gt;
 POLI_DEGREE               : 1/... (degree of vertical interpolation: 1=linear, ...)&lt;br /&gt;
 &lt;br /&gt;
 AUX_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for auxiliar output HDF5 file;&lt;br /&gt;
                                  default is file provided in NEW_GRID_FILENAME)&lt;br /&gt;
 &lt;br /&gt;
 AUX_OUTPUTFILENAME        : ... (path/name of auxiliar output HDF5 file to contain result&lt;br /&gt;
                                  of horizontal grid interpolation)   &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the file indicated in AUX_GRID_FILENAME can be different from the one indicated in&lt;br /&gt;
   NEW_GRID_FILENAME in terms of bathymetry, while the horizontal grid should be, commonly, the&lt;br /&gt;
   same: this altered bathymetry can be used to extend the water column in the original data so&lt;br /&gt;
   that the process of vertical interpolation is done easily;&lt;br /&gt;
 &lt;br /&gt;
 - in case of INTERPOLATION3D : 1, ConvertToHDF5 can generate new versions of bathymetry which &lt;br /&gt;
   are consistent with the geometry definition (extension is '.new'); there are possibly three&lt;br /&gt;
   bathymetry changes referring to father grid, new grid and aux grid (the same bathymetry is&lt;br /&gt;
   not altered twice); although initially new and aux grid are the same they can result &lt;br /&gt;
   different because of bathymetry changes;&lt;br /&gt;
 &lt;br /&gt;
 - in case the new geometry is 2D and father geometry is 3D then POLI_DEGREE : 1 &lt;br /&gt;
   (linear interpolation) should be used;&lt;br /&gt;
 &lt;br /&gt;
 - EXTRAPOLATE_2D : 1/2/3/4/5 should be considered if it is expected that the coast line is not&lt;br /&gt;
   coincidental in the father and new grids, to avoid lack of data in the interpolation&lt;br /&gt;
   process; extrapolation is performed for all cells even the land cells; &lt;br /&gt;
 &lt;br /&gt;
 - in case of DO_NOT_BELIEVE_MAP : 1 the application generates a map based on cells where&lt;br /&gt;
   interpolation results are available; this causes that if EXTRAPOLATE_2D : 1/2/3/4/5 is used&lt;br /&gt;
   the AUX_GRID_FILENAME should not have land cells in order for the new map to be concurrent&lt;br /&gt;
   with the result of extrapolation and avoid errors generation, specially if INTERPOLATION3D :&lt;br /&gt;
   1 is considered.&lt;br /&gt;
&lt;br /&gt;
===PATCH HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of interpolation: 3 = Triangulation, default and only&lt;br /&gt;
                                  one implemented)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 (block for each father HDF5 file, should be at least two)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                     : ... (integer priority level: 1 = highest, increase for lower&lt;br /&gt;
                                  priority)&lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 N_REMOVE_FRAME            : 0   (width, in number of cells, of frame to remove)&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT ERA40 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of ERA40 NetCDF file)&lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
                                 (root of name for all files produced)&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII          : 0/1 (1 = convert variable heading info for ASCII file; 0 = default)&lt;br /&gt;
 CONVERT_TO_HDF5           : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 GRIDTO180                 : 0/1 (1 = convert grid from [0 360] to [-180 180], 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 YY_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 TIME_VARIABLE             : ... (name of time variable in the input file: usual name is&lt;br /&gt;
                                  &amp;quot;time&amp;quot;)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - either CONVERT_TO_ASCII : 1 or CONVERT_TO_HDF5 : 1 must be chosen for any action to be&lt;br /&gt;
 performed by ConvertToHDF5;&lt;br /&gt;
 &lt;br /&gt;
 - when CONVERT_TO_HDF5 : 1 an HDF5 file is produced for every variable contained in the&lt;br /&gt;
 original ERA40 file; the name of each file is composed of the name indicated on FILENAME&lt;br /&gt;
 concatenated with the ERA40 variable identifier;&lt;br /&gt;
 &lt;br /&gt;
 - to the XX_VARIABLE, YY_VARIABLE and TIME_VARIABLE keywords should generally be  &lt;br /&gt;
 specified &amp;quot;longitude&amp;quot;, &amp;quot;latitude&amp;quot; and &amp;quot;time&amp;quot;, respectively; the option to&lt;br /&gt;
 include as keywords was made only to make the application robust to future variable name&lt;br /&gt;
 changes.&lt;br /&gt;
&lt;br /&gt;
===CONVERT ALADIN FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 (path to aladin netcdf file)\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each Aladin property to convert in &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;...&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt; block must conform to the following variables&lt;br /&gt;
 &lt;br /&gt;
           ---ALADIN NAME---    ---MOHID NAME---&lt;br /&gt;
             soclotot            CloudCover_&lt;br /&gt;
             sohumrel            RelativeHumidity_&lt;br /&gt;
             sofluxir            NonSolarFlux_&lt;br /&gt;
             sosspres            AtmosphericPressure_&lt;br /&gt;
             sosolarf            SolarRadiation_&lt;br /&gt;
             sotemair            AirTemperature_&lt;br /&gt;
             sowinmod            WindModulus_&lt;br /&gt;
             sowaprec            Precipitation_&lt;br /&gt;
             sozotaux            WindStressX_&lt;br /&gt;
             sometauy            WindStressY_&lt;br /&gt;
             sowindu10           WindVelocityX_&lt;br /&gt;
             sowindv10           WindVelocityY_&lt;br /&gt;
&lt;br /&gt;
===CONVERT MM5 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MM5 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of MM5 file)&lt;br /&gt;
 TERRAIN_FILENAME          : ... (path/name of MM5 TERRAIN file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of MM5 data to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP                 : 0/1 (1 = compute and write mean sea level pressure field; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of MM5 properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of MM5 property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each MM5 property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must&lt;br /&gt;
 conform to the MOHID designation specified in code of ModuleGlobalData; the correspondence is &lt;br /&gt;
 the following (see [[Module_InterfaceWaterAir]] for a more detailed explanation).&lt;br /&gt;
 &lt;br /&gt;
           ---MM5 NAME---    ---MOHID NAME---&lt;br /&gt;
             T2             air temperature&lt;br /&gt;
             PSTARCRS       atmospheric pressure&lt;br /&gt;
             U10            wind velocity X&lt;br /&gt;
             V10            wind velocity Y&lt;br /&gt;
             UST            wind shear velocity&lt;br /&gt;
             LHFLUX         latent heat&lt;br /&gt;
             SWDOWN         sensible heat&lt;br /&gt;
             SWDOWN         solar radiation&lt;br /&gt;
             LWDOWN         infrared radiation&lt;br /&gt;
             SWOUT          top outgoing shortwave radiation&lt;br /&gt;
             LWOUT          top outgoing longwave radiation&lt;br /&gt;
             SOIL T 1       soil temperature layer 1&lt;br /&gt;
             SOIL T 1       soil temperature layer 2&lt;br /&gt;
             SOIL T 1       soil temperature layer 3&lt;br /&gt;
             SOIL T 1       soil temperature layer 4&lt;br /&gt;
             SOIL T 1       soil temperature layer 5&lt;br /&gt;
             SOIL T 1       soil temperature layer 6&lt;br /&gt;
             Q2             2-meter mixing ratio&lt;br /&gt;
             TSEASFC        sea water temperature&lt;br /&gt;
             PBL HGT        PBL height&lt;br /&gt;
             PBL REGIME     PBL regime&lt;br /&gt;
             RAIN CON       accumulated convective precipitation        (cm)&lt;br /&gt;
             RAIN NON       accumulated non-convective precipitation    (cm)&lt;br /&gt;
             GROUND T       ground temperature&lt;br /&gt;
             RES TEMP       infinite reservoir slab temperature&lt;br /&gt;
             U              wind velocity X_3D&lt;br /&gt;
             V              wind velocity Y_3D&lt;br /&gt;
             W              wind velocity Z_3D&lt;br /&gt;
             T              air temperature_3D&lt;br /&gt;
             PP             atmospheric pressure_3D&lt;br /&gt;
             Q              mixing ratio_3D&lt;br /&gt;
             CLW            cloud water mixing ratio_3D&lt;br /&gt;
             RNW            rain water mixing ratio_3D&lt;br /&gt;
             ICE            cloud ice mixing ratio_3D&lt;br /&gt;
             SNOW           snow mixing ratio_3D&lt;br /&gt;
             RAD TEND       atmospheric radiation tendency_3D&lt;br /&gt;
&lt;br /&gt;
===CONVERT WRF FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                       : CONVERT WRF FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                     : ... (path/name of WRF file)&lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of WRF data&lt;br /&gt;
                                     to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP_MM5             : 0/1 (1 = compute mean sea level pressure with MM5toGrads algorithm; 1 = default)&lt;br /&gt;
 COMPUTE_MSLP_WRF             : 0/1 (1 = compute mean sea level pressure with ARWPost algorithm; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 OUTPUT_DT                    : real (DT interval in seconds between each output; default = 0.0)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
  &lt;br /&gt;
 - the name of each property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must conform to the MOHID &lt;br /&gt;
   designation specified in code of ModuleGlobalData; the correspondence to WRF is in function &lt;br /&gt;
   VariableIsToRead in ModuleWRFFormat. Conversion is not direct since WRF outputs tendencies and not  &lt;br /&gt;
   total values. &lt;br /&gt;
 &lt;br /&gt;
 - Caution: This action is not extensively tested.&lt;br /&gt;
&lt;br /&gt;
===CONVERT MERCATOR FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION               : 1/2/3/4 (version of MERCATOR files)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 1:)&lt;br /&gt;
 BASE_BULLETIN             : ...&lt;br /&gt;
 DATES_FILE                : ...&lt;br /&gt;
 NUM_DATES                 : ... &lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 2/3:)&lt;br /&gt;
 INPUT_GRID_FILENAME       : ... (path/name of file with horizontal discretization of water&lt;br /&gt;
                                  properties and water level data)&lt;br /&gt;
 (if READ_OPTION : 2:)&lt;br /&gt;
 INPUT_GRID_FILENAME_U     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component U data)&lt;br /&gt;
 INPUT_GRID_FILENAME_V     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component V data)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 3:)&lt;br /&gt;
 INPUT_BATHY_FILENAME      : ... (path/name of file with bathymetry)&lt;br /&gt;
     &lt;br /&gt;
 (if READ_OPTION : 3/4:)&lt;br /&gt;
 CALC_BAROTROPIC_VEL       : 0/1 (1 = calculate barotropic velocity, 0 = not calculate; &lt;br /&gt;
                                  default = 0)&lt;br /&gt;
 &lt;br /&gt;
 (if CALC_BAROTROPIC_VEL : 1 and READ_OPTION : 3:)&lt;br /&gt;
 INPUT_MESH_ZGRID_FILENAME : ... (path/name of file with information about layers ticknesses)&lt;br /&gt;
 &lt;br /&gt;
 (block of MERCATOR data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of MERCATOR NetCDF data file, one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT LEVITUS FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT LEVITUS FORMAT&lt;br /&gt;
  &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Levitus data: &amp;quot;monthly&amp;quot;/&amp;quot;annual&amp;quot;; default is&lt;br /&gt;
                                  &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Levitus grid)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
 &lt;br /&gt;
 (block for each water property to be present in output HDF5 file, can be several)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property)&lt;br /&gt;
 ANNUAL_FILE               : ... (path/name of Levitus annual file)&lt;br /&gt;
 &lt;br /&gt;
 (block of Levitus data files)&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of Levitus data file (e.g. a monthly data file), one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT HELLERMAN ROSENSTEIN ASCII===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
  &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Hellerman Rosenstein data: &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Hellerman&lt;br /&gt;
                                  Rosenstein grid: default and only allowed value is &amp;quot;2.&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
   &lt;br /&gt;
 (block for each Hellerman Rosenstein data file)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property: &amp;quot;wind stress X&amp;quot;/&amp;quot;wind stress Y&amp;quot;)&lt;br /&gt;
 FILE                      : ... (path/name Hellerman Rosenstein file)&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CONVERT GENERIC NETCDF CF===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION              : CONVERT NETCDF CF TO HDF5 MOHID       &lt;br /&gt;
 HDF5_OUT            : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 OUTPUTFILENAME      : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)&lt;br /&gt;
 OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property for time, generally &amp;quot;time&amp;quot;&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT     : ... (name of the netcdf property for latitude, generally &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_LONG    : ... (name of the netcdf property for longitude, generally &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_MAPPING : ... (name of the netcdf field where is located the mapping 0 water 1 land)&lt;br /&gt;
                           (It can also be used any field, i.e. temperature)&lt;br /&gt;
 MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus &amp;gt;0.5 water)&lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER   : real (number of netcdf properties) &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property&lt;br /&gt;
 NAME                : name of the HDF5 Mohid property&lt;br /&gt;
 UNITS               : property units&lt;br /&gt;
 DESCRIPTION         : property description&lt;br /&gt;
 DIM                 : 2/3 Number of property dimensions &lt;br /&gt;
 VECTOR_INTENSITY    : 0/1 If property corresponds to a vector intensity&lt;br /&gt;
 VECTOR_X            : Decomposition of Vector Intensity X&lt;br /&gt;
 VECTOR_Y            : Decomposition of Vector Intensity Y&lt;br /&gt;
 BEAUFORT_SCALE      : 0/1 If property correspond to the beaufort scale&lt;br /&gt;
 ADD_FACTOR          : To add the property a fixed value&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 path to netcdf cf file&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT SEASONDE RADAR FORMAT ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 !HDF5 path and filename that will contain the results&lt;br /&gt;
 OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
 &lt;br /&gt;
 !griddata path and filename that will contain a griddata of the proxy bathymetry used in the hdf5 output file.&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Path and filename to the grid that maps the radar data. This grid must be constructed with the [[GIS]]&lt;br /&gt;
 !or MOHID Studio and must &amp;quot;fit&amp;quot; well where the points stand.&lt;br /&gt;
 INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
 &lt;br /&gt;
 !This is the version of the grid used by the seasonde radar system.&lt;br /&gt;
 !If the grid version of the seasonde radar changes, then most likely a new input grid must be&lt;br /&gt;
 !constructed with the GIS or MOHID Studio.&lt;br /&gt;
 IH_GRID_VERSION           : 4&lt;br /&gt;
 &lt;br /&gt;
 !This is a list with the Seasonde radar ascii data files. One file per instant.&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Samples==&lt;br /&gt;
All sample files are named ''ConvertToHDF5Action.dat''.&lt;br /&gt;
&lt;br /&gt;
===Glue several MOHID(.hdf5) files===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : SurfaceHydro_OP.hdf5&lt;br /&gt;
  &lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_21.hdf5&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_22.hdf5&lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 2D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME           : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
  &lt;br /&gt;
 START                    : 2006 6 21 17 22 30&lt;br /&gt;
 END                      : 2006 6 22 17 22 0&lt;br /&gt;
  &lt;br /&gt;
 FATHER_GRID_FILENAME     : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME        : TagusConstSpacing.dat&lt;br /&gt;
  &lt;br /&gt;
 BASE_GROUP               : /Results/Oil/Data_2D&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 3D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 1&lt;br /&gt;
 FATHER_FILENAME         : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME          : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2006 6 21 17 22 30&lt;br /&gt;
 END                     : 2006 6 22 17 22 0&lt;br /&gt;
 &lt;br /&gt;
 FATHER_GRID_FILENAME    : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP              : /Results/Oil/Data_2D&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D         : 1&lt;br /&gt;
 FATHER_GEOMETRY         : D:\Projectos\MohidRun\test\data\Geometry_1.dat&lt;br /&gt;
 NEW_GEOMETRY            : TagusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME      : Aux_GridRegular.hdf5&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Patch several MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 3&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2005 2 28 13 0 0&lt;br /&gt;
 END                     : 2005 3 1 13 0 0&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 3&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D1.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid1.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 2&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D2.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid2.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 1&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D3.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid3.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME          : MM5Forcing.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME       : K:\Simula\GeneralData\Batim\CostaPortuguesa.dat&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert an ERA40 file to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                  : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                : D:\Aplica\ERA40\1971ERA1973.nc&lt;br /&gt;
 OUTPUTFILENAME          : D:\Aplica\ERA40\1971ERA1973T2&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII        : 0&lt;br /&gt;
 CONVERT_TO_HDF5         : 1&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE             : longitude&lt;br /&gt;
 YY_VARIABLE             : latitude&lt;br /&gt;
 TIME_VARIABLE           : time&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a MM5 file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : MMOUT_DOMAIN2&lt;br /&gt;
 TERRAIN_FILENAME          : TERRAIN_DOMAIN2&lt;br /&gt;
 OUTPUTFILENAME            : D2.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : D2.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 !START                     : 2010 02 15 00 00 00&lt;br /&gt;
 !END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a WRF file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : wrfout_d01_2010-02-15_00.nc&lt;br /&gt;
 OUTPUTFILENAME            : wrfout_d01.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : wrfout_d01.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 START                     : 2010 02 15 00 00 00&lt;br /&gt;
 END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Mercator-Ocean(.nc) to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION              : 2&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Psy2v2r1v_R20060628/MercatorR20060628.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : Psy2v2r1v_R20060628/MercatorGridR20060628.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : Psy2v2r1v_R20060628/MercatorGeometryR20060628.dat&lt;br /&gt;
 &lt;br /&gt;
 INPUT_GRID_FILENAME      : GridFiles/ist_meteog-gridT.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_U    : GridFiles/ist_meteog-gridU.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_V    : GridFiles/ist_meteog-gridV.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060621_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060622_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060623_R20060628.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Levitus format to MOHID(.hdf5) and interpolate grid===&lt;br /&gt;
==== Convert ====&lt;br /&gt;
First convert the Levitus ASCII format to a raw HDF5 format:&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT LEVITUS FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Levitus.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : LevitusGeometry.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 0.25&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -16.0  31&lt;br /&gt;
 UPPER_RIGHT_CORNER       :   1.   40&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : salinity&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : temperature&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Temp\t000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Extrapolate ====&lt;br /&gt;
Then extrapolate the data (still in the raw HDF5 format):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME          : Levitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : LevitusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxLeviTusAllPointsWithData.hdf5&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 EXTRAPOLATE_2D           : 2&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Interpolate ====&lt;br /&gt;
Finally, interpolate to the final grid and geometry (same as the [[#Interpolate 3D MOHID(.hdf5) files to a new grid| Interpolate 3D sample]]):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 OUTPUTFILENAME           : CadizMonthlyLevitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 NEW_GRID_FILENAME        : Algarve0.02SigmaSmooth_V3_CartMoreLayers.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : Geometry_1.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxCadizMonthlyLevitus.hdf5&lt;br /&gt;
 AUX_GRID_FILENAME        : Aux12km.dat&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the programme may construct a new bathymetry twice. Use this bathymetry only on the AUX_GRID_FILENAME keyword.&lt;br /&gt;
&lt;br /&gt;
===Convert Hellerman Rosenstein ASCII format to MOHID(.hdf5)  ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : ClimatologicWindStress.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : ClimatologicWindStressGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 2.&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -180  -90&lt;br /&gt;
 UPPER_RIGHT_CORNER       : 180  90&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress X&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUXX.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress Y&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUYY.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert ALADIN(.nc) format to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKPRES_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKSOLAR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKTAIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKWIND_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_FLUXPRE_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSU_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSV_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_U10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_V10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKHUMI_OPASYMP_19723_20088.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Convert generic Netcdf CF to MOHID(.hdf5)  ===&lt;br /&gt;
&lt;br /&gt;
This sample is for converting a typical GFS file&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION : CONVERT NETCDF CF TO HDF5 MOHID&lt;br /&gt;
 HDF5_OUT : 1&lt;br /&gt;
 OUTPUTFILENAME : ..\..\data\hdf5\GFS.hdf5&lt;br /&gt;
 NETCDF_OUT : 1&lt;br /&gt;
 OUTPUT_NETCDF_FILE : ..\..\data\netcdf\GFS.nc&lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : time&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT : latitude&lt;br /&gt;
 NETCDF_NAME_LONG : longitude&lt;br /&gt;
 NETCDF_NAME_MAPPING : TMP_10mb&lt;br /&gt;
 MAPPING_LIMIT : -10000&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER : 6 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : PRMSL_meansealevel&lt;br /&gt;
 NAME : atmospheric pressure&lt;br /&gt;
 UNITS : Pa&lt;br /&gt;
 DESCRIPTION : GFS&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : UGRD_10mb&lt;br /&gt;
 NAME : wind velocity X&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : VGRD_10mb&lt;br /&gt;
 NAME : wind velocity Y&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus&lt;br /&gt;
 NAME                     : wind modulus &lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 VECTOR_INTENSITY         : 1&lt;br /&gt;
 VECTOR_X                 : wind velocity X&lt;br /&gt;
 VECTOR_Y                 : wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus_beaufort &lt;br /&gt;
 NAME                     : wind modulus beaufort &lt;br /&gt;
 UNITS : beaufort scale&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 BEAUFORT_SCALE           : 1&lt;br /&gt;
 VECTOR_X                 : wind modulus&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : TMP_2maboveground&lt;br /&gt;
 NAME : air temperature&lt;br /&gt;
 UNITS : oC&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 ADD_FACTOR  : -273&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ..\..\data\netcdf\gfs_4_20111115.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
=== Convert Seasonde RADAR data sample configuration file===&lt;br /&gt;
The input grid file must be created to be the recipient of the data in the ascii files.&lt;br /&gt;
To create this grid, it is recommended to convert manually, resorting to a good text editor, such as Notepad++, a few radar ascii files into the [[xyz]] Mohid format, then load them in the [[GIS]] or [[Mohid Studio]], and from there create and save a regular grid that fits the points. Use that grid to convert the data into one hdf5 file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;begin_file&amp;gt;&lt;br /&gt;
ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
&lt;br /&gt;
OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
IH_GRID_VERSION           : 4&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_30_1400.tuv.txt&lt;br /&gt;
&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
&amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OceanColor modules compilation ==&lt;br /&gt;
Compiling the [[ConvertToHDF5]] tool with the OceanColor modules is more complicated than one might expect. A solution is proposed here for a release version using the Compaq Visual Fortran 6.6c. The difficulties rise because C code is embedded with a fortran interface and also, extra libraries such as hdf4 are required.&lt;br /&gt;
&lt;br /&gt;
=== Pre-requisites ===&lt;br /&gt;
&lt;br /&gt;
This is a list of prerequisites to successfully compile the tool:&lt;br /&gt;
*Compaq Visual Fortran 6.5 with patch 6.6c,&lt;br /&gt;
*VS .NET 2003 (Vc7 in particular),&lt;br /&gt;
*Hdf5 libraries ('''hdf5.lib''' '''hdf5_fortran.lib''' '''hdf5_hl.lib'''),&lt;br /&gt;
*Netcdf libraries ('''netcdf.lib''' '''netcdf_.lib'''),&lt;br /&gt;
*Hdf4 libraries ('''hd421.lib''', '''hm421.lib'''),&lt;br /&gt;
*szlib, zlib and jpeg libraries ('''szlib.lib''', '''zlib.lib''' and '''libjpeg.lib'''),&lt;br /&gt;
*the fortran source files ('''ModuleConvertModisL2.F90 ModuleConvertModisL3.F90 ModuleConvertOceanColorL2.F90'''),&lt;br /&gt;
*the C source files and their fortran interface files ('''readL2scan.c readL2Seadas.c''' and '''cdata.f crossp.f fgeonav.f''').&lt;br /&gt;
&lt;br /&gt;
=== CVF IDE configuration ===&lt;br /&gt;
# Configure everything as specified in [[Compiling with CVF]].&lt;br /&gt;
# Add the source files listed in the prerequisites above to the source files listing.&lt;br /&gt;
# Go to '''Tools--&amp;gt;Options...--&amp;gt;Directories'''. There, add the '''$DOTNET2K3/Vc7/bin''' to the '''Executable files''''; the '''$DOTNET2K3/Vc7/include''' and '''$DOTNET2K3/Vc7/PlatformSDK/include''' to the '''Include files'''; and finally, the '''$DOTNET2K3/Vc7/lib''', '''$DOTNET2K3/Vc7/PlatformSDK/lib''' and  '''$DOTNET2K3/Vc7/PlatformSDK/bin''' to the '''Library files'''.&lt;br /&gt;
# Go to '''Projects--&amp;gt;Settings--&amp;gt;Release--&amp;gt;Link--&amp;gt;Input'''. There, add the following libraries: '''netcdf.lib netcdf_.lib hd421.lib hm421.lib libjpeg.lib'''. (Make sure the hdf5 libraries as well as the szlib and zlib libraries are already mentioned).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshoots ===&lt;br /&gt;
'''Q: I get unresolved external references during linkage, but I have all the libraries mentioned above included. What should I do?'''&lt;br /&gt;
&lt;br /&gt;
A: Unresolved external references can come out for two reasons:&lt;br /&gt;
#you didn't specified all the libraries required or all the paths for the default libraries or,&lt;br /&gt;
#[http://en.wikipedia.org/wiki/Name_decoration name mangling] problems. Use the [[dumpbin]] utility to the libraries to checkout which language convention they are using. If that's the problem then you need to try to get new libraries with the correct naming convention.&lt;br /&gt;
&lt;br /&gt;
That's it, you should now be able to build the [[ConvertToHdf5]] project successfully.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Q: I got a message saying the entry point _NF_PUT_ATT_REAL@28 could not be located in netcdf.dll'''&lt;br /&gt;
&lt;br /&gt;
A: copy the file netcdf.dll to the exe folder&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF5 Homepage]&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF4 Homepage]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
*[[Module_Atmosphere]]&lt;br /&gt;
*[[Module_InterfaceWaterAir]]&lt;br /&gt;
*[[Coupling_Water-Atmosphere_User_Manual]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Hdf5]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6289</id>
		<title>ConvertToHDF5</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6289"/>
				<updated>2012-06-05T15:34:56Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Input file (ConvertToHDF5Action.dat) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''ConvertToHDF5''' is an application which allows the making of several operations, called '''actions''', involving HDF5 files: conversion of data in other formats (e.g. NETCDF) to HDF5, grid interpolation, concatenation of several files.&lt;br /&gt;
&lt;br /&gt;
Running options for this application are specified by the user in a input file named [[ConvertToHDF5#Input file (ConvertToHDF5Action.dat)|'''ConvertToHDF5Action.dat''']]. Several actions can be specified in the same input file, being processed sequentially by the ConvertToHDF5 application.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
The operations involving HDF5 files performed by ConvertToHDF5, specified individually by an action, can be organized in:&lt;br /&gt;
&lt;br /&gt;
* [[#file management|file management]]&lt;br /&gt;
* [[#grid interpolation|grid interpolation]] and &lt;br /&gt;
* [[#format conversion|format conversion]]. &lt;br /&gt;
&lt;br /&gt;
These types and the respective actions are detailed in the next sections. &lt;br /&gt;
&lt;br /&gt;
The input file specification for each action can be found bellow in the [[#Input file (ConvertToHDF5Action.dat)|Input file (ConvertToHDF5Action.dat)]] section.&lt;br /&gt;
&lt;br /&gt;
==File management==&lt;br /&gt;
&lt;br /&gt;
===Glue files===&lt;br /&gt;
This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 files to be glued. &amp;quot;Grid&amp;quot; and &amp;quot;Results&amp;quot; data groups should be equal in all these files.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with glued &amp;quot;Results&amp;quot; data. &amp;quot;Residual&amp;quot; and &amp;quot;Statistics&amp;quot; HDF5 data groups are not copied to the output file since they are time period specific (different values potentially occour in each file). General statistics can be calculated for the glued HDF5 file data using tool [[HDF5Statistics]].&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Grid interpolation==&lt;br /&gt;
&lt;br /&gt;
===Interpolate files===&lt;br /&gt;
This action performs the conversion of one HDF5 file data existing in one 2D or 3D spatial grid to another 2D or 3D spatial grid, creating a new HDF5 file. The interpolation is performed only for the data located a time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
The HDF5 file containing data to be interpolated is called the '''father file'''.&lt;br /&gt;
&lt;br /&gt;
In case of 3D interpolation the application conducts first the horizontal grid interpolation&lt;br /&gt;
(keeping father geometry) and only after it conducts the vertical interpolation (from father geometry to new geometry).&lt;br /&gt;
&lt;br /&gt;
Several types of 2D interpolation are available for use: bilinear, spline 2D and triangulation.&lt;br /&gt;
For vertical interpolation (used in 3D interpolation) can be supplied several polinomial degrees for interpolation.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data for forcing or providing initial conditions for a MOHID Water model, e.g. a meteorological forcing file.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
For 2D/3D interpolation:&lt;br /&gt;
&lt;br /&gt;
- father HDF5 file;&lt;br /&gt;
&lt;br /&gt;
- father horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
For 3D interpolation also needed:&lt;br /&gt;
&lt;br /&gt;
- father vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- auxiliary horizontal data grid, in a grid data file in the format supported by MOHID; this file is used for horizontal grid interpolation in 3D interpolation operations.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with interpolated data. In case of 3D interpolation also produced an auxiliary HDF5 file with the result of the horizontal grid interpolation, which can be inspected to check if this operation is well performed.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].&lt;br /&gt;
&lt;br /&gt;
===Patch files===&lt;br /&gt;
This action consists in performing an interpolation of HDF5 data between grids, as in action [[#Interpolate files|Interpolate files]], but considering more than one HDF5 file as containing data to be interpolated to the new grid and a priority scale. The interpolation is performed only for the data located in the time window specified by the user. The present version of this action operates only on 2D data.&lt;br /&gt;
&lt;br /&gt;
Each HDF5 file containing data to be interpolated is called a '''father file''' and has an user-attributed '''priority level''' to be respected in the interpolation process: for each new grid cell the ConvertToHDF5 application will look for data first on the Level 1 father file and only in the case this data is inexistent will it look for data in Level 2 file, proceeding in looking for higher level files if no data is found subsequentely.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
To obtain an HDF5 file with data from several HDF5 files each containing data with different spatial resolution and only for a specific part of the new grid. This is, for instance, the case when one is preparing a best resolution meteorological HDF5 file for forcing MOHID Water from several meteorological model domains, having different spatial resolution and span, since the best resolution data is not available for all new grid cells.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
The new horizontal data grid, in a grid data file in the format supported by MOHID, and for each father file:&lt;br /&gt;
&lt;br /&gt;
- level of priority: 1 = maximum priority, priority decreases with increasing level value;&lt;br /&gt;
&lt;br /&gt;
- data grid, in the form of a grid data file in the format supported by MOHID.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with patched data.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#PATCH HDF5 FILES|PATCH HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Format conversion==&lt;br /&gt;
&lt;br /&gt;
===Meteorological model data===&lt;br /&gt;
Mohid does not simulate explicitly the atmosphere, but needs information about atmospheric properties in time and space. This requires that atmospheric properties are supplied to MOHID Water in supported formats. These formats can be derived from meteorological data in HDF5 format. Because the results of meteorological models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the MM5 and the ERA40. These are succintly detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''ERA40''====&lt;br /&gt;
This format refers to the European Centre for Medium-Range Weather Forecasts (ECMWF) 40 years re-analysises results, acessed by site http://data.ecmwf.int/data/d/era40_daily/. This data is available for several meteorological variables with maximum 6 hour periodicity for days in the period from 1957-09-01 to 2002-08-31. &lt;br /&gt;
&lt;br /&gt;
ERA40 data files are supplied by ECMWF in a NetCDF format and with an user-costumized time window, periodicity (time step range from 6 hours to a day) and meteorological properties set. The ERA40 meteorological properties which are recognized by MOHID are presented bellow together with the correspondent MOHID name: &lt;br /&gt;
&lt;br /&gt;
 ---ERA40 NAME---         ---MOHID NAME---&lt;br /&gt;
   sshf                     sensible heat                &lt;br /&gt;
   slhf                     latent heat                  &lt;br /&gt;
   msl                      atmospheric pressure &lt;br /&gt;
   tcc                      cloud cover &lt;br /&gt;
   p10u                     wind velocity X&lt;br /&gt;
   p10v                     wind velocity Y&lt;br /&gt;
   p2t                      air temperature&lt;br /&gt;
   ewss                     wind stress X&lt;br /&gt;
   nsss                     wind stress Y&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to all MOHID Water recognized property available in the ERA40 file, producing an individual HDF5 file for each property. The name of each HDF5 file generated includes the ERA40 meteorological property identificator correspondent to the data contained.&lt;br /&gt;
&lt;br /&gt;
Alternatively, ConvertToHDF5 can copy to a single ASCII file the heading information concerning each meteorological variable considered in the original ERA40 file.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data suitable for being used for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ERA40 NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file for each meteorological property contained in the original NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ERA40 FORMAT|CONVERT ERA40 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Aladin''====&lt;br /&gt;
This format relates to Aladin meteorological model results. Some of the atmospheric property needed by MOHID Water is present in Aladin output files, enabling to run prediction simulations with MOHID Water when access to Aladin prevision files is available.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts Aladin results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Aladin netcdf results file to convert.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with Aladin results and a grid data file in MOHID format with the Aladin grid pseudo-information: a fake orography is created of 100 m depth.&lt;br /&gt;
This last file can be used to interpolate the Aladin data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ALADIN FORMAT|CONVERT ALADIN FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MM5''====&lt;br /&gt;
This format relates to the Fifth-Generation NCAR / Penn State Mesoscale Model (MM5) output files format. Almost every atmospheric property needed by MOHID Water is present in MM5 output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts MM5 results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the MM5 files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
For conversion to be completed it is required the horizontal grid information of MM5 results which is available in special TERRAIN files.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
MM5 results file to convert and MM5 TERRAIN file. The TERRAIN file supplies the MM5 results grid information. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
A HDF5 file with MM5 results and a grid data file in MOHID format with the MM5 grid information.&lt;br /&gt;
This last file can be used to interpolate the MM5 data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MM5 FORMAT|CONVERT MM5 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''WRF''====&lt;br /&gt;
This format relates to the Weather Research and Forecast model (WRF) output files format. Almost every atmospheric property needed by MOHID Water is present in WRF output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts WRF results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the WRF properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the WRF files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
WRF direct output file.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with WRF results and a grid data file in MOHID format with the WRF grid information.&lt;br /&gt;
This last file can be used to interpolate the WRF data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! [[PROJ4 | PROJ4]] library is needed! See [[#Compile_ModuleWRFFormat |  Compile_ModuleWRFFormat]]&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT WRF FORMAT|CONVERT WRF FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Wave model data===&lt;br /&gt;
Mohid does not simulate explicitly the wave dynamics, but needs information about wave properties in time and space. This requires that wave properties are supplied to MOHID Water in supported formats. These formats can be derived from wave data in HDF5 format. Because the results of wave models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the table format of SWAN. This is succintly detailed in the next section.&lt;br /&gt;
&lt;br /&gt;
====''SWAN''====&lt;br /&gt;
SWAN data files are supplied in a ASCII format. The data is organized by time instant. For each time instant there is a table of data. Each column represents one property. &lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to gradients of wave stresses X and Y, mean amplitude, mean period and mean direction.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 SWAN data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ASCII (table type) SWAN results data files and bathymetry in MOHID grid data foramt. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (wave stresses X and Y, mean amplitude, mean period and mean direction). &lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT TO AND FROM SWAN|CONVERT TO AND FROM SWAN]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Ocean model data===&lt;br /&gt;
Ocean model data, available in diverse formats, can be used by MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation. These uses require that the model data is in HDF5 format and conversion is therefore needed.&lt;br /&gt;
&lt;br /&gt;
Currently the large scale ocean models formats convertible into HDF5 by ConvertToHDF5 includes MERCATOR.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MERCATOR''====&lt;br /&gt;
MERCATOR data files are supplied in a NetCDF format and with an user-costumized spatial window and periodicity. Water level and water properties (temperature and salinity) data is available in type T files, velocity component u data is available in type U files and velocity component v data is available in type V files. The type of data of a specific MERCATOR file is generally indicated in the file name.&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to temperature, salinity, water level, component u of velocity and component v of velocity.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 MERCATOR data usable for forcing or validation of MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
NetCDF MERCATOR results data files and NetCDF MERCATOR grid data files. It should be provided one grid data file of each type: T, U and V. These are generally provided by the MERCATOR services together with the results files.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (temperature, salinity, water level, velocity u and velocity v) and the correspondent grid data and geometry files, containing respectively the horizontal grid and the vertical discretization of the HDF5 file. The grid data and geometry files can be used afterwards to interpolate the MERCATOR data to another grid and geometry (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MERCATOR FORMAT|CONVERT MERCATOR FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Climatological data===&lt;br /&gt;
Climatological data can be used in MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation, in case more realistic data (measurements or model) data is unavailable. This data is generally supplied by producers in formats not readly usable by MOHID Water which justifies the existence of a conversion tool.&lt;br /&gt;
&lt;br /&gt;
Two climatological data format conversions are implemented in ConvertToHDF5: Levitus ocean data and Hellerman Rosenstein meteorological data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''Levitus''====&lt;br /&gt;
The Levitus climatology provides results for water temperature and salinity.&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window requested by the user. &lt;br /&gt;
Typically, it requires 3 steps to complete the task:&lt;br /&gt;
&lt;br /&gt;
- convert levitus format &lt;br /&gt;
&lt;br /&gt;
- extrapolate the data to the whole levitus domain(required to avoid uncoincidental coastlines) &lt;br /&gt;
&lt;br /&gt;
- interpolate with the model grid(bathymetry)&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as boundary forcing and/or initial condition specification in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Levitus climatological data files, one per property and per time period (e.g a month).&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Levitus climatological data, grid data file with the horizontal&lt;br /&gt;
grid of the data and a geometry file with vertical discretization of the data (MOHID formats).&lt;br /&gt;
The grid data and the geometry files can be used to interpolate the climatological data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT LEVITUS FORMAT|CONVERT LEVITUS FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Hellerman Rosenstein''====&lt;br /&gt;
This is a meteorological climatology providing wind stress. There is a file per wind stress component. Since the data refer to surface values it is a 2D field.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window provided by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as meteorological forcing in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Hellerman Rosenstein climatological data ASCII files, one per wind stress component.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Hellerman Rosenstein climatological data and grid data file with the horizontal&lt;br /&gt;
grid of the climatological data. This grid data file can be used to interpolate the climatological data from the original horizontal grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT HELLERMAN ROSENSTEIN ASCII|CONVERT HELLERMAN ROSENSTEIN ASCII]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''World Ocean Atlas 2005''====&lt;br /&gt;
The World Ocean Atlas (WOA) 2005 climatology provides results for water temperature, salinity and several water quality and biology properties.&lt;br /&gt;
&lt;br /&gt;
Description, Action and Input Files are described in a separate page: [[ConvertToHDF5 WOA2005]].&lt;br /&gt;
&lt;br /&gt;
===Generic NETCDF CF FILES===&lt;br /&gt;
&lt;br /&gt;
Converts any netcdf file following the CF convention into Mohid HDF5 files. Check the [[ConvertToHDF5#CONVERT_GENERIC_NETCDF_CF | Input File]] and [[ConvertToHDF5#Convert_generic_Netcdf_CF_to_MOHID.28.hdf5.29 | Sample File]].&lt;br /&gt;
&lt;br /&gt;
===Radar data===&lt;br /&gt;
====Seasonde RADAR Data====&lt;br /&gt;
Converts a list of ascii files from the Seasonde radar data, which measures currents over a given region of space, into an hdf5 file with the MOHID format. Useful to validate coastal and estuarine models where radars are located.&lt;br /&gt;
&lt;br /&gt;
==Input file (ConvertToHDF5Action.dat)==&lt;br /&gt;
===General structure===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt; (block containing instructions for running a specific action) &lt;br /&gt;
 ACTION                    : ... (intended action)&lt;br /&gt;
 ... (action specific instructions)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : ...&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GLUES HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 3D_FILE                   : 0/1 (0 = 2D file, 1 = 3D file)&lt;br /&gt;
 &lt;br /&gt;
 TIME_GROUP                : ... (Default=&amp;quot;Time&amp;quot;. Other option: &amp;quot;SurfaceTime&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (Default=&amp;quot;Results&amp;quot;. Other options: &amp;quot;Residual&amp;quot;, &amp;quot;SurfaceResults&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 &lt;br /&gt;
 (block of HDF5 data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of HDF5 file with data to be included in glue, one per line, at least two files)&lt;br /&gt;
 ...                      &lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===INTERPOLATE GRIDS===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of horizontal interpolation: 1 = Bilinear, 2 = Spline2D,&lt;br /&gt;
                                  3 = Triangulation)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION_WINDOW      : ... ... ... ... (2D spatial window to consider for interpolation: &lt;br /&gt;
                                              Xmin Ymin Xmax Ymax; default = all domain)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D           : 0/1 (0 = 2D interpolation, 1 = 3D interpolation)&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_2D            : 0/1/2/3/4/5 (2D extrapolation: 0=no extrapolation, 1=medium&lt;br /&gt;
                                      triangulation, 2=high triangulation, &lt;br /&gt;
                                      3=nearest neighbour, 4=nearest cell, &lt;br /&gt;
                                      5=constant value)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_VALUE         : ... (name of the value to extrapolate to when EXTRAPOLATE_2D is&lt;br /&gt;
                                  set to constant value (5))&lt;br /&gt;
 &lt;br /&gt;
 DO_NOT_BELIEVE_MAP        : 0/1 (0=consider input HDF5 file map, 1=do not consider input HDF5&lt;br /&gt;
                                  file map)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (name of base group of HDF5 variables containing data to be &lt;br /&gt;
                                  interpolated; default is &amp;quot;/Results&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (if INTERPOLATION3D : 1 also required:)&lt;br /&gt;
 FATHER_GEOMETRY           : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  of input HDF5 file)&lt;br /&gt;
 NEW_GEOMETRY              : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  intended for output HDF5 file)&lt;br /&gt;
 POLI_DEGREE               : 1/... (degree of vertical interpolation: 1=linear, ...)&lt;br /&gt;
 &lt;br /&gt;
 AUX_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for auxiliar output HDF5 file;&lt;br /&gt;
                                  default is file provided in NEW_GRID_FILENAME)&lt;br /&gt;
 &lt;br /&gt;
 AUX_OUTPUTFILENAME        : ... (path/name of auxiliar output HDF5 file to contain result&lt;br /&gt;
                                  of horizontal grid interpolation)   &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the file indicated in AUX_GRID_FILENAME can be different from the one indicated in&lt;br /&gt;
   NEW_GRID_FILENAME in terms of bathymetry, while the horizontal grid should be, commonly, the&lt;br /&gt;
   same: this altered bathymetry can be used to extend the water column in the original data so&lt;br /&gt;
   that the process of vertical interpolation is done easily;&lt;br /&gt;
 &lt;br /&gt;
 - in case of INTERPOLATION3D : 1, ConvertToHDF5 can generate new versions of bathymetry which &lt;br /&gt;
   are consistent with the geometry definition (extension is '.new'); there are possibly three&lt;br /&gt;
   bathymetry changes referring to father grid, new grid and aux grid (the same bathymetry is&lt;br /&gt;
   not altered twice); although initially new and aux grid are the same they can result &lt;br /&gt;
   different because of bathymetry changes;&lt;br /&gt;
 &lt;br /&gt;
 - in case the new geometry is 2D and father geometry is 3D then POLI_DEGREE : 1 &lt;br /&gt;
   (linear interpolation) should be used;&lt;br /&gt;
 &lt;br /&gt;
 - EXTRAPOLATE_2D : 1/2/3/4/5 should be considered if it is expected that the coast line is not&lt;br /&gt;
   coincidental in the father and new grids, to avoid lack of data in the interpolation&lt;br /&gt;
   process; extrapolation is performed for all cells even the land cells; &lt;br /&gt;
 &lt;br /&gt;
 - in case of DO_NOT_BELIEVE_MAP : 1 the application generates a map based on cells where&lt;br /&gt;
   interpolation results are available; this causes that if EXTRAPOLATE_2D : 1/2/3/4/5 is used&lt;br /&gt;
   the AUX_GRID_FILENAME should not have land cells in order for the new map to be concurrent&lt;br /&gt;
   with the result of extrapolation and avoid errors generation, specially if INTERPOLATION3D :&lt;br /&gt;
   1 is considered.&lt;br /&gt;
&lt;br /&gt;
===PATCH HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of interpolation: 3 = Triangulation, default and only&lt;br /&gt;
                                  one implemented)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 (block for each father HDF5 file, should be at least two)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                     : ... (integer priority level: 1 = highest, increase for lower&lt;br /&gt;
                                  priority)&lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 N_REMOVE_FRAME            : 0   (width, in number of cells, of frame to remove)&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT ERA40 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of ERA40 NetCDF file)&lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
                                 (root of name for all files produced)&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII          : 0/1 (1 = convert variable heading info for ASCII file; 0 = default)&lt;br /&gt;
 CONVERT_TO_HDF5           : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 GRIDTO180                 : 0/1 (1 = convert grid from [0 360] to [-180 180], 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 YY_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 TIME_VARIABLE             : ... (name of time variable in the input file: usual name is&lt;br /&gt;
                                  &amp;quot;time&amp;quot;)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - either CONVERT_TO_ASCII : 1 or CONVERT_TO_HDF5 : 1 must be chosen for any action to be&lt;br /&gt;
 performed by ConvertToHDF5;&lt;br /&gt;
 &lt;br /&gt;
 - when CONVERT_TO_HDF5 : 1 an HDF5 file is produced for every variable contained in the&lt;br /&gt;
 original ERA40 file; the name of each file is composed of the name indicated on FILENAME&lt;br /&gt;
 concatenated with the ERA40 variable identifier;&lt;br /&gt;
 &lt;br /&gt;
 - to the XX_VARIABLE, YY_VARIABLE and TIME_VARIABLE keywords should generally be  &lt;br /&gt;
 specified &amp;quot;longitude&amp;quot;, &amp;quot;latitude&amp;quot; and &amp;quot;time&amp;quot;, respectively; the option to&lt;br /&gt;
 include as keywords was made only to make the application robust to future variable name&lt;br /&gt;
 changes.&lt;br /&gt;
&lt;br /&gt;
===CONVERT ALADIN FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 (path to aladin netcdf file)\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each Aladin property to convert in &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;...&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt; block must conform to the following variables&lt;br /&gt;
 &lt;br /&gt;
           ---ALADIN NAME---    ---MOHID NAME---&lt;br /&gt;
             soclotot            CloudCover_&lt;br /&gt;
             sohumrel            RelativeHumidity_&lt;br /&gt;
             sofluxir            NonSolarFlux_&lt;br /&gt;
             sosspres            AtmosphericPressure_&lt;br /&gt;
             sosolarf            SolarRadiation_&lt;br /&gt;
             sotemair            AirTemperature_&lt;br /&gt;
             sowinmod            WindModulus_&lt;br /&gt;
             sowaprec            Precipitation_&lt;br /&gt;
             sozotaux            WindStressX_&lt;br /&gt;
             sometauy            WindStressY_&lt;br /&gt;
             sowindu10           WindVelocityX_&lt;br /&gt;
             sowindv10           WindVelocityY_&lt;br /&gt;
&lt;br /&gt;
===CONVERT MM5 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MM5 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of MM5 file)&lt;br /&gt;
 TERRAIN_FILENAME          : ... (path/name of MM5 TERRAIN file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of MM5 data to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP                 : 0/1 (1 = compute and write mean sea level pressure field; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of MM5 properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of MM5 property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each MM5 property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must&lt;br /&gt;
 conform to the MOHID designation specified in code of ModuleGlobalData; the correspondence is &lt;br /&gt;
 the following (see [[Module_InterfaceWaterAir]] for a more detailed explanation).&lt;br /&gt;
 &lt;br /&gt;
           ---MM5 NAME---    ---MOHID NAME---&lt;br /&gt;
             T2             air temperature&lt;br /&gt;
             PSTARCRS       atmospheric pressure&lt;br /&gt;
             U10            wind velocity X&lt;br /&gt;
             V10            wind velocity Y&lt;br /&gt;
             UST            wind shear velocity&lt;br /&gt;
             LHFLUX         latent heat&lt;br /&gt;
             SWDOWN         sensible heat&lt;br /&gt;
             SWDOWN         solar radiation&lt;br /&gt;
             LWDOWN         infrared radiation&lt;br /&gt;
             SWOUT          top outgoing shortwave radiation&lt;br /&gt;
             LWOUT          top outgoing longwave radiation&lt;br /&gt;
             SOIL T 1       soil temperature layer 1&lt;br /&gt;
             SOIL T 1       soil temperature layer 2&lt;br /&gt;
             SOIL T 1       soil temperature layer 3&lt;br /&gt;
             SOIL T 1       soil temperature layer 4&lt;br /&gt;
             SOIL T 1       soil temperature layer 5&lt;br /&gt;
             SOIL T 1       soil temperature layer 6&lt;br /&gt;
             Q2             2-meter mixing ratio&lt;br /&gt;
             TSEASFC        sea water temperature&lt;br /&gt;
             PBL HGT        PBL height&lt;br /&gt;
             PBL REGIME     PBL regime&lt;br /&gt;
             RAIN CON       accumulated convective precipitation        (cm)&lt;br /&gt;
             RAIN NON       accumulated non-convective precipitation    (cm)&lt;br /&gt;
             GROUND T       ground temperature&lt;br /&gt;
             RES TEMP       infinite reservoir slab temperature&lt;br /&gt;
             U              wind velocity X_3D&lt;br /&gt;
             V              wind velocity Y_3D&lt;br /&gt;
             W              wind velocity Z_3D&lt;br /&gt;
             T              air temperature_3D&lt;br /&gt;
             PP             atmospheric pressure_3D&lt;br /&gt;
             Q              mixing ratio_3D&lt;br /&gt;
             CLW            cloud water mixing ratio_3D&lt;br /&gt;
             RNW            rain water mixing ratio_3D&lt;br /&gt;
             ICE            cloud ice mixing ratio_3D&lt;br /&gt;
             SNOW           snow mixing ratio_3D&lt;br /&gt;
             RAD TEND       atmospheric radiation tendency_3D&lt;br /&gt;
&lt;br /&gt;
===CONVERT WRF FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                       : CONVERT WRF FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                     : ... (path/name of WRF file)&lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of WRF data&lt;br /&gt;
                                     to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP_MM5             : 0/1 (1 = compute mean sea level pressure with MM5toGrads algorithm; 1 = default)&lt;br /&gt;
 COMPUTE_MSLP_WRF             : 0/1 (1 = compute mean sea level pressure with ARWPost algorithm; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 OUTPUT_DT                    : real (DT interval in seconds between each output; default = 0.0)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
  &lt;br /&gt;
 - the name of each property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must conform to the MOHID &lt;br /&gt;
   designation specified in code of ModuleGlobalData; the correspondence to WRF is in function &lt;br /&gt;
   VariableIsToRead in ModuleWRFFormat. Conversion is not direct since WRF outputs tendencies and not  &lt;br /&gt;
   total values. &lt;br /&gt;
 &lt;br /&gt;
 - Caution: This action is not extensively tested.&lt;br /&gt;
&lt;br /&gt;
===CONVERT MERCATOR FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION               : 1/2/3/4 (version of MERCATOR files)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 1:)&lt;br /&gt;
 BASE_BULLETIN             : ...&lt;br /&gt;
 DATES_FILE                : ...&lt;br /&gt;
 NUM_DATES                 : ... &lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 2/3:)&lt;br /&gt;
 INPUT_GRID_FILENAME       : ... (path/name of file with horizontal discretization of water&lt;br /&gt;
                                  properties and water level data)&lt;br /&gt;
 (if READ_OPTION : 2:)&lt;br /&gt;
 INPUT_GRID_FILENAME_U     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component U data)&lt;br /&gt;
 INPUT_GRID_FILENAME_V     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component V data)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 3:)&lt;br /&gt;
 INPUT_BATHY_FILENAME      : ... (path/name of file with bathymetry)&lt;br /&gt;
     &lt;br /&gt;
 (if READ_OPTION : 3/4:)&lt;br /&gt;
 CALC_BAROTROPIC_VEL       : 0/1 (1 = calculate barotropic velocity, 0 = not calculate; &lt;br /&gt;
                                  default = 0)&lt;br /&gt;
 &lt;br /&gt;
 (if CALC_BAROTROPIC_VEL : 1 and READ_OPTION : 3:)&lt;br /&gt;
 INPUT_MESH_ZGRID_FILENAME : ... (path/name of file with information about layers ticknesses)&lt;br /&gt;
 &lt;br /&gt;
 (block of MERCATOR data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of MERCATOR NetCDF data file, one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT LEVITUS FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT LEVITUS FORMAT&lt;br /&gt;
  &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Levitus data: &amp;quot;monthly&amp;quot;/&amp;quot;annual&amp;quot;; default is&lt;br /&gt;
                                  &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Levitus grid)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
 &lt;br /&gt;
 (block for each water property to be present in output HDF5 file, can be several)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property)&lt;br /&gt;
 ANNUAL_FILE               : ... (path/name of Levitus annual file)&lt;br /&gt;
 &lt;br /&gt;
 (block of Levitus data files)&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of Levitus data file (e.g. a monthly data file), one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT HELLERMAN ROSENSTEIN ASCII===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
  &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Hellerman Rosenstein data: &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Hellerman&lt;br /&gt;
                                  Rosenstein grid: default and only allowed value is &amp;quot;2.&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
   &lt;br /&gt;
 (block for each Hellerman Rosenstein data file)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property: &amp;quot;wind stress X&amp;quot;/&amp;quot;wind stress Y&amp;quot;)&lt;br /&gt;
 FILE                      : ... (path/name Hellerman Rosenstein file)&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CONVERT GENERIC NETCDF CF===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION              : CONVERT NETCDF CF TO HDF5 MOHID       &lt;br /&gt;
 HDF5_OUT            : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 OUTPUTFILENAME      : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)&lt;br /&gt;
 OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property for time, generally &amp;quot;time&amp;quot;&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT     : ... (name of the netcdf property for latitude, generally &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_LONG    : ... (name of the netcdf property for longitude, generally &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_MAPPING : ... (name of the netcdf field where is located the mapping 0 water 1 land)&lt;br /&gt;
                           (It can also be used any field, i.e. temperature)&lt;br /&gt;
 MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus &amp;gt;0.5 water)&lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER   : real (number of netcdf properties) &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property&lt;br /&gt;
 NAME                : name of the HDF5 Mohid property&lt;br /&gt;
 UNITS               : property units&lt;br /&gt;
 DESCRIPTION         : property description&lt;br /&gt;
 DIM                 : 2/3 Number of property dimensions &lt;br /&gt;
 VECTOR_INTENSITY    : 0/1 If property corresponds to a vector intensity&lt;br /&gt;
 VECTOR_X            : Decomposition of Vector Intensity X&lt;br /&gt;
 VECTOR_Y            : Decomposition of Vector Intensity Y&lt;br /&gt;
 BEAUFORT_SCALE      : 0/1 If property correspond to the beaufort scale&lt;br /&gt;
 ADD_FACTOR          : To add the property a fixed value&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 path to netcdf cf file&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT SEASONDE RADAR FORMAT ===&lt;br /&gt;
&amp;lt;begin_file&amp;gt;&lt;br /&gt;
ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
&lt;br /&gt;
!HDF5 path and filename that will contain the results&lt;br /&gt;
OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
&lt;br /&gt;
!griddata path and filename that will contain a griddata of the proxy bathymetry used in the hdf5 output file.&lt;br /&gt;
OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
&lt;br /&gt;
!Path and filename to the grid that maps the radar data. This grid must be constructed with the [[GIS]]&lt;br /&gt;
!or MOHID Studio and must &amp;quot;fit&amp;quot; well where the points stand.&lt;br /&gt;
INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
&lt;br /&gt;
!This is the version of the grid used by the seasonde radar system.&lt;br /&gt;
!If the grid version of the seasonde radar changes, then most likely a new input grid must be&lt;br /&gt;
!constructed with the GIS or MOHID Studio.&lt;br /&gt;
IH_GRID_VERSION           : 4&lt;br /&gt;
&lt;br /&gt;
!This is a list with the Seasonde radar ascii data files. One file per instant.&lt;br /&gt;
&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Samples==&lt;br /&gt;
All sample files are named ''ConvertToHDF5Action.dat''.&lt;br /&gt;
&lt;br /&gt;
===Glue several MOHID(.hdf5) files===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : SurfaceHydro_OP.hdf5&lt;br /&gt;
  &lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_21.hdf5&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_22.hdf5&lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 2D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME           : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
  &lt;br /&gt;
 START                    : 2006 6 21 17 22 30&lt;br /&gt;
 END                      : 2006 6 22 17 22 0&lt;br /&gt;
  &lt;br /&gt;
 FATHER_GRID_FILENAME     : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME        : TagusConstSpacing.dat&lt;br /&gt;
  &lt;br /&gt;
 BASE_GROUP               : /Results/Oil/Data_2D&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 3D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 1&lt;br /&gt;
 FATHER_FILENAME         : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME          : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2006 6 21 17 22 30&lt;br /&gt;
 END                     : 2006 6 22 17 22 0&lt;br /&gt;
 &lt;br /&gt;
 FATHER_GRID_FILENAME    : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP              : /Results/Oil/Data_2D&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D         : 1&lt;br /&gt;
 FATHER_GEOMETRY         : D:\Projectos\MohidRun\test\data\Geometry_1.dat&lt;br /&gt;
 NEW_GEOMETRY            : TagusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME      : Aux_GridRegular.hdf5&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Patch several MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 3&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2005 2 28 13 0 0&lt;br /&gt;
 END                     : 2005 3 1 13 0 0&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 3&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D1.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid1.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 2&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D2.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid2.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 1&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D3.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid3.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME          : MM5Forcing.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME       : K:\Simula\GeneralData\Batim\CostaPortuguesa.dat&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert an ERA40 file to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                  : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                : D:\Aplica\ERA40\1971ERA1973.nc&lt;br /&gt;
 OUTPUTFILENAME          : D:\Aplica\ERA40\1971ERA1973T2&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII        : 0&lt;br /&gt;
 CONVERT_TO_HDF5         : 1&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE             : longitude&lt;br /&gt;
 YY_VARIABLE             : latitude&lt;br /&gt;
 TIME_VARIABLE           : time&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a MM5 file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : MMOUT_DOMAIN2&lt;br /&gt;
 TERRAIN_FILENAME          : TERRAIN_DOMAIN2&lt;br /&gt;
 OUTPUTFILENAME            : D2.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : D2.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 !START                     : 2010 02 15 00 00 00&lt;br /&gt;
 !END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a WRF file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : wrfout_d01_2010-02-15_00.nc&lt;br /&gt;
 OUTPUTFILENAME            : wrfout_d01.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : wrfout_d01.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 START                     : 2010 02 15 00 00 00&lt;br /&gt;
 END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Mercator-Ocean(.nc) to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION              : 2&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Psy2v2r1v_R20060628/MercatorR20060628.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : Psy2v2r1v_R20060628/MercatorGridR20060628.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : Psy2v2r1v_R20060628/MercatorGeometryR20060628.dat&lt;br /&gt;
 &lt;br /&gt;
 INPUT_GRID_FILENAME      : GridFiles/ist_meteog-gridT.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_U    : GridFiles/ist_meteog-gridU.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_V    : GridFiles/ist_meteog-gridV.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060621_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060622_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060623_R20060628.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Levitus format to MOHID(.hdf5) and interpolate grid===&lt;br /&gt;
==== Convert ====&lt;br /&gt;
First convert the Levitus ASCII format to a raw HDF5 format:&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT LEVITUS FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Levitus.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : LevitusGeometry.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 0.25&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -16.0  31&lt;br /&gt;
 UPPER_RIGHT_CORNER       :   1.   40&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : salinity&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : temperature&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Temp\t000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Extrapolate ====&lt;br /&gt;
Then extrapolate the data (still in the raw HDF5 format):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME          : Levitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : LevitusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxLeviTusAllPointsWithData.hdf5&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 EXTRAPOLATE_2D           : 2&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Interpolate ====&lt;br /&gt;
Finally, interpolate to the final grid and geometry (same as the [[#Interpolate 3D MOHID(.hdf5) files to a new grid| Interpolate 3D sample]]):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 OUTPUTFILENAME           : CadizMonthlyLevitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 NEW_GRID_FILENAME        : Algarve0.02SigmaSmooth_V3_CartMoreLayers.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : Geometry_1.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxCadizMonthlyLevitus.hdf5&lt;br /&gt;
 AUX_GRID_FILENAME        : Aux12km.dat&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the programme may construct a new bathymetry twice. Use this bathymetry only on the AUX_GRID_FILENAME keyword.&lt;br /&gt;
&lt;br /&gt;
===Convert Hellerman Rosenstein ASCII format to MOHID(.hdf5)  ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : ClimatologicWindStress.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : ClimatologicWindStressGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 2.&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -180  -90&lt;br /&gt;
 UPPER_RIGHT_CORNER       : 180  90&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress X&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUXX.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress Y&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUYY.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert ALADIN(.nc) format to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKPRES_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKSOLAR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKTAIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKWIND_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_FLUXPRE_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSU_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSV_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_U10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_V10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKHUMI_OPASYMP_19723_20088.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Convert generic Netcdf CF to MOHID(.hdf5)  ===&lt;br /&gt;
&lt;br /&gt;
This sample is for converting a typical GFS file&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION : CONVERT NETCDF CF TO HDF5 MOHID&lt;br /&gt;
 HDF5_OUT : 1&lt;br /&gt;
 OUTPUTFILENAME : ..\..\data\hdf5\GFS.hdf5&lt;br /&gt;
 NETCDF_OUT : 1&lt;br /&gt;
 OUTPUT_NETCDF_FILE : ..\..\data\netcdf\GFS.nc&lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : time&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT : latitude&lt;br /&gt;
 NETCDF_NAME_LONG : longitude&lt;br /&gt;
 NETCDF_NAME_MAPPING : TMP_10mb&lt;br /&gt;
 MAPPING_LIMIT : -10000&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER : 6 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : PRMSL_meansealevel&lt;br /&gt;
 NAME : atmospheric pressure&lt;br /&gt;
 UNITS : Pa&lt;br /&gt;
 DESCRIPTION : GFS&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : UGRD_10mb&lt;br /&gt;
 NAME : wind velocity X&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : VGRD_10mb&lt;br /&gt;
 NAME : wind velocity Y&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus&lt;br /&gt;
 NAME                     : wind modulus &lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 VECTOR_INTENSITY         : 1&lt;br /&gt;
 VECTOR_X                 : wind velocity X&lt;br /&gt;
 VECTOR_Y                 : wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus_beaufort &lt;br /&gt;
 NAME                     : wind modulus beaufort &lt;br /&gt;
 UNITS : beaufort scale&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 BEAUFORT_SCALE           : 1&lt;br /&gt;
 VECTOR_X                 : wind modulus&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : TMP_2maboveground&lt;br /&gt;
 NAME : air temperature&lt;br /&gt;
 UNITS : oC&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 ADD_FACTOR  : -273&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ..\..\data\netcdf\gfs_4_20111115.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
=== Convert Seasonde RADAR data sample configuration file===&lt;br /&gt;
The input grid file must be created to be the recipient of the data in the ascii files.&lt;br /&gt;
To create this grid, it is recommended to convert manually, resorting to a good text editor, such as Notepad++, a few radar ascii files into the [[xyz]] Mohid format, then load them in the [[GIS]] or [[Mohid Studio]], and from there create and save a regular grid that fits the points. Use that grid to convert the data into one hdf5 file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;begin_file&amp;gt;&lt;br /&gt;
ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
&lt;br /&gt;
OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
IH_GRID_VERSION           : 4&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_30_1400.tuv.txt&lt;br /&gt;
&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
&amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OceanColor modules compilation ==&lt;br /&gt;
Compiling the [[ConvertToHDF5]] tool with the OceanColor modules is more complicated than one might expect. A solution is proposed here for a release version using the Compaq Visual Fortran 6.6c. The difficulties rise because C code is embedded with a fortran interface and also, extra libraries such as hdf4 are required.&lt;br /&gt;
&lt;br /&gt;
=== Pre-requisites ===&lt;br /&gt;
&lt;br /&gt;
This is a list of prerequisites to successfully compile the tool:&lt;br /&gt;
*Compaq Visual Fortran 6.5 with patch 6.6c,&lt;br /&gt;
*VS .NET 2003 (Vc7 in particular),&lt;br /&gt;
*Hdf5 libraries ('''hdf5.lib''' '''hdf5_fortran.lib''' '''hdf5_hl.lib'''),&lt;br /&gt;
*Netcdf libraries ('''netcdf.lib''' '''netcdf_.lib'''),&lt;br /&gt;
*Hdf4 libraries ('''hd421.lib''', '''hm421.lib'''),&lt;br /&gt;
*szlib, zlib and jpeg libraries ('''szlib.lib''', '''zlib.lib''' and '''libjpeg.lib'''),&lt;br /&gt;
*the fortran source files ('''ModuleConvertModisL2.F90 ModuleConvertModisL3.F90 ModuleConvertOceanColorL2.F90'''),&lt;br /&gt;
*the C source files and their fortran interface files ('''readL2scan.c readL2Seadas.c''' and '''cdata.f crossp.f fgeonav.f''').&lt;br /&gt;
&lt;br /&gt;
=== CVF IDE configuration ===&lt;br /&gt;
# Configure everything as specified in [[Compiling with CVF]].&lt;br /&gt;
# Add the source files listed in the prerequisites above to the source files listing.&lt;br /&gt;
# Go to '''Tools--&amp;gt;Options...--&amp;gt;Directories'''. There, add the '''$DOTNET2K3/Vc7/bin''' to the '''Executable files''''; the '''$DOTNET2K3/Vc7/include''' and '''$DOTNET2K3/Vc7/PlatformSDK/include''' to the '''Include files'''; and finally, the '''$DOTNET2K3/Vc7/lib''', '''$DOTNET2K3/Vc7/PlatformSDK/lib''' and  '''$DOTNET2K3/Vc7/PlatformSDK/bin''' to the '''Library files'''.&lt;br /&gt;
# Go to '''Projects--&amp;gt;Settings--&amp;gt;Release--&amp;gt;Link--&amp;gt;Input'''. There, add the following libraries: '''netcdf.lib netcdf_.lib hd421.lib hm421.lib libjpeg.lib'''. (Make sure the hdf5 libraries as well as the szlib and zlib libraries are already mentioned).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshoots ===&lt;br /&gt;
'''Q: I get unresolved external references during linkage, but I have all the libraries mentioned above included. What should I do?'''&lt;br /&gt;
&lt;br /&gt;
A: Unresolved external references can come out for two reasons:&lt;br /&gt;
#you didn't specified all the libraries required or all the paths for the default libraries or,&lt;br /&gt;
#[http://en.wikipedia.org/wiki/Name_decoration name mangling] problems. Use the [[dumpbin]] utility to the libraries to checkout which language convention they are using. If that's the problem then you need to try to get new libraries with the correct naming convention.&lt;br /&gt;
&lt;br /&gt;
That's it, you should now be able to build the [[ConvertToHdf5]] project successfully.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Q: I got a message saying the entry point _NF_PUT_ATT_REAL@28 could not be located in netcdf.dll'''&lt;br /&gt;
&lt;br /&gt;
A: copy the file netcdf.dll to the exe folder&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF5 Homepage]&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF4 Homepage]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
*[[Module_Atmosphere]]&lt;br /&gt;
*[[Module_InterfaceWaterAir]]&lt;br /&gt;
*[[Coupling_Water-Atmosphere_User_Manual]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Hdf5]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6288</id>
		<title>ConvertToHDF5</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6288"/>
				<updated>2012-06-05T13:25:54Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Samples */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''ConvertToHDF5''' is an application which allows the making of several operations, called '''actions''', involving HDF5 files: conversion of data in other formats (e.g. NETCDF) to HDF5, grid interpolation, concatenation of several files.&lt;br /&gt;
&lt;br /&gt;
Running options for this application are specified by the user in a input file named [[ConvertToHDF5#Input file (ConvertToHDF5Action.dat)|'''ConvertToHDF5Action.dat''']]. Several actions can be specified in the same input file, being processed sequentially by the ConvertToHDF5 application.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
The operations involving HDF5 files performed by ConvertToHDF5, specified individually by an action, can be organized in:&lt;br /&gt;
&lt;br /&gt;
* [[#file management|file management]]&lt;br /&gt;
* [[#grid interpolation|grid interpolation]] and &lt;br /&gt;
* [[#format conversion|format conversion]]. &lt;br /&gt;
&lt;br /&gt;
These types and the respective actions are detailed in the next sections. &lt;br /&gt;
&lt;br /&gt;
The input file specification for each action can be found bellow in the [[#Input file (ConvertToHDF5Action.dat)|Input file (ConvertToHDF5Action.dat)]] section.&lt;br /&gt;
&lt;br /&gt;
==File management==&lt;br /&gt;
&lt;br /&gt;
===Glue files===&lt;br /&gt;
This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 files to be glued. &amp;quot;Grid&amp;quot; and &amp;quot;Results&amp;quot; data groups should be equal in all these files.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with glued &amp;quot;Results&amp;quot; data. &amp;quot;Residual&amp;quot; and &amp;quot;Statistics&amp;quot; HDF5 data groups are not copied to the output file since they are time period specific (different values potentially occour in each file). General statistics can be calculated for the glued HDF5 file data using tool [[HDF5Statistics]].&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Grid interpolation==&lt;br /&gt;
&lt;br /&gt;
===Interpolate files===&lt;br /&gt;
This action performs the conversion of one HDF5 file data existing in one 2D or 3D spatial grid to another 2D or 3D spatial grid, creating a new HDF5 file. The interpolation is performed only for the data located a time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
The HDF5 file containing data to be interpolated is called the '''father file'''.&lt;br /&gt;
&lt;br /&gt;
In case of 3D interpolation the application conducts first the horizontal grid interpolation&lt;br /&gt;
(keeping father geometry) and only after it conducts the vertical interpolation (from father geometry to new geometry).&lt;br /&gt;
&lt;br /&gt;
Several types of 2D interpolation are available for use: bilinear, spline 2D and triangulation.&lt;br /&gt;
For vertical interpolation (used in 3D interpolation) can be supplied several polinomial degrees for interpolation.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data for forcing or providing initial conditions for a MOHID Water model, e.g. a meteorological forcing file.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
For 2D/3D interpolation:&lt;br /&gt;
&lt;br /&gt;
- father HDF5 file;&lt;br /&gt;
&lt;br /&gt;
- father horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
For 3D interpolation also needed:&lt;br /&gt;
&lt;br /&gt;
- father vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- auxiliary horizontal data grid, in a grid data file in the format supported by MOHID; this file is used for horizontal grid interpolation in 3D interpolation operations.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with interpolated data. In case of 3D interpolation also produced an auxiliary HDF5 file with the result of the horizontal grid interpolation, which can be inspected to check if this operation is well performed.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].&lt;br /&gt;
&lt;br /&gt;
===Patch files===&lt;br /&gt;
This action consists in performing an interpolation of HDF5 data between grids, as in action [[#Interpolate files|Interpolate files]], but considering more than one HDF5 file as containing data to be interpolated to the new grid and a priority scale. The interpolation is performed only for the data located in the time window specified by the user. The present version of this action operates only on 2D data.&lt;br /&gt;
&lt;br /&gt;
Each HDF5 file containing data to be interpolated is called a '''father file''' and has an user-attributed '''priority level''' to be respected in the interpolation process: for each new grid cell the ConvertToHDF5 application will look for data first on the Level 1 father file and only in the case this data is inexistent will it look for data in Level 2 file, proceeding in looking for higher level files if no data is found subsequentely.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
To obtain an HDF5 file with data from several HDF5 files each containing data with different spatial resolution and only for a specific part of the new grid. This is, for instance, the case when one is preparing a best resolution meteorological HDF5 file for forcing MOHID Water from several meteorological model domains, having different spatial resolution and span, since the best resolution data is not available for all new grid cells.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
The new horizontal data grid, in a grid data file in the format supported by MOHID, and for each father file:&lt;br /&gt;
&lt;br /&gt;
- level of priority: 1 = maximum priority, priority decreases with increasing level value;&lt;br /&gt;
&lt;br /&gt;
- data grid, in the form of a grid data file in the format supported by MOHID.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with patched data.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#PATCH HDF5 FILES|PATCH HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Format conversion==&lt;br /&gt;
&lt;br /&gt;
===Meteorological model data===&lt;br /&gt;
Mohid does not simulate explicitly the atmosphere, but needs information about atmospheric properties in time and space. This requires that atmospheric properties are supplied to MOHID Water in supported formats. These formats can be derived from meteorological data in HDF5 format. Because the results of meteorological models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the MM5 and the ERA40. These are succintly detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''ERA40''====&lt;br /&gt;
This format refers to the European Centre for Medium-Range Weather Forecasts (ECMWF) 40 years re-analysises results, acessed by site http://data.ecmwf.int/data/d/era40_daily/. This data is available for several meteorological variables with maximum 6 hour periodicity for days in the period from 1957-09-01 to 2002-08-31. &lt;br /&gt;
&lt;br /&gt;
ERA40 data files are supplied by ECMWF in a NetCDF format and with an user-costumized time window, periodicity (time step range from 6 hours to a day) and meteorological properties set. The ERA40 meteorological properties which are recognized by MOHID are presented bellow together with the correspondent MOHID name: &lt;br /&gt;
&lt;br /&gt;
 ---ERA40 NAME---         ---MOHID NAME---&lt;br /&gt;
   sshf                     sensible heat                &lt;br /&gt;
   slhf                     latent heat                  &lt;br /&gt;
   msl                      atmospheric pressure &lt;br /&gt;
   tcc                      cloud cover &lt;br /&gt;
   p10u                     wind velocity X&lt;br /&gt;
   p10v                     wind velocity Y&lt;br /&gt;
   p2t                      air temperature&lt;br /&gt;
   ewss                     wind stress X&lt;br /&gt;
   nsss                     wind stress Y&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to all MOHID Water recognized property available in the ERA40 file, producing an individual HDF5 file for each property. The name of each HDF5 file generated includes the ERA40 meteorological property identificator correspondent to the data contained.&lt;br /&gt;
&lt;br /&gt;
Alternatively, ConvertToHDF5 can copy to a single ASCII file the heading information concerning each meteorological variable considered in the original ERA40 file.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data suitable for being used for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ERA40 NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file for each meteorological property contained in the original NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ERA40 FORMAT|CONVERT ERA40 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Aladin''====&lt;br /&gt;
This format relates to Aladin meteorological model results. Some of the atmospheric property needed by MOHID Water is present in Aladin output files, enabling to run prediction simulations with MOHID Water when access to Aladin prevision files is available.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts Aladin results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Aladin netcdf results file to convert.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with Aladin results and a grid data file in MOHID format with the Aladin grid pseudo-information: a fake orography is created of 100 m depth.&lt;br /&gt;
This last file can be used to interpolate the Aladin data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ALADIN FORMAT|CONVERT ALADIN FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MM5''====&lt;br /&gt;
This format relates to the Fifth-Generation NCAR / Penn State Mesoscale Model (MM5) output files format. Almost every atmospheric property needed by MOHID Water is present in MM5 output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts MM5 results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the MM5 files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
For conversion to be completed it is required the horizontal grid information of MM5 results which is available in special TERRAIN files.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
MM5 results file to convert and MM5 TERRAIN file. The TERRAIN file supplies the MM5 results grid information. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
A HDF5 file with MM5 results and a grid data file in MOHID format with the MM5 grid information.&lt;br /&gt;
This last file can be used to interpolate the MM5 data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MM5 FORMAT|CONVERT MM5 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''WRF''====&lt;br /&gt;
This format relates to the Weather Research and Forecast model (WRF) output files format. Almost every atmospheric property needed by MOHID Water is present in WRF output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts WRF results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the WRF properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the WRF files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
WRF direct output file.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with WRF results and a grid data file in MOHID format with the WRF grid information.&lt;br /&gt;
This last file can be used to interpolate the WRF data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! [[PROJ4 | PROJ4]] library is needed! See [[#Compile_ModuleWRFFormat |  Compile_ModuleWRFFormat]]&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT WRF FORMAT|CONVERT WRF FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Wave model data===&lt;br /&gt;
Mohid does not simulate explicitly the wave dynamics, but needs information about wave properties in time and space. This requires that wave properties are supplied to MOHID Water in supported formats. These formats can be derived from wave data in HDF5 format. Because the results of wave models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the table format of SWAN. This is succintly detailed in the next section.&lt;br /&gt;
&lt;br /&gt;
====''SWAN''====&lt;br /&gt;
SWAN data files are supplied in a ASCII format. The data is organized by time instant. For each time instant there is a table of data. Each column represents one property. &lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to gradients of wave stresses X and Y, mean amplitude, mean period and mean direction.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 SWAN data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ASCII (table type) SWAN results data files and bathymetry in MOHID grid data foramt. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (wave stresses X and Y, mean amplitude, mean period and mean direction). &lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT TO AND FROM SWAN|CONVERT TO AND FROM SWAN]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Ocean model data===&lt;br /&gt;
Ocean model data, available in diverse formats, can be used by MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation. These uses require that the model data is in HDF5 format and conversion is therefore needed.&lt;br /&gt;
&lt;br /&gt;
Currently the large scale ocean models formats convertible into HDF5 by ConvertToHDF5 includes MERCATOR.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MERCATOR''====&lt;br /&gt;
MERCATOR data files are supplied in a NetCDF format and with an user-costumized spatial window and periodicity. Water level and water properties (temperature and salinity) data is available in type T files, velocity component u data is available in type U files and velocity component v data is available in type V files. The type of data of a specific MERCATOR file is generally indicated in the file name.&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to temperature, salinity, water level, component u of velocity and component v of velocity.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 MERCATOR data usable for forcing or validation of MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
NetCDF MERCATOR results data files and NetCDF MERCATOR grid data files. It should be provided one grid data file of each type: T, U and V. These are generally provided by the MERCATOR services together with the results files.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (temperature, salinity, water level, velocity u and velocity v) and the correspondent grid data and geometry files, containing respectively the horizontal grid and the vertical discretization of the HDF5 file. The grid data and geometry files can be used afterwards to interpolate the MERCATOR data to another grid and geometry (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MERCATOR FORMAT|CONVERT MERCATOR FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Climatological data===&lt;br /&gt;
Climatological data can be used in MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation, in case more realistic data (measurements or model) data is unavailable. This data is generally supplied by producers in formats not readly usable by MOHID Water which justifies the existence of a conversion tool.&lt;br /&gt;
&lt;br /&gt;
Two climatological data format conversions are implemented in ConvertToHDF5: Levitus ocean data and Hellerman Rosenstein meteorological data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''Levitus''====&lt;br /&gt;
The Levitus climatology provides results for water temperature and salinity.&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window requested by the user. &lt;br /&gt;
Typically, it requires 3 steps to complete the task:&lt;br /&gt;
&lt;br /&gt;
- convert levitus format &lt;br /&gt;
&lt;br /&gt;
- extrapolate the data to the whole levitus domain(required to avoid uncoincidental coastlines) &lt;br /&gt;
&lt;br /&gt;
- interpolate with the model grid(bathymetry)&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as boundary forcing and/or initial condition specification in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Levitus climatological data files, one per property and per time period (e.g a month).&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Levitus climatological data, grid data file with the horizontal&lt;br /&gt;
grid of the data and a geometry file with vertical discretization of the data (MOHID formats).&lt;br /&gt;
The grid data and the geometry files can be used to interpolate the climatological data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT LEVITUS FORMAT|CONVERT LEVITUS FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Hellerman Rosenstein''====&lt;br /&gt;
This is a meteorological climatology providing wind stress. There is a file per wind stress component. Since the data refer to surface values it is a 2D field.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window provided by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as meteorological forcing in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Hellerman Rosenstein climatological data ASCII files, one per wind stress component.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Hellerman Rosenstein climatological data and grid data file with the horizontal&lt;br /&gt;
grid of the climatological data. This grid data file can be used to interpolate the climatological data from the original horizontal grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT HELLERMAN ROSENSTEIN ASCII|CONVERT HELLERMAN ROSENSTEIN ASCII]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''World Ocean Atlas 2005''====&lt;br /&gt;
The World Ocean Atlas (WOA) 2005 climatology provides results for water temperature, salinity and several water quality and biology properties.&lt;br /&gt;
&lt;br /&gt;
Description, Action and Input Files are described in a separate page: [[ConvertToHDF5 WOA2005]].&lt;br /&gt;
&lt;br /&gt;
===Generic NETCDF CF FILES===&lt;br /&gt;
&lt;br /&gt;
Converts any netcdf file following the CF convention into Mohid HDF5 files. Check the [[ConvertToHDF5#CONVERT_GENERIC_NETCDF_CF | Input File]] and [[ConvertToHDF5#Convert_generic_Netcdf_CF_to_MOHID.28.hdf5.29 | Sample File]].&lt;br /&gt;
&lt;br /&gt;
===Radar data===&lt;br /&gt;
====Seasonde RADAR Data====&lt;br /&gt;
Converts a list of ascii files from the Seasonde radar data, which measures currents over a given region of space, into an hdf5 file with the MOHID format. Useful to validate coastal and estuarine models where radars are located.&lt;br /&gt;
&lt;br /&gt;
==Input file (ConvertToHDF5Action.dat)==&lt;br /&gt;
===General structure===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt; (block containing instructions for running a specific action) &lt;br /&gt;
 ACTION                    : ... (intended action)&lt;br /&gt;
 ... (action specific instructions)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : ...&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GLUES HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 3D_FILE                   : 0/1 (0 = 2D file, 1 = 3D file)&lt;br /&gt;
 &lt;br /&gt;
 TIME_GROUP                : ... (Default=&amp;quot;Time&amp;quot;. Other option: &amp;quot;SurfaceTime&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (Default=&amp;quot;Results&amp;quot;. Other options: &amp;quot;Residual&amp;quot;, &amp;quot;SurfaceResults&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 &lt;br /&gt;
 (block of HDF5 data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of HDF5 file with data to be included in glue, one per line, at least two files)&lt;br /&gt;
 ...                      &lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===INTERPOLATE GRIDS===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of horizontal interpolation: 1 = Bilinear, 2 = Spline2D,&lt;br /&gt;
                                  3 = Triangulation)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION_WINDOW      : ... ... ... ... (2D spatial window to consider for interpolation: &lt;br /&gt;
                                              Xmin Ymin Xmax Ymax; default = all domain)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D           : 0/1 (0 = 2D interpolation, 1 = 3D interpolation)&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_2D            : 0/1/2/3/4/5 (2D extrapolation: 0=no extrapolation, 1=medium&lt;br /&gt;
                                      triangulation, 2=high triangulation, &lt;br /&gt;
                                      3=nearest neighbour, 4=nearest cell, &lt;br /&gt;
                                      5=constant value)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_VALUE         : ... (name of the value to extrapolate to when EXTRAPOLATE_2D is&lt;br /&gt;
                                  set to constant value (5))&lt;br /&gt;
 &lt;br /&gt;
 DO_NOT_BELIEVE_MAP        : 0/1 (0=consider input HDF5 file map, 1=do not consider input HDF5&lt;br /&gt;
                                  file map)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (name of base group of HDF5 variables containing data to be &lt;br /&gt;
                                  interpolated; default is &amp;quot;/Results&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (if INTERPOLATION3D : 1 also required:)&lt;br /&gt;
 FATHER_GEOMETRY           : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  of input HDF5 file)&lt;br /&gt;
 NEW_GEOMETRY              : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  intended for output HDF5 file)&lt;br /&gt;
 POLI_DEGREE               : 1/... (degree of vertical interpolation: 1=linear, ...)&lt;br /&gt;
 &lt;br /&gt;
 AUX_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for auxiliar output HDF5 file;&lt;br /&gt;
                                  default is file provided in NEW_GRID_FILENAME)&lt;br /&gt;
 &lt;br /&gt;
 AUX_OUTPUTFILENAME        : ... (path/name of auxiliar output HDF5 file to contain result&lt;br /&gt;
                                  of horizontal grid interpolation)   &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the file indicated in AUX_GRID_FILENAME can be different from the one indicated in&lt;br /&gt;
   NEW_GRID_FILENAME in terms of bathymetry, while the horizontal grid should be, commonly, the&lt;br /&gt;
   same: this altered bathymetry can be used to extend the water column in the original data so&lt;br /&gt;
   that the process of vertical interpolation is done easily;&lt;br /&gt;
 &lt;br /&gt;
 - in case of INTERPOLATION3D : 1, ConvertToHDF5 can generate new versions of bathymetry which &lt;br /&gt;
   are consistent with the geometry definition (extension is '.new'); there are possibly three&lt;br /&gt;
   bathymetry changes referring to father grid, new grid and aux grid (the same bathymetry is&lt;br /&gt;
   not altered twice); although initially new and aux grid are the same they can result &lt;br /&gt;
   different because of bathymetry changes;&lt;br /&gt;
 &lt;br /&gt;
 - in case the new geometry is 2D and father geometry is 3D then POLI_DEGREE : 1 &lt;br /&gt;
   (linear interpolation) should be used;&lt;br /&gt;
 &lt;br /&gt;
 - EXTRAPOLATE_2D : 1/2/3/4/5 should be considered if it is expected that the coast line is not&lt;br /&gt;
   coincidental in the father and new grids, to avoid lack of data in the interpolation&lt;br /&gt;
   process; extrapolation is performed for all cells even the land cells; &lt;br /&gt;
 &lt;br /&gt;
 - in case of DO_NOT_BELIEVE_MAP : 1 the application generates a map based on cells where&lt;br /&gt;
   interpolation results are available; this causes that if EXTRAPOLATE_2D : 1/2/3/4/5 is used&lt;br /&gt;
   the AUX_GRID_FILENAME should not have land cells in order for the new map to be concurrent&lt;br /&gt;
   with the result of extrapolation and avoid errors generation, specially if INTERPOLATION3D :&lt;br /&gt;
   1 is considered.&lt;br /&gt;
&lt;br /&gt;
===PATCH HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of interpolation: 3 = Triangulation, default and only&lt;br /&gt;
                                  one implemented)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 (block for each father HDF5 file, should be at least two)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                     : ... (integer priority level: 1 = highest, increase for lower&lt;br /&gt;
                                  priority)&lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 N_REMOVE_FRAME            : 0   (width, in number of cells, of frame to remove)&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT ERA40 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of ERA40 NetCDF file)&lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
                                 (root of name for all files produced)&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII          : 0/1 (1 = convert variable heading info for ASCII file; 0 = default)&lt;br /&gt;
 CONVERT_TO_HDF5           : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 GRIDTO180                 : 0/1 (1 = convert grid from [0 360] to [-180 180], 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 YY_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 TIME_VARIABLE             : ... (name of time variable in the input file: usual name is&lt;br /&gt;
                                  &amp;quot;time&amp;quot;)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - either CONVERT_TO_ASCII : 1 or CONVERT_TO_HDF5 : 1 must be chosen for any action to be&lt;br /&gt;
 performed by ConvertToHDF5;&lt;br /&gt;
 &lt;br /&gt;
 - when CONVERT_TO_HDF5 : 1 an HDF5 file is produced for every variable contained in the&lt;br /&gt;
 original ERA40 file; the name of each file is composed of the name indicated on FILENAME&lt;br /&gt;
 concatenated with the ERA40 variable identifier;&lt;br /&gt;
 &lt;br /&gt;
 - to the XX_VARIABLE, YY_VARIABLE and TIME_VARIABLE keywords should generally be  &lt;br /&gt;
 specified &amp;quot;longitude&amp;quot;, &amp;quot;latitude&amp;quot; and &amp;quot;time&amp;quot;, respectively; the option to&lt;br /&gt;
 include as keywords was made only to make the application robust to future variable name&lt;br /&gt;
 changes.&lt;br /&gt;
&lt;br /&gt;
===CONVERT ALADIN FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 (path to aladin netcdf file)\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each Aladin property to convert in &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;...&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt; block must conform to the following variables&lt;br /&gt;
 &lt;br /&gt;
           ---ALADIN NAME---    ---MOHID NAME---&lt;br /&gt;
             soclotot            CloudCover_&lt;br /&gt;
             sohumrel            RelativeHumidity_&lt;br /&gt;
             sofluxir            NonSolarFlux_&lt;br /&gt;
             sosspres            AtmosphericPressure_&lt;br /&gt;
             sosolarf            SolarRadiation_&lt;br /&gt;
             sotemair            AirTemperature_&lt;br /&gt;
             sowinmod            WindModulus_&lt;br /&gt;
             sowaprec            Precipitation_&lt;br /&gt;
             sozotaux            WindStressX_&lt;br /&gt;
             sometauy            WindStressY_&lt;br /&gt;
             sowindu10           WindVelocityX_&lt;br /&gt;
             sowindv10           WindVelocityY_&lt;br /&gt;
&lt;br /&gt;
===CONVERT MM5 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MM5 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of MM5 file)&lt;br /&gt;
 TERRAIN_FILENAME          : ... (path/name of MM5 TERRAIN file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of MM5 data to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP                 : 0/1 (1 = compute and write mean sea level pressure field; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of MM5 properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of MM5 property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each MM5 property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must&lt;br /&gt;
 conform to the MOHID designation specified in code of ModuleGlobalData; the correspondence is &lt;br /&gt;
 the following (see [[Module_InterfaceWaterAir]] for a more detailed explanation).&lt;br /&gt;
 &lt;br /&gt;
           ---MM5 NAME---    ---MOHID NAME---&lt;br /&gt;
             T2             air temperature&lt;br /&gt;
             PSTARCRS       atmospheric pressure&lt;br /&gt;
             U10            wind velocity X&lt;br /&gt;
             V10            wind velocity Y&lt;br /&gt;
             UST            wind shear velocity&lt;br /&gt;
             LHFLUX         latent heat&lt;br /&gt;
             SWDOWN         sensible heat&lt;br /&gt;
             SWDOWN         solar radiation&lt;br /&gt;
             LWDOWN         infrared radiation&lt;br /&gt;
             SWOUT          top outgoing shortwave radiation&lt;br /&gt;
             LWOUT          top outgoing longwave radiation&lt;br /&gt;
             SOIL T 1       soil temperature layer 1&lt;br /&gt;
             SOIL T 1       soil temperature layer 2&lt;br /&gt;
             SOIL T 1       soil temperature layer 3&lt;br /&gt;
             SOIL T 1       soil temperature layer 4&lt;br /&gt;
             SOIL T 1       soil temperature layer 5&lt;br /&gt;
             SOIL T 1       soil temperature layer 6&lt;br /&gt;
             Q2             2-meter mixing ratio&lt;br /&gt;
             TSEASFC        sea water temperature&lt;br /&gt;
             PBL HGT        PBL height&lt;br /&gt;
             PBL REGIME     PBL regime&lt;br /&gt;
             RAIN CON       accumulated convective precipitation        (cm)&lt;br /&gt;
             RAIN NON       accumulated non-convective precipitation    (cm)&lt;br /&gt;
             GROUND T       ground temperature&lt;br /&gt;
             RES TEMP       infinite reservoir slab temperature&lt;br /&gt;
             U              wind velocity X_3D&lt;br /&gt;
             V              wind velocity Y_3D&lt;br /&gt;
             W              wind velocity Z_3D&lt;br /&gt;
             T              air temperature_3D&lt;br /&gt;
             PP             atmospheric pressure_3D&lt;br /&gt;
             Q              mixing ratio_3D&lt;br /&gt;
             CLW            cloud water mixing ratio_3D&lt;br /&gt;
             RNW            rain water mixing ratio_3D&lt;br /&gt;
             ICE            cloud ice mixing ratio_3D&lt;br /&gt;
             SNOW           snow mixing ratio_3D&lt;br /&gt;
             RAD TEND       atmospheric radiation tendency_3D&lt;br /&gt;
&lt;br /&gt;
===CONVERT WRF FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                       : CONVERT WRF FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                     : ... (path/name of WRF file)&lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of WRF data&lt;br /&gt;
                                     to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP_MM5             : 0/1 (1 = compute mean sea level pressure with MM5toGrads algorithm; 1 = default)&lt;br /&gt;
 COMPUTE_MSLP_WRF             : 0/1 (1 = compute mean sea level pressure with ARWPost algorithm; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 OUTPUT_DT                    : real (DT interval in seconds between each output; default = 0.0)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
  &lt;br /&gt;
 - the name of each property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must conform to the MOHID &lt;br /&gt;
   designation specified in code of ModuleGlobalData; the correspondence to WRF is in function &lt;br /&gt;
   VariableIsToRead in ModuleWRFFormat. Conversion is not direct since WRF outputs tendencies and not  &lt;br /&gt;
   total values. &lt;br /&gt;
 &lt;br /&gt;
 - Caution: This action is not extensively tested.&lt;br /&gt;
&lt;br /&gt;
===CONVERT MERCATOR FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION               : 1/2/3/4 (version of MERCATOR files)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 1:)&lt;br /&gt;
 BASE_BULLETIN             : ...&lt;br /&gt;
 DATES_FILE                : ...&lt;br /&gt;
 NUM_DATES                 : ... &lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 2/3:)&lt;br /&gt;
 INPUT_GRID_FILENAME       : ... (path/name of file with horizontal discretization of water&lt;br /&gt;
                                  properties and water level data)&lt;br /&gt;
 (if READ_OPTION : 2:)&lt;br /&gt;
 INPUT_GRID_FILENAME_U     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component U data)&lt;br /&gt;
 INPUT_GRID_FILENAME_V     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component V data)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 3:)&lt;br /&gt;
 INPUT_BATHY_FILENAME      : ... (path/name of file with bathymetry)&lt;br /&gt;
     &lt;br /&gt;
 (if READ_OPTION : 3/4:)&lt;br /&gt;
 CALC_BAROTROPIC_VEL       : 0/1 (1 = calculate barotropic velocity, 0 = not calculate; &lt;br /&gt;
                                  default = 0)&lt;br /&gt;
 &lt;br /&gt;
 (if CALC_BAROTROPIC_VEL : 1 and READ_OPTION : 3:)&lt;br /&gt;
 INPUT_MESH_ZGRID_FILENAME : ... (path/name of file with information about layers ticknesses)&lt;br /&gt;
 &lt;br /&gt;
 (block of MERCATOR data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of MERCATOR NetCDF data file, one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT LEVITUS FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT LEVITUS FORMAT&lt;br /&gt;
  &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Levitus data: &amp;quot;monthly&amp;quot;/&amp;quot;annual&amp;quot;; default is&lt;br /&gt;
                                  &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Levitus grid)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
 &lt;br /&gt;
 (block for each water property to be present in output HDF5 file, can be several)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property)&lt;br /&gt;
 ANNUAL_FILE               : ... (path/name of Levitus annual file)&lt;br /&gt;
 &lt;br /&gt;
 (block of Levitus data files)&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of Levitus data file (e.g. a monthly data file), one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT HELLERMAN ROSENSTEIN ASCII===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
  &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Hellerman Rosenstein data: &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Hellerman&lt;br /&gt;
                                  Rosenstein grid: default and only allowed value is &amp;quot;2.&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
   &lt;br /&gt;
 (block for each Hellerman Rosenstein data file)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property: &amp;quot;wind stress X&amp;quot;/&amp;quot;wind stress Y&amp;quot;)&lt;br /&gt;
 FILE                      : ... (path/name Hellerman Rosenstein file)&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CONVERT GENERIC NETCDF CF===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION              : CONVERT NETCDF CF TO HDF5 MOHID       &lt;br /&gt;
 HDF5_OUT            : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 OUTPUTFILENAME      : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)&lt;br /&gt;
 OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property for time, generally &amp;quot;time&amp;quot;&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT     : ... (name of the netcdf property for latitude, generally &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_LONG    : ... (name of the netcdf property for longitude, generally &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_MAPPING : ... (name of the netcdf field where is located the mapping 0 water 1 land)&lt;br /&gt;
                           (It can also be used any field, i.e. temperature)&lt;br /&gt;
 MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus &amp;gt;0.5 water)&lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER   : real (number of netcdf properties) &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property&lt;br /&gt;
 NAME                : name of the HDF5 Mohid property&lt;br /&gt;
 UNITS               : property units&lt;br /&gt;
 DESCRIPTION         : property description&lt;br /&gt;
 DIM                 : 2/3 Number of property dimensions &lt;br /&gt;
 VECTOR_INTENSITY    : 0/1 If property corresponds to a vector intensity&lt;br /&gt;
 VECTOR_X            : Decomposition of Vector Intensity X&lt;br /&gt;
 VECTOR_Y            : Decomposition of Vector Intensity Y&lt;br /&gt;
 BEAUFORT_SCALE      : 0/1 If property correspond to the beaufort scale&lt;br /&gt;
 ADD_FACTOR          : To add the property a fixed value&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 path to netcdf cf file&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Samples==&lt;br /&gt;
All sample files are named ''ConvertToHDF5Action.dat''.&lt;br /&gt;
&lt;br /&gt;
===Glue several MOHID(.hdf5) files===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : SurfaceHydro_OP.hdf5&lt;br /&gt;
  &lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_21.hdf5&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_22.hdf5&lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 2D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME           : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
  &lt;br /&gt;
 START                    : 2006 6 21 17 22 30&lt;br /&gt;
 END                      : 2006 6 22 17 22 0&lt;br /&gt;
  &lt;br /&gt;
 FATHER_GRID_FILENAME     : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME        : TagusConstSpacing.dat&lt;br /&gt;
  &lt;br /&gt;
 BASE_GROUP               : /Results/Oil/Data_2D&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 3D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 1&lt;br /&gt;
 FATHER_FILENAME         : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME          : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2006 6 21 17 22 30&lt;br /&gt;
 END                     : 2006 6 22 17 22 0&lt;br /&gt;
 &lt;br /&gt;
 FATHER_GRID_FILENAME    : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP              : /Results/Oil/Data_2D&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D         : 1&lt;br /&gt;
 FATHER_GEOMETRY         : D:\Projectos\MohidRun\test\data\Geometry_1.dat&lt;br /&gt;
 NEW_GEOMETRY            : TagusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME      : Aux_GridRegular.hdf5&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Patch several MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 3&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2005 2 28 13 0 0&lt;br /&gt;
 END                     : 2005 3 1 13 0 0&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 3&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D1.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid1.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 2&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D2.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid2.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 1&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D3.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid3.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME          : MM5Forcing.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME       : K:\Simula\GeneralData\Batim\CostaPortuguesa.dat&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert an ERA40 file to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                  : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                : D:\Aplica\ERA40\1971ERA1973.nc&lt;br /&gt;
 OUTPUTFILENAME          : D:\Aplica\ERA40\1971ERA1973T2&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII        : 0&lt;br /&gt;
 CONVERT_TO_HDF5         : 1&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE             : longitude&lt;br /&gt;
 YY_VARIABLE             : latitude&lt;br /&gt;
 TIME_VARIABLE           : time&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a MM5 file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : MMOUT_DOMAIN2&lt;br /&gt;
 TERRAIN_FILENAME          : TERRAIN_DOMAIN2&lt;br /&gt;
 OUTPUTFILENAME            : D2.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : D2.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 !START                     : 2010 02 15 00 00 00&lt;br /&gt;
 !END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a WRF file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : wrfout_d01_2010-02-15_00.nc&lt;br /&gt;
 OUTPUTFILENAME            : wrfout_d01.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : wrfout_d01.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 START                     : 2010 02 15 00 00 00&lt;br /&gt;
 END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Mercator-Ocean(.nc) to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION              : 2&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Psy2v2r1v_R20060628/MercatorR20060628.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : Psy2v2r1v_R20060628/MercatorGridR20060628.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : Psy2v2r1v_R20060628/MercatorGeometryR20060628.dat&lt;br /&gt;
 &lt;br /&gt;
 INPUT_GRID_FILENAME      : GridFiles/ist_meteog-gridT.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_U    : GridFiles/ist_meteog-gridU.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_V    : GridFiles/ist_meteog-gridV.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060621_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060622_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060623_R20060628.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Levitus format to MOHID(.hdf5) and interpolate grid===&lt;br /&gt;
==== Convert ====&lt;br /&gt;
First convert the Levitus ASCII format to a raw HDF5 format:&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT LEVITUS FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Levitus.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : LevitusGeometry.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 0.25&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -16.0  31&lt;br /&gt;
 UPPER_RIGHT_CORNER       :   1.   40&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : salinity&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : temperature&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Temp\t000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Extrapolate ====&lt;br /&gt;
Then extrapolate the data (still in the raw HDF5 format):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME          : Levitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : LevitusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxLeviTusAllPointsWithData.hdf5&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 EXTRAPOLATE_2D           : 2&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Interpolate ====&lt;br /&gt;
Finally, interpolate to the final grid and geometry (same as the [[#Interpolate 3D MOHID(.hdf5) files to a new grid| Interpolate 3D sample]]):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 OUTPUTFILENAME           : CadizMonthlyLevitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 NEW_GRID_FILENAME        : Algarve0.02SigmaSmooth_V3_CartMoreLayers.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : Geometry_1.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxCadizMonthlyLevitus.hdf5&lt;br /&gt;
 AUX_GRID_FILENAME        : Aux12km.dat&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the programme may construct a new bathymetry twice. Use this bathymetry only on the AUX_GRID_FILENAME keyword.&lt;br /&gt;
&lt;br /&gt;
===Convert Hellerman Rosenstein ASCII format to MOHID(.hdf5)  ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : ClimatologicWindStress.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : ClimatologicWindStressGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 2.&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -180  -90&lt;br /&gt;
 UPPER_RIGHT_CORNER       : 180  90&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress X&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUXX.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress Y&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUYY.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert ALADIN(.nc) format to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKPRES_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKSOLAR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKTAIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKWIND_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_FLUXPRE_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSU_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSV_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_U10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_V10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKHUMI_OPASYMP_19723_20088.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Convert generic Netcdf CF to MOHID(.hdf5)  ===&lt;br /&gt;
&lt;br /&gt;
This sample is for converting a typical GFS file&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION : CONVERT NETCDF CF TO HDF5 MOHID&lt;br /&gt;
 HDF5_OUT : 1&lt;br /&gt;
 OUTPUTFILENAME : ..\..\data\hdf5\GFS.hdf5&lt;br /&gt;
 NETCDF_OUT : 1&lt;br /&gt;
 OUTPUT_NETCDF_FILE : ..\..\data\netcdf\GFS.nc&lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : time&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT : latitude&lt;br /&gt;
 NETCDF_NAME_LONG : longitude&lt;br /&gt;
 NETCDF_NAME_MAPPING : TMP_10mb&lt;br /&gt;
 MAPPING_LIMIT : -10000&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER : 6 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : PRMSL_meansealevel&lt;br /&gt;
 NAME : atmospheric pressure&lt;br /&gt;
 UNITS : Pa&lt;br /&gt;
 DESCRIPTION : GFS&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : UGRD_10mb&lt;br /&gt;
 NAME : wind velocity X&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : VGRD_10mb&lt;br /&gt;
 NAME : wind velocity Y&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus&lt;br /&gt;
 NAME                     : wind modulus &lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 VECTOR_INTENSITY         : 1&lt;br /&gt;
 VECTOR_X                 : wind velocity X&lt;br /&gt;
 VECTOR_Y                 : wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus_beaufort &lt;br /&gt;
 NAME                     : wind modulus beaufort &lt;br /&gt;
 UNITS : beaufort scale&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 BEAUFORT_SCALE           : 1&lt;br /&gt;
 VECTOR_X                 : wind modulus&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : TMP_2maboveground&lt;br /&gt;
 NAME : air temperature&lt;br /&gt;
 UNITS : oC&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 ADD_FACTOR  : -273&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ..\..\data\netcdf\gfs_4_20111115.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
=== Convert Seasonde RADAR data sample configuration file===&lt;br /&gt;
The input grid file must be created to be the recipient of the data in the ascii files.&lt;br /&gt;
To create this grid, it is recommended to convert manually, resorting to a good text editor, such as Notepad++, a few radar ascii files into the [[xyz]] Mohid format, then load them in the [[GIS]] or [[Mohid Studio]], and from there create and save a regular grid that fits the points. Use that grid to convert the data into one hdf5 file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;begin_file&amp;gt;&lt;br /&gt;
ACTION                    : CONVERT IH RADAR FORMAT&lt;br /&gt;
&lt;br /&gt;
OUTPUTFILENAME            : IHRADAR_201205_1400.hdf5&lt;br /&gt;
OUTPUT_GRID_FILENAME      : IHRADAR_griddata.dat&lt;br /&gt;
INPUT_GRID_FILENAME       : ../IH-Radar-GridVersion4.grd&lt;br /&gt;
IH_GRID_VERSION           : 4&lt;br /&gt;
&lt;br /&gt;
&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_01_1400.tuv.txt&lt;br /&gt;
../RadarFiles/TOTL_IHOC_2012_05_30_1400.tuv.txt&lt;br /&gt;
&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
&amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OceanColor modules compilation ==&lt;br /&gt;
Compiling the [[ConvertToHDF5]] tool with the OceanColor modules is more complicated than one might expect. A solution is proposed here for a release version using the Compaq Visual Fortran 6.6c. The difficulties rise because C code is embedded with a fortran interface and also, extra libraries such as hdf4 are required.&lt;br /&gt;
&lt;br /&gt;
=== Pre-requisites ===&lt;br /&gt;
&lt;br /&gt;
This is a list of prerequisites to successfully compile the tool:&lt;br /&gt;
*Compaq Visual Fortran 6.5 with patch 6.6c,&lt;br /&gt;
*VS .NET 2003 (Vc7 in particular),&lt;br /&gt;
*Hdf5 libraries ('''hdf5.lib''' '''hdf5_fortran.lib''' '''hdf5_hl.lib'''),&lt;br /&gt;
*Netcdf libraries ('''netcdf.lib''' '''netcdf_.lib'''),&lt;br /&gt;
*Hdf4 libraries ('''hd421.lib''', '''hm421.lib'''),&lt;br /&gt;
*szlib, zlib and jpeg libraries ('''szlib.lib''', '''zlib.lib''' and '''libjpeg.lib'''),&lt;br /&gt;
*the fortran source files ('''ModuleConvertModisL2.F90 ModuleConvertModisL3.F90 ModuleConvertOceanColorL2.F90'''),&lt;br /&gt;
*the C source files and their fortran interface files ('''readL2scan.c readL2Seadas.c''' and '''cdata.f crossp.f fgeonav.f''').&lt;br /&gt;
&lt;br /&gt;
=== CVF IDE configuration ===&lt;br /&gt;
# Configure everything as specified in [[Compiling with CVF]].&lt;br /&gt;
# Add the source files listed in the prerequisites above to the source files listing.&lt;br /&gt;
# Go to '''Tools--&amp;gt;Options...--&amp;gt;Directories'''. There, add the '''$DOTNET2K3/Vc7/bin''' to the '''Executable files''''; the '''$DOTNET2K3/Vc7/include''' and '''$DOTNET2K3/Vc7/PlatformSDK/include''' to the '''Include files'''; and finally, the '''$DOTNET2K3/Vc7/lib''', '''$DOTNET2K3/Vc7/PlatformSDK/lib''' and  '''$DOTNET2K3/Vc7/PlatformSDK/bin''' to the '''Library files'''.&lt;br /&gt;
# Go to '''Projects--&amp;gt;Settings--&amp;gt;Release--&amp;gt;Link--&amp;gt;Input'''. There, add the following libraries: '''netcdf.lib netcdf_.lib hd421.lib hm421.lib libjpeg.lib'''. (Make sure the hdf5 libraries as well as the szlib and zlib libraries are already mentioned).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshoots ===&lt;br /&gt;
'''Q: I get unresolved external references during linkage, but I have all the libraries mentioned above included. What should I do?'''&lt;br /&gt;
&lt;br /&gt;
A: Unresolved external references can come out for two reasons:&lt;br /&gt;
#you didn't specified all the libraries required or all the paths for the default libraries or,&lt;br /&gt;
#[http://en.wikipedia.org/wiki/Name_decoration name mangling] problems. Use the [[dumpbin]] utility to the libraries to checkout which language convention they are using. If that's the problem then you need to try to get new libraries with the correct naming convention.&lt;br /&gt;
&lt;br /&gt;
That's it, you should now be able to build the [[ConvertToHdf5]] project successfully.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Q: I got a message saying the entry point _NF_PUT_ATT_REAL@28 could not be located in netcdf.dll'''&lt;br /&gt;
&lt;br /&gt;
A: copy the file netcdf.dll to the exe folder&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF5 Homepage]&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF4 Homepage]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
*[[Module_Atmosphere]]&lt;br /&gt;
*[[Module_InterfaceWaterAir]]&lt;br /&gt;
*[[Coupling_Water-Atmosphere_User_Manual]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Hdf5]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6287</id>
		<title>ConvertToHDF5</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=ConvertToHDF5&amp;diff=6287"/>
				<updated>2012-06-05T13:21:07Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Format conversion */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The '''ConvertToHDF5''' is an application which allows the making of several operations, called '''actions''', involving HDF5 files: conversion of data in other formats (e.g. NETCDF) to HDF5, grid interpolation, concatenation of several files.&lt;br /&gt;
&lt;br /&gt;
Running options for this application are specified by the user in a input file named [[ConvertToHDF5#Input file (ConvertToHDF5Action.dat)|'''ConvertToHDF5Action.dat''']]. Several actions can be specified in the same input file, being processed sequentially by the ConvertToHDF5 application.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Introduction=&lt;br /&gt;
The operations involving HDF5 files performed by ConvertToHDF5, specified individually by an action, can be organized in:&lt;br /&gt;
&lt;br /&gt;
* [[#file management|file management]]&lt;br /&gt;
* [[#grid interpolation|grid interpolation]] and &lt;br /&gt;
* [[#format conversion|format conversion]]. &lt;br /&gt;
&lt;br /&gt;
These types and the respective actions are detailed in the next sections. &lt;br /&gt;
&lt;br /&gt;
The input file specification for each action can be found bellow in the [[#Input file (ConvertToHDF5Action.dat)|Input file (ConvertToHDF5Action.dat)]] section.&lt;br /&gt;
&lt;br /&gt;
==File management==&lt;br /&gt;
&lt;br /&gt;
===Glue files===&lt;br /&gt;
This action consists in joining or glue in a single HDF5 file two or more HDF5 files having the same HDF5 data groups and referring to time periods which come in sequence. Both sets of 2D and 3D HDF5 files can be glued.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Glue MOHID Water results files from several runs produced in continuous running of the model, for storage space economy reasons. Can be used to join data from other origins (e.g. results of meteorological models) as long as the HDF5 format is the one supported by MOHID Water.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 files to be glued. &amp;quot;Grid&amp;quot; and &amp;quot;Results&amp;quot; data groups should be equal in all these files.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with glued &amp;quot;Results&amp;quot; data. &amp;quot;Residual&amp;quot; and &amp;quot;Statistics&amp;quot; HDF5 data groups are not copied to the output file since they are time period specific (different values potentially occour in each file). General statistics can be calculated for the glued HDF5 file data using tool [[HDF5Statistics]].&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#GLUES HDF5 FILES|GLUES HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Grid interpolation==&lt;br /&gt;
&lt;br /&gt;
===Interpolate files===&lt;br /&gt;
This action performs the conversion of one HDF5 file data existing in one 2D or 3D spatial grid to another 2D or 3D spatial grid, creating a new HDF5 file. The interpolation is performed only for the data located a time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
The HDF5 file containing data to be interpolated is called the '''father file'''.&lt;br /&gt;
&lt;br /&gt;
In case of 3D interpolation the application conducts first the horizontal grid interpolation&lt;br /&gt;
(keeping father geometry) and only after it conducts the vertical interpolation (from father geometry to new geometry).&lt;br /&gt;
&lt;br /&gt;
Several types of 2D interpolation are available for use: bilinear, spline 2D and triangulation.&lt;br /&gt;
For vertical interpolation (used in 3D interpolation) can be supplied several polinomial degrees for interpolation.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data for forcing or providing initial conditions for a MOHID Water model, e.g. a meteorological forcing file.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
For 2D/3D interpolation:&lt;br /&gt;
&lt;br /&gt;
- father HDF5 file;&lt;br /&gt;
&lt;br /&gt;
- father horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new horizontal data grid, in a grid data file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
For 3D interpolation also needed:&lt;br /&gt;
&lt;br /&gt;
- father vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- new vertical geometry, in a geometry file in the format supported by MOHID;&lt;br /&gt;
&lt;br /&gt;
- auxiliary horizontal data grid, in a grid data file in the format supported by MOHID; this file is used for horizontal grid interpolation in 3D interpolation operations.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with interpolated data. In case of 3D interpolation also produced an auxiliary HDF5 file with the result of the horizontal grid interpolation, which can be inspected to check if this operation is well performed.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#INTERPOLATE GRIDS|INTERPOLATE GRIDS]].&lt;br /&gt;
&lt;br /&gt;
===Patch files===&lt;br /&gt;
This action consists in performing an interpolation of HDF5 data between grids, as in action [[#Interpolate files|Interpolate files]], but considering more than one HDF5 file as containing data to be interpolated to the new grid and a priority scale. The interpolation is performed only for the data located in the time window specified by the user. The present version of this action operates only on 2D data.&lt;br /&gt;
&lt;br /&gt;
Each HDF5 file containing data to be interpolated is called a '''father file''' and has an user-attributed '''priority level''' to be respected in the interpolation process: for each new grid cell the ConvertToHDF5 application will look for data first on the Level 1 father file and only in the case this data is inexistent will it look for data in Level 2 file, proceeding in looking for higher level files if no data is found subsequentely.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
To obtain an HDF5 file with data from several HDF5 files each containing data with different spatial resolution and only for a specific part of the new grid. This is, for instance, the case when one is preparing a best resolution meteorological HDF5 file for forcing MOHID Water from several meteorological model domains, having different spatial resolution and span, since the best resolution data is not available for all new grid cells.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
The new horizontal data grid, in a grid data file in the format supported by MOHID, and for each father file:&lt;br /&gt;
&lt;br /&gt;
- level of priority: 1 = maximum priority, priority decreases with increasing level value;&lt;br /&gt;
&lt;br /&gt;
- data grid, in the form of a grid data file in the format supported by MOHID.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with patched data.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#PATCH HDF5 FILES|PATCH HDF5 FILES]].&lt;br /&gt;
&lt;br /&gt;
==Format conversion==&lt;br /&gt;
&lt;br /&gt;
===Meteorological model data===&lt;br /&gt;
Mohid does not simulate explicitly the atmosphere, but needs information about atmospheric properties in time and space. This requires that atmospheric properties are supplied to MOHID Water in supported formats. These formats can be derived from meteorological data in HDF5 format. Because the results of meteorological models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the MM5 and the ERA40. These are succintly detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''ERA40''====&lt;br /&gt;
This format refers to the European Centre for Medium-Range Weather Forecasts (ECMWF) 40 years re-analysises results, acessed by site http://data.ecmwf.int/data/d/era40_daily/. This data is available for several meteorological variables with maximum 6 hour periodicity for days in the period from 1957-09-01 to 2002-08-31. &lt;br /&gt;
&lt;br /&gt;
ERA40 data files are supplied by ECMWF in a NetCDF format and with an user-costumized time window, periodicity (time step range from 6 hours to a day) and meteorological properties set. The ERA40 meteorological properties which are recognized by MOHID are presented bellow together with the correspondent MOHID name: &lt;br /&gt;
&lt;br /&gt;
 ---ERA40 NAME---         ---MOHID NAME---&lt;br /&gt;
   sshf                     sensible heat                &lt;br /&gt;
   slhf                     latent heat                  &lt;br /&gt;
   msl                      atmospheric pressure &lt;br /&gt;
   tcc                      cloud cover &lt;br /&gt;
   p10u                     wind velocity X&lt;br /&gt;
   p10v                     wind velocity Y&lt;br /&gt;
   p2t                      air temperature&lt;br /&gt;
   ewss                     wind stress X&lt;br /&gt;
   nsss                     wind stress Y&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to all MOHID Water recognized property available in the ERA40 file, producing an individual HDF5 file for each property. The name of each HDF5 file generated includes the ERA40 meteorological property identificator correspondent to the data contained.&lt;br /&gt;
&lt;br /&gt;
Alternatively, ConvertToHDF5 can copy to a single ASCII file the heading information concerning each meteorological variable considered in the original ERA40 file.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain an HDF5 file with data suitable for being used for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ERA40 NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''Output:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file for each meteorological property contained in the original NetCDF file.&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ERA40 FORMAT|CONVERT ERA40 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Aladin''====&lt;br /&gt;
This format relates to Aladin meteorological model results. Some of the atmospheric property needed by MOHID Water is present in Aladin output files, enabling to run prediction simulations with MOHID Water when access to Aladin prevision files is available.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts Aladin results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Aladin netcdf results file to convert.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with Aladin results and a grid data file in MOHID format with the Aladin grid pseudo-information: a fake orography is created of 100 m depth.&lt;br /&gt;
This last file can be used to interpolate the Aladin data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT ALADIN FORMAT|CONVERT ALADIN FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MM5''====&lt;br /&gt;
This format relates to the Fifth-Generation NCAR / Penn State Mesoscale Model (MM5) output files format. Almost every atmospheric property needed by MOHID Water is present in MM5 output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts MM5 results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the MM5 properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the MM5 files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
For conversion to be completed it is required the horizontal grid information of MM5 results which is available in special TERRAIN files.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
MM5 results file to convert and MM5 TERRAIN file. The TERRAIN file supplies the MM5 results grid information. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
A HDF5 file with MM5 results and a grid data file in MOHID format with the MM5 grid information.&lt;br /&gt;
This last file can be used to interpolate the MM5 data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! The ConvertToHDF5 executable must be compiled with the [[Big-endian little-endian|Big-Endian]] option set (see compatibility in the project's settings).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MM5 FORMAT|CONVERT MM5 FORMAT]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''WRF''====&lt;br /&gt;
This format relates to the Weather Research and Forecast model (WRF) output files format. Almost every atmospheric property needed by MOHID Water is present in WRF output files.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts WRF results files from the original format to HDF5 format, allowing the easy use of these results in the MOHID framework. Conversion is only performed for the WRF properties and the time window specified by the user.&lt;br /&gt;
&lt;br /&gt;
Besides the conversion, the application can calculate some properties not contained in&lt;br /&gt;
the WRF files using the available information: these are wind stress, relative humidity and mean sea level pressure.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Produce HDF5 meteorological data usable to force MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
WRF direct output file.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
An HDF5 file with WRF results and a grid data file in MOHID format with the WRF grid information.&lt;br /&gt;
This last file can be used to interpolate the WRF data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]), for instance to produce an HDF5 file suitable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Compilation:'''&lt;br /&gt;
&lt;br /&gt;
Caution! [[PROJ4 | PROJ4]] library is needed! See [[#Compile_ModuleWRFFormat |  Compile_ModuleWRFFormat]]&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT WRF FORMAT|CONVERT WRF FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Wave model data===&lt;br /&gt;
Mohid does not simulate explicitly the wave dynamics, but needs information about wave properties in time and space. This requires that wave properties are supplied to MOHID Water in supported formats. These formats can be derived from wave data in HDF5 format. Because the results of wave models are accessed in different formats conversion is required. &lt;br /&gt;
&lt;br /&gt;
The formats currently convertible to HDF5 in ConvertToHDF5 include the table format of SWAN. This is succintly detailed in the next section.&lt;br /&gt;
&lt;br /&gt;
====''SWAN''====&lt;br /&gt;
SWAN data files are supplied in a ASCII format. The data is organized by time instant. For each time instant there is a table of data. Each column represents one property. &lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to gradients of wave stresses X and Y, mean amplitude, mean period and mean direction.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 SWAN data usable for forcing MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
ASCII (table type) SWAN results data files and bathymetry in MOHID grid data foramt. &lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (wave stresses X and Y, mean amplitude, mean period and mean direction). &lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT TO AND FROM SWAN|CONVERT TO AND FROM SWAN]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Ocean model data===&lt;br /&gt;
Ocean model data, available in diverse formats, can be used by MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation. These uses require that the model data is in HDF5 format and conversion is therefore needed.&lt;br /&gt;
&lt;br /&gt;
Currently the large scale ocean models formats convertible into HDF5 by ConvertToHDF5 includes MERCATOR.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''MERCATOR''====&lt;br /&gt;
MERCATOR data files are supplied in a NetCDF format and with an user-costumized spatial window and periodicity. Water level and water properties (temperature and salinity) data is available in type T files, velocity component u data is available in type U files and velocity component v data is available in type V files. The type of data of a specific MERCATOR file is generally indicated in the file name.&lt;br /&gt;
&lt;br /&gt;
The standard ConvertToHDF5 action is to convert to HDF5 the data referring to temperature, salinity, water level, component u of velocity and component v of velocity.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain HDF5 MERCATOR data usable for forcing or validation of MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
NetCDF MERCATOR results data files and NetCDF MERCATOR grid data files. It should be provided one grid data file of each type: T, U and V. These are generally provided by the MERCATOR services together with the results files.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
One HDF5 file containing all properties contained in the recognized set of properties (temperature, salinity, water level, velocity u and velocity v) and the correspondent grid data and geometry files, containing respectively the horizontal grid and the vertical discretization of the HDF5 file. The grid data and geometry files can be used afterwards to interpolate the MERCATOR data to another grid and geometry (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT MERCATOR FORMAT|CONVERT MERCATOR FORMAT]].&lt;br /&gt;
&lt;br /&gt;
===Climatological data===&lt;br /&gt;
Climatological data can be used in MOHID Water to specify boundary (open ocean boundary and surface), initial conditions or for validation, in case more realistic data (measurements or model) data is unavailable. This data is generally supplied by producers in formats not readly usable by MOHID Water which justifies the existence of a conversion tool.&lt;br /&gt;
&lt;br /&gt;
Two climatological data format conversions are implemented in ConvertToHDF5: Levitus ocean data and Hellerman Rosenstein meteorological data.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''Levitus''====&lt;br /&gt;
The Levitus climatology provides results for water temperature and salinity.&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window requested by the user. &lt;br /&gt;
Typically, it requires 3 steps to complete the task:&lt;br /&gt;
&lt;br /&gt;
- convert levitus format &lt;br /&gt;
&lt;br /&gt;
- extrapolate the data to the whole levitus domain(required to avoid uncoincidental coastlines) &lt;br /&gt;
&lt;br /&gt;
- interpolate with the model grid(bathymetry)&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as boundary forcing and/or initial condition specification in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Levitus climatological data files, one per property and per time period (e.g a month).&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Levitus climatological data, grid data file with the horizontal&lt;br /&gt;
grid of the data and a geometry file with vertical discretization of the data (MOHID formats).&lt;br /&gt;
The grid data and the geometry files can be used to interpolate the climatological data from the original grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT LEVITUS FORMAT|CONVERT LEVITUS FORMAT]].&lt;br /&gt;
&lt;br /&gt;
====''Hellerman Rosenstein''====&lt;br /&gt;
This is a meteorological climatology providing wind stress. There is a file per wind stress component. Since the data refer to surface values it is a 2D field.&lt;br /&gt;
&lt;br /&gt;
The ConvertToHDF5 action converts the climatological data for the properties and spatial window provided by the user.&lt;br /&gt;
&lt;br /&gt;
'''Typical use:'''&lt;br /&gt;
&lt;br /&gt;
Obtain climatological data in HDF5 format to use as meteorological forcing in MOHID Water models.&lt;br /&gt;
&lt;br /&gt;
'''Data input requirements:'''&lt;br /&gt;
&lt;br /&gt;
Hellerman Rosenstein climatological data ASCII files, one per wind stress component.&lt;br /&gt;
&lt;br /&gt;
'''Ouput:'''&lt;br /&gt;
&lt;br /&gt;
HDF5 file with Hellerman Rosenstein climatological data and grid data file with the horizontal&lt;br /&gt;
grid of the climatological data. This grid data file can be used to interpolate the climatological data from the original horizontal grid to a new grid (see [[#Interpolate files|Interpolate files]]).&lt;br /&gt;
&lt;br /&gt;
'''ConvertToHDF5 action:''' [[#CONVERT HELLERMAN ROSENSTEIN ASCII|CONVERT HELLERMAN ROSENSTEIN ASCII]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====''World Ocean Atlas 2005''====&lt;br /&gt;
The World Ocean Atlas (WOA) 2005 climatology provides results for water temperature, salinity and several water quality and biology properties.&lt;br /&gt;
&lt;br /&gt;
Description, Action and Input Files are described in a separate page: [[ConvertToHDF5 WOA2005]].&lt;br /&gt;
&lt;br /&gt;
===Generic NETCDF CF FILES===&lt;br /&gt;
&lt;br /&gt;
Converts any netcdf file following the CF convention into Mohid HDF5 files. Check the [[ConvertToHDF5#CONVERT_GENERIC_NETCDF_CF | Input File]] and [[ConvertToHDF5#Convert_generic_Netcdf_CF_to_MOHID.28.hdf5.29 | Sample File]].&lt;br /&gt;
&lt;br /&gt;
===Radar data===&lt;br /&gt;
====Seasonde RADAR Data====&lt;br /&gt;
Converts a list of ascii files from the Seasonde radar data, which measures currents over a given region of space, into an hdf5 file with the MOHID format. Useful to validate coastal and estuarine models where radars are located.&lt;br /&gt;
&lt;br /&gt;
==Input file (ConvertToHDF5Action.dat)==&lt;br /&gt;
===General structure===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt; (block containing instructions for running a specific action) &lt;br /&gt;
 ACTION                    : ... (intended action)&lt;br /&gt;
 ... (action specific instructions)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : ...&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===GLUES HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 3D_FILE                   : 0/1 (0 = 2D file, 1 = 3D file)&lt;br /&gt;
 &lt;br /&gt;
 TIME_GROUP                : ... (Default=&amp;quot;Time&amp;quot;. Other option: &amp;quot;SurfaceTime&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (Default=&amp;quot;Results&amp;quot;. Other options: &amp;quot;Residual&amp;quot;, &amp;quot;SurfaceResults&amp;quot;.)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 &lt;br /&gt;
 (block of HDF5 data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of HDF5 file with data to be included in glue, one per line, at least two files)&lt;br /&gt;
 ...                      &lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===INTERPOLATE GRIDS===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of horizontal interpolation: 1 = Bilinear, 2 = Spline2D,&lt;br /&gt;
                                  3 = Triangulation)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION_WINDOW      : ... ... ... ... (2D spatial window to consider for interpolation: &lt;br /&gt;
                                              Xmin Ymin Xmax Ymax; default = all domain)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D           : 0/1 (0 = 2D interpolation, 1 = 3D interpolation)&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_2D            : 0/1/2/3/4/5 (2D extrapolation: 0=no extrapolation, 1=medium&lt;br /&gt;
                                      triangulation, 2=high triangulation, &lt;br /&gt;
                                      3=nearest neighbour, 4=nearest cell, &lt;br /&gt;
                                      5=constant value)&lt;br /&gt;
 &lt;br /&gt;
 EXTRAPOLATE_VALUE         : ... (name of the value to extrapolate to when EXTRAPOLATE_2D is&lt;br /&gt;
                                  set to constant value (5))&lt;br /&gt;
 &lt;br /&gt;
 DO_NOT_BELIEVE_MAP        : 0/1 (0=consider input HDF5 file map, 1=do not consider input HDF5&lt;br /&gt;
                                  file map)&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP                : ... (name of base group of HDF5 variables containing data to be &lt;br /&gt;
                                  interpolated; default is &amp;quot;/Results&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (if INTERPOLATION3D : 1 also required:)&lt;br /&gt;
 FATHER_GEOMETRY           : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  of input HDF5 file)&lt;br /&gt;
 NEW_GEOMETRY              : ... (path/name of file (MOHID format) with vertical discretization&lt;br /&gt;
                                  intended for output HDF5 file)&lt;br /&gt;
 POLI_DEGREE               : 1/... (degree of vertical interpolation: 1=linear, ...)&lt;br /&gt;
 &lt;br /&gt;
 AUX_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for auxiliar output HDF5 file;&lt;br /&gt;
                                  default is file provided in NEW_GRID_FILENAME)&lt;br /&gt;
 &lt;br /&gt;
 AUX_OUTPUTFILENAME        : ... (path/name of auxiliar output HDF5 file to contain result&lt;br /&gt;
                                  of horizontal grid interpolation)   &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the file indicated in AUX_GRID_FILENAME can be different from the one indicated in&lt;br /&gt;
   NEW_GRID_FILENAME in terms of bathymetry, while the horizontal grid should be, commonly, the&lt;br /&gt;
   same: this altered bathymetry can be used to extend the water column in the original data so&lt;br /&gt;
   that the process of vertical interpolation is done easily;&lt;br /&gt;
 &lt;br /&gt;
 - in case of INTERPOLATION3D : 1, ConvertToHDF5 can generate new versions of bathymetry which &lt;br /&gt;
   are consistent with the geometry definition (extension is '.new'); there are possibly three&lt;br /&gt;
   bathymetry changes referring to father grid, new grid and aux grid (the same bathymetry is&lt;br /&gt;
   not altered twice); although initially new and aux grid are the same they can result &lt;br /&gt;
   different because of bathymetry changes;&lt;br /&gt;
 &lt;br /&gt;
 - in case the new geometry is 2D and father geometry is 3D then POLI_DEGREE : 1 &lt;br /&gt;
   (linear interpolation) should be used;&lt;br /&gt;
 &lt;br /&gt;
 - EXTRAPOLATE_2D : 1/2/3/4/5 should be considered if it is expected that the coast line is not&lt;br /&gt;
   coincidental in the father and new grids, to avoid lack of data in the interpolation&lt;br /&gt;
   process; extrapolation is performed for all cells even the land cells; &lt;br /&gt;
 &lt;br /&gt;
 - in case of DO_NOT_BELIEVE_MAP : 1 the application generates a map based on cells where&lt;br /&gt;
   interpolation results are available; this causes that if EXTRAPOLATE_2D : 1/2/3/4/5 is used&lt;br /&gt;
   the AUX_GRID_FILENAME should not have land cells in order for the new map to be concurrent&lt;br /&gt;
   with the result of extrapolation and avoid errors generation, specially if INTERPOLATION3D :&lt;br /&gt;
   1 is considered.&lt;br /&gt;
&lt;br /&gt;
===PATCH HDF5 FILES===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION     : ... (type of interpolation: 3 = Triangulation, default and only&lt;br /&gt;
                                  one implemented)&lt;br /&gt;
 &lt;br /&gt;
 START                     : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                       : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 &lt;br /&gt;
 (block for each father HDF5 file, should be at least two)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                     : ... (integer priority level: 1 = highest, increase for lower&lt;br /&gt;
                                  priority)&lt;br /&gt;
 FATHER_FILENAME           : ... (path/name of input HDF5 file with data to be interpolated)&lt;br /&gt;
 FATHER_GRID_FILENAME      : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization of input HDF5 file)&lt;br /&gt;
 N_REMOVE_FRAME            : 0   (width, in number of cells, of frame to remove)&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of output HDF5 file to be created)&lt;br /&gt;
 NEW_GRID_FILENAME         : ... (path/name of input grid data file with horizontal&lt;br /&gt;
                                  discretization intended for output HDF5 file)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT ERA40 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of ERA40 NetCDF file)&lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
                                 (root of name for all files produced)&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII          : 0/1 (1 = convert variable heading info for ASCII file; 0 = default)&lt;br /&gt;
 CONVERT_TO_HDF5           : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 GRIDTO180                 : 0/1 (1 = convert grid from [0 360] to [-180 180], 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 YY_VARIABLE               : ... (name of longitude variable in the input file: usual name &lt;br /&gt;
                                  is &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 TIME_VARIABLE             : ... (name of time variable in the input file: usual name is&lt;br /&gt;
                                  &amp;quot;time&amp;quot;)&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - either CONVERT_TO_ASCII : 1 or CONVERT_TO_HDF5 : 1 must be chosen for any action to be&lt;br /&gt;
 performed by ConvertToHDF5;&lt;br /&gt;
 &lt;br /&gt;
 - when CONVERT_TO_HDF5 : 1 an HDF5 file is produced for every variable contained in the&lt;br /&gt;
 original ERA40 file; the name of each file is composed of the name indicated on FILENAME&lt;br /&gt;
 concatenated with the ERA40 variable identifier;&lt;br /&gt;
 &lt;br /&gt;
 - to the XX_VARIABLE, YY_VARIABLE and TIME_VARIABLE keywords should generally be  &lt;br /&gt;
 specified &amp;quot;longitude&amp;quot;, &amp;quot;latitude&amp;quot; and &amp;quot;time&amp;quot;, respectively; the option to&lt;br /&gt;
 include as keywords was made only to make the application robust to future variable name&lt;br /&gt;
 changes.&lt;br /&gt;
&lt;br /&gt;
===CONVERT ALADIN FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 (path to aladin netcdf file)\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each Aladin property to convert in &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;...&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt; block must conform to the following variables&lt;br /&gt;
 &lt;br /&gt;
           ---ALADIN NAME---    ---MOHID NAME---&lt;br /&gt;
             soclotot            CloudCover_&lt;br /&gt;
             sohumrel            RelativeHumidity_&lt;br /&gt;
             sofluxir            NonSolarFlux_&lt;br /&gt;
             sosspres            AtmosphericPressure_&lt;br /&gt;
             sosolarf            SolarRadiation_&lt;br /&gt;
             sotemair            AirTemperature_&lt;br /&gt;
             sowinmod            WindModulus_&lt;br /&gt;
             sowaprec            Precipitation_&lt;br /&gt;
             sozotaux            WindStressX_&lt;br /&gt;
             sometauy            WindStressY_&lt;br /&gt;
             sowindu10           WindVelocityX_&lt;br /&gt;
             sowindv10           WindVelocityY_&lt;br /&gt;
&lt;br /&gt;
===CONVERT MM5 FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MM5 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                  : ... (path/name of MM5 file)&lt;br /&gt;
 TERRAIN_FILENAME          : ... (path/name of MM5 TERRAIN file)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of MM5 data to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP                 : 0/1 (1 = compute and write mean sea level pressure field; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of MM5 properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of MM5 property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
 &lt;br /&gt;
 - the name of each MM5 property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must&lt;br /&gt;
 conform to the MOHID designation specified in code of ModuleGlobalData; the correspondence is &lt;br /&gt;
 the following (see [[Module_InterfaceWaterAir]] for a more detailed explanation).&lt;br /&gt;
 &lt;br /&gt;
           ---MM5 NAME---    ---MOHID NAME---&lt;br /&gt;
             T2             air temperature&lt;br /&gt;
             PSTARCRS       atmospheric pressure&lt;br /&gt;
             U10            wind velocity X&lt;br /&gt;
             V10            wind velocity Y&lt;br /&gt;
             UST            wind shear velocity&lt;br /&gt;
             LHFLUX         latent heat&lt;br /&gt;
             SWDOWN         sensible heat&lt;br /&gt;
             SWDOWN         solar radiation&lt;br /&gt;
             LWDOWN         infrared radiation&lt;br /&gt;
             SWOUT          top outgoing shortwave radiation&lt;br /&gt;
             LWOUT          top outgoing longwave radiation&lt;br /&gt;
             SOIL T 1       soil temperature layer 1&lt;br /&gt;
             SOIL T 1       soil temperature layer 2&lt;br /&gt;
             SOIL T 1       soil temperature layer 3&lt;br /&gt;
             SOIL T 1       soil temperature layer 4&lt;br /&gt;
             SOIL T 1       soil temperature layer 5&lt;br /&gt;
             SOIL T 1       soil temperature layer 6&lt;br /&gt;
             Q2             2-meter mixing ratio&lt;br /&gt;
             TSEASFC        sea water temperature&lt;br /&gt;
             PBL HGT        PBL height&lt;br /&gt;
             PBL REGIME     PBL regime&lt;br /&gt;
             RAIN CON       accumulated convective precipitation        (cm)&lt;br /&gt;
             RAIN NON       accumulated non-convective precipitation    (cm)&lt;br /&gt;
             GROUND T       ground temperature&lt;br /&gt;
             RES TEMP       infinite reservoir slab temperature&lt;br /&gt;
             U              wind velocity X_3D&lt;br /&gt;
             V              wind velocity Y_3D&lt;br /&gt;
             W              wind velocity Z_3D&lt;br /&gt;
             T              air temperature_3D&lt;br /&gt;
             PP             atmospheric pressure_3D&lt;br /&gt;
             Q              mixing ratio_3D&lt;br /&gt;
             CLW            cloud water mixing ratio_3D&lt;br /&gt;
             RNW            rain water mixing ratio_3D&lt;br /&gt;
             ICE            cloud ice mixing ratio_3D&lt;br /&gt;
             SNOW           snow mixing ratio_3D&lt;br /&gt;
             RAD TEND       atmospheric radiation tendency_3D&lt;br /&gt;
&lt;br /&gt;
===CONVERT WRF FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                       : CONVERT WRF FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                     : ... (path/name of WRF file)&lt;br /&gt;
 OUTPUTFILENAME               : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME         : ... (path/name of grid data file with horizontal grid of WRF data&lt;br /&gt;
                                     to be created)&lt;br /&gt;
 &lt;br /&gt;
 COMPUTE_WINDSTRESS           : 0/1 (1 = compute and write wind stress field; 0 = default)&lt;br /&gt;
 COMPUTE_WINDMODULUS          : 0/1 (1 = compute wind modulus; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY    : 0/1 (1 = compute and write 2-meter relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY_3D : 0/1 (1 = compute and write 3D relative humidity field; 0 = default)&lt;br /&gt;
 COMPUTE_PRECIPITATION        : 0/1 (1 = compute and write precipitation field; 0 = default)&lt;br /&gt;
 COMPUTE_MSLP_MM5             : 0/1 (1 = compute mean sea level pressure with MM5toGrads algorithm; 1 = default)&lt;br /&gt;
 COMPUTE_MSLP_WRF             : 0/1 (1 = compute mean sea level pressure with ARWPost algorithm; 0 = default)&lt;br /&gt;
 &lt;br /&gt;
 WRITE_XYZ                    : 0/1 (1 = write xyz center grid cells; 0 = default)&lt;br /&gt;
 WRITE_TERRAIN                : 0/1 (1 = write MM5 TERRAIN fields; 0 = default)&lt;br /&gt;
 OUTPUT_DT                    : real (DT interval in seconds between each output; default = 0.0)&lt;br /&gt;
 &lt;br /&gt;
 START                        : ... (start date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
 END                          : ... (end date for output file: yyyy mm dd hh mm ss)&lt;br /&gt;
  &lt;br /&gt;
 (block of properties to convert)&lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 ... (name of property to convert do HDF5 format, one per line)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 ''Remarks:''&lt;br /&gt;
  &lt;br /&gt;
 - the name of each property to convert in &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;...&amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt; block must conform to the MOHID &lt;br /&gt;
   designation specified in code of ModuleGlobalData; the correspondence to WRF is in function &lt;br /&gt;
   VariableIsToRead in ModuleWRFFormat. Conversion is not direct since WRF outputs tendencies and not  &lt;br /&gt;
   total values. &lt;br /&gt;
 &lt;br /&gt;
 - Caution: This action is not extensively tested.&lt;br /&gt;
&lt;br /&gt;
===CONVERT MERCATOR FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION               : 1/2/3/4 (version of MERCATOR files)&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 1:)&lt;br /&gt;
 BASE_BULLETIN             : ...&lt;br /&gt;
 DATES_FILE                : ...&lt;br /&gt;
 NUM_DATES                 : ... &lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 2/3:)&lt;br /&gt;
 INPUT_GRID_FILENAME       : ... (path/name of file with horizontal discretization of water&lt;br /&gt;
                                  properties and water level data)&lt;br /&gt;
 (if READ_OPTION : 2:)&lt;br /&gt;
 INPUT_GRID_FILENAME_U     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component U data)&lt;br /&gt;
 INPUT_GRID_FILENAME_V     : ... (path/name of file with horizontal discretization of velocity&lt;br /&gt;
                                  component V data)&lt;br /&gt;
 &lt;br /&gt;
 (if READ_OPTION : 3:)&lt;br /&gt;
 INPUT_BATHY_FILENAME      : ... (path/name of file with bathymetry)&lt;br /&gt;
     &lt;br /&gt;
 (if READ_OPTION : 3/4:)&lt;br /&gt;
 CALC_BAROTROPIC_VEL       : 0/1 (1 = calculate barotropic velocity, 0 = not calculate; &lt;br /&gt;
                                  default = 0)&lt;br /&gt;
 &lt;br /&gt;
 (if CALC_BAROTROPIC_VEL : 1 and READ_OPTION : 3:)&lt;br /&gt;
 INPUT_MESH_ZGRID_FILENAME : ... (path/name of file with information about layers ticknesses)&lt;br /&gt;
 &lt;br /&gt;
 (block of MERCATOR data files)&lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of MERCATOR NetCDF data file, one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT LEVITUS FORMAT===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT LEVITUS FORMAT&lt;br /&gt;
  &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME  : ... (path/name of geometry file with vertical discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Levitus data: &amp;quot;monthly&amp;quot;/&amp;quot;annual&amp;quot;; default is&lt;br /&gt;
                                  &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Levitus grid)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
 &lt;br /&gt;
 (block for each water property to be present in output HDF5 file, can be several)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property)&lt;br /&gt;
 ANNUAL_FILE               : ... (path/name of Levitus annual file)&lt;br /&gt;
 &lt;br /&gt;
 (block of Levitus data files)&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 ... (path/name of Levitus data file (e.g. a monthly data file), one per line, can be several)&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===CONVERT HELLERMAN ROSENSTEIN ASCII===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : ... (path/name of grid data with horizontal discretization to be&lt;br /&gt;
                                  created)&lt;br /&gt;
  &lt;br /&gt;
 PERIODICITY               : ... (periodicity of Hellerman Rosenstein data: &amp;quot;monthly&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 SPATIAL_RESOLUTION        : ... (spatial resolution (degrees) of horizontal Hellerman&lt;br /&gt;
                                  Rosenstein grid: default and only allowed value is &amp;quot;2.&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 FILL_VALUE                : ... (real value identificator for missing data; default is &lt;br /&gt;
                                  &amp;quot;-99.999900&amp;quot;)&lt;br /&gt;
 &lt;br /&gt;
 (definition of spatial window to be present in output HDF5 file)&lt;br /&gt;
 LOWER_LEFT_CORNER         : ... ... (longitude and latitude (degrees) of south west corner)&lt;br /&gt;
 UPPER_RIGHT_CORNER        : ... ... (longitude and latitude (degrees) of north east corner)&lt;br /&gt;
   &lt;br /&gt;
 (block for each Hellerman Rosenstein data file)&lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                      : ... (name of property: &amp;quot;wind stress X&amp;quot;/&amp;quot;wind stress Y&amp;quot;)&lt;br /&gt;
 FILE                      : ... (path/name Hellerman Rosenstein file)&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===CONVERT GENERIC NETCDF CF===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION              : CONVERT NETCDF CF TO HDF5 MOHID       &lt;br /&gt;
 HDF5_OUT            : 0/1 (1 = convert to HDF5 file; 0 = default)&lt;br /&gt;
 OUTPUTFILENAME      : ... (path/name of HDF5 file to be created)&lt;br /&gt;
 NETCDF_OUT          : 0/1 (1 = convert to netcdf file; 0 = default)&lt;br /&gt;
 OUTPUT_NETCDF_FILE  : ... (path/name of netcdf file to be created)&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property for time, generally &amp;quot;time&amp;quot;&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT     : ... (name of the netcdf property for latitude, generally &amp;quot;latitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_LONG    : ... (name of the netcdf property for longitude, generally &amp;quot;longitude&amp;quot;)&lt;br /&gt;
 NETCDF_NAME_MAPPING : ... (name of the netcdf field where is located the mapping 0 water 1 land)&lt;br /&gt;
                           (It can also be used any field, i.e. temperature)&lt;br /&gt;
 MAPPING_LIMIT       : real (limit for netcdf value mapping; default = 0.5, thus &amp;gt;0.5 water)&lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER   : real (number of netcdf properties) &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME         : name of the netcdf property&lt;br /&gt;
 NAME                : name of the HDF5 Mohid property&lt;br /&gt;
 UNITS               : property units&lt;br /&gt;
 DESCRIPTION         : property description&lt;br /&gt;
 DIM                 : 2/3 Number of property dimensions &lt;br /&gt;
 VECTOR_INTENSITY    : 0/1 If property corresponds to a vector intensity&lt;br /&gt;
 VECTOR_X            : Decomposition of Vector Intensity X&lt;br /&gt;
 VECTOR_Y            : Decomposition of Vector Intensity Y&lt;br /&gt;
 BEAUFORT_SCALE      : 0/1 If property correspond to the beaufort scale&lt;br /&gt;
 ADD_FACTOR          : To add the property a fixed value&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 path to netcdf cf file&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Samples==&lt;br /&gt;
All sample files are named ''ConvertToHDF5Action.dat''.&lt;br /&gt;
&lt;br /&gt;
===Glue several MOHID(.hdf5) files===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : GLUES HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : SurfaceHydro_OP.hdf5&lt;br /&gt;
  &lt;br /&gt;
 &amp;lt;&amp;lt;begin_list&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_21.hdf5&lt;br /&gt;
 D:\Projectos\SurfaceHydrodynamic_22.hdf5&lt;br /&gt;
 &amp;lt;&amp;lt;end_list&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 2D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME           : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
  &lt;br /&gt;
 START                    : 2006 6 21 17 22 30&lt;br /&gt;
 END                      : 2006 6 22 17 22 0&lt;br /&gt;
  &lt;br /&gt;
 FATHER_GRID_FILENAME     : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME        : TagusConstSpacing.dat&lt;br /&gt;
  &lt;br /&gt;
 BASE_GROUP               : /Results/Oil/Data_2D&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Interpolate 3D MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 1&lt;br /&gt;
 FATHER_FILENAME         : D:\Projectos\MohidRun\test\res\Lagrangian_1.hdf5 &lt;br /&gt;
 OUTPUTFILENAME          : OilSpillThickness_GridRegular.hdf5&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2006 6 21 17 22 30&lt;br /&gt;
 END                     : 2006 6 22 17 22 0&lt;br /&gt;
 &lt;br /&gt;
 FATHER_GRID_FILENAME    : D:\Projectos\MohidRun\GeneralData\batim\Tagus.dat_A&lt;br /&gt;
 NEW_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 &lt;br /&gt;
 BASE_GROUP              : /Results/Oil/Data_2D&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D         : 1&lt;br /&gt;
 FATHER_GEOMETRY         : D:\Projectos\MohidRun\test\data\Geometry_1.dat&lt;br /&gt;
 NEW_GEOMETRY            : TagusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME       : TagusConstSpacing.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME      : Aux_GridRegular.hdf5&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Patch several MOHID(.hdf5) files to a new grid===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION : PATCH HDF5 FILES&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION   : 3&lt;br /&gt;
 &lt;br /&gt;
 START                   : 2005 2 28 13 0 0&lt;br /&gt;
 END                     : 2005 3 1 13 0 0&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 3&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D1.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid1.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 2&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D2.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid2.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_father&amp;gt;&amp;gt;&lt;br /&gt;
 LEVEL                   : 1&lt;br /&gt;
 FATHER_FILENAME         : K:\MM5output\2005022812_2005030712\MM5OUT_D3.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME    : K:\MM5output\2005022812_2005030712\grid3.dat&lt;br /&gt;
 &amp;lt;&amp;lt;end_father&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME          : MM5Forcing.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME       : K:\Simula\GeneralData\Batim\CostaPortuguesa.dat&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert an ERA40 file to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                  : CONVERT ERA40 FORMAT&lt;br /&gt;
 &lt;br /&gt;
 FILENAME                : D:\Aplica\ERA40\1971ERA1973.nc&lt;br /&gt;
 OUTPUTFILENAME          : D:\Aplica\ERA40\1971ERA1973T2&lt;br /&gt;
 &lt;br /&gt;
 CONVERT_TO_ASCII        : 0&lt;br /&gt;
 CONVERT_TO_HDF5         : 1&lt;br /&gt;
 &lt;br /&gt;
 XX_VARIABLE             : longitude&lt;br /&gt;
 YY_VARIABLE             : latitude&lt;br /&gt;
 TIME_VARIABLE           : time&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a MM5 file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : MMOUT_DOMAIN2&lt;br /&gt;
 TERRAIN_FILENAME          : TERRAIN_DOMAIN2&lt;br /&gt;
 OUTPUTFILENAME            : D2.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : D2.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 !START                     : 2010 02 15 00 00 00&lt;br /&gt;
 !END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert a WRF file to MOHID(.hdf5)===&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT WRF FORMAT&lt;br /&gt;
 FILENAME                  : wrfout_d01_2010-02-15_00.nc&lt;br /&gt;
 OUTPUTFILENAME            : wrfout_d01.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : wrfout_d01.dat&lt;br /&gt;
 COMPUTE_WINDSTRESS        : 1&lt;br /&gt;
 COMPUTE_RELATIVE_HUMIDITY : 1&lt;br /&gt;
 COMPUTE_PRECIPITATION     : 1&lt;br /&gt;
 COMPUTE_MSLP              : 1&lt;br /&gt;
 COMPUTE_WINDMODULUS       : 1&lt;br /&gt;
 WRITE_XYZ                 : 0&lt;br /&gt;
 WRITE_TERRAIN             : 0&lt;br /&gt;
 OUTPUT_DT                 : 3600&lt;br /&gt;
 &lt;br /&gt;
 START                     : 2010 02 15 00 00 00&lt;br /&gt;
 END                       : 2010 02 15 06 00 00&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginFields&amp;gt;&amp;gt;&lt;br /&gt;
 air temperature&lt;br /&gt;
 atmospheric pressure&lt;br /&gt;
 downward long wave radiation&lt;br /&gt;
 latent heat&lt;br /&gt;
 sensible heat&lt;br /&gt;
 sea water temperature&lt;br /&gt;
 solar radiation&lt;br /&gt;
 top outgoing shortwave radiation&lt;br /&gt;
 upward long wave radiation&lt;br /&gt;
 wind velocity X&lt;br /&gt;
 wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;EndFields&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Mercator-Ocean(.nc) to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT MERCATOR FORMAT&lt;br /&gt;
 &lt;br /&gt;
 READ_OPTION              : 2&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Psy2v2r1v_R20060628/MercatorR20060628.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : Psy2v2r1v_R20060628/MercatorGridR20060628.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : Psy2v2r1v_R20060628/MercatorGeometryR20060628.dat&lt;br /&gt;
 &lt;br /&gt;
 INPUT_GRID_FILENAME      : GridFiles/ist_meteog-gridT.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_U    : GridFiles/ist_meteog-gridU.nc&lt;br /&gt;
 INPUT_GRID_FILENAME_V    : GridFiles/ist_meteog-gridV.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060621_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060622_R20060628.nc&lt;br /&gt;
 Psy2v2r1v_R20060628/ist_meteog-mercatorPsy2v2r1v_T_MEAN_ANA_20060623_R20060628.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert Levitus format to MOHID(.hdf5) and interpolate grid===&lt;br /&gt;
==== Convert ====&lt;br /&gt;
First convert the Levitus ASCII format to a raw HDF5 format:&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT LEVITUS FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : Levitus.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 OUTPUT_GEOMETRY_FILENAME : LevitusGeometry.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 0.25&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -16.0  31&lt;br /&gt;
 UPPER_RIGHT_CORNER       :   1.   40&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : salinity&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Salinity\s012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : temperature&lt;br /&gt;
 ANNUAL_FILE              : DataCenter\DadosBase\Ocean\Levitus\Data\Temp\t000hr.obj&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t001&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t002&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t003&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t004&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t005&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t006&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t007&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t008&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t009&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t010&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t011&lt;br /&gt;
 DataCenter\DadosBase\Ocean\Levitus\Data\Temperature\t012&lt;br /&gt;
 &amp;lt;&amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Extrapolate ====&lt;br /&gt;
Then extrapolate the data (still in the raw HDF5 format):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 &lt;br /&gt;
 FATHER_FILENAME          : Levitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 NEW_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : LevitusGeometry.dat&lt;br /&gt;
 AUX_GRID_FILENAME        : LevitusGrid.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxLeviTusAllPointsWithData.hdf5&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 EXTRAPOLATE_2D           : 2&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Interpolate ====&lt;br /&gt;
Finally, interpolate to the final grid and geometry (same as the [[#Interpolate 3D MOHID(.hdf5) files to a new grid| Interpolate 3D sample]]):&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : INTERPOLATE GRIDS&lt;br /&gt;
 &lt;br /&gt;
 TYPE_OF_INTERPOLATION    : 1&lt;br /&gt;
 FATHER_FILENAME          : LeviTusAllPointsWithData.hdf5&lt;br /&gt;
 OUTPUTFILENAME           : CadizMonthlyLevitus.hdf5&lt;br /&gt;
 FATHER_GRID_FILENAME     : LevitusGrid.dat&lt;br /&gt;
 NEW_GRID_FILENAME        : Algarve0.02SigmaSmooth_V3_CartMoreLayers.dat&lt;br /&gt;
 &lt;br /&gt;
 START                    : -9999 1  1 0 0 0&lt;br /&gt;
 END                      : -9999 12 1 0 0 0&lt;br /&gt;
 &lt;br /&gt;
 INTERPOLATION3D          : 1&lt;br /&gt;
 FATHER_GEOMETRY          : LevitusGeometry.dat&lt;br /&gt;
 NEW_GEOMETRY             : Geometry_1.dat&lt;br /&gt;
 AUX_OUTPUTFILENAME       : AuxCadizMonthlyLevitus.hdf5&lt;br /&gt;
 AUX_GRID_FILENAME        : Aux12km.dat&lt;br /&gt;
 &lt;br /&gt;
 POLI_DEGREE              : 3&lt;br /&gt;
 DO_NOT_BELIEVE_MAP       : 1&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the programme may construct a new bathymetry twice. Use this bathymetry only on the AUX_GRID_FILENAME keyword.&lt;br /&gt;
&lt;br /&gt;
===Convert Hellerman Rosenstein ASCII format to MOHID(.hdf5)  ===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                   : CONVERT HELLERMAN ROSENSTEIN ASCII&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME           : ClimatologicWindStress.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME     : ClimatologicWindStressGrid.dat&lt;br /&gt;
 &lt;br /&gt;
 PERIODICITY              : monthly&lt;br /&gt;
 SPATIAL_RESOLUTION       : 2.&lt;br /&gt;
 FILL_VALUE               : -99.9999&lt;br /&gt;
 &lt;br /&gt;
 LOWER_LEFT_CORNER        : -180  -90&lt;br /&gt;
 UPPER_RIGHT_CORNER       : 180  90&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress X&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUXX.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;beginfield&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                     : wind stress Y&lt;br /&gt;
 FILE                     : D:\Aplica\Dados\Hellerman_Rosenstein\TAUYY.DAT&lt;br /&gt;
 &amp;lt;&amp;lt;endfield&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Convert ALADIN(.nc) format to MOHID(.hdf5)===&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 ACTION                    : CONVERT ALADIN FORMAT&lt;br /&gt;
 &lt;br /&gt;
 OUTPUTFILENAME            : aladin.hdf5&lt;br /&gt;
 OUTPUT_GRID_FILENAME      : aladin_griddata.dat&lt;br /&gt;
 &lt;br /&gt;
 !Put here the name of any netcdf file for grid-data generation's sake.&lt;br /&gt;
 INPUT_GRID_FILENAME      :   D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKPRES_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKSOLAR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKTAIR_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKWIND_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_FLUXPRE_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSU_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_STRESSV_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_U10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_V10_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKCLOUD_OPASYMP_19723_20088.nc&lt;br /&gt;
 D:\Aplica\BiscayAplica\FORCAGES\METEO\ALADIN_BULKHUMI_OPASYMP_19723_20088.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Convert generic Netcdf CF to MOHID(.hdf5)  ===&lt;br /&gt;
&lt;br /&gt;
This sample is for converting a typical GFS file&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;begin_file&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ACTION : CONVERT NETCDF CF TO HDF5 MOHID&lt;br /&gt;
 HDF5_OUT : 1&lt;br /&gt;
 OUTPUTFILENAME : ..\..\data\hdf5\GFS.hdf5&lt;br /&gt;
 NETCDF_OUT : 1&lt;br /&gt;
 OUTPUT_NETCDF_FILE : ..\..\data\netcdf\GFS.nc&lt;br /&gt;
 &amp;lt;&amp;lt;begin_time&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : time&lt;br /&gt;
 &amp;lt;&amp;lt;end_time&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_grid&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME_LAT : latitude&lt;br /&gt;
 NETCDF_NAME_LONG : longitude&lt;br /&gt;
 NETCDF_NAME_MAPPING : TMP_10mb&lt;br /&gt;
 MAPPING_LIMIT : -10000&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;end_grid&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 PROPERTIES_NUMBER : 6 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : PRMSL_meansealevel&lt;br /&gt;
 NAME : atmospheric pressure&lt;br /&gt;
 UNITS : Pa&lt;br /&gt;
 DESCRIPTION : GFS&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : UGRD_10mb&lt;br /&gt;
 NAME : wind velocity X&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : VGRD_10mb&lt;br /&gt;
 NAME : wind velocity Y&lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus&lt;br /&gt;
 NAME                     : wind modulus &lt;br /&gt;
 UNITS : m/s&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 VECTOR_INTENSITY         : 1&lt;br /&gt;
 VECTOR_X                 : wind velocity X&lt;br /&gt;
 VECTOR_Y                 : wind velocity Y&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME              : wind_modulus_beaufort &lt;br /&gt;
 NAME                     : wind modulus beaufort &lt;br /&gt;
 UNITS : beaufort scale&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 BEAUFORT_SCALE           : 1&lt;br /&gt;
 VECTOR_X                 : wind modulus&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_field&amp;gt;&amp;gt;&lt;br /&gt;
 NETCDF_NAME : TMP_2maboveground&lt;br /&gt;
 NAME : air temperature&lt;br /&gt;
 UNITS : oC&lt;br /&gt;
 DESCRIPTION : MOHID&lt;br /&gt;
 DIM : 2&lt;br /&gt;
 ADD_FACTOR  : -273&lt;br /&gt;
 &amp;lt;&amp;lt;end_field&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;begin_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 ..\..\data\netcdf\gfs_4_20111115.nc&lt;br /&gt;
 &amp;lt;&amp;lt;end_input_files&amp;gt;&amp;gt;&lt;br /&gt;
 &amp;lt;end_file&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== OceanColor modules compilation ==&lt;br /&gt;
Compiling the [[ConvertToHDF5]] tool with the OceanColor modules is more complicated than one might expect. A solution is proposed here for a release version using the Compaq Visual Fortran 6.6c. The difficulties rise because C code is embedded with a fortran interface and also, extra libraries such as hdf4 are required.&lt;br /&gt;
&lt;br /&gt;
=== Pre-requisites ===&lt;br /&gt;
&lt;br /&gt;
This is a list of prerequisites to successfully compile the tool:&lt;br /&gt;
*Compaq Visual Fortran 6.5 with patch 6.6c,&lt;br /&gt;
*VS .NET 2003 (Vc7 in particular),&lt;br /&gt;
*Hdf5 libraries ('''hdf5.lib''' '''hdf5_fortran.lib''' '''hdf5_hl.lib'''),&lt;br /&gt;
*Netcdf libraries ('''netcdf.lib''' '''netcdf_.lib'''),&lt;br /&gt;
*Hdf4 libraries ('''hd421.lib''', '''hm421.lib'''),&lt;br /&gt;
*szlib, zlib and jpeg libraries ('''szlib.lib''', '''zlib.lib''' and '''libjpeg.lib'''),&lt;br /&gt;
*the fortran source files ('''ModuleConvertModisL2.F90 ModuleConvertModisL3.F90 ModuleConvertOceanColorL2.F90'''),&lt;br /&gt;
*the C source files and their fortran interface files ('''readL2scan.c readL2Seadas.c''' and '''cdata.f crossp.f fgeonav.f''').&lt;br /&gt;
&lt;br /&gt;
=== CVF IDE configuration ===&lt;br /&gt;
# Configure everything as specified in [[Compiling with CVF]].&lt;br /&gt;
# Add the source files listed in the prerequisites above to the source files listing.&lt;br /&gt;
# Go to '''Tools--&amp;gt;Options...--&amp;gt;Directories'''. There, add the '''$DOTNET2K3/Vc7/bin''' to the '''Executable files''''; the '''$DOTNET2K3/Vc7/include''' and '''$DOTNET2K3/Vc7/PlatformSDK/include''' to the '''Include files'''; and finally, the '''$DOTNET2K3/Vc7/lib''', '''$DOTNET2K3/Vc7/PlatformSDK/lib''' and  '''$DOTNET2K3/Vc7/PlatformSDK/bin''' to the '''Library files'''.&lt;br /&gt;
# Go to '''Projects--&amp;gt;Settings--&amp;gt;Release--&amp;gt;Link--&amp;gt;Input'''. There, add the following libraries: '''netcdf.lib netcdf_.lib hd421.lib hm421.lib libjpeg.lib'''. (Make sure the hdf5 libraries as well as the szlib and zlib libraries are already mentioned).&lt;br /&gt;
&lt;br /&gt;
=== Troubleshoots ===&lt;br /&gt;
'''Q: I get unresolved external references during linkage, but I have all the libraries mentioned above included. What should I do?'''&lt;br /&gt;
&lt;br /&gt;
A: Unresolved external references can come out for two reasons:&lt;br /&gt;
#you didn't specified all the libraries required or all the paths for the default libraries or,&lt;br /&gt;
#[http://en.wikipedia.org/wiki/Name_decoration name mangling] problems. Use the [[dumpbin]] utility to the libraries to checkout which language convention they are using. If that's the problem then you need to try to get new libraries with the correct naming convention.&lt;br /&gt;
&lt;br /&gt;
That's it, you should now be able to build the [[ConvertToHdf5]] project successfully.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Q: I got a message saying the entry point _NF_PUT_ATT_REAL@28 could not be located in netcdf.dll'''&lt;br /&gt;
&lt;br /&gt;
A: copy the file netcdf.dll to the exe folder&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF5 Homepage]&lt;br /&gt;
*[http://www.hdfgroup.org/ HDF4 Homepage]&lt;br /&gt;
&lt;br /&gt;
== Links ==&lt;br /&gt;
&lt;br /&gt;
*[[Module_Atmosphere]]&lt;br /&gt;
*[[Module_InterfaceWaterAir]]&lt;br /&gt;
*[[Coupling_Water-Atmosphere_User_Manual]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Tools]]&lt;br /&gt;
[[Category:Hdf5]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6127</id>
		<title>Module Lagrangian</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6127"/>
				<updated>2012-04-27T14:29:07Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Main processes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
Lagrangian transport models are very useful to simulate localized processes with sharp gradients (submarine outfalls, sediment erosion due to dredging works, hydrodynamic calibration, oil dispersion, etc.).&lt;br /&gt;
MOHID’s Lagrangian module uses the concept of lagrangian tracers. The most important property of a tracer is its position (x,y,z). For a physicist a tracer can be a water mass, for a geologist it can be a sediment particle or a group of sediment particles and for a chemist it can be a molecule or a group of molecules. A biologist can spot phytoplankton cells in a tracer (at the bottom of the food chain) as well as a shark (at the top of the food chain), which means that a model of this kind can simulate a wide spectrum of processes.&lt;br /&gt;
The movement of the tracers can be influenced by the velocity field from the hydrodynamic module, by the wind from the surface module, by the spreading velocity from oil dispersion module and by random velocity.&lt;br /&gt;
At the present stage the model is able to simulate oil dispersion, water quality processes and sediment transport. To simulate oil dispersion the lagrangian module interacts with the [[Module Oil|oil dispersion module]], to simulate water quality the lagrangian module uses the [[Module WaterQuality|water quality module]]. Sediment transport can be associated directly to the tracers using the concept of [[settling velocity]]. Another feature of the lagrangian transport model is the ability to calculate [[residence time]]. This can be very useful when studying the exchange of water masses in bays or estuaries.&lt;br /&gt;
&lt;br /&gt;
== Concepts ==&lt;br /&gt;
Like referred above, the Lagrangian module uses the concept of tracer. The tracers are characterized by there spatial coordinates, volume and a list of properties (each with a given concentration). The properties can be the same one like the ones described in the water properties module or coliform bacteria. Each tracer has associated a time to perform the random movement.&lt;br /&gt;
The tracers are “born” at origins. Tracers which belong to the same origin have the same list of properties and use the same parameters for random walk, coliform decay, etc. Origins can differ in the way they emit tracers. &lt;br /&gt;
&lt;br /&gt;
There are three different ways to define origins in space:&lt;br /&gt;
*a '''[[Point Origin]]''' emits tracers at a given point;&lt;br /&gt;
*a '''[[Boxes#Module_Lagrangian|Box Origin]]''' emits tracers over a given area;&lt;br /&gt;
*a '''Accident Origin''' emit tracers in a circular form around a point;&lt;br /&gt;
&lt;br /&gt;
There are two different ways in which origins can emit tracers in time:&lt;br /&gt;
*a '''Continuous Origin''' emits tracers during a period of time;&lt;br /&gt;
*a '''Instantaneous Origin''' emits tracers at one instant;&lt;br /&gt;
*a '''Moving Origin''' emits tracers during a period of time along a defined track;&lt;br /&gt;
Origins can be grouped together in Groups. Origins which belong to the same group are grouped together in the output file, so it is more easy to analyze the results.&lt;br /&gt;
&lt;br /&gt;
== Main processes ==&lt;br /&gt;
&lt;br /&gt;
=== Tracer Movement ===&lt;br /&gt;
&lt;br /&gt;
=== Turbulent Diffusion ===&lt;br /&gt;
&lt;br /&gt;
=== Residence Time ===&lt;br /&gt;
&lt;br /&gt;
==== [[Boxes#Module_Lagrangian_2|Monitor boxes]] ====&lt;br /&gt;
&lt;br /&gt;
=== Oil spills ===&lt;br /&gt;
&lt;br /&gt;
=== Water quality processes ===&lt;br /&gt;
&lt;br /&gt;
To use the Water Quality processes in the lagrangian module it is necessary to define a WaterQuality.dat file different from the one used for the eulerian calculations. Defining its location by the keyword WQM_DATA_FILE. &lt;br /&gt;
&lt;br /&gt;
The waterquality files need to include the different parameters separately in two files in the case that both waterquality processes are calculated. &lt;br /&gt;
&lt;br /&gt;
==== Larvae ====&lt;br /&gt;
&lt;br /&gt;
To model larvae as lagrangian properties it is necessary to configure the properties larvae, age and oxygen in the lagrangian file &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME           : Generic&lt;br /&gt;
 EMISSION_SPATIAL      : Box&lt;br /&gt;
 EMISSION_TEMPORAL     : Instantaneous&lt;br /&gt;
 MOVEMENT              : NotRandom&lt;br /&gt;
 ADVECTION             : 1&lt;br /&gt;
 BOX_NUMBER            : 1&lt;br /&gt;
 BOXVOLINIC            : 10000&lt;br /&gt;
 OLD                   : 0&lt;br /&gt;
 WQM_DATA_FILE         : ..\..\Test\data\WaterQuality_3.dat&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : larvae&lt;br /&gt;
 UNITS                 : kg/m3&lt;br /&gt;
 CONCENTRATION         : 10e4&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : age&lt;br /&gt;
 UNITS                 : ---&lt;br /&gt;
 CONCENTRATION         : 5.6&lt;br /&gt;
 MIN_CONCENTRATION     : 0.&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : oxygen&lt;br /&gt;
 UNITS                 : mg/l&lt;br /&gt;
 CONCENTRATION         : 10.&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 10.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Ecology ====&lt;br /&gt;
&lt;br /&gt;
==== First order decayment (coliform bacteria) ====&lt;br /&gt;
&lt;br /&gt;
=== Sediment transport ===&lt;br /&gt;
&lt;br /&gt;
=== Contaminants/Partition coefficients ===&lt;br /&gt;
&lt;br /&gt;
== Other features ==&lt;br /&gt;
&lt;br /&gt;
== User manual ==&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
&lt;br /&gt;
Add in '''nomfich.dat'''&lt;br /&gt;
 PARTIC_DATA                   : ../../WestIberia_ET2_2K4/Portugal/data/Lagrangian_1.dat&lt;br /&gt;
 PARTIC_HDF                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.hdf&lt;br /&gt;
 PARTIC_FIN                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.fin&lt;br /&gt;
 &lt;br /&gt;
Add in '''model.dat'''&lt;br /&gt;
 LAGRANGIAN                    : 1&lt;br /&gt;
&lt;br /&gt;
Create '''Lagrangian.dat'''&lt;br /&gt;
 OUTPUT_TIME             : 0 3600&lt;br /&gt;
 OUTPUT_MAX_TRACER       : 1&lt;br /&gt;
 OUTPUT_CONC             : 2&lt;br /&gt;
 &lt;br /&gt;
 DT_PARTIC               : 60&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME             : Off Vigo&lt;br /&gt;
 GROUP_ID                : 1&lt;br /&gt;
 EMISSION_SPATIAL        : Point&lt;br /&gt;
 EMISSION_TEMPORAL       : Instantaneous&lt;br /&gt;
 BOTTOM_EMISSION         : 0&lt;br /&gt;
 OLD                     : 0&lt;br /&gt;
 &lt;br /&gt;
 POINT_VOLUME            : 1&lt;br /&gt;
 NBR_PARTIC              : 8&lt;br /&gt;
 &lt;br /&gt;
 FLOAT                   : 1&lt;br /&gt;
 &lt;br /&gt;
 MOVEMENT                : SullivanAllen&lt;br /&gt;
 VARVELHX                : 0.1&lt;br /&gt;
 VARVELH                 : 0.03&lt;br /&gt;
 TURB_V                  : Constant&lt;br /&gt;
 VARVELVX                : 0.01&lt;br /&gt;
 VARVELV                 : 0.003&lt;br /&gt;
 &lt;br /&gt;
 POSITION_COORDINATES    : -10.0 43&lt;br /&gt;
 !POSITION_CELLS          : 45.5 21.5&lt;br /&gt;
 DEPTH_METERS            : 0.&lt;br /&gt;
 &lt;br /&gt;
 START_PARTIC_EMIT       : 2007 04 25 09 33 20&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.mohid.com/hydrogroup/mohidkeywords/_MohidWater.xml MohidWater keywords]&lt;br /&gt;
&lt;br /&gt;
[[Category:Modules]]&lt;br /&gt;
[[Category:MOHID Water]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6126</id>
		<title>Module Lagrangian</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6126"/>
				<updated>2012-04-27T14:28:32Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Main processes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
Lagrangian transport models are very useful to simulate localized processes with sharp gradients (submarine outfalls, sediment erosion due to dredging works, hydrodynamic calibration, oil dispersion, etc.).&lt;br /&gt;
MOHID’s Lagrangian module uses the concept of lagrangian tracers. The most important property of a tracer is its position (x,y,z). For a physicist a tracer can be a water mass, for a geologist it can be a sediment particle or a group of sediment particles and for a chemist it can be a molecule or a group of molecules. A biologist can spot phytoplankton cells in a tracer (at the bottom of the food chain) as well as a shark (at the top of the food chain), which means that a model of this kind can simulate a wide spectrum of processes.&lt;br /&gt;
The movement of the tracers can be influenced by the velocity field from the hydrodynamic module, by the wind from the surface module, by the spreading velocity from oil dispersion module and by random velocity.&lt;br /&gt;
At the present stage the model is able to simulate oil dispersion, water quality processes and sediment transport. To simulate oil dispersion the lagrangian module interacts with the [[Module Oil|oil dispersion module]], to simulate water quality the lagrangian module uses the [[Module WaterQuality|water quality module]]. Sediment transport can be associated directly to the tracers using the concept of [[settling velocity]]. Another feature of the lagrangian transport model is the ability to calculate [[residence time]]. This can be very useful when studying the exchange of water masses in bays or estuaries.&lt;br /&gt;
&lt;br /&gt;
== Concepts ==&lt;br /&gt;
Like referred above, the Lagrangian module uses the concept of tracer. The tracers are characterized by there spatial coordinates, volume and a list of properties (each with a given concentration). The properties can be the same one like the ones described in the water properties module or coliform bacteria. Each tracer has associated a time to perform the random movement.&lt;br /&gt;
The tracers are “born” at origins. Tracers which belong to the same origin have the same list of properties and use the same parameters for random walk, coliform decay, etc. Origins can differ in the way they emit tracers. &lt;br /&gt;
&lt;br /&gt;
There are three different ways to define origins in space:&lt;br /&gt;
*a '''[[Point Origin]]''' emits tracers at a given point;&lt;br /&gt;
*a '''[[Boxes#Module_Lagrangian|Box Origin]]''' emits tracers over a given area;&lt;br /&gt;
*a '''Accident Origin''' emit tracers in a circular form around a point;&lt;br /&gt;
&lt;br /&gt;
There are two different ways in which origins can emit tracers in time:&lt;br /&gt;
*a '''Continuous Origin''' emits tracers during a period of time;&lt;br /&gt;
*a '''Instantaneous Origin''' emits tracers at one instant;&lt;br /&gt;
*a '''Moving Origin''' emits tracers during a period of time along a defined track;&lt;br /&gt;
Origins can be grouped together in Groups. Origins which belong to the same group are grouped together in the output file, so it is more easy to analyze the results.&lt;br /&gt;
&lt;br /&gt;
== Main processes ==&lt;br /&gt;
&lt;br /&gt;
=== Tracer Movement ===&lt;br /&gt;
&lt;br /&gt;
=== Turbulent Diffusion ===&lt;br /&gt;
&lt;br /&gt;
=== Residence Time ===&lt;br /&gt;
&lt;br /&gt;
==== [[Boxes#Module_Lagrangian|Monitor boxes]] ====&lt;br /&gt;
&lt;br /&gt;
=== Oil spills ===&lt;br /&gt;
&lt;br /&gt;
=== Water quality processes ===&lt;br /&gt;
&lt;br /&gt;
To use the Water Quality processes in the lagrangian module it is necessary to define a WaterQuality.dat file different from the one used for the eulerian calculations. Defining its location by the keyword WQM_DATA_FILE. &lt;br /&gt;
&lt;br /&gt;
The waterquality files need to include the different parameters separately in two files in the case that both waterquality processes are calculated. &lt;br /&gt;
&lt;br /&gt;
==== Larvae ====&lt;br /&gt;
&lt;br /&gt;
To model larvae as lagrangian properties it is necessary to configure the properties larvae, age and oxygen in the lagrangian file &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME           : Generic&lt;br /&gt;
 EMISSION_SPATIAL      : Box&lt;br /&gt;
 EMISSION_TEMPORAL     : Instantaneous&lt;br /&gt;
 MOVEMENT              : NotRandom&lt;br /&gt;
 ADVECTION             : 1&lt;br /&gt;
 BOX_NUMBER            : 1&lt;br /&gt;
 BOXVOLINIC            : 10000&lt;br /&gt;
 OLD                   : 0&lt;br /&gt;
 WQM_DATA_FILE         : ..\..\Test\data\WaterQuality_3.dat&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : larvae&lt;br /&gt;
 UNITS                 : kg/m3&lt;br /&gt;
 CONCENTRATION         : 10e4&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : age&lt;br /&gt;
 UNITS                 : ---&lt;br /&gt;
 CONCENTRATION         : 5.6&lt;br /&gt;
 MIN_CONCENTRATION     : 0.&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : oxygen&lt;br /&gt;
 UNITS                 : mg/l&lt;br /&gt;
 CONCENTRATION         : 10.&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 10.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Ecology ====&lt;br /&gt;
&lt;br /&gt;
==== First order decayment (coliform bacteria) ====&lt;br /&gt;
&lt;br /&gt;
=== Sediment transport ===&lt;br /&gt;
&lt;br /&gt;
=== Contaminants/Partition coefficients ===&lt;br /&gt;
&lt;br /&gt;
== Other features ==&lt;br /&gt;
&lt;br /&gt;
== User manual ==&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
&lt;br /&gt;
Add in '''nomfich.dat'''&lt;br /&gt;
 PARTIC_DATA                   : ../../WestIberia_ET2_2K4/Portugal/data/Lagrangian_1.dat&lt;br /&gt;
 PARTIC_HDF                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.hdf&lt;br /&gt;
 PARTIC_FIN                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.fin&lt;br /&gt;
 &lt;br /&gt;
Add in '''model.dat'''&lt;br /&gt;
 LAGRANGIAN                    : 1&lt;br /&gt;
&lt;br /&gt;
Create '''Lagrangian.dat'''&lt;br /&gt;
 OUTPUT_TIME             : 0 3600&lt;br /&gt;
 OUTPUT_MAX_TRACER       : 1&lt;br /&gt;
 OUTPUT_CONC             : 2&lt;br /&gt;
 &lt;br /&gt;
 DT_PARTIC               : 60&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME             : Off Vigo&lt;br /&gt;
 GROUP_ID                : 1&lt;br /&gt;
 EMISSION_SPATIAL        : Point&lt;br /&gt;
 EMISSION_TEMPORAL       : Instantaneous&lt;br /&gt;
 BOTTOM_EMISSION         : 0&lt;br /&gt;
 OLD                     : 0&lt;br /&gt;
 &lt;br /&gt;
 POINT_VOLUME            : 1&lt;br /&gt;
 NBR_PARTIC              : 8&lt;br /&gt;
 &lt;br /&gt;
 FLOAT                   : 1&lt;br /&gt;
 &lt;br /&gt;
 MOVEMENT                : SullivanAllen&lt;br /&gt;
 VARVELHX                : 0.1&lt;br /&gt;
 VARVELH                 : 0.03&lt;br /&gt;
 TURB_V                  : Constant&lt;br /&gt;
 VARVELVX                : 0.01&lt;br /&gt;
 VARVELV                 : 0.003&lt;br /&gt;
 &lt;br /&gt;
 POSITION_COORDINATES    : -10.0 43&lt;br /&gt;
 !POSITION_CELLS          : 45.5 21.5&lt;br /&gt;
 DEPTH_METERS            : 0.&lt;br /&gt;
 &lt;br /&gt;
 START_PARTIC_EMIT       : 2007 04 25 09 33 20&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.mohid.com/hydrogroup/mohidkeywords/_MohidWater.xml MohidWater keywords]&lt;br /&gt;
&lt;br /&gt;
[[Category:Modules]]&lt;br /&gt;
[[Category:MOHID Water]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6125</id>
		<title>Module Lagrangian</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6125"/>
				<updated>2012-04-27T14:27:47Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Concepts */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
Lagrangian transport models are very useful to simulate localized processes with sharp gradients (submarine outfalls, sediment erosion due to dredging works, hydrodynamic calibration, oil dispersion, etc.).&lt;br /&gt;
MOHID’s Lagrangian module uses the concept of lagrangian tracers. The most important property of a tracer is its position (x,y,z). For a physicist a tracer can be a water mass, for a geologist it can be a sediment particle or a group of sediment particles and for a chemist it can be a molecule or a group of molecules. A biologist can spot phytoplankton cells in a tracer (at the bottom of the food chain) as well as a shark (at the top of the food chain), which means that a model of this kind can simulate a wide spectrum of processes.&lt;br /&gt;
The movement of the tracers can be influenced by the velocity field from the hydrodynamic module, by the wind from the surface module, by the spreading velocity from oil dispersion module and by random velocity.&lt;br /&gt;
At the present stage the model is able to simulate oil dispersion, water quality processes and sediment transport. To simulate oil dispersion the lagrangian module interacts with the [[Module Oil|oil dispersion module]], to simulate water quality the lagrangian module uses the [[Module WaterQuality|water quality module]]. Sediment transport can be associated directly to the tracers using the concept of [[settling velocity]]. Another feature of the lagrangian transport model is the ability to calculate [[residence time]]. This can be very useful when studying the exchange of water masses in bays or estuaries.&lt;br /&gt;
&lt;br /&gt;
== Concepts ==&lt;br /&gt;
Like referred above, the Lagrangian module uses the concept of tracer. The tracers are characterized by there spatial coordinates, volume and a list of properties (each with a given concentration). The properties can be the same one like the ones described in the water properties module or coliform bacteria. Each tracer has associated a time to perform the random movement.&lt;br /&gt;
The tracers are “born” at origins. Tracers which belong to the same origin have the same list of properties and use the same parameters for random walk, coliform decay, etc. Origins can differ in the way they emit tracers. &lt;br /&gt;
&lt;br /&gt;
There are three different ways to define origins in space:&lt;br /&gt;
*a '''[[Point Origin]]''' emits tracers at a given point;&lt;br /&gt;
*a '''[[Boxes#Module_Lagrangian|Box Origin]]''' emits tracers over a given area;&lt;br /&gt;
*a '''Accident Origin''' emit tracers in a circular form around a point;&lt;br /&gt;
&lt;br /&gt;
There are two different ways in which origins can emit tracers in time:&lt;br /&gt;
*a '''Continuous Origin''' emits tracers during a period of time;&lt;br /&gt;
*a '''Instantaneous Origin''' emits tracers at one instant;&lt;br /&gt;
*a '''Moving Origin''' emits tracers during a period of time along a defined track;&lt;br /&gt;
Origins can be grouped together in Groups. Origins which belong to the same group are grouped together in the output file, so it is more easy to analyze the results.&lt;br /&gt;
&lt;br /&gt;
== Main processes ==&lt;br /&gt;
&lt;br /&gt;
=== Tracer Movement ===&lt;br /&gt;
&lt;br /&gt;
=== Turbulent Diffusion ===&lt;br /&gt;
&lt;br /&gt;
=== Residence Time ===&lt;br /&gt;
&lt;br /&gt;
==== Monitor boxes ====&lt;br /&gt;
&lt;br /&gt;
=== Oil spills ===&lt;br /&gt;
&lt;br /&gt;
=== Water quality processes ===&lt;br /&gt;
&lt;br /&gt;
To use the Water Quality processes in the lagrangian module it is necessary to define a WaterQuality.dat file different from the one used for the eulerian calculations. Defining its location by the keyword WQM_DATA_FILE. &lt;br /&gt;
&lt;br /&gt;
The waterquality files need to include the different parameters separately in two files in the case that both waterquality processes are calculated. &lt;br /&gt;
&lt;br /&gt;
==== Larvae ====&lt;br /&gt;
&lt;br /&gt;
To model larvae as lagrangian properties it is necessary to configure the properties larvae, age and oxygen in the lagrangian file &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME           : Generic&lt;br /&gt;
 EMISSION_SPATIAL      : Box&lt;br /&gt;
 EMISSION_TEMPORAL     : Instantaneous&lt;br /&gt;
 MOVEMENT              : NotRandom&lt;br /&gt;
 ADVECTION             : 1&lt;br /&gt;
 BOX_NUMBER            : 1&lt;br /&gt;
 BOXVOLINIC            : 10000&lt;br /&gt;
 OLD                   : 0&lt;br /&gt;
 WQM_DATA_FILE         : ..\..\Test\data\WaterQuality_3.dat&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : larvae&lt;br /&gt;
 UNITS                 : kg/m3&lt;br /&gt;
 CONCENTRATION         : 10e4&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : age&lt;br /&gt;
 UNITS                 : ---&lt;br /&gt;
 CONCENTRATION         : 5.6&lt;br /&gt;
 MIN_CONCENTRATION     : 0.&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : oxygen&lt;br /&gt;
 UNITS                 : mg/l&lt;br /&gt;
 CONCENTRATION         : 10.&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 10.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Ecology ====&lt;br /&gt;
&lt;br /&gt;
==== First order decayment (coliform bacteria) ====&lt;br /&gt;
&lt;br /&gt;
=== Sediment transport ===&lt;br /&gt;
&lt;br /&gt;
=== Contaminants/Partition coefficients ===&lt;br /&gt;
&lt;br /&gt;
== Other features ==&lt;br /&gt;
&lt;br /&gt;
== User manual ==&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
&lt;br /&gt;
Add in '''nomfich.dat'''&lt;br /&gt;
 PARTIC_DATA                   : ../../WestIberia_ET2_2K4/Portugal/data/Lagrangian_1.dat&lt;br /&gt;
 PARTIC_HDF                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.hdf&lt;br /&gt;
 PARTIC_FIN                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.fin&lt;br /&gt;
 &lt;br /&gt;
Add in '''model.dat'''&lt;br /&gt;
 LAGRANGIAN                    : 1&lt;br /&gt;
&lt;br /&gt;
Create '''Lagrangian.dat'''&lt;br /&gt;
 OUTPUT_TIME             : 0 3600&lt;br /&gt;
 OUTPUT_MAX_TRACER       : 1&lt;br /&gt;
 OUTPUT_CONC             : 2&lt;br /&gt;
 &lt;br /&gt;
 DT_PARTIC               : 60&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME             : Off Vigo&lt;br /&gt;
 GROUP_ID                : 1&lt;br /&gt;
 EMISSION_SPATIAL        : Point&lt;br /&gt;
 EMISSION_TEMPORAL       : Instantaneous&lt;br /&gt;
 BOTTOM_EMISSION         : 0&lt;br /&gt;
 OLD                     : 0&lt;br /&gt;
 &lt;br /&gt;
 POINT_VOLUME            : 1&lt;br /&gt;
 NBR_PARTIC              : 8&lt;br /&gt;
 &lt;br /&gt;
 FLOAT                   : 1&lt;br /&gt;
 &lt;br /&gt;
 MOVEMENT                : SullivanAllen&lt;br /&gt;
 VARVELHX                : 0.1&lt;br /&gt;
 VARVELH                 : 0.03&lt;br /&gt;
 TURB_V                  : Constant&lt;br /&gt;
 VARVELVX                : 0.01&lt;br /&gt;
 VARVELV                 : 0.003&lt;br /&gt;
 &lt;br /&gt;
 POSITION_COORDINATES    : -10.0 43&lt;br /&gt;
 !POSITION_CELLS          : 45.5 21.5&lt;br /&gt;
 DEPTH_METERS            : 0.&lt;br /&gt;
 &lt;br /&gt;
 START_PARTIC_EMIT       : 2007 04 25 09 33 20&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.mohid.com/hydrogroup/mohidkeywords/_MohidWater.xml MohidWater keywords]&lt;br /&gt;
&lt;br /&gt;
[[Category:Modules]]&lt;br /&gt;
[[Category:MOHID Water]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6124</id>
		<title>Module Lagrangian</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Module_Lagrangian&amp;diff=6124"/>
				<updated>2012-04-27T14:27:24Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
Lagrangian transport models are very useful to simulate localized processes with sharp gradients (submarine outfalls, sediment erosion due to dredging works, hydrodynamic calibration, oil dispersion, etc.).&lt;br /&gt;
MOHID’s Lagrangian module uses the concept of lagrangian tracers. The most important property of a tracer is its position (x,y,z). For a physicist a tracer can be a water mass, for a geologist it can be a sediment particle or a group of sediment particles and for a chemist it can be a molecule or a group of molecules. A biologist can spot phytoplankton cells in a tracer (at the bottom of the food chain) as well as a shark (at the top of the food chain), which means that a model of this kind can simulate a wide spectrum of processes.&lt;br /&gt;
The movement of the tracers can be influenced by the velocity field from the hydrodynamic module, by the wind from the surface module, by the spreading velocity from oil dispersion module and by random velocity.&lt;br /&gt;
At the present stage the model is able to simulate oil dispersion, water quality processes and sediment transport. To simulate oil dispersion the lagrangian module interacts with the [[Module Oil|oil dispersion module]], to simulate water quality the lagrangian module uses the [[Module WaterQuality|water quality module]]. Sediment transport can be associated directly to the tracers using the concept of [[settling velocity]]. Another feature of the lagrangian transport model is the ability to calculate [[residence time]]. This can be very useful when studying the exchange of water masses in bays or estuaries.&lt;br /&gt;
&lt;br /&gt;
== Concepts ==&lt;br /&gt;
Like referred above, the Lagrangian module uses the concept of tracer. The tracers are characterized by there spatial coordinates, volume and a list of properties (each with a given concentration). The properties can be the same one like the ones described in the water properties module or coliform bacteria. Each tracer has associated a time to perform the random movement.&lt;br /&gt;
The tracers are “born” at origins. Tracers which belong to the same origin have the same list of properties and use the same parameters for random walk, coliform decay, etc. Origins can differ in the way they emit tracers. &lt;br /&gt;
&lt;br /&gt;
There are three different ways to define origins in space:&lt;br /&gt;
*a '''[[Point Origin]]''' emits tracers at a given point;&lt;br /&gt;
*a '''[[Boxes|Box Origin]]''' emits tracers over a given area;&lt;br /&gt;
*a '''Accident Origin''' emit tracers in a circular form around a point;&lt;br /&gt;
&lt;br /&gt;
There are two different ways in which origins can emit tracers in time:&lt;br /&gt;
*a '''Continuous Origin''' emits tracers during a period of time;&lt;br /&gt;
*a '''Instantaneous Origin''' emits tracers at one instant;&lt;br /&gt;
*a '''Moving Origin''' emits tracers during a period of time along a defined track;&lt;br /&gt;
Origins can be grouped together in Groups. Origins which belong to the same group are grouped together in the output file, so it is more easy to analyze the results.&lt;br /&gt;
&lt;br /&gt;
== Main processes ==&lt;br /&gt;
&lt;br /&gt;
=== Tracer Movement ===&lt;br /&gt;
&lt;br /&gt;
=== Turbulent Diffusion ===&lt;br /&gt;
&lt;br /&gt;
=== Residence Time ===&lt;br /&gt;
&lt;br /&gt;
==== Monitor boxes ====&lt;br /&gt;
&lt;br /&gt;
=== Oil spills ===&lt;br /&gt;
&lt;br /&gt;
=== Water quality processes ===&lt;br /&gt;
&lt;br /&gt;
To use the Water Quality processes in the lagrangian module it is necessary to define a WaterQuality.dat file different from the one used for the eulerian calculations. Defining its location by the keyword WQM_DATA_FILE. &lt;br /&gt;
&lt;br /&gt;
The waterquality files need to include the different parameters separately in two files in the case that both waterquality processes are calculated. &lt;br /&gt;
&lt;br /&gt;
==== Larvae ====&lt;br /&gt;
&lt;br /&gt;
To model larvae as lagrangian properties it is necessary to configure the properties larvae, age and oxygen in the lagrangian file &lt;br /&gt;
&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME           : Generic&lt;br /&gt;
 EMISSION_SPATIAL      : Box&lt;br /&gt;
 EMISSION_TEMPORAL     : Instantaneous&lt;br /&gt;
 MOVEMENT              : NotRandom&lt;br /&gt;
 ADVECTION             : 1&lt;br /&gt;
 BOX_NUMBER            : 1&lt;br /&gt;
 BOXVOLINIC            : 10000&lt;br /&gt;
 OLD                   : 0&lt;br /&gt;
 WQM_DATA_FILE         : ..\..\Test\data\WaterQuality_3.dat&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : larvae&lt;br /&gt;
 UNITS                 : kg/m3&lt;br /&gt;
 CONCENTRATION         : 10e4&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : age&lt;br /&gt;
 UNITS                 : ---&lt;br /&gt;
 CONCENTRATION         : 5.6&lt;br /&gt;
 MIN_CONCENTRATION     : 0.&lt;br /&gt;
 AMBIENT_CONC          : 0.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;&amp;lt;BeginProperty&amp;gt;&amp;gt;&lt;br /&gt;
 NAME                  : oxygen&lt;br /&gt;
 UNITS                 : mg/l&lt;br /&gt;
 CONCENTRATION         : 10.&lt;br /&gt;
 MIN_CONCENTRATION     : 0.0&lt;br /&gt;
 AMBIENT_CONC          : 10.0&lt;br /&gt;
 &amp;lt;&amp;lt;EndProperty&amp;gt;&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Ecology ====&lt;br /&gt;
&lt;br /&gt;
==== First order decayment (coliform bacteria) ====&lt;br /&gt;
&lt;br /&gt;
=== Sediment transport ===&lt;br /&gt;
&lt;br /&gt;
=== Contaminants/Partition coefficients ===&lt;br /&gt;
&lt;br /&gt;
== Other features ==&lt;br /&gt;
&lt;br /&gt;
== User manual ==&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
&lt;br /&gt;
Add in '''nomfich.dat'''&lt;br /&gt;
 PARTIC_DATA                   : ../../WestIberia_ET2_2K4/Portugal/data/Lagrangian_1.dat&lt;br /&gt;
 PARTIC_HDF                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.hdf&lt;br /&gt;
 PARTIC_FIN                    : ../../WestIberia_ET2_2K4/Portugal/res/Lagrangian_1.fin&lt;br /&gt;
 &lt;br /&gt;
Add in '''model.dat'''&lt;br /&gt;
 LAGRANGIAN                    : 1&lt;br /&gt;
&lt;br /&gt;
Create '''Lagrangian.dat'''&lt;br /&gt;
 OUTPUT_TIME             : 0 3600&lt;br /&gt;
 OUTPUT_MAX_TRACER       : 1&lt;br /&gt;
 OUTPUT_CONC             : 2&lt;br /&gt;
 &lt;br /&gt;
 DT_PARTIC               : 60&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ORIGIN_NAME             : Off Vigo&lt;br /&gt;
 GROUP_ID                : 1&lt;br /&gt;
 EMISSION_SPATIAL        : Point&lt;br /&gt;
 EMISSION_TEMPORAL       : Instantaneous&lt;br /&gt;
 BOTTOM_EMISSION         : 0&lt;br /&gt;
 OLD                     : 0&lt;br /&gt;
 &lt;br /&gt;
 POINT_VOLUME            : 1&lt;br /&gt;
 NBR_PARTIC              : 8&lt;br /&gt;
 &lt;br /&gt;
 FLOAT                   : 1&lt;br /&gt;
 &lt;br /&gt;
 MOVEMENT                : SullivanAllen&lt;br /&gt;
 VARVELHX                : 0.1&lt;br /&gt;
 VARVELH                 : 0.03&lt;br /&gt;
 TURB_V                  : Constant&lt;br /&gt;
 VARVELVX                : 0.01&lt;br /&gt;
 VARVELV                 : 0.003&lt;br /&gt;
 &lt;br /&gt;
 POSITION_COORDINATES    : -10.0 43&lt;br /&gt;
 !POSITION_CELLS          : 45.5 21.5&lt;br /&gt;
 DEPTH_METERS            : 0.&lt;br /&gt;
 &lt;br /&gt;
 START_PARTIC_EMIT       : 2007 04 25 09 33 20&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
*[http://www.mohid.com/hydrogroup/mohidkeywords/_MohidWater.xml MohidWater keywords]&lt;br /&gt;
&lt;br /&gt;
[[Category:Modules]]&lt;br /&gt;
[[Category:MOHID Water]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6123</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6123"/>
				<updated>2012-04-27T14:25:24Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===[[Module WaterProperties]]===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===[[Module Lagrangian]]===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6\times 10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6\times 10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
Regarding the lagrangian particules, there is one output file per box: a LBM file. This file contains the total volume of lagrangian tracers per origin at each time instant, one origin per column.&lt;br /&gt;
&lt;br /&gt;
===[[Module Hydrodynamic]]===&lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
&lt;br /&gt;
===[[Module WaterProperties]]===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===[[Module Lagrangian]]===&lt;br /&gt;
 MONITOR_BOX               : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6122</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6122"/>
				<updated>2012-04-27T14:24:59Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Initialization Boxes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===[[Module WaterProperties]]===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===[[Module Lagrangian]]===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6\times 10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6\times 10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
Regarding the lagrangian particules, there is one output file per box: a LBM file. This file contains the total volume of lagrangian tracers per origin at each time instant, one origin per column.&lt;br /&gt;
&lt;br /&gt;
===Module Hydrodynamic===&lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
 MONITOR_BOX               : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6121</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6121"/>
				<updated>2012-04-27T14:24:42Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Module Lagrangian */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===[[Module Lagrangian]]===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6\times 10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6\times 10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
Regarding the lagrangian particules, there is one output file per box: a LBM file. This file contains the total volume of lagrangian tracers per origin at each time instant, one origin per column.&lt;br /&gt;
&lt;br /&gt;
===Module Hydrodynamic===&lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
 MONITOR_BOX               : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6120</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6120"/>
				<updated>2012-04-27T12:52:17Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6\times 10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6\times 10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
Regarding the lagrangian particules, there is one output file per box: a LBM file. This file contains the total volume of lagrangian tracers per origin at each time instant, one origin per column.&lt;br /&gt;
&lt;br /&gt;
===Module Hydrodynamic===&lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
 MONITOR_BOX               : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6119</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6119"/>
				<updated>2012-04-27T12:48:20Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Monitoring Boxes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6\times 10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6\times 10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
Regarding the lagrangian particules, there is one output file per box: a LBM file. This file contains the total volume of lagrangian tracers per origin at each time instant, one origin per column.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
 MONITOR_BOX               : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6118</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6118"/>
				<updated>2012-04-27T12:42:40Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6\times 10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6\times 10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
 MONITOR_BOX               : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6117</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6117"/>
				<updated>2012-04-27T12:40:26Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Module Lagrangian */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6\times 10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6\times 10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6116</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6116"/>
				<updated>2012-04-27T12:40:06Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Module Lagrangian */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6x10^{10}\; m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6x10^5\; m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6115</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6115"/>
				<updated>2012-04-27T12:39:44Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Module Lagrangian */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6x10^10 m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6x10^5 m^3&amp;lt;/math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6114</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6114"/>
				<updated>2012-04-27T12:39:28Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
=== Sample ===&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
==== 2D box file ====&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== 3D box file ====&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Module Lagrangian===&lt;br /&gt;
Boxes can be used to initialize a polygon with lagrangian tracers as opposed to a pointwise discharge. For each lagrangian origin, the box number (one box per origin and ID of lagrangian tracers) and the initial volume of one lagrangian particle must be given. The lagrangian box initial emission is such that the total volume of lagrangian particles is equal to the total volume of the box. Thus, if the box has a volume of &amp;lt;math&amp;gt;6x10^10 m^3&amp;lt;/math&amp;gt; and the lagrangian initial volume (set in keyword BOXVOLINIC) is &amp;lt;math&amp;gt;6x10^5 m^3&amp;lt;7math&amp;gt;, then a total of &amp;lt;math&amp;gt;10^5&amp;lt;/math&amp;gt; lagrangian particles will be initialy distributed evenly inside the  box. The higher the number the of lagrangian particles and the longer the time of computation in a linear proportionality so the BOXVOLINIC is a critical parameter to determine the duration of the simulation.&lt;br /&gt;
&lt;br /&gt;
 PARTIC_BOX                : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ... &lt;br /&gt;
 &amp;lt;BeginOrigin&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 EMISSION_SPATIAL          : Box&lt;br /&gt;
 EMISSION_TEMPORAL         : Instantaneous&lt;br /&gt;
 BOXVOLINIC                : 600000&lt;br /&gt;
 BOX_NUMBER                : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;EndOrigin&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
===Module WaterProperties===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6113</id>
		<title>Boxes</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Boxes&amp;diff=6113"/>
				<updated>2012-04-27T12:06:16Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Overview ==&lt;br /&gt;
A box file is used to define an area, which can be 2D or 3D. These areas can be used to initialize properties fields or integrate values in time and space inside and between boxes, allowing computing global and zonal budgets for almost every modeled variables. [[Module BoxDif]] is the module responsible for handling and interpreting the boxes files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Boxes file ==&lt;br /&gt;
Boxes files can be automatically generated by [[Mohid_GIS#Create_Boxes|MOHID GIS]] based on a [[bathymetry]] file and on a [[polygon]] file. &lt;br /&gt;
&lt;br /&gt;
A box file requires the definition polygons. These polygons are defined by vertices indicated by the grid cell [i,j] indexes. Thus, a box file is always specific of a certain [[grid]] file. Please note that in [[polygon]] files, used in MOHID GIS, the polygon vertices are defined by real coordinates [x,y]. &lt;br /&gt;
&lt;br /&gt;
In a box file, several boxes can be defined. An ID number is given to each box, based on the order in which the box file is read. Box 1 is the first block in the file, Box 2 the second and so on. By default a Box 0 (zero) is always created, corresponding to the box containing all the grid points that were not included inside the boxes. This way if box integration is requested and no boxes are defined, the output will be the integration of the entire domain.&lt;br /&gt;
&lt;br /&gt;
When used to integrate values, the correspondent outputs are written in [[Time Series]] format. Thus, in the box file needs information on the time step to write results, which is given by keyword: &lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                :  3600&lt;br /&gt;
&lt;br /&gt;
As a safety feature, a [[Grid Data]] file can be written in the beginning of a simulation, where in to each grid cell, the index of the corresponding box is written. This can be done by defining keyword: &lt;br /&gt;
&lt;br /&gt;
 WRITE_BOXES                   : 1&lt;br /&gt;
&lt;br /&gt;
and then the name of the output file to be written: &lt;br /&gt;
&lt;br /&gt;
 OUTPUT_FILE                   : ..\GeneralData\Boxes\BoxesFileInGridDataFormat.dat&lt;br /&gt;
&lt;br /&gt;
by default this file is written on the exe folder.&lt;br /&gt;
&lt;br /&gt;
This sets the time-step to compute only every 300 seconds (default is 300s).&lt;br /&gt;
 DT_BOXES                       : 300&lt;br /&gt;
&lt;br /&gt;
== Sample ==&lt;br /&gt;
This example shows the definition of a box with 4 vertices. By default [[Module BoxDif]] automatically introduces an extra vertice at the end of the list which is equal to the first vertex, thus insuring the polygon is closed. &lt;br /&gt;
&lt;br /&gt;
=== 2D box file ===&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;''' &lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
  44 39&lt;br /&gt;
  33 77&lt;br /&gt;
  71 88&lt;br /&gt;
  82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== 3D box file ===&lt;br /&gt;
This example shows the definition of two boxes, defined by the same polygon, but which integrate in the vertical direction, from layer 1 to 5, and from layer 6 to 10.&lt;br /&gt;
&lt;br /&gt;
 DT_OUTPUT_TIME                : 3600&lt;br /&gt;
 WRITE_BOXES                   : 0&lt;br /&gt;
 DT_BOXES                      : 300&lt;br /&gt;
 &lt;br /&gt;
 '''&amp;lt;beginpolygon&amp;gt;'''&lt;br /&gt;
  &amp;lt;&amp;lt;beginvertix&amp;gt;&amp;gt;&lt;br /&gt;
   44 39&lt;br /&gt;
   33 77&lt;br /&gt;
   71 88&lt;br /&gt;
   82 49&lt;br /&gt;
  &amp;lt;&amp;lt;endvertix&amp;gt;&amp;gt;&lt;br /&gt;
  &amp;lt;&amp;lt;beginverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
   1  5&lt;br /&gt;
   6  10&lt;br /&gt;
  &amp;lt;&amp;lt;endverticallayer&amp;gt;&amp;gt;&lt;br /&gt;
 '''&amp;lt;endpolygon&amp;gt;'''&lt;br /&gt;
&lt;br /&gt;
== Initialization with Boxes ==&lt;br /&gt;
Boxes can be used to initialize a waterproperty. The waterproperty concentration for each box must be given ordered along the box id starting from Box 1 to the last Box. Box 0 is set accordingly to the default value of the waterproperty.&lt;br /&gt;
&lt;br /&gt;
===WaterProperties_x.dat configuration===&lt;br /&gt;
Boxes values are set for Box 1 and Box 2 (3D sample). Default value will be set in Box 0.&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 INITIALIZATION_METHOD     : BOXES&lt;br /&gt;
 FILENAME                  : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 BOXES_VALUES              : 15.5 25.3&lt;br /&gt;
 DEFAULTVALUE              : 36.&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Monitoring Boxes ==&lt;br /&gt;
Regarding water quality parameters such as nutrients, there are 2 output files created by the model: a BXF and a BXM file.&lt;br /&gt;
The first shows the instantaneous fluxes between the existing boxes, and the second shows the instantaneous mass of the property simulated (ex:ammonia, nitrate, etc) in the entire box.&lt;br /&gt;
&lt;br /&gt;
The values for the instantaneous fluxes are g/s (for ammonia : gN/s) and for the instantaneous mass, in grams.&lt;br /&gt;
&lt;br /&gt;
As for water fluxes the units are, for the BXF file, in m3/s, and for the BXM file in m3.&lt;br /&gt;
&lt;br /&gt;
===WaterProperties_x.dat configuration===&lt;br /&gt;
 &lt;br /&gt;
 BOXFLUXES                 : ..\General Data\Initial Conditions\Boxes.dat&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;beginproperty&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 BOX_TIME_SERIE            : 1&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;endproperty&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See also==&lt;br /&gt;
*[[DrawFluxesInHDF5]]&lt;br /&gt;
*[[Box2HDF5]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Input Data Formats]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Compilation_preprocessor_settings&amp;diff=6080</id>
		<title>Compilation preprocessor settings</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Compilation_preprocessor_settings&amp;diff=6080"/>
				<updated>2012-04-24T13:04:26Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;During compilation of the MOHID source code, at preprocessing time, depending on the definition and values of preprocessor variables, different regions of the code will be compiled. Each preprocessor variable has a scope within the code where it is used. The scope of a preprocessor variable definition can be a single module or it can be the whole solution or only one project of the solution (such as Base1 or Base2).&lt;br /&gt;
&lt;br /&gt;
The advanced MOHID user should be aware of the optional preprocessor settings as the released executables don't contain all the possibilities available and this obliges one to compile its own version of the MOHID executable under certain circumstances.&lt;br /&gt;
&lt;br /&gt;
[[image:VStudio-Ifort-PreprocessorDefinitions-HowTo.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Exclude modules ==&lt;br /&gt;
Some modules can be completely excluded from compilation. If your simulations do not use these modules you can use this pre-processor keywords.&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidWater''&lt;br /&gt;
&lt;br /&gt;
 '''_LAGRANGIAN_'''	   excludes Modules Lagrangian + Jet + Oil&lt;br /&gt;
 '''_AIR_'''	           excludes Modules InterfaceWaterAir + Atmosphere&lt;br /&gt;
 '''_WAVES_'''	           excludes Module Waves&lt;br /&gt;
 '''_SEDIMENT_'''	   excludes Modules SedimentProperties + Consolidation&lt;br /&gt;
&lt;br /&gt;
== Operating System options ==&lt;br /&gt;
Some parts of the program involves performing some actions at the filesystem level. This is inherent to the operating system. The default operating system is MS-Windows. To compile for the Linux operating system one must set the following preprocessor definition:&lt;br /&gt;
&lt;br /&gt;
 ''Scope: ConvertToHdf5, ConvertToXyz''&lt;br /&gt;
&lt;br /&gt;
 '''_USE_NIX'''           Uses linux filesystem commands.&lt;br /&gt;
&lt;br /&gt;
== Library Options ==&lt;br /&gt;
As the pre-built Netcdf library for windows x64 with the fortran binding is a rare bird to find, sometimes one may have to exclude the regions of code containing access to netcdf files.&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1, MohidBase2, ConvertToHdf5''&lt;br /&gt;
&lt;br /&gt;
 '''_NO_NETCDF'''         Excludes regions of code that access netcdf files. To use when a pre-built netcdf library is unavailable.&lt;br /&gt;
&lt;br /&gt;
== Performance options ==&lt;br /&gt;
Use this option if you want to nest several domains&lt;br /&gt;
&lt;br /&gt;
 ''Scope: global''&lt;br /&gt;
&lt;br /&gt;
 '''_USE_MPI'''           includes MPI code&lt;br /&gt;
&lt;br /&gt;
== Time Series Maximum Number of Columns in Character size ==&lt;br /&gt;
Default line_length of input/output ascii files such as TimeSeries is 256, however this can be a problem if the time series contains many many columns with many many properties and exceeds the 256 characters limit. Conveniently, this can be changed by defining the following preprocessor options&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleGlobalData)''&lt;br /&gt;
&lt;br /&gt;
 '''_SHORT_LINE_LENGTH'''        sets line_length = 64&lt;br /&gt;
 '''_LONG_LINE_LENGTH'''         sets line_length = 1024&lt;br /&gt;
 '''_BIG_LINE_LENGTH'''          sets line_length = 6144&lt;br /&gt;
 '''_EXTRA_LONG_LINE_LENGTH'''   sets line_length = 131072&lt;br /&gt;
 '''_EXTRA_SHORT_LINE_LENGTH'''  sets line_length = 32&lt;br /&gt;
&lt;br /&gt;
== Instances Management ==&lt;br /&gt;
MOHID is Object-Oriented (OO) in a centralized way, meaning that it has a central module that collects, registers and monitors every object instanciation. The downside is that it is limited to 500 instantiations of objects. Sometimes it is necessary to&lt;br /&gt;
increase this number (this is true, in particular, when a high number of Tide gauges are used)&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleGlobalData)''&lt;br /&gt;
&lt;br /&gt;
 '''_INCREASE_MAXINSTANCES'''  sets maximum number of object instances to 2000 (default is 500)&lt;br /&gt;
&lt;br /&gt;
==Stack Management ==&lt;br /&gt;
Stack memory is limited to 1GB in all recent Windows versions (either 32 or 64 bits). Thus, it happens quite frequently that simulations that include the Waterquality or Life modules use stack extensively. One way to deal with [[Stack_overflow|Stack limitations]] is by defining ''Stack Reserve'' in the linker options. However, when ''Stack Reserve'' fails, then removing some features of the software can help reduce the stack consumption. In particular, this option, when enabled, removes the calculation of the Minimum and Maximum attributes in the results in the HDF5 files.&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleHDF5)''&lt;br /&gt;
&lt;br /&gt;
 '''_STACK_LIMITS_''' disables the calculation of the Minimum and Maximum attributes in the results in the HDF5 files.&lt;br /&gt;
&lt;br /&gt;
== Graphical options ==&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleGlobalData, ModuleHdf5)''&lt;br /&gt;
&lt;br /&gt;
 '''_GUI_'''              includes GUI code&lt;br /&gt;
&lt;br /&gt;
== Google maps compatible output ==&lt;br /&gt;
 ''Scope: MohidBase2, MohidWater''&lt;br /&gt;
&lt;br /&gt;
 '''_GOOGLEMAPS'''        Generates google compatible mapping coordinates&lt;br /&gt;
&lt;br /&gt;
==Errors that may arise from incorrect preprocessor variables definition==&lt;br /&gt;
&lt;br /&gt;
[[Category:programming]]&lt;br /&gt;
[[Category:Compiling]]&lt;br /&gt;
[[Category:Mohid]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Compilation_preprocessor_settings&amp;diff=6079</id>
		<title>Compilation preprocessor settings</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Compilation_preprocessor_settings&amp;diff=6079"/>
				<updated>2012-04-24T11:56:48Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;During compilation of the MOHID source code, at preprocessing time, depending on the definition and values of preprocessor variables, different regions of the code will be compiled. Each preprocessor variable has a scope within the code where it is used. The scope of a preprocessor variable definition can be a single module or it can be the whole solution or only one project of the solution (such as Base1 or Base2).&lt;br /&gt;
&lt;br /&gt;
The advanced MOHID user should be aware of the optional preprocessor settings as the released executables don't contain all the possibilities available and this obliges one to compile its own version of the MOHID executable under certain circumstances.&lt;br /&gt;
&lt;br /&gt;
[[image:VStudio-Ifort-PreprocessorDefinitions-HowTo.PNG]]&lt;br /&gt;
&lt;br /&gt;
== Exclude modules ==&lt;br /&gt;
Some modules can be completely excluded from compilation. If your simulations do not use these modules you can use this pre-processor keywords.&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidWater''&lt;br /&gt;
&lt;br /&gt;
 '''_LAGRANGIAN_'''	   excludes Modules Lagrangian + Jet + Oil&lt;br /&gt;
 '''_AIR_'''	           excludes Modules InterfaceWaterAir + Atmosphere&lt;br /&gt;
 '''_WAVES_'''	           excludes Module Waves&lt;br /&gt;
 '''_SEDIMENT_'''	   excludes Modules SedimentProperties + Consolidation&lt;br /&gt;
&lt;br /&gt;
== Operating System options ==&lt;br /&gt;
Some parts of the program involves performing some actions at the filesystem level. This is inherent to the operating system. The default operating system is MS-Windows. To compile for the Linux operating system one must set the following preprocessor definition:&lt;br /&gt;
&lt;br /&gt;
 ''Scope: ConvertToHdf5, ConvertToXyz''&lt;br /&gt;
&lt;br /&gt;
 '''_USE_NIX'''           Uses linux filesystem commands.&lt;br /&gt;
&lt;br /&gt;
== Library Options ==&lt;br /&gt;
As the pre-built Netcdf library for windows x64 with the fortran binding is a rare bird to find, sometimes one may have to exclude the regions of code containing access to netcdf files.&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1, MohidBase2, ConvertToHdf5''&lt;br /&gt;
&lt;br /&gt;
 '''_NO_NETCDF'''         Excludes regions of code that access netcdf files. To use when a pre-built netcdf library is unavailable.&lt;br /&gt;
&lt;br /&gt;
== Performance options ==&lt;br /&gt;
Use this option if you want to nest several domains&lt;br /&gt;
&lt;br /&gt;
 ''Scope: global''&lt;br /&gt;
&lt;br /&gt;
 '''_USE_MPI'''           includes MPI code&lt;br /&gt;
&lt;br /&gt;
== Time Series Maximum Number of Columns in Character size ==&lt;br /&gt;
Default line_length of input/output ascii files such as TimeSeries is 256, however this can be a problem if the time series contains many many columns with many many properties and exceeds the 256 characters limit. Conveniently, this can be changed by defining the following preprocessor options&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleGlobalData)''&lt;br /&gt;
&lt;br /&gt;
 '''_SHORT_LINE_LENGTH'''        sets line_length = 64&lt;br /&gt;
 '''_LONG_LINE_LENGTH'''         sets line_length = 1024&lt;br /&gt;
 '''_BIG_LINE_LENGTH'''          sets line_length = 6144&lt;br /&gt;
 '''_EXTRA_LONG_LINE_LENGTH'''   sets line_length = 131072&lt;br /&gt;
 '''_EXTRA_SHORT_LINE_LENGTH'''  sets line_length = 32&lt;br /&gt;
&lt;br /&gt;
== Instances Management ==&lt;br /&gt;
MOHID is Object-Oriented (OO) in a centralized way, meaning that it has a central module that collects, registers and monitors every object instanciation. The downside is that it is limited to 500 instantiations of objects. Sometimes it is necessary to&lt;br /&gt;
increase this number (this is true, in particular, when a high number of Tide gauges are used)&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleGlobalData)''&lt;br /&gt;
&lt;br /&gt;
 '''_INCREASE_MAXINSTANCES'''  sets maximum number of object instances to 2000 (default is 500)&lt;br /&gt;
&lt;br /&gt;
==Stack Management ==&lt;br /&gt;
Stack memory is limited to 1GB in all recent Windows versions (either 32 or 64 bits). Thus, it happens quite frequently that simulations that include the Waterquality or Life modules use stack extensively. One way to deal with [[Stack_overflow|Stack limitations]] is by defining ''Stack Reserve'' in the linker options. However, when ''Stack Reserve'' fails, then removing some features of the software can help reduce the stack consumption. In particular, this option, when enabled, removes the calculation of the Minimum and Maximum attributes in the results in the HDF5 files.&lt;br /&gt;
&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleHDF5)''&lt;br /&gt;
&lt;br /&gt;
 '''_STACK_LIMITS_''' disables the calculation of the Minimum and Maximum attributes in the results in the HDF5 files.&lt;br /&gt;
&lt;br /&gt;
== Graphical options ==&lt;br /&gt;
 ''Scope: MohidBase1 (ModuleGlobalData, ModuleHdf5)''&lt;br /&gt;
&lt;br /&gt;
 '''_GUI_'''              includes GUI code&lt;br /&gt;
&lt;br /&gt;
==Errors that may arise from incorrect preprocessor variables definition==&lt;br /&gt;
&lt;br /&gt;
[[Category:programming]]&lt;br /&gt;
[[Category:Compiling]]&lt;br /&gt;
[[Category:Mohid]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Batch&amp;diff=6078</id>
		<title>Batch</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Batch&amp;diff=6078"/>
				<updated>2012-04-24T10:32:28Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Batch]] files are the original ms-dos scripting language. A [[batch file]] is a script that contains a list of ms-dos commands, with one command per line. When you try to execute the batch file, it will execute the ms-dos commands, one after another, waiting for each command to finish before starting the next one.&lt;br /&gt;
==Examples==&lt;br /&gt;
===For===&lt;br /&gt;
The following example will output each line of the text file to the stdout:&lt;br /&gt;
 &amp;gt; FOR /F %i in (list.txt) DO @echo %~ni&lt;br /&gt;
&lt;br /&gt;
The following example will allow to parse and edit the environment variables ('''invoke the command line with CMD /V'''):&lt;br /&gt;
 &amp;gt; for /F %i in ('dir /B /S *_1.dat') do @set subs=21 @set fil=%i &amp;amp; copy /Y !fil! !fil:20=%subs%!&lt;br /&gt;
'''If you want to write '''FOR''' loops in a batch file instead of the command line, then use '''%%i''' instead of '''%i'''.'''&lt;br /&gt;
&lt;br /&gt;
To place the first line of a file into a variable:&lt;br /&gt;
 &amp;gt; SET /P _MyVar=&amp;lt;MyFilename.txt&lt;br /&gt;
&lt;br /&gt;
To place the ''last'' line of a file into a variable:&lt;br /&gt;
 &amp;gt; FOR /F &amp;quot;tokens=*&amp;quot; %A IN (C:\boot.ini) DO SET TestVar=%A&lt;br /&gt;
&lt;br /&gt;
Nested FOR Loops&lt;br /&gt;
 &amp;gt; FOR /F %a IN (filelist.txt) DO (FOR /F %b IN (salinitytemperature.txt) DO echo %a %b)&lt;br /&gt;
&lt;br /&gt;
Nested FOR loops encapsulated in a batch file&lt;br /&gt;
 for /F %%a in (%1) do (&lt;br /&gt;
     for /R %%b in (../*) do (&lt;br /&gt;
         echo %%a&lt;br /&gt;
         echo %%b&lt;br /&gt;
     )&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
To set variables with delayed expansion inside IF or FOR directives, use the ! character instead of the %.&lt;br /&gt;
 for /f %%i in (revisions.log) do @( &lt;br /&gt;
 	set VARIT=%%i&lt;br /&gt;
 	set VARIT=!VARIT:~1! &lt;br /&gt;
 	if !VARIT! LEQ 44000 echo !VARIT!&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Delimeters===&lt;br /&gt;
This command will look for the first underscore in the list of filenames&lt;br /&gt;
and will split each filename in two at the underscore.&lt;br /&gt;
 &amp;gt; for /f &amp;quot;tokens=1-4 delims=_&amp;quot; %i in ('dir /B *.eps') do @echo  %i %j %k %l&lt;br /&gt;
[http://ss64.com/nt/for_f.html Check out this site for more.]&lt;br /&gt;
&lt;br /&gt;
===If...Else...===&lt;br /&gt;
Example of a &amp;quot;if ... else ...&amp;quot; flow structure&lt;br /&gt;
 &amp;gt; IF %1.==. (SET /P REVIS=&amp;lt;revisions.log) ELSE (SET REVIS=%1)&lt;br /&gt;
&lt;br /&gt;
==Misc==&lt;br /&gt;
===Manipulating environment variables===&lt;br /&gt;
Substring find and replace&lt;br /&gt;
 &amp;gt; set HELLO=HelloWorld&lt;br /&gt;
 &amp;gt; echo %HELLO:l=w%&lt;br /&gt;
 echo&amp;gt; HewwoWorwd&lt;br /&gt;
&lt;br /&gt;
Substring&lt;br /&gt;
 &amp;gt; set HELLO=HelloWorld&lt;br /&gt;
 &amp;gt; echo %HELLO:~1%&lt;br /&gt;
 echo&amp;gt; elloWorld&lt;br /&gt;
&lt;br /&gt;
Extension stripping&lt;br /&gt;
 &amp;gt; For /F %%i in (list.txt) DO echo %%~ni&lt;br /&gt;
&lt;br /&gt;
Delayed environment variable expansion. This is useful when the environment variable&lt;br /&gt;
is manipulated inside the batch file.&lt;br /&gt;
 SETLOCAL ENABLEDELAYEDEXPANSION &lt;br /&gt;
 ...&lt;br /&gt;
 ENDLOCAL&lt;br /&gt;
&lt;br /&gt;
See more help&lt;br /&gt;
 &amp;gt;set /?&lt;br /&gt;
&lt;br /&gt;
===Redirecting output===&lt;br /&gt;
How to redirect output from both standard output and standard error to a file&lt;br /&gt;
 &amp;gt; echo Hello World &amp;gt; filename.txt 2&amp;gt;&amp;amp;1&lt;br /&gt;
&lt;br /&gt;
How to redirect Standard Output and Standard Error to separate files&lt;br /&gt;
 &amp;gt; echo Hello World &amp;gt; logfile.txt 2&amp;gt; errorlog.txt&lt;br /&gt;
&lt;br /&gt;
===Escaping characters===&lt;br /&gt;
&amp;amp;lt;,|,&amp;amp;gt; and % characters are special characters in dos. To escape them use the ^ character or a double %&lt;br /&gt;
 &amp;gt; echo ^&amp;lt;example^&amp;gt;&lt;br /&gt;
 &amp;lt;example&amp;gt;&lt;br /&gt;
===Displaying blank lines===&lt;br /&gt;
Use command echo to display a blank line instead of its default status result&lt;br /&gt;
 &amp;gt;echo.&lt;br /&gt;
&lt;br /&gt;
==Sample applications==&lt;br /&gt;
&lt;br /&gt;
===Copy a clean MOHID project===&lt;br /&gt;
Here's a combination with a batch file, that creates a clean copy of a MOHID simulation:&lt;br /&gt;
&lt;br /&gt;
 &amp;gt; copysimulation MySimulation&lt;br /&gt;
&lt;br /&gt;
 #'''copysimulation.bat content'''&lt;br /&gt;
 #Input argument %1 stands for simulation name&lt;br /&gt;
 @echo off&lt;br /&gt;
 set COPYHOME=C:\Program Files\2gif&lt;br /&gt;
 xcopy %1\*.* %1_copy /E /EXCLUDE:%COPYHOME%\exclui.txt&lt;br /&gt;
 perl %COPYHOME%/replace.pl 's/%2/\.\.\/\.\./g' *&lt;br /&gt;
 perl %COPYHOME%/replace.pl 's/\\/\//g' *&lt;br /&gt;
 @echo on&lt;br /&gt;
&lt;br /&gt;
 #'''exclui.txt content'''&lt;br /&gt;
 .hdf5&lt;br /&gt;
 .srh&lt;br /&gt;
 .bmp&lt;br /&gt;
 .fin&lt;br /&gt;
 .srw&lt;br /&gt;
 .ppt&lt;br /&gt;
 .jpg&lt;br /&gt;
 .gif&lt;br /&gt;
 .pdf&lt;br /&gt;
 .ps&lt;br /&gt;
 .eps&lt;br /&gt;
&lt;br /&gt;
===Remove all openmp directives from the code===&lt;br /&gt;
''NOTE: cygwin or [http://sourceforge.net/projects/getgnuwin32/files/ gnuwin32] with all the gnu tools executables must be installed and accessible from the path command line.''&lt;br /&gt;
 $ for /F %i in ('dir /B /S *.F90') do @cat %i | grep -v !$OMP &amp;gt; %~ni.tpp&lt;br /&gt;
 $ for /F %i in ('dir /B /S *.tpp') do @copy %i %~ni.F90&lt;br /&gt;
 $ for /F %i in ('dir /B /S *.tpp') do @del %i&lt;br /&gt;
&lt;br /&gt;
=== Appending hourly data files from Instituto Hidrográfico ===&lt;br /&gt;
 for /F %i in ('dir /B *') DO @type %i | grep MCAS &amp;gt;&amp;gt; one-file.txt&lt;br /&gt;
&lt;br /&gt;
=== Duplicating a Run in a MOHID Simulation ===&lt;br /&gt;
This batch file duplicates a run with a new number (and updates the Nomfich files correspondingly). It requires a '''CMD /V''' console calling and also the gnu utility [[Sed]].&lt;br /&gt;
 @echo off&lt;br /&gt;
 REM DUPLICATE_RUN.BAT&lt;br /&gt;
 REM ATTENTION: Must be run with the CMD /V option!&lt;br /&gt;
 REM ARG1 %1 SOURCE RUN ID&lt;br /&gt;
 REM ARG2 %2 TARGET RUN ID&lt;br /&gt;
 &lt;br /&gt;
 SETLOCAL ENABLEDELAYEDEXPANSION &lt;br /&gt;
 REM Duplicates the filenames&lt;br /&gt;
 for /F &amp;quot;delims=*&amp;quot; %%i in ('dir /S /B *_%1.dat') do (&lt;br /&gt;
 	set NAME=%%i&lt;br /&gt;
 	@echo Created !NAME:%1=%2!&lt;br /&gt;
 	copy /Y &amp;quot;!NAME!&amp;quot; &amp;quot;!NAME:%1=%2!&amp;quot;&lt;br /&gt;
 )&lt;br /&gt;
 &lt;br /&gt;
 REM Updates the nomfich_N.dat files&lt;br /&gt;
 for /F %%i in ('dir /S /B Nomfich_%2.dat') do (&lt;br /&gt;
 	sed -e &amp;quot;s/%1/%2/g&amp;quot; %%i &amp;gt; %%i.bak&lt;br /&gt;
 	move /Y %%i.bak %%i&lt;br /&gt;
 )&lt;br /&gt;
 ENDLOCAL&lt;br /&gt;
=== Set a run number ===&lt;br /&gt;
 echo off&lt;br /&gt;
 REM Set_Run.bat&lt;br /&gt;
 REM ATTENTION: Must be run with the CMD /V option!&lt;br /&gt;
 REM ARG1 %1 SOURCE RUN ID&lt;br /&gt;
 &lt;br /&gt;
 REM Activate the chosen run&lt;br /&gt;
 for /F %%i in ('dir ..\*Nomfich.dat /S /B ') do (&lt;br /&gt;
 	set MYDIR=%%~di%%~pi&lt;br /&gt;
 	copy /Y !MYDIR:~0,-4!data\Nomfich_%1.dat %%i&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
===Finding error in revisions===&lt;br /&gt;
 SETLOCAL ENABLEDELAYEDEXPANSION &lt;br /&gt;
 REM Requires linux commands grep, cut and tee to be installed as well as the svn command-line client&lt;br /&gt;
 SET PATH=%PATH%;C:\Program Files\SlikSvn\bin&lt;br /&gt;
 SET SOURCESVN=https://mohid.svn.codeplex.com/svn&lt;br /&gt;
 SET TARGETP=E:\Projects\MOHID\test3&lt;br /&gt;
 SET DEVENV=&amp;quot;c:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv&amp;quot;&lt;br /&gt;
 SET NUMERICS=%TARGETP%\Solutions\VisualStudio2008_IntelFortran11\MOHIDNumerics&lt;br /&gt;
 REM Uncomment this line only for the first time you run this batch in your computer.&lt;br /&gt;
 REM svn co %SOURCESVN% %TARGETP%&lt;br /&gt;
 &lt;br /&gt;
 svn log %SOURCESVN% &amp;gt; codeplex.log&lt;br /&gt;
 type codeplex.log | grep ^r[0-9][0-9][0-9] | cut -f 1 -d &amp;quot;|&amp;quot; &amp;gt; revisions.log&lt;br /&gt;
 &lt;br /&gt;
 REM Check if argument is passed. If not then read it from revisions.log file&lt;br /&gt;
 IF %1.==. (SET /P REVIS=&amp;lt;revisions.log) ELSE (SET REVIS=%1)&lt;br /&gt;
 SET REVIS=!REVIS:~1!&lt;br /&gt;
 &lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; runnedRevisions.log&lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; svnupdate.log&lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; vs_clean_rebuild.log&lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; mohid_run.log&lt;br /&gt;
 FOR /F %%i in (revisions.log) DO (&lt;br /&gt;
 	set NUM=%%i&lt;br /&gt;
 	set NUM=!NUM:~1!&lt;br /&gt;
 	echo %%i &amp;gt;&amp;gt; runnedRevisions.log&lt;br /&gt;
 	svn update -%%i %TARGETP% | tee -a svnupdate.log&lt;br /&gt;
 	%DEVENV% &amp;quot;%NUMERICS%\MOHIDNumerics.sln&amp;quot; /clean &amp;quot;Release Double|x64&amp;quot; /project MOHIDWater	| tee -a  vs_clean_rebuild.log&lt;br /&gt;
 	%DEVENV% &amp;quot;%NUMERICS%\MOHIDNumerics.sln&amp;quot; /rebuild &amp;quot;Release Double|x64&amp;quot; /project MOHIDWater | tee -a  vs_clean_rebuild.log&lt;br /&gt;
 	echo %%i &amp;gt;&amp;gt; mohid_run.log&lt;br /&gt;
 	&amp;quot;%NUMERICS%\MOHIDWater\x64\Release Double\MOHIDWater_x64_release_double.exe&amp;quot; | tee -a mohid_run.log&lt;br /&gt;
 )&lt;br /&gt;
 ENDLOCAL&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://www.robvanderwoude.com/ntfor.html Batch files tutorial];&lt;br /&gt;
*[http://www.ss64.com/nt/for.html for command reference];&lt;br /&gt;
*[http://www.ss64.com/nt/ windows nt command-line reference];&lt;br /&gt;
*[http://sourceforge.net/projects/getgnuwin32/files/ gnuwin32 download]&lt;br /&gt;
&lt;br /&gt;
[[Category:Windows]]&lt;br /&gt;
[[Category:Script]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	<entry>
		<id>http://www.wiki.mohid.com/index.php?title=Batch&amp;diff=6053</id>
		<title>Batch</title>
		<link rel="alternate" type="text/html" href="http://www.wiki.mohid.com/index.php?title=Batch&amp;diff=6053"/>
				<updated>2012-04-13T11:56:35Z</updated>
		
		<summary type="html">&lt;p&gt;Guillaume: /* Redirecting output */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Batch]] files are the original ms-dos scripting language. A [[batch file]] is a script that contains a list of ms-dos commands, with one command per line. When you try to execute the batch file, it will execute the ms-dos commands, one after another, waiting for each command to finish before starting the next one.&lt;br /&gt;
==Examples==&lt;br /&gt;
===For===&lt;br /&gt;
The following example will output each line of the text file to the stdout:&lt;br /&gt;
 &amp;gt; FOR /F %i in (list.txt) DO @echo %~ni&lt;br /&gt;
&lt;br /&gt;
The following example will allow to parse and edit the environment variables ('''invoke the command line with CMD /V'''):&lt;br /&gt;
 &amp;gt; for /F %i in ('dir /B /S *_1.dat') do @set subs=21 @set fil=%i &amp;amp; copy /Y !fil! !fil:20=%subs%!&lt;br /&gt;
'''If you want to write '''FOR''' loops in a batch file instead of the command line, then use '''%%i''' instead of '''%i'''.'''&lt;br /&gt;
&lt;br /&gt;
To place the first line of a file into a variable:&lt;br /&gt;
 &amp;gt; SET /P _MyVar=&amp;lt;MyFilename.txt&lt;br /&gt;
&lt;br /&gt;
To place the ''last'' line of a file into a variable:&lt;br /&gt;
 &amp;gt; FOR /F &amp;quot;tokens=*&amp;quot; %A IN (C:\boot.ini) DO SET TestVar=%A&lt;br /&gt;
&lt;br /&gt;
Nested FOR Loops&lt;br /&gt;
 &amp;gt; FOR /F %a IN (filelist.txt) DO (FOR /F %b IN (salinitytemperature.txt) DO echo %a %b)&lt;br /&gt;
&lt;br /&gt;
Nested FOR loops encapsulated in a batch file&lt;br /&gt;
 for /F %%a in (%1) do (&lt;br /&gt;
     for /R %%b in (../*) do (&lt;br /&gt;
         echo %%a&lt;br /&gt;
         echo %%b&lt;br /&gt;
     )&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
To set variables with delayed expansion inside IF or FOR directives, use the ! character instead of the %.&lt;br /&gt;
 for /f %%i in (revisions.log) do @( &lt;br /&gt;
 	set VARIT=%%i&lt;br /&gt;
 	set VARIT=!VARIT:~1! &lt;br /&gt;
 	if !VARIT! LEQ 44000 echo !VARIT!&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Delimeters===&lt;br /&gt;
This command will look for the first underscore in the list of filenames&lt;br /&gt;
and will split each filename in two at the underscore.&lt;br /&gt;
 &amp;gt; for /f &amp;quot;tokens=1-4 delims=_&amp;quot; %i in ('dir /B *.eps') do @echo  %i %j %k %l&lt;br /&gt;
[http://ss64.com/nt/for_f.html Check out this site for more.]&lt;br /&gt;
&lt;br /&gt;
===If...Else...===&lt;br /&gt;
Example of a &amp;quot;if ... else ...&amp;quot; flow structure&lt;br /&gt;
 &amp;gt; IF %1.==. (SET /P REVIS=&amp;lt;revisions.log) ELSE (SET REVIS=%1)&lt;br /&gt;
&lt;br /&gt;
==Misc==&lt;br /&gt;
===Manipulating environment variables===&lt;br /&gt;
Substring find and replace&lt;br /&gt;
 &amp;gt; set HELLO=HelloWorld&lt;br /&gt;
 &amp;gt; echo %HELLO:l=w%&lt;br /&gt;
 echo&amp;gt; HewwoWorwd&lt;br /&gt;
&lt;br /&gt;
Substring&lt;br /&gt;
 &amp;gt; set HELLO=HelloWorld&lt;br /&gt;
 &amp;gt; echo %HELLO:~1%&lt;br /&gt;
 echo&amp;gt; elloWorld&lt;br /&gt;
&lt;br /&gt;
Extension stripping&lt;br /&gt;
 &amp;gt; For /F %%i in (list.txt) DO echo %%~ni&lt;br /&gt;
&lt;br /&gt;
See more help&lt;br /&gt;
 &amp;gt;set /?&lt;br /&gt;
&lt;br /&gt;
===Redirecting output===&lt;br /&gt;
How to redirect output from both standard output and standard error to a file&lt;br /&gt;
 &amp;gt; echo Hello World &amp;gt; filename.txt 2&amp;gt;&amp;amp;1&lt;br /&gt;
&lt;br /&gt;
How to redirect Standard Output and Standard Error to separate files&lt;br /&gt;
 &amp;gt; echo Hello World &amp;gt; logfile.txt 2&amp;gt; errorlog.txt&lt;br /&gt;
&lt;br /&gt;
===Escaping characters===&lt;br /&gt;
&amp;amp;lt;,|,&amp;amp;gt; and % characters are special characters in dos. To escape them use the ^ character or a double %&lt;br /&gt;
 &amp;gt; echo ^&amp;lt;example^&amp;gt;&lt;br /&gt;
 &amp;lt;example&amp;gt;&lt;br /&gt;
===Displaying blank lines===&lt;br /&gt;
Use command echo to display a blank line instead of its default status result&lt;br /&gt;
 &amp;gt;echo.&lt;br /&gt;
&lt;br /&gt;
==Sample applications==&lt;br /&gt;
&lt;br /&gt;
===Copy a clean MOHID project===&lt;br /&gt;
Here's a combination with a batch file, that creates a clean copy of a MOHID simulation:&lt;br /&gt;
&lt;br /&gt;
 &amp;gt; copysimulation MySimulation&lt;br /&gt;
&lt;br /&gt;
 #'''copysimulation.bat content'''&lt;br /&gt;
 #Input argument %1 stands for simulation name&lt;br /&gt;
 @echo off&lt;br /&gt;
 set COPYHOME=C:\Program Files\2gif&lt;br /&gt;
 xcopy %1\*.* %1_copy /E /EXCLUDE:%COPYHOME%\exclui.txt&lt;br /&gt;
 perl %COPYHOME%/replace.pl 's/%2/\.\.\/\.\./g' *&lt;br /&gt;
 perl %COPYHOME%/replace.pl 's/\\/\//g' *&lt;br /&gt;
 @echo on&lt;br /&gt;
&lt;br /&gt;
 #'''exclui.txt content'''&lt;br /&gt;
 .hdf5&lt;br /&gt;
 .srh&lt;br /&gt;
 .bmp&lt;br /&gt;
 .fin&lt;br /&gt;
 .srw&lt;br /&gt;
 .ppt&lt;br /&gt;
 .jpg&lt;br /&gt;
 .gif&lt;br /&gt;
 .pdf&lt;br /&gt;
 .ps&lt;br /&gt;
 .eps&lt;br /&gt;
&lt;br /&gt;
===Remove all openmp directives from the code===&lt;br /&gt;
''NOTE: cygwin or [http://sourceforge.net/projects/getgnuwin32/files/ gnuwin32] with all the gnu tools executables must be installed and accessible from the path command line.''&lt;br /&gt;
 $ for /F %i in ('dir /B /S *.F90') do @cat %i | grep -v !$OMP &amp;gt; %~ni.tpp&lt;br /&gt;
 $ for /F %i in ('dir /B /S *.tpp') do @copy %i %~ni.F90&lt;br /&gt;
 $ for /F %i in ('dir /B /S *.tpp') do @del %i&lt;br /&gt;
&lt;br /&gt;
=== Appending hourly data files from Instituto Hidrográfico ===&lt;br /&gt;
 for /F %i in ('dir /B *') DO @type %i | grep MCAS &amp;gt;&amp;gt; one-file.txt&lt;br /&gt;
&lt;br /&gt;
=== Duplicating a Run in a MOHID Simulation ===&lt;br /&gt;
This batch file duplicates a run with a new number (and updates the Nomfich files correspondingly). It requires a '''CMD /V''' console calling and also the gnu utility [[Sed]].&lt;br /&gt;
 @echo off&lt;br /&gt;
 REM DUPLICATE_RUN.BAT&lt;br /&gt;
 REM ATTENTION: Must be run with the CMD /V option!&lt;br /&gt;
 REM ARG1 %1 SOURCE RUN ID&lt;br /&gt;
 REM ARG2 %2 TARGET RUN ID&lt;br /&gt;
 &lt;br /&gt;
 REM Duplicates the filenames&lt;br /&gt;
 for /F &amp;quot;delims=*&amp;quot; %%i in ('dir /S /B *_%1.dat') do (&lt;br /&gt;
 	set NAME=%%i&lt;br /&gt;
 	@echo Created !NAME:%1=%2!&lt;br /&gt;
 	copy /Y &amp;quot;!NAME!&amp;quot; &amp;quot;!NAME:%1=%2!&amp;quot;&lt;br /&gt;
 )&lt;br /&gt;
 &lt;br /&gt;
 REM Updates the nomfich_N.dat files&lt;br /&gt;
 for /F %%i in ('dir /S /B Nomfich_%2.dat') do (&lt;br /&gt;
 	sed -e &amp;quot;s/%1/%2/g&amp;quot; %%i &amp;gt; %%i.bak&lt;br /&gt;
 	move /Y %%i.bak %%i&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
=== Set a run number ===&lt;br /&gt;
 echo off&lt;br /&gt;
 REM Set_Run.bat&lt;br /&gt;
 REM ATTENTION: Must be run with the CMD /V option!&lt;br /&gt;
 REM ARG1 %1 SOURCE RUN ID&lt;br /&gt;
 &lt;br /&gt;
 REM Activate the chosen run&lt;br /&gt;
 for /F %%i in ('dir ..\*Nomfich.dat /S /B ') do (&lt;br /&gt;
 	set MYDIR=%%~di%%~pi&lt;br /&gt;
 	copy /Y !MYDIR:~0,-4!data\Nomfich_%1.dat %%i&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
===Finding error in revisions===&lt;br /&gt;
 REM Requires linux commands grep, cut and tee to be installed as well as the svn command-line client&lt;br /&gt;
 SET PATH=%PATH%;C:\Program Files\SlikSvn\bin&lt;br /&gt;
 SET SOURCESVN=https://mohid.svn.codeplex.com/svn&lt;br /&gt;
 SET TARGETP=E:\Projects\MOHID\test3&lt;br /&gt;
 SET DEVENV=&amp;quot;c:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv&amp;quot;&lt;br /&gt;
 SET NUMERICS=%TARGETP%\Solutions\VisualStudio2008_IntelFortran11\MOHIDNumerics&lt;br /&gt;
 REM Uncomment this line only for the first time you run this batch in your computer.&lt;br /&gt;
 REM svn co %SOURCESVN% %TARGETP%&lt;br /&gt;
 &lt;br /&gt;
 svn log %SOURCESVN% &amp;gt; codeplex.log&lt;br /&gt;
 type codeplex.log | grep ^r[0-9][0-9][0-9] | cut -f 1 -d &amp;quot;|&amp;quot; &amp;gt; revisions.log&lt;br /&gt;
 &lt;br /&gt;
 REM Check if argument is passed. If not then read it from revisions.log file&lt;br /&gt;
 IF %1.==. (SET /P REVIS=&amp;lt;revisions.log) ELSE (SET REVIS=%1)&lt;br /&gt;
 SET REVIS=!REVIS:~1!&lt;br /&gt;
 &lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; runnedRevisions.log&lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; svnupdate.log&lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; vs_clean_rebuild.log&lt;br /&gt;
 echo &amp;quot;&amp;quot; &amp;gt; mohid_run.log&lt;br /&gt;
 FOR /F %%i in (revisions.log) DO (&lt;br /&gt;
 	set NUM=%%i&lt;br /&gt;
 	set NUM=!NUM:~1!&lt;br /&gt;
 	echo %%i &amp;gt;&amp;gt; runnedRevisions.log&lt;br /&gt;
 	svn update -%%i %TARGETP% | tee -a svnupdate.log&lt;br /&gt;
 	%DEVENV% &amp;quot;%NUMERICS%\MOHIDNumerics.sln&amp;quot; /clean &amp;quot;Release Double|x64&amp;quot; /project MOHIDWater	| tee -a  vs_clean_rebuild.log&lt;br /&gt;
 	%DEVENV% &amp;quot;%NUMERICS%\MOHIDNumerics.sln&amp;quot; /rebuild &amp;quot;Release Double|x64&amp;quot; /project MOHIDWater | tee -a  vs_clean_rebuild.log&lt;br /&gt;
 	echo %%i &amp;gt;&amp;gt; mohid_run.log&lt;br /&gt;
 	&amp;quot;%NUMERICS%\MOHIDWater\x64\Release Double\MOHIDWater_x64_release_double.exe&amp;quot; | tee -a mohid_run.log&lt;br /&gt;
 )&lt;br /&gt;
&lt;br /&gt;
==External References==&lt;br /&gt;
*[http://www.robvanderwoude.com/ntfor.html Batch files tutorial];&lt;br /&gt;
*[http://www.ss64.com/nt/for.html for command reference];&lt;br /&gt;
*[http://www.ss64.com/nt/ windows nt command-line reference];&lt;br /&gt;
*[http://sourceforge.net/projects/getgnuwin32/files/ gnuwin32 download]&lt;br /&gt;
&lt;br /&gt;
[[Category:Windows]]&lt;br /&gt;
[[Category:Script]]&lt;/div&gt;</summary>
		<author><name>Guillaume</name></author>	</entry>

	</feed>