87 lines
3.3 KiB
Plaintext
87 lines
3.3 KiB
Plaintext
SICS Invocation
|
|
|
|
SICS is a client server system. This means there are two programs. The first
|
|
is a SICServer which does the actual instrument control work. A user rarely
|
|
needs to bother about this server program as it is meant to run all the
|
|
time. See instructions below if things go wrong. The user has only to deal
|
|
with the SICS client programs. These implement the user interface to SICS.
|
|
SICS Clients and the SICServer communicate with each other through TCP/IP
|
|
sockets.
|
|
|
|
Currently four SICS clients are available:
|
|
|
|
* A command line control client which allows to control the measurement.
|
|
* A status display for DMC.
|
|
* A status display for TOPSI.
|
|
* A status display for SANS.
|
|
|
|
These programs can be started on a DigitalUnix system by issuing the
|
|
following commands at the command prompt:
|
|
|
|
sics &
|
|
for the control client.
|
|
powderstatus &
|
|
for the DMC status display client.
|
|
topsistatus &
|
|
for the TOPSI status display.
|
|
sansstatus &
|
|
for the SANS status display.
|
|
|
|
On a PC you may find icons for starting the different prograsm on the
|
|
desktop. Each of these clients has usage instructions online which can be
|
|
displayed through the help/about menu entry.
|
|
|
|
Connecting and Logging in
|
|
|
|
After startup any SICS client is not connected to a SICS server and thus not
|
|
active. A connection is established through the connect menu of the client.
|
|
|
|
SICS is a multi user instrument control system. In order to prevent
|
|
malicious manipulations of the instrument SICS supports a hierarchy of user
|
|
rights. In order to run an experiment you need at least user level
|
|
privilege. In order to achieve this privilege you have to invoke the User
|
|
Parameter/Set Rights dialog. There you have to enter the apropriate username
|
|
and password kindly provided by your instrument scientist.
|
|
|
|
Restarting the Server
|
|
|
|
The SICS server should be running all the time. It is only down if something
|
|
went wrong. You can check for the presence of the SICS server by loging in
|
|
to the instrument computer and typing CheckSICS at the command prompt. The
|
|
output will tell you what is happening. If you need to restart the SICS
|
|
server log in as the instrument user at the instrument computer and invoke
|
|
the apropriate command to start the server. These are:
|
|
|
|
DMC
|
|
Computer = lnsa05,User = DMC, Command = DMCServer
|
|
TOPSI
|
|
Computer = lnsa03,User = TOPSI, Command = TOPSIServer
|
|
SANS
|
|
Computer = lnsa07,User = SANS, Command = SANSServer
|
|
|
|
If all this does not help look under trouble shooting SICS.
|
|
SICS News Ticker
|
|
|
|
This page contains information about the latest bug fixes, releases and
|
|
other miscellaneous information about SICS.
|
|
|
|
Juli 1998
|
|
|
|
Status OutOfMemory
|
|
Bug in status display clients fixed which caused OutOfMemory after some
|
|
time of automatic update.
|
|
topsistatus
|
|
TOPSI has got a java status client now as well. Can be invoked with
|
|
topsistatus. On the WWW also.
|
|
commandlog
|
|
On popular demand the SICS server can now write a log file which logs
|
|
all communication between clients with user or manager privilege and
|
|
the SICserver. This log is off by default. There is a new SICS command
|
|
commandlog which serves to configure this log.
|
|
8-fold counterboxes.
|
|
SICS now reads all eight monitors.
|
|
sicsinstall
|
|
There is now a shell script which automatizes updating and installing
|
|
SICS. For more information see the setup section of the SICS managers
|
|
guide.
|