Changes between Version 23 and Version 24 of Doc/env/TgccCurie


Ignore:
Timestamp:
09/25/15 15:02:05 (9 years ago)
Author:
acosce
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Doc/env/TgccCurie

    v23 v24  
    139139# Fat nodes / Thin nodes # 
    140140 
    141 Fat nodes for the IPSLCM5A-LR coupled model are slower than titane (130%). Thin nodes are two times faster than fat nodes for computations; they are as fast as fat nodes for post processing. 
     141Thin nodes are two times faster than fat nodes for computations; they are as fast as fat nodes for post processing. 
    142142 
    143143We decided to use thin nodes for computations and fat nodes for post processing. Be careful! Since November 21st 2012, you must use at least libIGCM_v2.0_rc1 to perform post processing on fat nodes. 
    … …  
    394394# REDO # 
    395395 
    396 Simulations with the IPSLCM5A coupled model are reproducible if you use the same Bands file for LMDZ. See trusting TGCC/curie on this webpage: http://webservices.ipsl.jussieu.fr/trusting/ 
    397  
    398 # Feedback # 
    399  
    400 ## On November 20th 2012 ## 
    401  
    402 The maintenance has noticed and corrected the last two problems. 
    403  
    404 ## In June 2012 ## 
    405  
    406 The 100-yr simulation of piControl in June 2012 : 
    407  * 9% of jobs were resubmitted manually (3/34). 
    408  * 0,6 % of the jobs and post processing were resubmitted manually (4/694). 
    409  
    410 ## Error to watch in the post processing: WARNING Intra-file non-monotonicity. Record coordinate "time_counter" does not monotonically increase ## 
    411  * To identify quickly: grep -i monoton create_ts* | awk -F: '{print $1}' |sort -u  
    412    * (Command to type in ${SCRATCHDIR}/IGCM_OUT/${!TagName}/${!SpaceName}/${!ExperimentName}/${!JobName}/Out.  
    413    * For example /ccc/scratch/cont003/dsm/p25mart/IGCM_OUT/IPSLCM5A/DEVT/lgm/LGMBR03/Out) 
    414  * Example : 
    415 {{{ 
    416 + IGCM_sys_ncrcat --hst -v lon,lat,plev,time_counter,time_counter_bnds,zg v3.rcp45GHG1_20160101_20161231_HF_histhfNMC.nc v3.rcp45GHG1_20170101_20171231_HF_histhfNMC.nc v3.rcp45GHG1_20180101_20181231_HF_histhfNMC.nc v3.rcp45GHG1_20190101_20191231_HF_histhfNMC.nc v3.rcp45GHG1_20200101_20201231_HF_histhfNMC.nc v3.rcp45GHG1_20210101_20211231_HF_histhfNMC.nc v3.rcp45GHG1_20220101_20221231_HF_histhfNMC.nc v3.rcp45GHG1_20230101_20231231_HF_histhfNMC.nc v3.rcp45GHG1_20240101_20241231_HF_histhfNMC.nc v3.rcp45GHG1_20250101_20251231_HF_histhfNMC.nc v3.rcp45GHG1_20160101_20251231_HF_zg.nc 
    417 ncrcat: WARNING Intra-file non-monotonicity. Record coordinate "time_counter" does not monotonically increase between (input file v3.rcp45GHG1_20190101_20191231_HF_histhfNMC.nc record indices: 418, 419) (output file v3.rcp45GHG1_20160101_20251231_HF_zg.nc record indices 4798, 4799) record coordinate values 419007600.000000, 0.000000 
    418 }}} 
    419  * Check the non monotonic time axis: 
    420 {{{ 
    421 /ccc/cont003/home/dsm/p86broc/dev_python/is_monotone.py OCE/Analyse/TS_DA/v5.historicalMR3_19800101_19891231_1D_vosaline.nc_KO_monoton time_counter 
    422 False 
    423 }}} 
    424  * Solution: rm the TS files created and restart with TimeSeries_Checker 
    425  
     396Simulations with the IPSLCM5/IPSLCM6 coupled model are reproducible if you use the same Bands file for LMDZ. See trusting TGCC/curie on this webpage: http://webservices.ipsl.jussieu.fr/trusting/ 
     397