Changes between Version 1 and Version 2 of Doc/ComputingCenters/TGCC


Ignore:
Timestamp:
03/24/14 16:16:50 (6 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Doc/ComputingCenters/TGCC

    v1 v2  
     1{{{ 
     2#!html 
     3<h1>Working on TGCC</h1> 
     4}}} 
     5---- 
     6[[PageOutline(1-3,Index du chapitre,,numbered)]] 
     7 
     8# TGCC users' manual # 
     9 
     10http://www-hpc.cea.fr/fr/complexe/tgcc.htm 
     11 
     12# TGCC's machines and file systems # 
     13 
     14[[Image(wiki:DocBenv:TGCC.jpg, 360px)]] 
     15 
     16# How to install your environment on TGCC # 
     17 
     18 * More information on the open-access website: http://www-hpc.cea.fr/fr/complexe/tgcc.htm 
     19 * Online access to the machines' users manual (you will need a TGCC login and password): https://www-tgcc.ccc.cea.fr/ 
     20 * [https://www-ccrt.ccc.cea.fr/intranetccrt/fr/ccrt/environnement_des_codes.htm TGCC scripts environment] 
     21 * The available TGCC's machine is currently '''curie''' (Bull Sandybridge). 
     22 * Note: the '''$HOME/.snapshot''' directory contains hourly, daily, and weekly backups of your $HOME files. 
     23 
     24[[NoteBox(note,It is important to take the time to install a comfortable and efficient environment.)]] 
     25 
     26We suggest the user to use the p86ipsl login's environment (in bash) as an example (either copy or source the `~p86ipsl/.bashrc` file). See the `~p86ipsl/.bashrc` file 
     27{{{ 
     28#!sh 
     29ryyy999@curie: cat ~/.bashrc 
     30#------------------------------------------------------ 
     31# PLATFORM ENVIRONMENT 
     32#------------------------------------------------------ 
     33source ~p86ipsl/.bashrc 
     34ryyy999@curie: cp ~p86ipsl/.profile . 
     35}}} 
     36 
     37In this environement is specified: 
     38 * the path to the compiler tool `fcm` and to the `rebuild` tool which recombines output files from a parallel model: 
     39{{{  
     40export PATH=~p86ipsl/fcm/bin:~p86ipsl/X64_CURIE/bin:$PATH 
     41}}} 
     42 * the load of modules giving access to computing or post processing libraries and tools needed on our Home (done in ~p86ipsl/ .atlas_env_calcul_curie_ksh and ~p86ipsl/ .atlas_env_post_curie_ksh). The revision numbers may change, currently (21/01/2014) following modules are loaded for computing. Note the netcdf 3.6.3 library: 
     43{{{ 
     44module load ghostscript/9.04 
     45module load ferret/6.6.7 
     46module load netcdf/3.6.3 
     47module load gsl/1.14 
     48module load hdf5/1.8.8 
     49module load nco/4.0.5 
     50module load cdo/1.4.6 
     51module load netpbm/10.47.34 
     52module load imagemagick/6.7.4 
     53}}} 
     54 
     55The revision numbers may change, currently (21/01/2014) following modules are loaded for postprocessing: 
     56{{{ 
     57module load ghostscript/9.04 
     58module load ferret/6.6.7 
     59module load netcdf/4.2 
     60module load gsl/1.14 
     61module load hdf5/1.8.8 
     62module load nco/4.1.0 
     63module load cdo/1.4.6 
     64module load netpbm/10.47.34 
     65module load imagemagick/6.7.4 
     66}}} 
     67 
     68# Project and computing needs # 
     69 * To find out the computing time used by the projects you are involved in (daily update): 
     70{{{ 
     71#!sh 
     72ryyy999@curie: ccc_myproject 
     73}}} 
     74 * Specify in the header the project from which your job will use computing time: 
     75{{{ 
     76#!sh 
     77#MSUB -A genxxx 
     78}}} 
     79 
     80# About file systems # 
     81 
     82## Quotas ## 
     83To check the available and used storage capacities of `HOME`, `SCRATCH`, `CCCWORKDIR` and `CCCSTOREDIR`: 
     84{{{ 
     85#!sh 
     86ryyy999@curie: ccc_quota 
     87}}} 
     88 
     89On the curie machine this command will also return the space used by scratch (a specificity of the curie machine). 
     90 
     91 
     92## CCCWORKDIR ## 
     93The `$CCCWORKDIR` directory corresponds to the `$WORKDIR` directory on curie. It is large but its content is not backed up. 
     94 
     95## CCCSTOREDIR ## 
     96To manipulate the files in /ccc/store a few commands are useful:  
     97{{{ 
     98#!sh 
     99# Demigrate a list of files on CCCSTOREDIR, see also "ccc_hsm -h" 
     100ccc_hsm get $CCCSTOREDIR/FICHIER1 $CCCSTOREDIR/FICHIER2 ... 
     101 
     102# Demigrate recursively the files from a CCCSTOREDIR directory, see also "ccc_hsm -h" 
     103ccc_hsm get -r $CCCSTOREDIR/REPERTOIRE 
     104 
     105# Find out the used space on CCCSTOREDIR 
     106cd $CCCSTOREDIR ; find . -printf "%y %s %p \n" | awk '{ SUM+=$2 } END {print "SUM " SUM/1000000 " Mo " SUM/1000000000 " Go" }' 
     107 
     108# or use --apparent-size with du : 
     109du -sh --apparent-size 
     110}}} 
     111 
     112 
     113## ccc_home command to know directory complete pathname ## 
     114 
     115ccc_home could help you to find directory complete pathname for an other user or for you . 
     116{{{ 
     117>ccc_home -h 
     118ccc_home: Print the path of a user directory (default: home directory). 
     119usage: ccc_home [ -H | -s | -t | -W | -A | -G | -a] [-u user] 
     120                [-h, --help] 
     121 
     122 -H, --home         :  (default) print the home directory path ($HOME) 
     123 -s, -t, --scratch  :  print the scratch directory path   ($SCRATCHDIR) 
     124 -W, --cccwork      :  print the CCC work directory path  ($CCCWORKDIR) 
     125 -A, --cccstore     :  print the CCC store directory path ($CCCSTOREDIR) 
     126 -G, --cccgenostore :  print the CCC genostore directory path ($CCCGENOSTOREDIR) 
     127 -a, --all          :  print all paths 
     128 -u user            :  show paths for the specified user instead of the current user 
     129 -h, --help         :  display this help and exit 
     130 
     131> ccc_home -A -u p86denv    
     132/ccc/store/cont003/dsm/p86denv 
     133 
     134}}} 
     135## Storage spaces available from DODS ## 
     136To store a file for the first time on dods, you must ask for dods write access by mail to the TGCC hotline access : `hotline.tgcc@cea.fr`. 
     137  
     138# End-of-job messages # 
     139 
     140To receive the end-of-job messages sent by the job itself: end of simulation, error,... you must specify your address in the $`HOME/.forward` file. 
     141 
     142# Simulation outputs # 
     143 
     144Final simulation outputs are stored in `$CCCSTOREDIR/IGCM_OUT` and on `$CCCWORKDIR/IGCM_OUT` regarding the `ATLAS` and `MONITORING` directories. 
     145 
     146The dods servers on TGCC are available via:  `dods.extra.cea.fr/store`  (files such as `Analyse/TS` and `Analyse/SE`) and `dods.extra.cea.fr/work` for `ATLAS` and `MONITORING`. 
     147 
     148# About password # 
     149 
     150ccc_password_expiration helps you to know expiration date of your password. Currently password have to be changed one time per year. 
     151{{{ 
     152 > ccc_password_expiration 
     153Password for xxxxx@USERS-CCRT.CCC.CEA.FR: PPPPPPPPPP 
     154Your password will expire in 70 days on Fri Nov 22 08:42:59 2013 
     155 > ccc_password_expiration -h 
     156Usage: ccc_password_expiration [username[@realm]] 
     157 
     158}}} 
     159 
     160 
     161# The TGCC's machines #  
     162 * [wiki:DocBenvBtgccAcurie Curie] 
     163