90 lines
4.0 KiB
HTML
90 lines
4.0 KiB
HTML
<HTML>
|
|
<HEAD>
|
|
<TITLE>General SICS Setup</TITLE>
|
|
</HEAD>
|
|
<BODY>
|
|
<H1>General SICS Setup</H1>
|
|
<P>
|
|
SICS is a client server system. This implies that there is a server program
|
|
which implements all the functionlity and client programs which implement
|
|
the user interface. The client program is the only thing the user is
|
|
intended to see. This also means that the location of the client programs is
|
|
quite independent from the computer where the server runs. In the following
|
|
the layout of a server installation is described as established at SINQ.
|
|
</P>
|
|
<p>
|
|
For each instrument there is a data aquisition computer. On this computer
|
|
there exists a user name and consequently a home directory for the
|
|
instrument. In the following text this instrument root directory will be called
|
|
sicsroot. This root directory has the following subdirectories:
|
|
<DL>
|
|
<DT>bin
|
|
<DD> The bin directory is the place where the actual executable for the SICS
|
|
server is kept along with local copies of all necessary clients, the server
|
|
initialisation files and special macro files defined for the instrument.
|
|
<DT>data
|
|
<DD>The data directory is the central place where all data files collected
|
|
at the instrument are stored. Additionally this directory holds a file named
|
|
DataNumber which keeps the current serial number of the data files. This
|
|
file should never be edited. However, on the first of january an instrument
|
|
manager should reset the serial number in this file to 0.
|
|
<DT>log
|
|
<DD> The log directory contains the server log files and the automatically
|
|
generated client log files. Any now and then, and especially when disk space
|
|
problems loom, the client*.log files should be deleted by the instrument
|
|
manager.
|
|
<DT> doc
|
|
<DD> This directory holds a copy of the SICS user documentation for the
|
|
instrument. These are html files which can be viewed with WWW-browsers such
|
|
as lynx or netscape.
|
|
<DT> sim
|
|
<DD> The sim directory is meant to hold all files necessary for a SICServer
|
|
initialised for the instrument but configured with simulated hardware. This
|
|
facility is meant for testing of command files.
|
|
</DL>
|
|
Besides these directories there should be nothing on the instrument account.
|
|
All evaluated data, personal command files etc. should be held on the normal
|
|
user account of the instrument user.
|
|
</p>
|
|
<p>
|
|
For this purpose the /data/lnslib/bin directory holds copies of the
|
|
apropriate command line and status display clients for each instrument. A user can make
|
|
this directory (and much more) available by including the line <b>
|
|
source /data/lnslib/bin/lns.login</b> into her .login file.
|
|
</p>
|
|
<h2> SICS Installation</h2>
|
|
<p>
|
|
All executables and files necessary to run SICS for each instrument is
|
|
avaialable under the /data/lnslib/src/sics hierarchy. The bin directory
|
|
holds general executable files and a directory for each instrument which
|
|
holds instrument specific files. SICS installation on a unix system is
|
|
greatly simplified by using the <b>sicsinstall</b> korn shell script. This
|
|
script is available to each user. sicsinstall can be invoked simply by
|
|
typing sicsinstall at the command prompt. sicsinstall needs a subcommand in
|
|
order to know what it is expected to do:
|
|
<dl>
|
|
<DT>dev
|
|
<DD>copies knew executables from the development area to the distribution
|
|
directory. This command is meant to be used by computing staff only.
|
|
<DT>devfull
|
|
<DD>as dev, but copies all files. This command is meant to be used by computing staff only.
|
|
<DT>dmc
|
|
<DD>copies all files necessary for the instrument DMC.
|
|
<DT>topsi
|
|
<DD>copies all files necessary for the instrument TOPSI.
|
|
<DT>sans
|
|
<DD>copies all files necessary for the instrument SANS.
|
|
<DT>doc
|
|
<DD>updates only the documentation on your disk.
|
|
<DT>exe
|
|
<DD>copies only new executable files from the distribution area. This is the
|
|
recommended option when you want to be sure, that you have the latest
|
|
version of SICS before reporting a bug.
|
|
</dl>
|
|
Most of these options require you to be in the home directory of the
|
|
instrument account. sicsinstall checks for this and warns you if this is not
|
|
the case. Directory structures are checked for and created as needed.
|
|
</p>
|
|
</BODY>
|
|
</HTML>
|