RotatingSymmetry180::poison_boundaries should not check for NaNs

currently poison_boundaries causes RotatingSymmetry180 checks for both the poison value and for nonfinite values in the boundary. It should probably not check for NaN in case there are grid functions that do actually contain nan values near the boundaries (right not I have a run where this is true for ML_BSSN::H where I don't care about the NaNs). RotatingSymmetry's output completely clutters stdout since it list every single nan point it find.

If one wants to check for NaN values in the constraints one can always use NaNChecker so no functionality is lost.

Also RotatingSymmetry might well see NaN values when combined with say ReflectionSymmetry if the NaNs would be overwritten by say a z-reflection symmetry afterwards (I am not sure what the order in which symmetries are applied is).

Keyword: McLachlan

Comments (5)