#1961: Carpet treats prolongation_operator=none as prolongation_operator=sync --------------------------+------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: Carpet | Version: development version Resolution: | Keywords: --------------------------+------------------------------------------------- Description changed by rhaas:

Old description:

Currently Carpet treats a user set prolongation operator of "none" the same as "sync" (see line 2187 of SetupGH.cc in the {{{get_transport_operator}}} routine: {{{ if (CCTK_Equals(prolong_string, "none")) { // This would surprise too many people // return op_none; } else if (CCTK_Equals(prolong_string, "sync")) { return op_sync; }}} It would however sometimes be useful to actually have a prolongation operator that does nothing so that one can leave in the SYNC statements in the schedule (which cannot be made conditional) and switch a variable from being correctly computed everywhere to being correct only in the interior of the components if this variable is eg only for diagnostics and one can avoid inspecting the incorrect values at the borders.

I would thus like to introduce a new prolongation operator string "no_synchronization" that should do what "none" claimed to do and would internally actually be translated into {{{op_none}}}. Or alternative make "none" map to "op_none" again but then this may surprise people once more.

New description:

Currently Carpet treats a user set prolongation operator of "none" the same as "sync" (see line 2187 of SetupGH.cc in the {{{get_transport_operator}}} routine: {{{ if (CCTK_Equals(prolong_string, "none")) { // This would surprise too many people // return op_none; return op_sync; } else if (CCTK_Equals(prolong_string, "sync")) { return op_sync; }}} It would however sometimes be useful to actually have a prolongation operator that does nothing so that one can leave in the SYNC statements in the schedule (which cannot be made conditional) and switch a variable from being correctly computed everywhere to being correct only in the interior of the components if this variable is eg only for diagnostics and one can avoid inspecting the incorrect values at the borders.

I would thus like to introduce a new prolongation operator string "no_synchronization" that should do what "none" claimed to do and would internally actually be translated into {{{op_none}}}. Or alternative make "none" map to "op_none" again but then this may surprise people once more.

--

#1961: Carpet treats prolongation_operator=none as prolongation_operator=sync --------------------------+------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: Carpet | Version: development version Resolution: | Keywords: --------------------------+-------------------------------------------------

Comment (by eschnett):

Use {{{no_prolongation_and_no_restriction_and_no_sync_and_i_really_mean_it_so_dont_change_the_meaning_of_this_setting_just_to_appease_some_people_ever}}}.

#1961: Carpet treats prolongation_operator=none as prolongation_operator=sync --------------------------+------------------------------------------------- Reporter: rhaas | Owner: eschnett Type: enhancement | Status: new Priority: minor | Milestone: Component: Carpet | Version: development version Resolution: | Keywords: --------------------------+-------------------------------------------------

Comment (by rhaas):

Very good. Since Erik is the main author we now have a name for the new parameter and I will go ahead and implement this.