Changes between Version 22 and Version 23 of ticket/0665_mass_heat_salt_fluxes


Ignore:
Timestamp:
2010-05-11T06:11:36+02:00 (10 years ago)
Author:
gm
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • ticket/0665_mass_heat_salt_fluxes

    v22 v23  
    211211   '''LIM3''' : the modules involved in the change are : (see also the '''revision -''') 
    212212 
    213  
    214  
    215       '''==>> TO BE DONE later''' 
     213      • '''ice.F90''' : add arrays to describe the heat content associated with both snow and ice mass changes and also change the name of the mass changes. As for LIM-2, the mass flux array names change from rdmsnif and rdmicif  to more readable rdm_snw and rdm_ice  ; and 2 heat content arrays have been added : rdq_snw and rdq_ice  
     214 
     215      • '''thd_ice.F90''' : associated 1D array names (rdsnif_1d, rdmicif_1d) have been changed into (rdm_snw_1d, rdm_ice_1d) and (rdq_snw_1d, rdq_ice_1d) have been added. 
     216 
     217      • '''limthd.F90''' : introduce the new variable names, and pass the new variables (rdq_snw, rdq_ice) to the lim_thd_zdf and lim_thd_lac routines 
     218 
     219         '''BUG''' correction : In LIM-3 a betas exponent has been introduced when computing the solid precipitation over the sea ice. Part of the snow that falls over sea-ice is put in the lead areas by the wind. Nevertheless, the latent heat flux due to snow melting is computed with sprecip *(1-at_i) whereas the actual solid precipitation over lead area is sprecip*(1-at_i**betas).  If betas /=1, some latent heat is missing (see #670). 
     220 
     221        '''BUG''' correction : limthd : use fse3t_m instead of fse3t 
     222 
     223      '''==>> ONGOING work''' 
    216224 
    217225'''(2) Non-solar flux including the heat content of mass exchanges'''   see '''revision 1859''' 
     
    582590   • In the same idea : the embedded sea-ice should become the defaut case, with in option the 2 levitating cases. A test should then force a levitating sea-ice if key_linssh defined 
    583591 
     592   • Idea for LIM-3 optimisation : instead of 2D => 1D transformation, is it possible to introduce a 3D (including ice categories) => 1D transformation. Gain: longer vector so clear in vector computer, less obvious on scalar one, except that the limthd... will become 1 gigantic done loop => better also for scalar. 
     593 
    584594'''CAUTION''' 
    585595