From 72316fa2ce045a2cba8da8cb267f9f900a43067b Mon Sep 17 00:00:00 2001 From: Dhanya Thattil Date: Fri, 25 Nov 2022 10:09:15 +0100 Subject: [PATCH] release notes --- RELEASE.txt | 17 ----------------- 1 file changed, 17 deletions(-) diff --git a/RELEASE.txt b/RELEASE.txt index c48568037..762fb68b4 100755 --- a/RELEASE.txt +++ b/RELEASE.txt @@ -48,23 +48,6 @@ This document describes the differences between v6.1.2 and v6.1.1. Fixed some minor functions returned empty error messages when failing. - Client - ------ - - 1. [Eiger] Stop command freezes server (apparent in large detectors) - For example, if module A got a "stop" during an acquisition, - it stops to an 'Idle' state. If module B gets a "stop" before an - acquisition, it will return it is in 'Idle' state and continue - to start the next acquisition, but module B then waits for "ready - for trigger" synchronization from module A, which it will never get. - Since module B missed the asynchronous stop command, the workaround - in the client is to send another "stop" command (upto 10 retries) - till it returns Idle. - - 2. [Eiger][Jungfrau][Moench][Ctb] - A "stop" command will also check for inconsistent 'nextframenumber' - between the modules and set it to the max + 1 to ensure that they - all start with the same frame number for the next acquisition. Client ------