Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
docs
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
exa
docs
Commits
b9bca4c0
Commit
b9bca4c0
authored
3 years ago
by
William D. Fullmer
Browse files
Options
Downloads
Patches
Plain Diff
add a bit of verbosity to @drangara hypre settings
parent
576a5a46
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/source/inputs/InputsHypre.rst
+12
-5
12 additions, 5 deletions
docs/source/inputs/InputsHypre.rst
docs/source/inputs/InputsMultigrid.rst
+3
-0
3 additions, 0 deletions
docs/source/inputs/InputsMultigrid.rst
with
15 additions
and
5 deletions
docs/source/inputs/InputsHypre.rst
+
12
−
5
View file @
b9bca4c0
...
...
@@ -4,13 +4,20 @@ Hypre Inputs
=============
The following inputs control the hypre settings and are read directly
by AMReX when we use hypre as the bottom solver.
by AMReX when we use hypre as the bottom solver, i.e., when
:cpp:`nodal_proj.bottom_solver = hypre` and/or when
:cpp:`mac_proj.bottom_solver = hypre` (see :ref:`Chap:InputsMultigrid`)
These settings must be preceded by the hypre_namespace setting corresponding
to the solver (see :ref:`Chap:InputsMultigrid`).
NOTE: Default uses the same hypre namespace "hypre" for all solvers. However,
the hypre namespace can be set at the solver level and the hypre settings
can be configured for each MLMG solver.
NOTE: If either the :cpp:`nodal_proj` or :cpp:`mac_proj` bottom solvers are
set to :cpp:`hypre`, the default behavior is to set the `hypre_namespace = "hypre"`.
In that case, the settings below should be preceded by the (default) hypre namespace,
:cpp:`hypre`, and apply to either or all solvers which use hypre. However,
the hypre namespace can be set at the solver level so that the hypre settings
can be configured for each MLMG solver. In which case, the settings below should be
preceded by the solver specific :cpp:`hypre_namespace`.
These settings must be preceded by the hypre_namespace setting corresponding to the solver (see :ref:`Chap:InputsMultigrid`)
+-----------------------------------+-----------------------------------------------------------------------+-------------+--------------+
| | Description | Type | Default |
...
...
This diff is collapsed.
Click to expand it.
docs/source/inputs/InputsMultigrid.rst
+
3
−
0
View file @
b9bca4c0
...
...
@@ -75,6 +75,9 @@ These control the MAC projection and must be preceded by "mac_proj":
| | Options are ij, semi_structured or structured | | |
+-------------------------+-----------------------------------------------------------------------+-------------+--------------+
NOTE: If the :cpp:`nodal_proj` and :cpp:`mac_proj` :cpp:`hypre_namespace`'s are set, they must be distinct unless set to
:cpp:`hypre`, in which case the default behavior is recovered in which case hypre settings apply to all solvers.
These control the diffusion solver and must be preceded by "diffusion":
+-------------------------+-----------------------------------------------------------------------+-------------+--------------+
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment