Ocean_skin
(2 files, 152 lines)
ecrad
(5 files, 2265 lines)
rrtm
(4 files, 1014 lines)
[root]/branches/LMDZ_ECRad/libf/phylmd
Ocean_skin
(2 files, 152 lines)
ecrad
(5 files, 2265 lines)
rrtm
(4 files, 1014 lines)
| Author | Changes | Lines of Code | Lines per Change |
|---|---|---|---|
| Totals | 41 (100.0%) | 225 (100.0%) | 5.4 |
| lguez | 33 (80.5%) | 183 (81.3%) | 5.5 |
| idelkadi | 8 (19.5%) | 42 (18.7%) | 5.2 |
Sync latest trunk changes to branch LMDZ_ECRad.
3 lines of code changed in 5 files:
Do not use `handle_err`
`handle_err` is no longer in NetCDF95. In the modified procedures in
the present commit, `handle_err` was used after a call to
`nf90_get_var`, because `nf95_get_var` did not exist in NetCDF95 when
the procedures were written. Now, we can just use `nf95_get_var`.
25 lines of code changed in 8 files:
Implementation of the Ecrad radiative transfer code in the LMD model (continued) :
Integration of aerosols (direct effect)
42 lines of code changed in 8 files:
Bug fix: declare nf95_gw_var
2 lines of code changed in 1 file:
Use custom procedure to read aerosol optics file
Replace call to `config%aerosol_optics%setup` by call to an LMDZ
procedure, `setup_aerosol_optics_lmdz`, adapted to our aerosol optics
NetCDF file. The main differences between our file and the file
expected by `config%aerosol_optics%setup` are:
- Our file has groups.
- The SW bands in our file are ordered (as befits a NetCDF
coordinate).
- Our file does not contain variables for monochromatic asymmetry
factor, single-scattering albedo and lidar backscattering
ratio. These variables are not used by ECRad but they are
nevertheless read and required by `config%aerosol_optics%setup`.
124 lines of code changed in 1 file:
Use an external updated NetCDF95 library
Remove NetCDF95 from source files. We want to use an up-to-date
NetCDF95 library to read a NetCDF file containing groups, for aerosol
optical properties. It seems complicated to keep the NetCDF95 library
inside LMDZ because:
- NetCDF95 now also needs a C compiler. I do not know how to make this
work with FCM.
- NetCDF95 cannot be compiled with the `-r8` option: some specific
procedures in a generic interface become identical.
- Secondarily, we would have to change the names of files to adhere to the LMDZ
standard. We are not glad to do that every time we update.
For now, we can compile using the options `-include` and `-link` of
`makelmdz_fcm`.
As we use an updated NetCDF95 library, we have to update some of the
calls in LMDZ. Those are the calls to `nf95_inquire_variable` and
`nf95_gw_var` which used to take a pointer argument and now take an
allocatable argument.
29 lines of code changed in 18 files: