- Further work towards broadcast:

  * Server broadcast module now triggered by server's clock (at interval jumps)
  * Diagnostic work. Problem arose because atomic operations (triggering and reading a timestamp) were not strictly encoded as such

(This version does NOT include any more syntax errors)

Clocks-Test-4.q

@@ -18,22 +18,32 @@ E<> P_ClientBehavior.UNICAST_OFFSET_CALCULATION
 /*
 
 */
-E<> P_ClientBehavior.FINISH_PROCEDURE and (P_ClientClock.client_clock_counter == P_ServerClock.server_clock_counter)
+E<> P_ClientBehavior.FINISH_PROCEDURE and (P_ClientClock.client_clock_counter == server_clock_counter)
 
 /*
 
 */
-E<> P_ClientClock.FINISH_CLOCKOUTOFBOUNDS
+A[] not P_ClientClock.FINISH_CLOCKOUTOFBOUNDS
 
 /*
 
 */
-A[] P_ClientBehavior.FINISH_PROCEDURE imply (P_ClientClock.client_clock_counter - P_ServerClock.server_clock_counter < P_ClientBehavior.unicast_roundtrip / 2)
+A[] P_ClientBehavior.FINISH_PROCEDURE imply (P_ClientClock.client_clock_counter - server_clock_counter < P_ClientBehavior.unicast_roundtrip / 2)
 
 /*
 
 */
-A[] P_ClientBehavior.UNICAST_FINISHED imply (P_ClientClock.client_clock_counter - P_ServerClock.server_clock_counter < P_ClientBehavior.unicast_roundtrip / 2)
+A[] P_ClientBehavior.UNICAST_FINISHED imply (P_ClientClock.client_clock_counter - server_clock_counter < P_ClientBehavior.unicast_roundtrip / 2)
+
+/*
+
+*/
+//NO_QUERY
+
+/*
+
+*/
+E<> server_interval_counter == 5
 
 /*
 
@@ -48,7 +58,7 @@ A<> P_ClientBehavior.UNICAST_RESPONSE_RECEIVED and unicast_repetitions_counter =
 /*
 
 */
-A<> P_ClientBehavior.UNICAST_RESPONSE_TIMESTAMPED and unicast_repetitions_counter == 2
+A<> P_ClientBehavior.UNICAST_RESPONSE_TIMESTAMPED & unicast_repetitions_counter == 2
 
 /*