Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Nemo
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Requirements
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sam Hatfield
Nemo
Commits
238fd979
Commit
238fd979
authored
3 years ago
by
Tomas Lovato
Browse files
Options
Downloads
Patches
Plain Diff
fix some typos preventing compilation
parent
10980ca7
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/latex/NEMO/subfiles/chap_DIA.tex
+14
-10
14 additions, 10 deletions
doc/latex/NEMO/subfiles/chap_DIA.tex
doc/latex/global/coding_rules.tex
+1
-2
1 addition, 2 deletions
doc/latex/global/coding_rules.tex
with
15 additions
and
12 deletions
doc/latex/NEMO/subfiles/chap_DIA.tex
+
14
−
10
View file @
238fd979
...
...
@@ -66,7 +66,7 @@ of the use of this I/O server is presented in the next section.
%% =================================================================================================
\section
{
Standard model output (
\textt
{
iom
\_
put
}
)
}
\section
{
Standard model output (
\textt
t
{
iom
\_
put
}
)
}
\label
{
sec:DIA
_
iom
}
Since version 3.2,
\rou
{
iom
\_
put
}
is the
\NEMO\
output interface of choice.
...
...
@@ -268,7 +268,7 @@ See the XML basics section below for more details on XML syntax and rules.
\end{table}
The rest of the XML controls and definitions for XIOS-
\NEMO\
interaction are contained in a series of
XML files included via the
\
file
{
context
\_
nemo.xml
}
file which, is itself, included in iodef.xml. E.g.:
XML files included via the
\
texttt
{
context
\_
nemo.xml
}
file which, is itself, included in iodef.xml. E.g.:
\begin{xmllines}
iodef.xml: <context id="nemo" src="./context
_
nemo.xml"/> <!-- NEMO -->
context
_
nemo.xml: <field
_
definition src="./field
_
def
_
nemo-oce.xml"/> <!-- NEMO ocean dynamics -->
...
...
@@ -646,7 +646,7 @@ For example, in \path{cfgs/ORCA2_ICE_PISCES/EXPREF/axis_def_nemo.xml}, we provid
</axis>
\end{xmllines}
\noindent
The use of this vertical zoom is done through the definition of a new grid in
\
file
{
grid
_
def
_
nemo.xml
}
:
\noindent
The use of this vertical zoom is done through the definition of a new grid in
\
texttt
{
grid
\
_
def
\
_
nemo.xml
}
:
\begin{xmllines}
<grid id="grid
_
T
_
zoom
_
300">
...
...
@@ -655,14 +655,14 @@ For example, in \path{cfgs/ORCA2_ICE_PISCES/EXPREF/axis_def_nemo.xml}, we provid
</grid>
\end{xmllines}
\noindent
and subsequent application in a field definition (e.g.
\
file
{
field
_
def
_
nemo-oce.xml
}
):
\noindent
and subsequent application in a field definition (e.g.
\
texttt
{
field
\
_
def
\
_
nemo-oce.xml
}
):
\begin{xmllines}
<field id="toce
_
e3t
_
300" field
_
ref="toce
_
e3t" unit="degree
_
C"
grid
_
ref="grid
_
T
_
zoom
_
300" detect
_
missing
_
value="true" />
\end{xmllines}
\noindent
This variable can then be added to a file
_
definition for actual output.
\noindent
This variable can then be added to a file
\
_
definition for actual output.
%% =================================================================================================
\subsubsection
{
Control of the output file names
}
...
...
@@ -726,7 +726,9 @@ the following part of the name and the name\_suffix (that can be inherited) will
\end{table}
\noindent
For example,
\xmlline
|<file id="myfile
_
hzoom" name="myfile
_
@expname@
_
@startdate@
_
freq@freq@" output
_
freq="1d" >|
\begin{xmllines}
<file id="myfile
_
hzoom" name="myfile
_
@expname@
_
@startdate@
_
freq@freq@" output
_
freq="1d" >
\end{xmllines}
\noindent
with the namelist:
\begin{forlines}
...
...
@@ -749,13 +751,15 @@ By convention, these attributes are defined to ''auto'' (for string) or ''0000''
There is the list of these attributes in the previous table.
\\
\begin{table}
\begin{tabular
x}
{
\textwidth
}{
|X|X|X
|
}
\begin{tabular
}
{
|l|c|c
|
}
\hline
tag ids affected by automatic definition
of some of their attributes
&
tag ids affected by automatic definition
&
name attribute
&
attribute value
\\
of some of their attributes
&
&
\\
\hline
\hline
field
\_
definition
&
...
...
@@ -788,7 +792,7 @@ There is the list of these attributes in the previous table.
name
\_
suffix
&
\\
\hline
\end{tabular
x
}
\end{tabular}
\end{table}
%% =================================================================================================
...
...
This diff is collapsed.
Click to expand it.
doc/latex/global/coding_rules.tex
+
1
−
2
View file @
238fd979
...
...
@@ -413,8 +413,7 @@ to reduce unnecessary array dimensions. A good example are the substitutions int
\end{clines}
which are used to reduce 4-d arrays to a 3-d functional form or an invariant, 3-d array depending on other
options. Such macros should be located in files with
\texttt
{
\_
substitute.h90
}
endings to their names (
e.g.
\file
{
domzgr
\_
substitute.h90
}
).
options. Such macros should be located in files with
\texttt
{
\_
substitute.h90
}
endings to their names (e.g.
\texttt
{
domzgr
\_
substitute.h90
}
).
From 4.2, a more pervasive use of macros has been introduced in the form of DO LOOP macros. These macros
have replaced standard nested, loops over the spatial dimensions. In particular:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment