aboutsummaryrefslogtreecommitdiff
path: root/Docs/source/running_cpp
diff options
context:
space:
mode:
authorGravatar RevathiJambunathan <revanathan@gmail.com> 2019-05-22 21:55:41 -0700
committerGravatar RevathiJambunathan <revanathan@gmail.com> 2019-05-22 21:55:41 -0700
commit63f7eb0be04f4b14ec4ca32e743f0afb0f85fb21 (patch)
treeb36598eab92ce5472423269a08922ad3bbef8bda /Docs/source/running_cpp
parent4d775b8a252ee8df832e7f04af268c6f2b209d2f (diff)
downloadWarpX-63f7eb0be04f4b14ec4ca32e743f0afb0f85fb21.tar.gz
WarpX-63f7eb0be04f4b14ec4ca32e743f0afb0f85fb21.tar.zst
WarpX-63f7eb0be04f4b14ec4ca32e743f0afb0f85fb21.zip
Adding changes suggested in the PR-review on github
Diffstat (limited to 'Docs/source/running_cpp')
-rw-r--r--Docs/source/running_cpp/parameters.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Docs/source/running_cpp/parameters.rst b/Docs/source/running_cpp/parameters.rst
index 7d4c12ca1..c78ccf030 100644
--- a/Docs/source/running_cpp/parameters.rst
+++ b/Docs/source/running_cpp/parameters.rst
@@ -702,9 +702,9 @@ Diagnostics and output
Whether to plot the magnetic field.
* ``slice.dom_lo`` and ``slice.dom_hi`` (`2 floats in 2D`, `3 floats in 3D`; in meters similar to the units of the simulation box.)
- The extent of the slice are defined by the co-ordinates of the lower conrer (``slice.dom_lo``) and upper corner (``slice.dom_hi``). The slice could be 1D, 2D, or 3D, aligned with the co-ordinate axes and the first axis of the coordinates is x. For eg: if for a 3D simulation, an x-z slice is to be extracted at y = 0.0, then the y-value of slice.dom_lo and slice.dom_hi must be equal to 0.0
+ The extent of the slice are defined by the co-ordinates of the lower corner (``slice.dom_lo``) and upper corner (``slice.dom_hi``). The slice could be 1D, 2D, or 3D, aligned with the co-ordinate axes and the first axis of the coordinates is x. For example: if for a 3D simulation, an x-z slice is to be extracted at y = 0.0, then the y-value of slice.dom_lo and slice.dom_hi must be equal to 0.0
-* ``slice.coarsening_ratio`` (`2 integers in 2D`, `3 integers in 3D`; default `1`)
+* ``slice.coarsening_ratio`` (`2 inxampleegers in 2D`, `3 integers in 3D`; default `1`)
The coarsening ratio input must be greater than 0. Default is 1 in all directions.
In the directions that is reduced, i.e., for an x-z slice in 3D, the reduced y-dimension has a default coarsening ratio equal to 1.