Update 3.2 User interfaces authored by Udo Ziegler's avatar Udo Ziegler
......@@ -1742,7 +1742,7 @@ coordinates of a testpoint (`x`,`y`,`z`):
The user must return the mesh refinement level (`level`) with which the
vicinity of the given testpoint should be resolved with the limitation
\|`level`\|`_C.imr` where code paramter `_C.imr` is
\|`level`\|`_C.imr` where code paramter `_C.imr` is
the maximum allowed initial mesh refinement level specified by the user
in the parameter interface `nirvana.par` under the category
`MESH REFINEMENT`. In practice, the user defines spatial domains in
......@@ -1804,7 +1804,7 @@ situation, in the testproblem `/nirvana/testproblems/GRAVITY/problem1`.
User-specified refined domains are normally subject to subsequent
derefinement according to the standard refinement criteria. However, if
the returned refinement level is given a negative sign
(`level` < 0) it tells the calling function that the
(`level`<0) it tells the calling function that the
user-specified domain should be regarded as statically refined. This
implies that there is no subsequent derefinement of this domain during
runtime.
......@@ -1820,10 +1820,10 @@ Function arguments are the coordinates of a testpoint (`x`,`y`,`z`):
The user must return the refinement control parameter `level`
(initialized to 0) for the vicinity of the testpoint (`x`,`y`,`z`). A
return value `level` = 0 has no effect on mesh refinement. A
return value `level` = − 1 prohibits mesh refinement. A return
return value `level`=0 has no effect on mesh refinement. A
return value `level`=−1 prohibits mesh refinement. A return
value `level` > 0 forces mesh refinement up to refinement
level `level` with the limitation `level``_C.amr`
level `level` with the limitation `level``_C.amr`
where code parameter `_C.amr` is the maximum allowed mesh refinement
level specified by the user in the parameter interface `nirvana.par`
under category `MESH REFINEMENT`. Like in the `initDomainUser.c`
......
......