Ignore:
Timestamp:
Jan 3, 2025, 6:14:41 PM (5 weeks ago)
Author:
fhourdin
Message:

For sequential and debug compilation

File:
1 edited

Legend:

Unmodified
Added
Removed
  • BOL/LMDZ_Setup/README0_HowTo

    r5429 r5465  
    112112
    113113============================================================
    114 III. Repatriation of input data
     114III. Downloading input data
    115115============================================================
    116116
    117117Installation requires downloading data from
    118118from http://http://lmdz.lmd.jussieu.fr/pub/3DInputData
    119 Repatriation is managed by a series of functions found in
     119Downloading is managed by a series of functions found in
    120120lmdz_env.sh: wget_pub cp_from_pub ln_from_pub get_input_files
    121121
    122 In my opinion, LMDZ_Setup's approach to data management is to be able to perform a complete
    123 installation on any account on any machine, by distributing data from wget http://lmdz....
    124 In the new version, you don't duplicate any of the fields you download, and you only download them once to an account.
     122One specificity of LMDZ_Setup is to enable installation on any account on any machine,
     123downloading data from wget.
     124All data are gathered on a directory $LMDZpub so that the
     125downloading is done once for all for a given account.
     126LMDZsub can be changed on in lmdz_env.sh
     127
    125128This is very small compared to the amount of data generated.
    126129So I think we're very parsimonious in our use of IT resources.
    127 Of course, this has to do with the fact that we don't manage a lot of different configurations in terms of boundary conditions, forcing, etc.
    128 But that's where libiGCM comes in.
     130The counterpart is that LMDZ_Setup doesn't manage a lot of different configurations
     131in terms of boundary conditions, forcing, etc.
     132libiGCM installations should be privileged then.
    129133
    130134
     
    134138
    135139Running zoomed or coarse grid simulations
    136     May cause problems with routing and aerosols
    137     Suggesting to run without aerosols, aerosols="n", in this case
     140May cause problems with routing and aerosols
     141Suggesting to run without aerosols, aerosols="n", in this case
    138142
    139143
     
    142146============================================================
    143147
    144 2024-12 (FH) : retravail de l'accès au données sur http://lmdz...
    145 
    146 2024-11 : Travail de portage multi-machine par Amaury Barral.
     1482025-01 (FH) : retravail de l'accès au données sur http://lmdz...
     149        reactivation options sequential/debug.
     150        Configuration SPLA muti machines
     151
     1522024-11 (AB) : Travail de portage multi-machine par Amaury Barral.
    147153          Précédemment sur jean-zay uniquement.
    148154          Porté sur adastra et machines locales.
Note: See TracChangeset for help on using the changeset viewer.