New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Changeset 2242 – NEMO

Changeset 2242


Ignore:
Timestamp:
2010-10-13T11:13:58+02:00 (14 years ago)
Author:
gm
Message:

ticket:#658 update SBC with diurnal cycle

Location:
branches/DEV_r1826_DOC/DOC/TexFiles
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • branches/DEV_r1826_DOC/DOC/TexFiles/Chapters/Chap_SBC.tex

    r2197 r2242  
    382382 the option for the user to increase vertical mixing in the vicinity of the rivermouth. 
    383383 
    384 However, this method is not very appropriate for coastal modelling.  As such its now possible 
    385  to specify, in a netcdf input file, the temperature and salinity of the river, along with the  
     384However, this method is not very appropriate for coastal modelling.  As such its now possible  
     385to specify, in a NetCDF input file, the temperature and salinity of the river, along with the  
    386386depth (in metres) which the river should be added to.  This enables to river to be correctly  
    387387added through the water column, instead of as a surface flux, and also means the temperature  
     
    433433\includegraphics[width=0.8\textwidth]{./TexFiles/Figures/Fig_SBC_diurnal.pdf} 
    434434\caption{Example of recontruction of the diurnal cycle variation of short wave flux   
    435 from daily mean values. The reconstructed diurnal cycle (red squares) is chosen  
    436 as the mid time step value of the analytically cycle (blue line), not as  
    437 the mean value of the analytical cycle over a time step (black line).  
    438 The misfit is however small and without systematic bias. From \citet{Bernie_al_CD07}.} 
     435from daily mean values. The reconstructed diurnal cycle (black line) is chosen  
     436as the mean value of the analytical cycle (blue line) over a time step, not  
     437as the mid time step value of the analytically cycle (red square). From \citet{Bernie_al_CD07}.} 
    439438\end{center}   \end{figure} 
    440439%>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
     
    462461CORE bulk formulea (\np{ln\_blk\_core}=true) or the flux formulation (\np{ln\_flx}=true).  
    463462The reconstruction is performed in the \mdl{sbcdcy} module. The detail of the algoritm used  
    464 can be found in the appendix~A of \cite{Bernie_al_CD07}. It is not a strictly conservative  
    465 algorithm as the mid time step analytical value is used instead of the mean value of  
    466 the analytical cycle over a time step (Fig.\ref{Fig_SBC_diurnal}). Nevertheless, the error is   
    467 quite small, reaching locally a maximum value of a few tenth of W/m$^2$ with a 2~h sampling,  
    468 the error decreasing with increasing the sampling. Moreover, the error is not a systematic, and  
    469 thus does not lead to seasonal bias.  
    470             
    471 Fig.\ref{Fig_SBC_dcy} show an example of 12 reconstructed diurnal cycle, one every 2~hours  
    472 (from 1am to 11pm). The difference between the original daily mean and the daily mean  
    473 reconstructed diurnal cycle (not shown) is small (extrema of $\pm$0.4 W/m$^2$). 
     463can be found in the appendix~A of \cite{Bernie_al_CD07}. The algorithm preserve the daily  
     464mean incomming SWF as the reconstructed SWF at a given time step is the mean value  
     465of the analytical cycle over this time step (Fig.\ref{Fig_SBC_diurnal}).  
     466The use of diurnal cycle reconstruction requires the input SWF to be daily  
     467($i.e.$ a frequency of 24 and a time interpolation set to true in \np{sn\_qsr} namelist parameter). 
     468Furthermore, it is recommended to have a least 8 surface module time step per day, 
     469that is  $\rdt \ \np{nn\_fsbc} < 10,800~s = 3~h$. An example of recontructed SWF  
     470is given in Fig.\ref{Fig_SBC_dcy} for a 12 reconstructed diurnal cycle, one every 2~hours  
     471(from 1am to 11pm). 
    474472 
    475473%>>>>>>>>>>>>>>>>>>>>>>>>>>>> 
Note: See TracChangeset for help on using the changeset viewer.