We use 1D TVD limiter to prolongate blocks, but in 2D or 3D they can
produce negative values of positive variables in the corners. Detect
such situation and limit the derivatives until the whole interpolated
region is positive.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
Since the borders are undefined, it is better to fill them with the copy
of the last available boundary layers. Even though they will be later
updated by the boundary update, it eliminates the possibilty of
propagating NaNs inside the blocks.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
The efficiency should be large, if the adaptive mesh uses few blocks
comparing to the corresponding uniform mesh. When the number of adaptive
blocks increase, the efficiency should drop.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
The actual block prolongation has been moved from update_mesh() to a
separate one called refine_selected_blocks().
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
The actual block restriction has been moved from update_mesh() to
a separate one called derefine_selected_blocks().
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
After checking refinement flags and process neighbors, we need to check
if all siblings of blocks which were selected for derefinement, are
eligible for derefinement too, i.e. lay at the same level, and are also
selected for derefinement. After this step, we bring all siblings to the
same processor, so the derefinement can be done efficiently.
In this commit, the above step is moved from update_mesh() to
prepare_sibling_derefinement().
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
The second part of update_mesh(), in which we update neighbor refinement
flags, has been moved to a new subroutine update_neighbor_refinement().
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
The first part of update_mesh(), where we check and update the
refinement flags, has been moved to a new private subroutine
check_data_block_refinement().
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
Add subroutines to iterate over all block neighbors and check if they
reference to correct meta blocks. The neighbor consistency check is
done after initial mesh generation and each time the mesh has been
updated.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
The job restart with smaller number of processors than the number of
files didn't work well, since all metablocks of all remaining files
where set to the last process before actually reading the corresponding
data blocks. This resulted in a crash in redistribute_blocks() due to
pointer not associated.
The fix lets the meta blocks to be restored with the original process
numbers. While reading files with the indices larger than the index of
the last process, all meta blocks which corresponding data blocks are
stored in the read file, are set to the process number of the reading
process. After reading data blocks from each file, the blocks are
redistributed. However, only data blocks belonging to the active
processes are redistributed.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
In this patch we make a general subroutine iterating over all neighbors
iterate_over_neighbors() which takes as arguments a pointer to the block
which neighbors are evaluated and pointer to subroutine which should be
called with each neighbor. So far two such subroutines are used, one to
select the proper refinement flag, and another to select the neighbor
for update.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
If we take the whole domain and divide it between blocks of the size
corresponding to the current lever, the field %coords identifies the
position of the current block in the domain.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
Subroutine print_error() does not stop the execution anymore. This
should be controlled by the code.
Signed-off-by: Grzegorz Kowal <grzegorz@amuncode.org>
