| 1 |
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> |
| 2 |
<html> |
| 3 |
<head> |
| 4 |
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> |
| 5 |
<meta name="GENERATOR" content="Mozilla/4.72 [en] (X11; U; Linux 2.2.14-5.0 i686) [Netscape]"> |
| 6 |
<title>viaCVS</title> |
| 7 |
</head> |
| 8 |
<body text="#000000" bgcolor="#FFFFFF" link="#0000EF" vlink="#51188E" alink="#FF0000"> |
| 9 |
|
| 10 |
<center> |
| 11 |
<h2> |
| 12 |
Hardware/software requirements</h2></center> |
| 13 |
This page summarises computer system requirements for using MITgcm in a |
| 14 |
<a href="../online_documents/manual/sarch.html#fig:mitgcm_architecture_goals">range |
| 15 |
of scenarios</a> that spans simulations on a desktop PC to simulations |
| 16 |
run on a high-end supercomputer. The side bar on the left contains |
| 17 |
links to sites from which third party software and hardware, which you |
| 18 |
may require, can be obtained. The text below and the <a href="../online_documents/index.html" target="mainFrame">online |
| 19 |
document</a> explain in what situations you will need these items. |
| 20 |
In many cases the software you need will already be installed on your computer |
| 21 |
system and you can go straight ahead and <a href="../getting_started/index.html" target="mainFrame">start |
| 22 |
using</a> the model. |
| 23 |
<p><b>MITgcm</b> |
| 24 |
<ul> |
| 25 |
<li> |
| 26 |
runs on a wide <a href="../online_documents/manual/targethw.html">range |
| 27 |
of computer systems.</a></li> |
| 28 |
|
| 29 |
<li> |
| 30 |
includes special software (called <a href="../online_documents/manual/wrapper.html">WRAPPER</a>) |
| 31 |
to support efficient execution and relatively easy portablity.</li> |
| 32 |
</ul> |
| 33 |
<b>Platforms where MITgcm is run regularly include</b> |
| 34 |
<ul> |
| 35 |
<li> |
| 36 |
<a href="sideMenuBarFrame.html#hardware" target="sideMenuBarFrame">Unix |
| 37 |
PC's</a> ( both Intel and AMD processor based) running Linux.</li> |
| 38 |
|
| 39 |
<li> |
| 40 |
<a href="sideMenuBarFrame.html#hardware" target="sideMenuBarFrame">Unix |
| 41 |
workstations</a> from Sun, SGI, HP, IBM, Compaq.</li> |
| 42 |
|
| 43 |
<li> |
| 44 |
Unix based PC and workstation <a href="sideMenuBarFrame.html#interconnects" target="sideMenuBarFrame">clusters</a>.</li> |
| 45 |
|
| 46 |
<li> |
| 47 |
high-end <a href="sideMenuBarFrame.html#hardware" target="sideMenuBarFrame">symetric |
| 48 |
multi-processor systems</a>.</li> |
| 49 |
</ul> |
| 50 |
|
| 51 |
<ul>Under the WRAPPER, code can also run very efficiently on high-end vector |
| 52 |
processing systems, but we can't afford one.</ul> |
| 53 |
<b>The minimum you require to run the model is</b> |
| 54 |
<ul> |
| 55 |
<li> |
| 56 |
a computer runing a <a href="sideMenuBarFrame.html#os" target="sideMenuBarFrame">Unix |
| 57 |
style operating system</a>.</li> |
| 58 |
|
| 59 |
<li> |
| 60 |
a Fortran 77, Fortran 90 or Fortran 95 <a href="sideMenuBarFrame.html#compilers" target="sideMenuBarFrame">compiler</a>.</li> |
| 61 |
|
| 62 |
<li> |
| 63 |
a <a href="sideMenuBarFrame.html#compilers" target="sideMenuBarFrame">C |
| 64 |
compiler</a>.</li> |
| 65 |
</ul> |
| 66 |
<b>To run parallel configurations you need</b> |
| 67 |
<ul> |
| 68 |
<li> |
| 69 |
a multi-process <a href="sideMenuBarFrame.html#hardware" target="sideMenuBarFrame">computer</a></li> |
| 70 |
|
| 71 |
<br>and either of |
| 72 |
<li> |
| 73 |
a <a href="sideMenuBarFrame.html#compilers" target="sideMenuBarFrame">compiler</a> |
| 74 |
and that supports multi-threaded programs.</li> |
| 75 |
|
| 76 |
<li> |
| 77 |
a system with an implementation of the <a href="sideMenuBarFrame.html#parallelism" target="sideMenuBarFrame">MPI |
| 78 |
library installed</a>.</li><br><br> |
| 79 |
Instructions on running multi-process codes can be found <a href=x>here</a>. |
| 80 |
Instructions regarding muti-threaded execution can be found <a href=x>here</a>. |
| 81 |
Specialized communication software, to optimize performance on a specific |
| 82 |
platform, can also be introduced into the WRAPPER. This process |
| 83 |
is discussed <a href=x>here</a>. Before running a parallel code we recommend you try one of the |
| 84 |
<a href=x>basic examples</a></ul> |
| 85 |
|
| 86 |
<b>To perform derivative calculations you need</b> |
| 87 |
<ul> |
| 88 |
<li> |
| 89 |
an <a href="sideMenuBarFrame.html#differentiation" target="sideMenuBarFrame"> |
| 90 |
automatic differentiation tool</a>. |
| 91 |
</li><br> |
| 92 |
An example experiment illustrating the automatic differentiation |
| 93 |
process can be found <a href=x>here</a>. |
| 94 |
</ul> |
| 95 |
|
| 96 |
<p><br><b>Once you have your computer set up</b> |
| 97 |
<blockquote>go <a href="../getting_started/index.html" target=mainFrame>here </a> |
| 98 |
to find out how to download the model. The full distribution (including |
| 99 |
examples with input datasets and sample output) is around 50MB. Instructions |
| 100 |
on estimating the computing resource requirements (CPU time, memory usage |
| 101 |
and disk space) for a set of numerical experiments can be found here.</blockquote> |
| 102 |
|
| 103 |
<p><br><b>Simulation output is usually examined</b> |
| 104 |
<blockquote>using one of several |
| 105 |
<a href="sideMenuBarFrame.html#analysis" target="sideMenuBarFrame">standard analysis tools</a>, |
| 106 |
depending on individual |
| 107 |
preference and experiemnce. |
| 108 |
</blockquote> |
| 109 |
|
| 110 |
<p><br><b>Still confused?</b> |
| 111 |
<blockquote>send us <a href=mailto:support@mitgcm.org>mail</a>. |
| 112 |
We like our software to be used and are happy to help out if we can. |
| 113 |
|
| 114 |
<hr WIDTH="100%"> |
| 115 |
<table CELLSPACING=0 CELLPADDING=0 WIDTH="100%" NOSAVE > |
| 116 |
<tr NOSAVE> |
| 117 |
<td NOSAVE>Last modified on $Date: 2001/10/21 18:13:36 $</td> |
| 118 |
|
| 119 |
<td> |
| 120 |
<div align=right>CVS: $Source: /u/gcmpack/mitgcm.org/sealion/download_software/viaCVS.html,v |
| 121 |
$Revision: 1.5 $</div> |
| 122 |
</td> |
| 123 |
</tr> |
| 124 |
</table> |
| 125 |
|
| 126 |
</body> |
| 127 |
</html> |
Parent Directory
| 
Revision Log
| 
Revision Graph