Index: palm/trunk/DOC/app/chapter_4.5.7.html
===================================================================
--- palm/trunk/DOC/app/chapter_4.5.7.html (revision 336)
+++ palm/trunk/DOC/app/chapter_4.5.7.html (revision 337)
@@ -68,12 +68,12 @@
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 opened by an internet browser to view the data (a special dvrp plugin is required for this).
Quickstart guide for using dvrp on the HLRN/IMUK-System (May 2009):
+can be opened by an internet browser to view the data (a special dvrp plugin is required for this).Quickstart guide for using dvrp on the HLRN/IMUK-System (May 2009):
In the following, please replace the string <UNAME> with your IMUK username, wherever it appears. Please also replace the string <UDIR> with a subdirectory name of your choice.
-
Add the following define statements for environment variables to the configuration file (.mrun.config):
%dvr_inc
-I/home/h/niksiraa/dvr_mvapich2/lib
lcsgih parallel
%dvr_lib -L/home/h/niksiraa/dvr_mvapich2/lib:-lDVRP2:-lftp lcsgih
-parallel
- Add the dvrp-steering parameters to your NAMELIST-parameter file, e.g.
&d3par end_time = 3600.0,
... /
&dvrp_graphics_par dvrp_username = '<replace by your IMUK username>',
dvrp_host = '130.75.105.2',
+parallel
- Add the dvrp-steering parameters to your NAMELIST-parameter file, e.g.
&d3par end_time = 3600.0,
... /
&dvrp_graphics_par dvrp_username = '<UNAME>',
dvrp_host = '130.75.105.2',
-dvrp_directory = '<replace by a name of your choice>', ... /
For other dvrp-parameters see chapter 4.2. An example parameter file can be found in directory ..../trunk/EXAMPLES/dvr_building.
- Submit the job with mrun-command
mrun .... -p dvrp_graphics ....
- After the job has finished, the dvrp-output can be found on the IMUK-cluster in a subdirectory under /data/raasch/Dvrp_daten. The name of the subdirectory is determined by the dvrp-parameter dvrp_directory (see above), i.e. if the user has set dvrp_directory = 'movie_1', the dvrp-data are stored under /data/raasch/Dvrp_daten/movie_1.
- Change to this subdirectory (e.g. /data/raasch/Dvrp_daten/movie_1) and enter the command
process_dvr_output
It will create a file with name all_streams_streaming.html.
- Call the opera-browser (i.e. enter the command opera) and open the file all_streams_streaming.html.
A complete example parameter file for ... can be found under .../trunk/.....
Further features:
The script process_dvr_output has additional options:
-s : create sequence output.
+dvrp_directory = '<UNAME>/<UDIR>', ... /
For other dvrp-parameters see chapter 4.2. An example parameter file can be found in directory ..../trunk/EXAMPLES/dvr .
On the IMUK-system, create a subdirectory in which the dvrp-data are stored.
mkdir /data/raasch/Dvrp_daten/<UNAME>
This directory has to be created only once, before dvrp is used for the first time.
Submit the job with mrun-command
mrun .... -p dvrp_graphics ....
After the job has finished, the dvrp-output can be found on the IMUK-cluster in a subdirectory under /data/raasch/Dvrp_daten. The name of the subdirectory is determined by the dvrp-parameter dvrp_directory (see above), i.e. if the user has set dvrp_directory = '<UNAME>/movie_1', the dvrp-data are stored under /data/raasch/Dvrp_daten/<UNAME>/movie_1.
Change to this subdirectory (e.g. /data/raasch/Dvrp_daten/<UNAME>/movie_1) and enter the command
process_dvr_output
It will create a file with name all_streams_streaming.html.
Call the opera-browser (i.e. enter the command opera) and open the file all_streams_streaming.html.
Further features:
The script process_dvr_output has additional options:
-s : create sequence output.
All streams (and static scenes) are collected to one sequence (one
static scene), which can be displayed with a browser without using the