Changeset 13267
- Timestamp:
- 2020-07-08T15:19:07+02:00 (4 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
NEMO/trunk/tests/STATION_ASF/README.md
r13264 r13267 1 1 # *Station Air-Sea Fluxes* demonstration case 2 2 3 Last sucessful test done with NEMOGCM trunk: `r13263` 3 Last successful test done with NEMOGCM trunk: `r13263` 4 5 Author: Laurent Brodeau, 2020 4 6 5 7 NOTE: if working with the trunk of NEMO, you are strongly advised to use the same test-case but on the `NEMO-examples` GitHub depo: … … 8 10 ## Objectives 9 11 10 ```STATION_ASF``` is a demonstration case that mimics an in-situ station (buoy, platform) dedicated to the estimation of surface air-sea fluxes by means of the measurement of traditionalmeteorological surface parameters.12 ```STATION_ASF``` is a demonstration test-case that mimics a (static) in-situ station (buoy, platform) dedicated to the estimation of surface air-sea fluxes by means of *widely-measured* (bulk) meteorological surface parameters. 11 13 12 ```STATION_ASF``` is based on the merging of the "single column" and the "standalone surface module" configurations of NEMO. In short, it coulbdefined as "SAS meets C1D". As such, the spatial domain of ```STATION_ASF``` is punctual (1D, well actually 3 x 3 as in C1D).14 ```STATION_ASF``` has been constructed by merging the *single column* and the *standalone surface module* configurations of NEMO. In short, it can be defined as "SAS meets C1D". As such, the spatial domain of ```STATION_ASF``` is punctual (1D, well actually 3 x 3 as in C1D). 13 15 14 ```STATION_ASF``` is therefore a versatile tool, and extremely light in terms of computing requirements, to test the different bulk algorithms and cool-skin/warm-layer parameterization options included in NEMO.16 ```STATION_ASF``` is therefore a versatile tool, and extremely lightweight in terms of computing requirements, to test the different bulk algorithms and cool-skin/warm-layer parameterization options included in NEMO. 15 17 16 18 As input ```STATION_ASF``` will require the traditional *bulk* sea surface parameters: … … 90 92 - ```PROD_DIR``` : Directory where to run the simulation 91 93 92 - ```DATA_IN_DIR``` : Directory containing sea-surface + atmospheric forcings ( get it there https://drive.google.com/file/d/1MxNvjhRHmMrL54y6RX7WIaM9-LGl--ZP/)94 - ```DATA_IN_DIR``` : Directory containing sea-surface + atmospheric forcings (found here in ```input_data/```) 93 95 94 96 If everything goes according to plan, ``launch_sasf.sh`` should have generated the 3 following sets of output files into `${PROD_DIR}/output`: … … 106 108 --- 107 109 108 */Laurent Brodeau, July 2020.*110 */Laurent, July 2020.* 109 111
Note: See TracChangeset
for help on using the changeset viewer.