Add or remove an element to existing aem
object
+ Add or remove an element from an existing aem
object
Source: R/aem.R
add_element.Rd
add_element()
adds a new element to the aem
object.
add_element()
adds a new element to or from an aem
object.
remove_element()
removes an element from the aem
object based on its name or type.
All functionsadd_element() remove_element()
- Add or remove an element to existing aem
object
+ Add or remove an element from an existing aem
object
-
aem()
solve(<aem>)
plot(<element>)
plot(<aem>)
diff --git a/reference/tracelines-6.png b/reference/tracelines-6.png
index e47fd08..e3ca417 100644
Binary files a/reference/tracelines-6.png and b/reference/tracelines-6.png differ
diff --git a/reference/tracelines-7.png b/reference/tracelines-7.png
index a62a9e1..9148686 100644
Binary files a/reference/tracelines-7.png and b/reference/tracelines-7.png differ
diff --git a/reference/tracelines.html b/reference/tracelines.html
index 664e771..c661abc 100644
--- a/reference/tracelines.html
+++ b/reference/tracelines.html
@@ -61,6 +61,7 @@ Usage
R = 1,
tfunc = NULL,
tol = 0.001,
+ ncores = 0,
...
)
@@ -110,6 +111,10 @@ Argumentsncores
+integer, number of cores to use when running in parallel. Defaults to 0 (no parallel computing). See details.
+
+
- ...
@@ -168,6 +173,8 @@ Details
perturbation is added to these elevations to avoid the particle tracking algorithm to get stuck at these locations.
If the algorithm does get stuck (i.e. excessive run-times), try resetting the z0
values to elevations well inside the saturated domain.
Backward particle tracking is performed by reversing the flow field (i.e. multiplying the velocities with -1
).
+Traceline computation is embarrassingly parallel. When ncores > 0
, the parallel
package is used to set up the cluster with the requested nodes and
+the tracelines are computed using parallel::parLapplyLB()
. ncores
should not exceed the number of available cores as returned by parallel::detectCores()
.
The marker
value can be used to plot point markers at given time intervals, e.g. every 365 days (see examples).
The x and y locations of each particle at the marked times are obtained by linearly interpolating from the computed particle locations.
aem
objectaem
objectaem()
solve(<aem>)
plot(<element>)
plot(<aem>)
diff --git a/reference/tracelines-6.png b/reference/tracelines-6.png
index e47fd08..e3ca417 100644
Binary files a/reference/tracelines-6.png and b/reference/tracelines-6.png differ
diff --git a/reference/tracelines-7.png b/reference/tracelines-7.png
index a62a9e1..9148686 100644
Binary files a/reference/tracelines-7.png and b/reference/tracelines-7.png differ
diff --git a/reference/tracelines.html b/reference/tracelines.html
index 664e771..c661abc 100644
--- a/reference/tracelines.html
+++ b/reference/tracelines.html
@@ -61,6 +61,7 @@ Usage
R = 1,
tfunc = NULL,
tol = 0.001,
+ ncores = 0,
...
)
@@ -110,6 +111,10 @@ Argumentsncores
integer, number of cores to use when running in parallel. Defaults to 0 (no parallel computing). See details.
Details
perturbation is added to these elevations to avoid the particle tracking algorithm to get stuck at these locations.
If the algorithm does get stuck (i.e. excessive run-times), try resetting the z0
values to elevations well inside the saturated domain.
Backward particle tracking is performed by reversing the flow field (i.e. multiplying the velocities with -1
).
+Traceline computation is embarrassingly parallel. When ncores > 0
, the parallel
package is used to set up the cluster with the requested nodes and
+the tracelines are computed using parallel::parLapplyLB()
. ncores
should not exceed the number of available cores as returned by parallel::detectCores()
.
The marker
value can be used to plot point markers at given time intervals, e.g. every 365 days (see examples).
The x and y locations of each particle at the marked times are obtained by linearly interpolating from the computed particle locations.
-1
).ncores > 0
, the parallel
package is used to set up the cluster with the requested nodes and
+the tracelines are computed using parallel::parLapplyLB()
. ncores
should not exceed the number of available cores as returned by parallel::detectCores()
.marker
value can be used to plot point markers at given time intervals, e.g. every 365 days (see examples).
The x and y locations of each particle at the marked times are obtained by linearly interpolating from the computed particle locations.