SICS is a client server system. This means there are at least two programs necessary to run the experiment. The first is the 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.
Then there are one to many client programs which interact with the instrument control server. These client programs implement the status displays and a command line application which allows to influence the course of the experiment. Graphical User Interfaces may be added at a later time. The user has only to deal with these SICS client programs. SICS Clients and the SICServer communicate with each other through TCP/IP sockets.
Currently five SICS clients are available:
These programs can be started on a DigitalUnix system by issuing the following commands at the command prompt:
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.
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:
If all this does not help look under trouble shooting SICS.