Changeset 5465 for BOL/LMDZ_Setup/README0_HowTo
- Timestamp:
- Jan 3, 2025, 6:14:41 PM (5 weeks ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
BOL/LMDZ_Setup/README0_HowTo
r5429 r5465 112 112 113 113 ============================================================ 114 III. Repatriation ofinput data114 III. Downloading input data 115 115 ============================================================ 116 116 117 117 Installation requires downloading data from 118 118 from http://http://lmdz.lmd.jussieu.fr/pub/3DInputData 119 Repatriationis managed by a series of functions found in119 Downloading is managed by a series of functions found in 120 120 lmdz_env.sh: wget_pub cp_from_pub ln_from_pub get_input_files 121 121 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. 122 One specificity of LMDZ_Setup is to enable installation on any account on any machine, 123 downloading data from wget. 124 All data are gathered on a directory $LMDZpub so that the 125 downloading is done once for all for a given account. 126 LMDZsub can be changed on in lmdz_env.sh 127 125 128 This is very small compared to the amount of data generated. 126 129 So 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. 130 The counterpart is that LMDZ_Setup doesn't manage a lot of different configurations 131 in terms of boundary conditions, forcing, etc. 132 libiGCM installations should be privileged then. 129 133 130 134 … … 134 138 135 139 Running zoomed or coarse grid simulations 136 137 140 May cause problems with routing and aerosols 141 Suggesting to run without aerosols, aerosols="n", in this case 138 142 139 143 … … 142 146 ============================================================ 143 147 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. 148 2025-01 (FH) : retravail de l'accès au données sur http://lmdz... 149 reactivation options sequential/debug. 150 Configuration SPLA muti machines 151 152 2024-11 (AB) : Travail de portage multi-machine par Amaury Barral. 147 153 Précédemment sur jean-zay uniquement. 148 154 Porté sur adastra et machines locales.
Note: See TracChangeset
for help on using the changeset viewer.