187 lines
6.0 KiB
HTML
187 lines
6.0 KiB
HTML
<html>
|
|
<head>
|
|
<title> SICS Invocation </title>
|
|
</head>
|
|
<body>
|
|
<h1>SICS Invocation</h1>
|
|
<p>
|
|
SICS means SINQ Instrument Control System.
|
|
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.
|
|
</p>
|
|
<p>
|
|
Then there are client programs which interact with the
|
|
instrument control server. These client programs implement the status
|
|
displays and a command line application which forwards commands to the
|
|
SICS server and displays its response. 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 the TCP/IP network.
|
|
</p>
|
|
<p>
|
|
Currently the following SICS clients are available:
|
|
<uL>
|
|
<li> A command line control client for sending commands to the SICS
|
|
server and displaying its repsonses.
|
|
<li> A status display for the powder diffractometers DMC and HRPT.
|
|
<li> A status display for MORPHEUS and general scans.
|
|
<li> A status display for SANS and SANS2.
|
|
<li> A status display for FOCUS.
|
|
<li> A AMOR control and status program.
|
|
<li> A triple axis control and status program.
|
|
<li> A SICS variable watcher. This application graphically logs the
|
|
change of a SICS variable over time. Useful for monitoring for
|
|
instance temperature controllers.
|
|
<li>A graphical client for TRICS.
|
|
</ul>
|
|
</p>
|
|
<p>
|
|
<h2>Steps necessary for logging in to SICS</h2>
|
|
The following actions have to be taken in order to interact with the
|
|
SICS server through a client:
|
|
<uL>
|
|
<li>Start the client application.
|
|
<li>Connect the client to a SICS server.
|
|
<li>In case of command line clients: authorize yourself as
|
|
privileged SICS user.
|
|
</uL>
|
|
</p>
|
|
<h2>Starting SICS client applications </h2>
|
|
<p>
|
|
These programs can be started on a Linux system by issuing the
|
|
following commands at the command prompt:
|
|
<dl>
|
|
<DT>sics &
|
|
<DD> for the control client.
|
|
<DT>powderstatus &
|
|
<DD> for the DMC status display client.
|
|
<DT>topsistatus &
|
|
<DD>for the MORPHEUS status display.
|
|
<DT>sansstatus &
|
|
<DD> for the SANS status display.
|
|
<DT>focustatus
|
|
<DD> for the FOCUS status display.
|
|
<DT>amor &
|
|
<DD> for the AMOR status display and control application.
|
|
<DT>tas &
|
|
<DD> for the triple axis status display and control application.
|
|
<DT>varwatch &
|
|
<DD> for the variable watcher.
|
|
<dt>trics &
|
|
<dd>for the starting the TRICS graphical client.
|
|
</dl>
|
|
</p>
|
|
<p>
|
|
Another option to start SICS clients is the Java Webstart mechanism
|
|
which is available for most platforms. Java webstart requires both
|
|
Java and Java webstart to be installed on the computer running the
|
|
client. Then clients can be started directly from a WWW-page. The
|
|
advantage is that clients are automatically updated in this system as
|
|
soon as new version have been copied to the WWW-site. Installation
|
|
instructions for Java webstart and links to start all SICS clients
|
|
though this mechanism can be found at:
|
|
<a href="http://lns00.psi.ch/sics/wstart"> the SICS webstart</a>
|
|
page. This service is only accessible within the PSI network.
|
|
</p>
|
|
<h2>Connecting</h2>
|
|
<p>
|
|
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.
|
|
</p>
|
|
<h2>Authorization</h2>
|
|
<p>
|
|
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 Authorize
|
|
dialog. There you have to enter the apropriate username and password
|
|
kindly provided by your instrument scientist.
|
|
</p>
|
|
<h2>Restarting the Server</h2>
|
|
<p>
|
|
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 <b>monit status</b> 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 appropriate command to start the server. These are:
|
|
<dl>
|
|
<DT>DMC
|
|
<DD>Computer = dmc, User = dmc
|
|
<DT>TOPSI
|
|
<DD>Computer = morpheus, User = morpheus
|
|
<DT>SANS
|
|
<DD>Computer = sans, User = sans
|
|
<DT>SANSLI
|
|
<DD>Computer = sans2, User = sans2
|
|
<DT>TRICS
|
|
<DD>Computer = trics, User = trics
|
|
<DT>HRPT
|
|
<DD>Computer = hrpt, User = hrpt
|
|
<DT>FOCUS
|
|
<DD>Computer = focus, User = focus
|
|
<DT>AMOR
|
|
<DD>Computer = amor, User = amor
|
|
<DT>TASP
|
|
<DD>Computer = tasp, User = tasp
|
|
<DT>POLDI
|
|
<DD>Computer = poldi, User = poldi
|
|
</dl>
|
|
The SICS server process are controlled through the monit program. Usually the monit
|
|
daemon is running. If not, for instance after a reboot, it can be
|
|
started by typing <b>monit</b> at the unix prompt logged in as the
|
|
instrument user. Further monit commands:
|
|
<dl>
|
|
<dt> monit start target
|
|
<dd>start the monit surveyed process target. For the choice of targets
|
|
see below.
|
|
<dt> monit stop target
|
|
<dd>stops the monit surveyed process target. For the choice of targets
|
|
see below.
|
|
<dt> monit restart target
|
|
<dd>restart the monit surveyed process target. Possible targets are:
|
|
<dl>
|
|
<dt>sicsserver
|
|
<dd>The SICServer
|
|
<dt>SerPortServer
|
|
<dd>The serial port control program
|
|
<dt>sync
|
|
<dd>The file synchronisation program. This is responsible for coyping
|
|
data files to the common AFS area.
|
|
<dt>simserver
|
|
<dd>Only on TASP: a simulation SICS server
|
|
<dt>all
|
|
<dd>Stop all processes
|
|
</dl>
|
|
<dt>monit status
|
|
<dd>prints a status listing of everything watched by monit
|
|
<dt>monit quit
|
|
<dd>Stops monit itself
|
|
</dl>
|
|
Stopping everything thus involves two commands:
|
|
<ul>
|
|
<li> monit stop all
|
|
<li> monit quit
|
|
</ul>
|
|
Restarting after this involves:
|
|
<ul>
|
|
<li>monit
|
|
</ul>
|
|
The older command startsics and killsics are still working and operate
|
|
on the monit daemon as of now.
|
|
</p>
|
|
<p>
|
|
If all this does not help look under <a href="trouble.htm">trouble shooting
|
|
SICS</a>.
|
|
</p>
|
|
</body>
|
|
</html>
|
|
|
|
|
|
|