Fix a problem found by Erik Schnetter & Thomas Radke involving

writing data to the SphericalSurface variables in a multiprocessor run.

In detail, the code writes data to the SphericalSurface variables
on each processor.  For everything except the horizon shape this
is fine.  However, the code formerly didn't broadcast the horizon shape
to all processors, so the values written to the SphericalSurface variables
were all 0 on processors other than the one that actually found that horizon.

The fix is to broadcast the horizon shape if any horizon info is
being written to the SphericalSurface variables.  (In addition to
broadcasting it whenever an excision mask is being set, which the
code already did.)


git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinAnalysis/AHFinderDirect/trunk@1392 f88db872-0e4f-0410-b76b-b9085cfa78c5

1 files changed, 3 insertions, 1 deletions

diff --git a/src/driver/find_horizons.cc b/src/driver/find_horizons.cc
index 24caa8c..24b5b7c 100644
--- a/src/driver/find_horizons.cc
+++ b/src/driver/find_horizons.cc
@@ -104,7 +104,9 @@ const int my_proc = state.my_proc;
 const int N_horizons = state.N_horizons;
 horizon_sequence& hs = *state.my_hs;
 const bool active_flag = hs.has_genuine_horizons();
-const bool broadcast_horizon_shape = state.mask_info.set_mask_for_any_horizon;
+const bool broadcast_horizon_shape
+	= state.mask_info.set_mask_for_any_horizon
+	  || state.store_info_in_SS_vars_for_any_horizon;
 
       struct cactus_grid_info&          cgi = state.cgi;
 const struct    geometry_info&           gi = state.gi;