Partition for coarsening in wrap parameters #283
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We add a
partition_for_coarsening
option to the wrap parameters and store ap4est_wrap_params_t
in the wrap.hollow
orcoarsen_delay
from thep4est_wrap_t
into ap4est_wrap_params_t
instance, which now is a member of the wrap.partition_for_coarsening
parameter, which is passed to the calls ofp4est_partition_ext
inp4est_wrap_partition
.initial_level
from thewrap_t
, as it is only needed for creating a p4est based on a connectivity and a wrap may also be created for an already existing p4est without providing an initial level.p4est_wrap_new_p4est_params
to create a wrap of an existing p4est based on an input parameter instance. This function is called both byp4est_wrap_new_p4est
andp4est_wrap_new_params
.Currently, the
btype
of the wrap is taken from thep4est_mesh_params_t
instance that is part of thep4est_wrap_params_t
. While this ensures consistent connect types across the different structs, the repeated calls towrap->params->mesh_params->btype
seem slightly counterintuitive, so it might make sense to add a duplicatebtype
to thewrap_params_t
.