mirror of
https://github.com/slsdetectorgroup/slsDetectorPackage.git
synced 2025-07-10 18:01:52 +02:00
release notes
This commit is contained in:
17
RELEASE.txt
17
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.
|
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
|
Client
|
||||||
------
|
------
|
||||||
|
Reference in New Issue
Block a user