Changes between Initial Version and Version 1 of doc/app/machine/nec_aurora_imuk


Ignore:
Timestamp:
Jan 20, 2020 10:44:07 AM (5 years ago)
Author:
raasch
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/machine/nec_aurora_imuk

    v1 v1  
     1= General hints for using the NEC SX-Aurora TSUBASA A300-8 system at IMUK =
     2
     3The system is part of the [https://www.luis.uni-hannover.de/scientific_computing.html LUIS-cluster at LUH].
     4
     5You need a user-account for the cluster-system to access the NEC-system. The login procesure is as follows:
     6
     7 1. Login to the LUIS cluster-system from a workstation at IMUK:
     8{{{ssh -X <your LUIS username>@login.luis.uni-hannover.de}}}
     9
     10 2. From the LUIS system, you need to start an interactive job on the NEC-machine:
     11{{{qsub -I -l nodes=1:ppn=1,mem=20gb -W x=PARTITION:muk}}}
     12
     13By default, the interactive job sessions runs for 24h. Your $HOME-filesystem of the LUIS cluster is mounted on the NEC-System. For storing large output files, use the NEC-local filesystem {{{/scratch/<your LUIS username>}}}
     14
     15
     16
     17On the NEC-machine only specific software to compile and run PALM is available (NEC Fortran compiler, NetCDF-,
     18
     19Furthermore, edit file {{{$HOME/.bash_profile}}} and add the following lines:
     20{{{
     21# User specific environment and startup programs
     22
     23PALM_BIN=$HOME/palm/current_version/trunk/SCRIPTS
     24export PALM_BIN
     25
     26PATH=$PALM_BIN:$PATH
     27export PATH
     28
     29LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/netcdf/4.1.1/lib
     30export LD_LIBRARY_PATH
     31}}}
     32
     33== tatara-system [http://www2.cc.kyushu-u.ac.jp/scp/system/general/CX/how_to_use] ==
     34
     35The system is supported starting from revision r1097. You can find a configuration file adjusted for this system in the svn-repository under [source:/palm/trunk/SCRIPTS/.mrun.config.tatara /palm/trunk/SCRIPTS/.mrun.config.tatara]. Just copy this file to your working directory
     36{{{
     37cd ~/palm/current_version
     38cp trunk/SCRIPTS/.mrun.config.tatara .mrun.config
     39}}}
     40Don't forget to edit the file in order to replace the string {{{<replace by your tatara username>}}} with your respective username.
     41
     42For the rest of the installation procedure just follow the instructions given on the [wiki:doc/install installation page].
     43
     44== hayaka-system [http://www2.cc.kyushu-u.ac.jp/scp/system/general/FX10/how_to_use] ==
     45
     46This system is supported starting from r1103 The configuration file adjusted for this system can be found under [source:/palm/trunk/SCRIPTS/.mrun.config.hayaka /palm/trunk/SCRIPTS/.mrun.config.hayaka]. Copy this file to your working directory
     47{{{
     48cd ~/palm/current_version
     49cp trunk/SCRIPTS/.mrun.config.hayaka .mrun.config
     50}}}
     51Don't forget to edit the file in order to replace the string {{{<replace by your hayaka username>}}} with your respective username.
     52
     53=== Restrictions on hayaka ===
     54
     55The hayaka login node only provides a cross compiler ({{{frtpx}}}) for the compute nodes. Therefore, the utility programs like {{{interpret_config}}} and {{{check_parameter_files}}} can be compiled, but they cannot be run. This requires to set appropriate {{{mrun}}} options
     56{{{
     57mrun ... -z -S ...
     58}}}
     59in order to switch off the parameter check ({{{-z}}}) and to interpret the configuration file directly from the script ({{{-S}}}).
     60
     61For compiling some parts of the PALM code, the Fujitsu compiler (frtpx) requires more memory than given by default. Please increase the maximum virtual memory size by command
     62{{{
     63ulimit -v 8097152
     64}}}
     65For convenience, you should add this command to the file {{{$HOME/.bash_profile}}}.
     66
     67No automatic restarts are possible on the hayaka system. You have to submit restart runs manually after the previous job has finished. In the job protocol file (see {{{~/job_queue}}}) of the previous run information is given about which '''mrun''' options are to be used for the restart.