# source:NEMO/trunk/doc/latex/SI3/subfiles/chap_output_diagnostics.tex@11015

Last change on this file since 11015 was 11015, checked in by nicolasmartin, 17 months ago

Modification of the content to be in line with the NEMO manual
SI3 manual can now be build like the NEMO manual with ./manual_build.sh SI3

• Mimick the directory organisation with main and subfiles folders.
• Regarding the particular case of namelists
• Remove the duplicates already contained in the global namelists folder at 1st level of ./doc
• Keep the namelists sub-folder only for namdyn_adv & namsbc which already exist in ocean namelists
• Rewriting of SI3_manual.tex with NEMO_manual.tex as template to easily highlight differences
• Updating of several paths for figures/namelists inclusion or LaTeX files referencing
• LaTeX source:
• Replacement of \forfile command for namelists with pre-configured \nlst alias
• " "" \bm with \mathbf (save installation of an extra package)
File size: 3.6 KB
Line
1\documentclass[../main/SI3_manual]{subfiles}
2
3\begin{document}
4
5% ================================================================
6% Chapter 9 - Outputs and diagnostics
7% ================================================================
8
9\chapter{Output and diagnostics}
10\label{chap:DIA}
11\minitoc
12
13\newpage
14$\$\newline    % force a new line
15
16\section{SIMIP diagnostics}
17
18The SIMIP protocol \citep{Notzetal16} was designed for CMIP6, to standardize sea ice model outputs in climate simulations. We tried to follow the data request as closely as possible. Outputs are in most cases directly managed with XIOS2 in \textbf{limwri.F90}, but not always. In the code, output fields keep their native LIM reference name.
19
20A corresponding entry exists in \textbf{field\_def\_nemo-lim.xml}, where fields are given their SIMIP specifications (standard name, long name, units). At the end of the file the fields are gathered in the field groups \textbf{SIday\_fields}, \textbf{SImon\_fields} and \textbf{SImon\_scalar} for separation of the daily (SIday) and monthly (SImon) requests.
21
22In \textbf{file\_def\_nemo-lim.xml}, the daily, monthly and scalar output files are created.
23
24In the reference xml files, the largest possible SIMIP-based diagnostics with LIM are distributed among the field groups. If some fields are to be discarded, the best way to do so is to remove them from the field groups in  field\_def\_nemo-lim.xml.
25
26\subsection{Missing SIMIP fields}
27
28About 90\% of the SIMIP fields can be output. Below is the list of the missing fields and why they are missing. \\
29
30\textbf{1. Fields that are not part of the sea ice representation in LIM3.6}
31\begin{itemize}
32\item sisnconc (snow area fraction), siitdsnconc (snow area fractions in thickness categories);
33\item simpconc (meltpond area fraction), simpmass (melt pond mass per area), simprefrozen (thickness of refrozen ice on ponds);
34\item sirdgconc (ridged ice area fraction), sirdgmass (ridged ice thickness);
35\item sidmasslat (lateral sea ice melt rate);
36\item sndmasswindrif (snow mass change through wind drift of snow);
37\end{itemize}
38
39\textbf{2. Fields which value is trivial}
40\begin{itemize}
41\item sipr (rainfall over sea ice): all rain falls in open water;
42\item sidragtop (atmospheric drag over sea ice): namelist parameter;
43\item sidragbot (oceanic drag over sea ice): namelist parameter
44\end{itemize}
45
46\textbf{3. Fields that belong to the atmospheric component}
47\begin{itemize}
48\item siflswdtop, siflswutop, siflswdbot, sifllwdtop, sifllwutop, siflsenstop, sifllatstop (surface energy budget components)
49\end{itemize}
50
51Ice thickness and snow depth were masked below 5\% ice concentration, because below this value, they become meaninglessly large in LIM. This is notably because of the Prather advection scheme. We hope to fix these issues for our next release. For similar reasons, the ice age is masked below 15\% concentration.
52
53Fluxes through straits and passages were not directly implemented. Instead, ice mass, snow mass, and ice area transports were implemented as 2D arrays, for x- and y- directions. A python script is available to derive the fluxes through straits and passages from full 2D arrays for ORCA2 and eORCA1 grids.
54