forked from erf-model/ERF
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
WIP merging and fixing merge errors from recent commits from developm…
…ent.
- Loading branch information
Showing
289 changed files
with
11,561 additions
and
11,085 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
# 23.10 | ||
|
||
-- First release since JOSS paper. Too many key ERF PRs to summarize. | ||
|
||
-- AMReX submodule set to 23.10 release hash (388738d) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
|
||
.. role:: cpp(code) | ||
:language: c++ | ||
|
||
.. _Particles: | ||
|
||
Particles | ||
========= | ||
|
||
ERF has the option to include Lagrangian particles in addition to the mesh-based solution. Currently the | ||
particle functionality is very simple -- the particles are initialized one per mesh cell | ||
in a particular plane, and are advected by the velocity field. | ||
|
||
However, the AMReX particle data structure is very general and particles may take on a number of | ||
different roles in future. | ||
|
||
To enable the use of particles, one must set | ||
|
||
:: | ||
|
||
USE_PARTICLES = TRUE | ||
|
||
in the GNUmakefile if using gmake, or add | ||
|
||
:: | ||
|
||
-DERF_ENABLE_PARTICLES:BOOL=ON \ | ||
|
||
to the cmake command if using cmake. (See, e.g., ``Build/cmake_with_particles.sh``) | ||
|
||
One must also set | ||
|
||
:: | ||
|
||
erf.use_tracer_particles = true | ||
|
||
in the inputs file or on the command line at runtime. | ||
|
||
Currently, by default, the particles are initialized at cell centers, one per cell when the cell index is | ||
(3,j,k), with zero initial velocity. They are advanced in time every time step. | ||
|
||
Caveat: the particle information is currently output when using the AMReX-native plotfile format, but not | ||
when using netcdf. Writing particles into the netcdf files is a WIP. | ||
|
||
To see an example of using the particle functionality, build the executable using gmake in Exec/DevTests/ParticlesOverWoA. | ||
|
||
To visualize the number of particles per cell as a mesh-based variable, add ``particle_count`` to the line in the inputs file | ||
|
||
:: | ||
|
||
erf.plot_vars_1 = | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
.. _Submodule: | ||
|
||
Git Submodules | ||
-------------- | ||
|
||
When using the submodule to build, it is ideal to properly update and match what is in the repository. Depending on Git version, different commands and options to ensure these match. An example workflow is to run ``git pull`` to get the latest commit on your current branch, and then run ``git submodule update`` to explicitly update the submodule. This should work for all versions of ``git`` which support submodules. | ||
|
||
The following example demonstrates a shorter form that combines both commands and requires Git 2.14 or newer: | ||
|
||
.. code:: shell | ||
# Replaces your git pull to use both the updated code and the updated submodule | ||
git pull --recurse-submodules | ||
The following example demonstrates setting defaults in the config file for the repository and requires Git 2.15 or newer: | ||
|
||
.. code:: shell | ||
# Set this once | ||
git config submodule.recurse true | ||
# When configured as true, this will use both the updated code and the updated submodule | ||
git pull | ||
# This option will override any configuration and not update the submodule | ||
git pull --no-recurse-submodules | ||
These example also apply to ``git checkout``. For more details see _`Git Tools Submodules`: https://git-scm.com/book/en/v2/Git-Tools-Submodules |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.