Index: palm/trunk/DOC/app/chapter_3.2.html =================================================================== --- palm/trunk/DOC/app/chapter_3.2.html (revision 335) +++ palm/trunk/DOC/app/chapter_3.2.html (revision 336) @@ -32,5 +32,5 @@
The following configuration
data
-exclusively applies to model runs on the IBM Regatta hanni of the
+exclusively applies to model runs on the SGI ICE system of the
HLRN when using several processing elements (i.e. for the parallel
version of the model). The proper installation of the model is
@@ -38,13 +38,9 @@
5.0). Furthermore it is supposed that the user is located in
the
-directory $HOME/palm/current_version/SOURCE
-on its local computer. There are the FORTRAN source codes of the
-model (*.f90)
-as
-well as the configuration file (name: .mrun.config)
-and the make file (name: Makefile).
+directory $HOME/palm/current_version
+ on its local computer, where the configuration file (.mrun.config) should reside.
The configuration file has the following contents (among other things):
-
% source_path $HOME/palm/current_version/SOURCE+
% mainprog palm.f90
% use_makefile true
% fopts -O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape ibmh parallel
% lopts -O3:-g:-qrealsize=8:-Q:-q64:-qmaxmem=-1:-qtune=pwr4:-qarch=pwr4:-qnosave:-qnoescape:-lesslsmp ibmh parallel
#
EC:[[ \$locat = execution]] & & cat RUN_CONTROL
#
PARIN in:job:npe d3# ~/palm/current_version/JOBS/$fname/INPUT _p3d
#
RUN_CONTROL out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _rc
HEADER out:loc:tr d3# ~/palm/current_version/JOBS/$fname/MONITORING _header
PLOT1D_PAR out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_par
PLOT1D_DATA out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr_in
%mainprog palm.f90
%base_directory $HOME/palm/current_version
%base_data ~/palm/current_version/JOBS
%source_path $base_directory/trunk/SOURCE
#
%fopts -g:-w:-xT:-O3:-cpp:-r8:-ftz:-fno-alias:-no-prec-div:-no-prec-sqrt:-ip:-nbs:-convert:little_endian lcsgih parallel
%lopts -g:-w:-xT:-O3:-cpp:-r8:-ftz:-fno-alias:-no-prec-div:-no-prec-sqrt:-ip:-nbs:-Vaxlib lcsgih parallel
#
EC:[[ \$locat = execution]] & & cat RUN_CONTROL
#
PARIN in:job d3# $base_data/$fname/INPUT _p3d
#
RUN_CONTROL out:loc:tr d3# $base_data/$fname/MONITORING _rc
HEADER out:loc:tr d3# $base_data/$fname/MONITORING _header
DATA_1D_PR_NETCDF out:loc:tr pr# ~/palm/current_version/JOBS/$fname/OUTPUT _pr nc
The first five lines specify values of @@ -56,15 +52,11 @@ variable. Again separated by blank the so-called validity domain can be indicated (later more). -With the first three variables mrun gets to know in +With the first four variables mrun gets to know in which directory the source code lies (source_path), -the file name of the main program (mainprog) -and that the make mechanism -should be -used for compiling (use_makefile -= true). mrun +the file name of the main program (mainprog). Also, two variables are defined which contain path informations used later in the file (base_directory, base_data). mrun needs these information, because for each -model run the executable is created by compiling the source files. +model run the executable is created by compiling the respective source file. Normally, only the main program (palm.f90) will be compiled while all other object files are just linked. These object files have already @@ -84,21 +76,12 @@ interpret these colons as blanks (2 colons written one behind the other will be interpreted as a colon). Thus in the example above fopts -has the value “-O3 --g --qrealsize=8 -Q -q64 -qmaxmem=-1 -qtune=pwr4 -qarch=pwr4 -qnosave --qnoescape”. -Thus a PALM executable is generated using high level optimization (-O3). +has the value “-g -w -xT -O3 -cpp -r8 -ftz -fno-alias -no-prec-div -no-prec-sqrt -ip -nbs -convert little_endian”. +Thus a PALM executable is generated using high level optimization (-O3). For all other options -see the compiler manual on the IBM (man -f90). +see the compiler manual on the SGI (man ifort). Additional libraries -which the compiler should use are described by +which the compiler should use may have to be given by the environment variable lopts -(loader options). -Here you -have to indicate a special IBM library (ESSL, Engineering -and Scientific Subroutine Library). -On the -IBM-Regatta, all compiler options have also to be given to the linker. +(loader options).
Compiler and loader options usually differ from computer to computer. In the @@ -111,10 +94,10 @@ the so-called validity domain which follows in the appropriate variable lines after the value of variables. -In the example above the entry “ibmh +In the example above the entry “lcsgih parallel” stands for fopts and lopts. These lines only become active if a run on the parallel computer of -the HLRN (ibmh) +the HLRN (lcsgih) on several (parallel) processors is started. The activation takes place when you @@ -124,5 +107,5 @@ (see below). This way, the validity domain can be limited also for all other environment-variables. If no validity domain -is indicated then the given values of variables are valid on all +is indicated then the given values of variables are valid for all computers.
After the value @@ -208,5 +191,5 @@ indicated within the mrun call by the option -r. Thus a call of the form
-mrun - h ibmh -d abcde -r d3+
mrun - h lcsgih -d abcde -r "d3#"
would lead to the fact that the input @@ -217,5 +200,5 @@ these files are to be copied of mrun then the call must be
-mrun -h ibmh -d abcde -r "d3 pr"+
mrun -h lcsgih -d abcde -r "d3# pr#"
Instead of the option -r you can @@ -225,5 +208,5 @@ file all file connection statements are actually executed then the call must be:
-mrun -h ibmh -d abcde -i d3 -o "d3 pr"+
mrun -h lcsgih -d abcde -i "d3#" -o "d3# pr#"
The
names of the
@@ -258,5 +241,5 @@
The example configuration
file also
-instructs mrun to copy four output files of the
+instructs mrun to copy three output files of the
model to
appropriate permanent files of the user at the end of the run.
@@ -266,7 +249,5 @@
are located, as well as a file with data of horizontally averaged
vertical profiles
-(PLOT1D_DATA)
-and an associated parameter file (PLOT1D_PAR),
-which can be used as input files for the plot program profil.
+(DATA_1D_PR_NETCDF).
A model run does not presuppose neither the file connection statements
for
@@ -283,7 +264,7 @@
execution of a
model run
-on several processors on the IBM Regatta "hanni" of the HLRN must be
+on several processors on the SGI ICE of the HLRN must be
supplemented by the following options in each case: Only the indication of -K
parallel causes the parallel execution of the
@@ -294,20 +275,17 @@
option -X
(e.g.
--X
-4).
+
mrun - K parallel -X … -t … -m …
+
mrun - K parallel -X ... -T ... -t ... -m ---
% -memory 1630 ibmh parallel+
% -cputime 1000 ibmh parallel
%memory 1500 lcsgih parallel
%cputime 1000 lcsgih parallel
The values indicated there can be overridden with the values of the options -t and/or -m, -respectivly.
+respectivly.Warning: When changing the coniguration file, please never use the TAB key!
Last change: Index: palm/trunk/DOC/app/chapter_4.2.html =================================================================== --- palm/trunk/DOC/app/chapter_4.2.html (revision 335) +++ palm/trunk/DOC/app/chapter_4.2.html (revision 336) @@ -10663,5 +10663,8 @@ -
The dvrp
-software developed by the RRZN
-(Stephan Olbrich, Carsten Chmielewski) allows a creation of plot
-sequences with PALM,
-which can be animated via a special plugin for internet browsers. With
-suitable graphic hardware even stereoscopic views are
-possible.
+
Preliminary note:
Usage of the dvrp-software requires installation of additional software components (dvrp-library, streaming-server, browser-plugin) which are not +part of the PALM distribution. Currently (May 2009), this software is +only available on the the HLRN/IMUK system and partly on RIAM's NEC +system. If you are interested in using dvrp on your system, please contact the PALM developers.
The dvrp +software was originally developed by the RRZN +(Stephan Olbrich, Carsten Chmielewski) and is meanwhile continuosly developed and improved under the name dsvr by the University of Düsseldorf (Prof. Stephan Olbrich, see webpage of the dsvr-software). It allows to create 3d-animations with PALM, +which can be displayed via a special plugin for internet browsers. With +suitable graphic hardware (e.g. NVIDIA quattro FX cards) even stereoscopic views are +possible.
In contrast to the other kinds of visualization output realized
-in PALM (profil, iso2d and AVS),
+in PALM (1d-, 2d-, 3d-NetCDF output),
where the data
-is output in a format suitable for the plot software, the creation of
-plots via dvrp
+is output in a format suitable for many kinds of post-processing graphic software, the creation of animations via dvrp
software is
integrated in PALM, i.e. respective routines are directly called within
@@ -46,18 +45,18 @@
the main focus of the BMBF project "Application of
tele-immersion in long-distance networks" (2001-2002),
-which was a joint project of RRZN, ZIB and IMUK. This work is currently
-continued by RRZN in the new DFG-funded project "EVITA - Untersuchung
+which was a joint project of RRZN, ZIB and IMUK. This work was
+continued by RRZN in the DFG-funded project "EVITA - Untersuchung
effizienter
-
Methoden zur visuellen und haptischen tele-immersiven
+Methoden zur visuellen und haptischen tele-immersiven
Exploration
-
komplexer Volumen- und Strömungsdaten aus
+komplexer Volumen- und Strömungsdaten aus
parallelisierten,
-
dynamischen 3D-Simulationen" (2005-2007).
The calls of the dvrp routines are +dynamischen 3D-Simulationen" (2005-2007).
+Using dvrp with PALM:
The calls of the dvrp routines are contained within a PALM software package (see chapter 3.7). -To use this package, the additional option -p -“dvrp_graphics” -has to be given in the mrun call. This +To use this package, the additional option -p +“dvrp_graphics” +has to be given in the mrun call. This automatically links the required libraries. @@ -67,22 +66,23 @@ graphic data are not output to local files but directly to a special remote -computer which is defined via the package parameter dvrp_host. -The -default values of the dvrp parameters are cause the output to be -directed to a so-called streaming server at the +computer which is defined via the package parameter dvrp_host. If the default values of the dvrp parameters are used, data are send to a so-called streaming server at the RRZN. Apart from graphic data an additional html file is created, which -can be used by an internet browser to view the data (a special dvrp plugin is -needed).
-Since July 2001, the basic
-functionality
-of the dvrp
-software is
-installed in PALM and steerable via the
-package parameters. However, some code modifications may still need to
-be done by the user (e.g. in
-the subroutine plot_dvrp
-in order to define suitable color tables).
-
For further detailed information please ask Siegfried Raasch.
-
Quickstart guide for using dvrp on the HLRN/IMUK-System (May 2009):
+ Last
Index: palm/trunk/DOC/app/chapter_4.6.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.6.html (revision 335)
+++ palm/trunk/DOC/app/chapter_4.6.html (revision 336)
@@ -6379,5 +6379,5 @@
-
+ groundplate_color P R(3) 0.0, 0.6, 0.0 Color of the ground plate
@@ -6634,5 +6634,5 @@
-
+ isosurface_color P R(3,10) 0.9, 0.9, 0.9
0.8, 0.1, 0.1
......Color of the isosurface(s).
@@ -13789,5 +13789,5 @@
- topography_grid_convention I C * 11 default depends on value of topography; see text for details Convention for defining the topography grid.
+ topography_color P R(3) 0.8, 0.7, 0.6 Color of the topography. topography_grid_convention I C * 11 default depends on value of topography; see text for details Convention for defining the topography grid.
Index: palm/trunk/DOC/app/chapter_5.0.html
===================================================================
--- palm/trunk/DOC/app/chapter_5.0.html (revision 335)
+++ palm/trunk/DOC/app/chapter_5.0.html (revision 336)
@@ -1,6 +1,5 @@
-