Skip to content

Commit

Permalink
fix typo
Browse files Browse the repository at this point in the history
  • Loading branch information
rjleveque committed May 22, 2020
1 parent a310777 commit 86497eb
Showing 1 changed file with 9 additions and 2 deletions.
11 changes: 9 additions & 2 deletions notebooks/geoclaw/MarchingFront.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@
"source": [
"The module [clawpack.geoclaw.marching_front.py](https://github.com/clawpack/geoclaw/blob/master/src/python/geoclaw/marching_front.py) defines a function `select_by_flooding` that takes as input an array `Ztopo` containing topography elevations on a rectangular grid and returns an array `pt_chosen` of the same shape with values 1 (if chosen) or 0 (if not chosen). Other inputs specify the criteria used to choose points, as described below.\n",
"\n",
"The basic idea is that chosen points satisfy certain elevation requirements along with connectivity to the coast. This was originally developed to identify points in a topography DEM where the topography value $Z$ is below MHW, but that should be initialized as dry land because they are in regions protected by dikes or levies. In this situation, the marching algorithm is used by initializing points well offshore (e.g. with $Z < -5$ meters) as *wet* and other points to *unset*. Then the front between *wet/unset* points is advanced by marking neighboring points as *dry* if $Z\\geq0$ or as *wet* if $Z<0$. This is repeated iteratively for each new front until there are no more *wet* points with *unset* neighbors. At this point any points still *unset* are entirely buffered by *dry* points and must lie behind dikes, so these are also set to *dry*. See the notebook [MarchingFront.ipynb](MarchingFront.ipynb) for more about this application.\n",
"The basic idea is that chosen points satisfy certain elevation requirements along with connectivity to the coast. This was originally developed to identify points in a topography DEM where the topography value $Z$ is below MHW, but that should be initialized as dry land because they are in regions protected by dikes or levies. In this situation, the marching algorithm is used by initializing points well offshore (e.g. with $Z < -5$ meters) as *wet* and other points to *unset*. Then the front between *wet/unset* points is advanced by marking neighboring points as *dry* if $Z\\geq0$ or as *wet* if $Z<0$. This is repeated iteratively for each new front until there are no more *wet* points with *unset* neighbors. At this point any points still *unset* are entirely buffered by *dry* points and must lie behind dikes, so these are also set to *dry*. See the notebook [ForceDry.ipynb](ForceDry.ipynb) for more about this application.\n",
"\n",
"Other applications are also described below along with some examples."
]
Expand Down Expand Up @@ -605,8 +605,15 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"The notebook [MarchingFront.ipynb](MarchingFront.ipynb) and the documentation page [Force Cells to be Dry Initially](http:https://www.clawpack.org/force_dry.html) contain more discussion of this example and shows how to create an array to provide to GeoClaw to indicate that this region should be initialized as dry in spite of being below MHW."
"The notebook [ForceDry.ipynb](ForceDry.ipynb) and the documentation page [Force Cells to be Dry Initially](http:https://www.clawpack.org/force_dry.html) contain more discussion of this example and shows how to create an array to provide to GeoClaw to indicate that this region should be initialized as dry in spite of being below MHW."
]
},
{
"cell_type": "code",
"execution_count": null,
"metadata": {},
"outputs": [],
"source": []
}
],
"metadata": {
Expand Down

0 comments on commit 86497eb

Please sign in to comment.