Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove the state_nghost parameter #2502

Merged
merged 2 commits into from
Jun 17, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGES.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
# 23.07

* The parameter castro.state_nghost, which allowed State_Type to have ghost
zones, has been removed. (#2502)

* The additional ghost zone in State_Type, used when radiation is enabled,
has been removed. The checkpoint version number has been updated to avoid
restarting from a checkpoint with the wrong number of ghost zones. (#2495)
Expand Down
4 changes: 1 addition & 3 deletions Docs/source/software.rst
Original file line number Diff line number Diff line change
Expand Up @@ -256,9 +256,7 @@ The current ``StateData`` names Castro carries are:
simply be advected, but we will allow rotation (in particular,
the Coriolis force) to affect them.

``State_Type`` ``MultiFab`` s have no ghost cells by default.
There is an option to force them to have ghost cells by
setting the parameter ``castro.state_nghost`` at runtime.
``State_Type`` ``MultiFab`` s have no ghost cells.

Note that the prediction of the hydrodynamic state to the interface
will require 4 ghost cells. This accommodated by creating a separate
Expand Down
4 changes: 0 additions & 4 deletions Exec/reacting_tests/reacting_bubble/inputs_2d_test
Original file line number Diff line number Diff line change
Expand Up @@ -23,10 +23,6 @@ castro.yr_ext_bc_type = 1

castro.hse_interp_temp = 1


# this is here just for test suite coverage
castro.state_nghost = 1

# WHICH PHYSICS
castro.do_hydro = 1
castro.do_react = 1
Expand Down
3 changes: 0 additions & 3 deletions Exec/reacting_tests/reacting_bubble/inputs_3d_test
Original file line number Diff line number Diff line change
Expand Up @@ -27,9 +27,6 @@ castro.fill_ambient_bc = 1
castro.ambient_fill_dir = 2
castro.ambient_outflow_vel = 1

# this is here just for test suite coverage
castro.state_nghost = 1

# WHICH PHYSICS
castro.do_hydro = 1
castro.do_react = 1
Expand Down
7 changes: 0 additions & 7 deletions Source/driver/Castro_advance_ctu.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -101,13 +101,6 @@ Castro::do_advance_ctu (Real time, Real dt)

do_new_sources(cur_time, dt);

// If the state has ghost zones, sync them up now since the hydro
// source and new-time sources only work on the valid zones.

if (S_new.nGrow() > 0) {
expand_state(S_new, cur_time, S_new.nGrow());
}

// Do the second half of the reactions for Strang, or the full burn for simplified SDC.

#ifdef REACTIONS
Expand Down
4 changes: 1 addition & 3 deletions Source/driver/Castro_setup.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -348,9 +348,7 @@ Castro::variableSetUp ()
bool state_data_extrap = false;
bool store_in_checkpoint;

int ngrow_state = state_nghost;

BL_ASSERT(ngrow_state >= 0);
int ngrow_state = 0;

store_in_checkpoint = true;
desc_lst.addDescriptor(State_Type,IndexType::TheCellType(),
Expand Down
5 changes: 0 additions & 5 deletions Source/driver/_cpp_parameters
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,6 @@ state_interp_order int 1
# 2: preserve linear combinations and prevent new extrema
lin_limit_state_interp int 0

# Number of ghost zones for state data to have. Note that
# if you are using radiation, choosing this to be zero will
# be overridden since radiation needs at least one ghost zone.
state_nghost int 0

# do we do the hyperbolic reflux at coarse-fine interfaces?
do_reflux int 1

Expand Down