Changes between Version 90 and Version 91 of Doc/FAQ
- Timestamp:
- 03/03/23 15:33:36 (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Doc/FAQ
v90 v91 309 309 The problem originates from the combination of two facts. 310 310 311 ''First ''311 ''Firstly''[[BR]] 312 312 Because the o2a.nc files produced by MOSAIC and MOSAIX differ (they have different coastlines), when interpolating from the ocean grid to the atmosphere grid points very close to the coast, land points can become sea points and vice versa if you switch from the MOSAIC to the MOSAIX weights. 313 313 314 ''Second ''315 The o2a.nc file is read only once by LMDZ when producing restart files and boundary conditions for a forced simulation with create_etat0_limit.e and is embedded in the restart files.314 ''Secondly''[[BR]] 315 The o2a.nc file is read only once by LMDZ : when producing restart files and boundary conditions for a forced simulation with create_etat0_limit.e and is embedded in the restart files. It is then transmited through the restarts to all subsequent simulations. 316 316 317 317 '''The actual problem''' … … 320 320 ### The trick to get around this ### 321 321 322 The problem being with the atmosphere you can use your NEMO restart files as is and keep the dynamical state of the ocean.323 324 For LMDZ you will have to restart the atmosphere from a initial state created with create_etat0_limit.e to make sure you use the MOSAIX o2a.nc file.322 The problem being with the atmosphere you can use your NEMO restart files as they are and keep the dynamical state of the ocean to restart your MOSAIX coupled simulation. 323 324 For LMDZ you will have to restart the atmosphere from an initial state created with create_etat0_limit.e to make sure you use the MOSAIX o2a.nc file. 325 325 326 326 Still, it is possible to improve the initial state of the atmosphere by running a forced simulation with the ocean surface quantities from the MOSAIC simulation.