#613: cherry picked changes where the memory error was serendipitously detected with a configuration non even feasible to begin with and therefore not part of the test harness)

Author: ppebay

config/synthetic-blocks.yaml

@@ -14,7 +14,7 @@ work_model:
     gamma: 0.0
     delta: 0.0
     upper_bounds:
-      max_memory_usage: 45.0
+      max_memory_usage: 10.0
 
 # Specify algorithm
 algorithm:
@@ -45,7 +45,7 @@ visualization:
   y_ranks: 2
   z_ranks: 1
   object_jitter: 0.5
-  rank_qoi: homing
+  rank_qoi: max_memory_usage
   object_qoi: shared_id
   save_meshes: true
   force_continuous_object_qoi: true

src/lbaf/Execution/lbsTemperedWithUpdatesCriterion.py

@@ -84,9 +84,7 @@ def compute(self, r_src: Rank, o_src: list, r_dst: Rank, o_dst: Optional[list]=N
 
         # Sanity check
         if w_max_new != w_max_up:
-            self._logger.error(f"Discrepancy in post update works: {w_max_new} <> {w_max_up}")
-            print(w1, w3)
-            print(w2, w4)
+            self._logger.error(f"Updated work: max({w1},{w2}) <> computed: max({w3},{w4})")
             raise SystemExit(1)
 
         # Return criterion value