 |
|
|
|
|
|
|
|
|
BLU-ICE Collaboration Features
|
|
|
|
|
|
|
|
Synchronized
BLU-ICE Clients
|
|
|
All information regarding motor
positions, shutter states, run definitions, and data
|
|
collection
status remains up-to-date on all BLU-ICE clients.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
BLU-ICE
Not Critical
|
|
|
A BLU-ICE client may be closed
|
|
|
and reopened
without affecting
|
|
|
ongoing data
collection.
|
|
|
Security
|
|
|
Only users enabled by staff may
|
|
connect to the
DCSS beam line
|
|
|
server.
|
|
|
|
|
|
|
|
|
|
|
Visible
Collaborators
|
|
|
BLU-ICE displays a list of other BLU-ICE
clients, who started the client, and from what
|
|
computer and
display it was started on.
|
|
|
One
BLU-ICE in Control
|
|
|
Each BLU-ICE client has the ability to
request control of the beam line.
However, DCSS
|
|
limits the
number of controlling clients to one.
This prevents conflicting instructions
|
|
from being
issued by two different users.
|
|
|
|
|