linse/sics
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- Initial versions of AMOR and triple axis manuals

Browse Source
This commit is contained in:
cvs
2002-07-10 11:56:17 +00:00
parent 3733c77caf
commit e0c5afcf6d
16 changed files with 1851 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
doc/user/amomisc.htm Normal file
View File

@ -0,0 +1,26 @@
<HTML>
<HEAD>
<TITLE>Miscellaneous AMOR Command</TITLE>
</HEAD>
<BODY>
<H1>Miscellaneous AMOR Commands</H1>
<P>
<h2><a name="shutter">Shutter Control</a></h2>
<p>
Even the shutter can be controlled from within SICS. This is safe because
the shutter will not open if the door to the instrument is open. In Local
Beam Control (LBC) speak this status is named "Enclosure is broken". Be
careful anyway because some idiots may climb the fence..... The following
SICS commands control the shutter:
<dl>
<DT>shutter
<DD>The command shutter without arguments returns the status of the shutter.
This can be one of open, closed, Enclosure is broken.
<DT>shutter open
<DD>opens the shutter when possible.
<DT>shutter close
<DD>closes the shutter.
</dl>
</p>
</BODY>
</HTML>

112
doc/user/amomot.htm Normal file
View File

@ -0,0 +1,112 @@
<HTML>
<HEAD>
<TITLE>AMOR Motors</TITLE>
</HEAD>
<BODY>
<H1>AMOR Motors</H1>
<hr size ="7" WIDTH="75%">
<p align="center">
<STRONG>!!!!!!! WARNING !!!!!!</STRONG>
</p>
<p>
The left and right slit motors of diaphragms 1 - 5 are NOT independent
motors, but are handled through a single driver. Which motor is driven
is selected MANUALLY through a little turn switch close to the motor
controller in the orange 19" rack besides the instrument.
</p>
<p align="center">
<STRONG>!!!!!!! WARNING END !!!!!!</STRONG>
</p>
<hr size ="7" WIDTH="75%">
<P>
<h2>Physical Motors</h2>
<DL>
<DT>D1L
<DD>Diaphragm 1 left slit.
<DT>D1R
<DD>Diaphragm 1 right slit.
<DT>D1T
<DD>Diaphragm 1 top slit.
<DT>D1B
<DD>Diaphragm 1 bottom slit.
<DT>MOZ
<dd>Polarizer omega table up and down
<DT>MOM
<DD>Polarizer omega.
<DT>MTY
<DD>Polarizer y movement.
<DT>MTZ
<DD>Whole polarizer up and down
<DT>D2L
<DD>Diaphragm 2 left slit.
<DT>D2R
<DD>Diaphragm 2 right slit.
<DT>D2T
<DD>Diaphragm 2 top slit.
<DT>D2B
<DD>Diaphragm 2 bottom slit.
<DT>D3L
<DD>Diaphragm 3 left slit.
<DT>D3R
<DD>Diaphragm 3 right slit.
<DT>D3T
<DD>Diaphragm 3 top slit.
<DT>D3B
<DD>Diaphragm 3 bottom slit.
<DT>STZ
<DD>sample height
<DT>SOM
<DD>sample omega
<DT>SCH
<DD>sample chi
<DT>SOZ
<DD>sample table height
<DT>STB
<DD>magnet height
<DT>D4L
<DD>Diaphragm 4 left slit.
<DT>D4R
<DD>Diaphragm 4 right slit.
<DT>D4T
<DD>Diaphragm 4 top slit.
<DT>D4B
<DD>Diaphragm 4 bottom slit.
<DT>AOZ
<DD>Analyzer table height
<DT>AOM
<DD>Analyzer omega
<DT>ATZ
<DD>Analyzer omega height
<DT>D5L
<DD>Diaphragm 5 left slit.
<DT>D5R
<DD>Diaphragm 5 right slit.
<DT>D5T
<DD>Diaphragm 5 top slit.
<DT>D5B
<DD>Diaphragm 5 bottom slit.
<DT>COZ
<DD>Counter table height
<DT>C3Z
<DD>second single counetr height.
<DT>COM
<DD>Counter omega
<DT>COX
<DD>Counter x.
</DL>
</P>
</BODY>
</HTML>

22
doc/user/amor2t.htm
View File

@ -16,7 +16,8 @@ movement. As such this object has no real user interface except the
usual printing of the position when the name of the virtual motor is usual printing of the position when the name of the virtual motor is
typed. However, in order to do his work this virtual motor needs a lot typed. However, in order to do his work this virtual motor needs a lot
of parameters. These are described below. It is assumed that the of parameters. These are described below. It is assumed that the
virtual motors name is a2t. virtual motors name is s2t. There is another virtual motor called
aom2t which is the analyzer two theta angle.
</P> </P>
<p> <p>
@ -39,20 +40,31 @@ height of the table itself.
<DD>The base height of diaphragm 5. <DD>The base height of diaphragm 5.
<DT>interrupt <DT>interrupt
<DD> The interrupt to issue if this motor fails to operate. <DD> The interrupt to issue if this motor fails to operate.
<DT>anah
<DD>Height of the analyzer.
<DT>anad
<DD>distance analyser - sample.
<dt>anaflag
<dd>Flag if analyzer movement should be calculated or not. -1 if not,
positive if yes.
<dt>c2h
<dd>height constant for single detector 2.
<dt>aomconst
<dd>constant part of analyzer omega angle.
</dl> </dl>
The values of parameters can be inquired by typing: The values of parameters can be inquired by typing:
<pre> <pre>
a2t parname s2t parname
</pre> </pre>
and set by: and set by:
<pre> <pre>
a2t parname newval s2t parname newval
</pre> </pre>
For example: For example:
<pre> <pre>
a2t detectord s2t detectord
155. 155.
a2t detectord 300. s2t detectord 300.
</pre> </pre>
</p> </p>

110
doc/user/amorcli.htm Normal file
View File

@ -0,0 +1,110 @@
<HTML>
<HEAD>
<TITLE>The AMOR Client</TITLE>
</HEAD>
<BODY>
<H1>The AMOR Client</H1>
<P>
The AMOR Client is the dedicated SICS client program for the
reflectometer AMOR. It is a Java application which runs on all
computers for which a Java runtime better then jdk 1.1.6 is available.
</P>
<h2>Starting the AMOR Client</h2>
<p>
There are various ways to start the AMOR client. On the unix systems,
simply type <em>amor &</em> at the command prompt. For PC's and
proper Macintosh systems (proper means MacOS &gt 10) it is recommended
to install Java WebStart and start the application from:
http://lns00.psi.ch/sics/wstart. The AMOR client can be exited through
the File/Exit menu option.
</p>
<h2>Connecting to a SICS Server</h2>
<p>
Before anything useful can be done with the AMOR client, it has to be
connected to a SICS server. This can be done through the Connect menu
in the application. Normally choose AMOR in this menu and everything
will be fine. The option Custom Connect is used if the SICS server had
to be relocated to another computer (because of a hardware problem)
and the connection parameters: computer and port number have to be
given explicitly.
</p>
<h2>Using the AMOR Client</h2>
<p>After starting the AMOR client you see a menu, a row of buttons
beneath the menu and a central display area, showing AMOR's fantastic
logo. Now, the AMOR client has six different views of the
instrument. These views can be selected through the button row below
the menubar. The views are:
<dl>
<dt>AMOR logo
<DD>The fantastic AMOR logo. IMHO, AMOR got the nicest logo.
<dt>AMOR Schema
<dd>A drawing of AMORS components annotated with motor names.
<dt>Command
<dd>The main interaction window for typing commands to the
instrument. I/O with the server is displayed in the large central text
area. Commands can be typed into the text field at the bottom. Then
there is a yellow line displaying the progress of the current counting
operation. To the left of the command entry field is a little red
button labelled <em>Interrupt</em>. This button aborts any current
operation. There is a menu point corresponding to this window. This
allows to select the following functions:
<dl>
<dt>User Rights
<dd>A dialog for gaining privileges in SICS. You need to specify a
username and a password.
<dt>Open Logfile
<dd>Open a log file on the local machine running the client.
<dt>Close Logfile
<dd>Close a local logfile.
</dl>
<dt>Histogram
<dd>This window displays a histogram of the current data
available. What can be seen here depends on AMOR's mode of operation:
In single detector mode, the current scan data is displayed. In TOF
mode, the counts summed over a rectangular region of the detector
(defined in the Area Detector view) is displayed against
time-of-flight. Yoy may <em>zoom in</em> on selected regions of the
histogram by dragging a rectangle from top to bottom. You can <em>zoom
out</em> through the opposite movement. Further histogram commands
hide under the Histogram menu entry. Here you can:
<dl>
<dt>Reset
<dd>Reset the plot boundaries to show everything.
<dt>Print
<dd>print the current plot into a postscript file.
<dt>Logarithmic
<dd>Toggle the logarithmic flag which, when set, causes the counts to
be displayed on a logarithmic basis.
</dl>
<dt>Area Detector
<dd>This display only makes sence in TOF-mode, with a PSD. It shows
the data in the histogram memory projected along the time axis. In the
text area below the picture, the current x, y position and the current
value at the cursor position are displayed. Double clicking on the
display opens a dialog which allows to set things like: <em>scale,
colour mapping, logarithmic mapping and the mapping range</em>.
Dragging a rectangle in this display will pop up a dialog asking you
for a name. The rectangle selected then becomes a <em>named
region</em> which will then be summed and plotted in the Histogram
display. Named regions can be removed through the Update Control/Clear
TOF Regions menu entry.
<dt>Parameter
<dd>Shows selected instrument parameters in textual form.
</dl>
</p>
<h3>Updating the Display</h3>
<p>
In single detector mode scan data will be automatically updated. In
TOF mode, updates to either the histogram display or the area detector
display have to obtained either:
<ul>
<li>Manually by hitting the green Update button at the bottom of the
screen.
<li>or automatically at certain time intervalls configured through the
Update Control/Update Intervall and enabled by toggling the Update
Control/Automatic Update flag.
</ul>
</p>
</BODY>
</HTML>

73
doc/user/amorman Normal file
View File

@ -0,0 +1,73 @@
\documentclass[12pt,a4paper]{report}
%%\usepackage[dvips]{graphics}
%%\usepackage{epsf}
\setlength{\textheight}{24cm}
\setlength{\textwidth}{16cm}
\setlength{\headheight}{0cm}
\setlength{\headsep}{0cm}
\setlength{\topmargin}{0cm}
\setlength{\oddsidemargin}{0cm}
\setlength{\evensidemargin}{0cm}
\setlength{\hoffset}{0cm}
\setlength{\marginparwidth}{0cm}
\begin{document}
%html -d hr " "
%html -s report
\begin{center}
\begin{huge}
AMOR--Reference Manual \\
\end{huge}
\today \\
Dr. Mark K\"onnecke \\
Labor f\"ur Neutronenstreuung\\
Paul Scherrer Institut\\
CH--5232 Villigen--PSI\\
Switzerland\\
\end{center}
\clearpage
\clearpage
\tableofcontents
\clearpage
\chapter{Introduction}
%html amor.htm 2
\section{Interaction with SICS}
%html sicsinvoc.htm 3
%html amorcli.htm 3
\chapter{General User Commands}
%html drive.htm 1
%html amomot.htm 2
%html amor2t.htm 3
%html logging.htm 2
%html logbook.htm 3
%html commandlog.htm 3
%html batch.htm 2
%html macro.htm 3
%html buffer.htm 3
%html token.htm 2
%html amomisc.htm 2
\chapter{AMOR in Single Counter Mode}
%html amorsingle.htm 2
%html topscan.htm 2
\chapter{AMOR in Time--Of--Flight Mode}
%html amortof.htm 2
%html count.htm 2
%html amorstore.htm 2
\chapter{Advanced Topics}
%html samenv.htm 2
%html histogram.htm 2
%html motor.htm 2
%html counter.htm 2
%html ctrl.htm 2
%html system.htm 2
%html config.htm 2
%html trouble.htm 2
\end{document}

21
doc/user/amorsingle.htm Normal file
View File

@ -0,0 +1,21 @@
<HTML>
<HEAD>
<TITLE>AMOR in Single Counter Mode</TITLE>
</HEAD>
<BODY>
<H1>AMOR in Single Counter Mode</H1>
<P>
In this mode the chopper is off. The first task is to adjust
diaphragms and monochromators in such a way that the neutron beam hits the
sample and afterwards finds its way into the detector. Then scans can
be peformed with the normal scan commands. Most often scans will be
performed varying two theta. Now, two theta is varied through
a complicated, coordinated movement of angles and distances at
AMOR. For this to work properly a lot of parameters have to be
entered manualy. See, the documentation for <a href="amor2t.htm">a2t</a>
for details. Scan results are stored in NeXus files. Do not forget to
set those SICS variables which need to be written to the data file as
described in the <a href="amorstore.htm">data storage</a> section.
</P>
</BODY>
</HTML>

56
doc/user/amorstore.htm Normal file
View File

@ -0,0 +1,56 @@
<HTML>
<HEAD>
<TITLE>AMOR Data Storage</TITLE>
</HEAD>
<BODY>
<H1>AMOR Data Storage</H1>
<P>
Data files at AMOR are stored in NeXus format, based on HDF-5. This is
a portable binary format. For more information see the <a
href="http://lns00.psi.ch/NeXus/"> NeXus WWW-pages</a>. Data storage
happens normally without user intervention during scans or after a
count command has finished. A couple of things are noteworthy,
however:
<ul>
<li>Data Storage in TOF-mode may take several minutes due to the
amount of data to transfer. In this time the SICS server will be quite
unresponsive.
<li>Data file writing can be interrupted. This is a unique feature at
AMOR. As a consequence, a data file is NOT automaticaly created when
a measurement has been interrupted.
<li>Data file writing can be forced by typing: <em>storeamor</em>.
<li>Data files can be found in directories: /home/AMOR/data/YYYY on
the instrument computer or (after a litlle delay) at
/data/lnslib/data/AMOR/YYYY . The YYYY is a placeholder for the year
of data collection.
<li>The last data file written can be overwritten with command:
<em>killfile</em>. Managers privilege is required for this command.
</ul>
</P>
<p>
In order to have complete information in the data files a couple of
SICS variables have to be set manually. A SICS variable's value can be
interrogated by typing the name of the variable, and set by typing the
name of the variable followed by the new value. The following
variables are relevant:
<dl>
<dt>chopperrotation
<dd>Chopper Rotation speed.
<dt>user
<dd>User name
<dt>email
<dd>User e-mail address.
<dt>fax
<dd>User fax number
<dt>phone
<dd>User phone number
<dt>adress
<dd>User address.
<dt>sample
<dd>Sample name.
<dt>title
<dd>Measurement title
</dl>
</p>
</BODY>
</HTML>

80
doc/user/amortof.htm Normal file
View File

@ -0,0 +1,80 @@
<HTML>
<HEAD>
<TITLE>AMOR in TOF Mode</TITLE>
</HEAD>
<BODY>
<H1>AMOR in Time Of Flight Mode</H1>
<P>
AMOR can be operated in time of flight mode with a large position
sensitive detector. Measuring in this mode involves:
<ul>
<li>Aligning the instrument.
<li>Configuring the histogram memory.
<li>Configuring the chopper.
<li>count for some time.
</ul>
</P>
<h2><a name="conf">Configuring the Histogram Memory</a></h2>
<p>
In order to use the histogram memory, it has to be configured. Two
things have to be taken care of:
<ul>
<li>Configuring the resolution.
<li>Configuring the time binning.
</ul>
See also the general <a href="histogram.htm"> histogram memory</a>
section.
</p>
<p>
The resolution of the PSD in pixels can be tailored to the experiment
at hand. To this purpose the command psdconfigure is available:
<dl>
<dt>psdconfigure hm <var>xsize ysize</var>
<DD>xsize and ysize are the resolution of the detector in x
direction (beam width) and y direction (two theta).
</dl>
Usually this should already have been set up for you.
</p>
<p>
Configuring the time binning is a two step process:
<ul>
<li>Generate the time binning in SICS with the command:
<dl>
<dt>hm genbin <var>start step nBins</var>
<DD>This generates an equidistant time binning starting at time start,
with stepwidth step and nBins time bins.
</dl>
<li>Configure the histogram memory to use the new time binning with:
<ul>
<li>hm init
</ul>
</ul>
Please note, that non equidistant time binnings are possible as
well. See the main <a href="histogram.htm">histogram memory</a>
documentation for details.
</p>
<h2><a name="chop">Configuring the Chopper</a></h2>
<p>
The most important thing about the chopper, its rotation speed, can
not be controlled from the instrument control system. It has to be
adjusted <strong>MANUALLY</strong> at the chopper control PC at the
hall floor. There are two other parameters, however, which are needed
by the detector electronics in order to process the chopper
synchronisation signal properly. The commands are:
<dl>
<dt>aw
<dd>Read the current value of the acceptance window.
<dt>aw <var>val</var>
<DD>Set the acceptance window to val.
<dt>td
<dd>Read the current value of the time to delay to start.
<dt>td <var>val</var>
<dd>Set the time delay to start to val.
</dl>
</p>
</BODY>
</HTML>

26
doc/user/histogram.htm
View File

@ -85,6 +85,32 @@ for its number type.
cope with the different notions of dimensions in the SINQ histogram memory cope with the different notions of dimensions in the SINQ histogram memory
and physics. and physics.
</DL> </DL>
</p>
<p>
In addition to these common options there exist additional options for
the EMBL position sensitive detectors (PSD) installed at TRICS and
AMOR. These PSDs can be operated at different pixel resolutions. The
position of a neutron event on these detectors is encoded in a delay
time value which is digitized into a range between 0 to 4096. This
resolution exceeds the resolution available from instrument physics by
far. Useful resolutions are obtained by dividing this raw range by a
factor. In addition, the coordinates of the center of the detector
have to given as well (usually size/2).This is done through the
configuration options:
<dl>
<dt>xFac
<DD>x direction division factor
<dt>yFac
<dd>y direction division factor
<dt>xOff
<dd>Offset of the detector center in x.
<dt>yOff
<dd>Offset of the detector center in y.
</dl>
Do not forget to change the standard options dim0, dim1 and length as
well when changing the PSD resolution.
</p>
<p>
For time of flight mode the time binnings can be retrieved and modified with For time of flight mode the time binnings can be retrieved and modified with
the following commands. Note that these commands do not follow the configure the following commands. Note that these commands do not follow the configure
syntax given above. Please note, that the usage of the commands for syntax given above. Please note, that the usage of the commands for

13
doc/user/sicsinvoc.htm
View File

@ -24,7 +24,7 @@ these SICS client programs. SICS Clients and the SICServer communicate
with each other through the TCP/IP network. with each other through the TCP/IP network.
</p> </p>
<p> <p>
Currently five SICS clients are available: Currently these SICS clients are available:
<uL> <uL>
<li> A command line control client for sending commands to the SICS <li> A command line control client for sending commands to the SICS
server and displaying its repsonses. server and displaying its repsonses.
@ -32,7 +32,8 @@ server and displaying its repsonses.
<li> A status display for TOPSI. <li> A status display for TOPSI.
<li> A status display for SANS. <li> A status display for SANS.
<li> A status display for FOCUS. <li> A status display for FOCUS.
<li> A status display for AMOR. <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 <li> A SICS variable watcher. This application graphically logs the
change of a SICS variable over time. Useful for monitoring for change of a SICS variable over time. Useful for monitoring for
instance temperature controllers. instance temperature controllers.
@ -64,8 +65,10 @@ following commands at the command prompt:
<DD> for the SANS status display. <DD> for the SANS status display.
<DT>focustatus <DT>focustatus
<DD> for the FOCUS status display. <DD> for the FOCUS status display.
<DT>amor <DT>amor &
<DD> for the AMOR status display and control application. <DD> for the AMOR status display and control application.
<DT>tas &
<DD> for the triple axis status display and control application.
<DT>varwatch & <DT>varwatch &
<DD> for the variable watcher. <DD> for the variable watcher.
</dl> </dl>
@ -95,7 +98,7 @@ went wrong. You can check for the presence of the SICS server by loging in
to the instrument computer and typing <b>CheckSICS</b> at the command to the instrument computer and typing <b>CheckSICS</b> at the command
prompt. The output will tell you what is happening. If you need to restart 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 the SICS server log in as the instrument user at the instrument computer and
invoke the apropriate command to start the server. These are: invoke the appropriate command to start the server. These are:
<dl> <dl>
<DT>DMC <DT>DMC
<DD>Computer = lnsa05,User = DMC <DD>Computer = lnsa05,User = DMC
@ -114,7 +117,7 @@ invoke the apropriate command to start the server. These are:
<DT>TASP <DT>TASP
<DD>Computer = lnsa12, User = TASP <DD>Computer = lnsa12, User = TASP
<DT>POLDI <DT>POLDI
<DD>Computer = pc2970, User = POLDI <DD>Computer = poldi, User = POLDI
</dl> </dl>
For starting the SICS server type <b>startsics</b>. This is a shell script For starting the SICS server type <b>startsics</b>. This is a shell script
which will starts all necessary server programs. This script works only on which will starts all necessary server programs. This script works only on

63
doc/user/sicsmad Normal file
View File

@ -0,0 +1,63 @@
\documentclass[12pt,a4paper]{report}
%%\usepackage[dvips]{graphics}
%%\usepackage{epsf}
\setlength{\textheight}{24cm}
\setlength{\textwidth}{16cm}
\setlength{\headheight}{0cm}
\setlength{\headsep}{0cm}
\setlength{\topmargin}{0cm}
\setlength{\oddsidemargin}{0cm}
\setlength{\evensidemargin}{0cm}
\setlength{\hoffset}{0cm}
\setlength{\marginparwidth}{0cm}
\begin{document}
%html -d hr " "
%html -s report
\begin{center}
\begin{huge}
SICS--MAD--Reference Manual \\
\end{huge}
\today \\
Dr. Mark K\"onnecke \\
Labor f\"ur Neutronenstreuung\\
Paul Scherrer Institut\\
CH--5232 Villigen--PSI\\
Switzerland\\
\end{center}
\clearpage
\clearpage
\tableofcontents
\clearpage
\chapter{Introduction}
%html sicsmad.htm 1
\chapter{Running SICS}
%html sicsinvoc.htm 2
%html tascli.htm 2
\chapter{SICS User Commands}
%html logging.htm 2
%html logbook.htm 3
%html commandlog.htm 3
%html batch.htm 2
%html macro.htm 3
%html buffer.htm 3
%html token.htm 2
%html tasstore.htm 2
%html tasmad.html 1
%html madsim.htm 1
\chapter{Advanced Topics}
%html samenv.htm 2
%html motor.htm 2
%html counter.htm 2
%html ctrl.htm 2
%html system.htm 2
%html config.htm 2
%html trouble.htm 2
\end{document}

98
doc/user/sicsmad.htm Normal file
View File

@ -0,0 +1,98 @@
<HTML>
<HEAD>
<TITLE>SICS MAD Reference Manual</TITLE>
</HEAD>
<BODY>
<!latex-off>
<H1>SICS MAD Reference Manual</H1>
<!latex-on>
<P>
Welcome to SICS-MAD! SICS-MAD is the SINQ solution for running triple
axis spectrometers. The name consists of two parts: SICS is the SINQ
Instrument Control System. MAD is mad. It is a compatability layer on
top of SICS which emulates the command set and behaviour of the
venerable MAD software from the ILL.
</P>
<p>
SICS is a client server system. This means there is a magic server
program running on the instrument computer which does all the work.
The user interacts with SICS
only with client applications which communicate with the server
through the network. Most instrument hardware (motor controllers,
counter boxes etc.) is connected to the system through RS-232 serial
connections. These RS-232 ports are connected to a terminal server
which is accessed through another server program, the SerPortServer
program, which is also running on the instrument computer.
The SICS server communicates with the terminal server and other
devices through the network.
</p>
<p>
The MAD compatibility layer is implemented in the SICS server. Most
MAD commands were mapped to their SICS equivalents through procedures
written in SICS internal scripting language. Some crucial operations,
such as driving and scanning, were implemented in C, sometimes even
using F77 routines from the ILL MAD sources for performing the triple
axis calculations.
</p>
<p>
SICS clients are small programs which implement the user interface to
the SICS server. Clients connect to the SICS server through the TCP/IP
network and display the instrument status or allow to control the
instrument. Of interest to the triple axis spectrometer user are the
dedicated TAS client, named tas, the general SICS comand line client,
sics, and the variable watcher, varwatch, which allows to plot any
SICS variable as a function of time. All clients are java applications
and can be run from any computer for which a JDK1.1 compatible Java
runtime system is available.
</p>
<!latex-off>
<h1>Running SICS</h1>
<p>
<ul>
<li><a href="sicsinvoc.htm">Logging</a> in to SICS.
<li>The <a href="tascli.htm">Triple Axis Client</a> program.
</ul>
</p>
<h1>General SICS Commands</h1>
<p>
<ul>
<li><a href="logging.htm">Logging</a> actions.
<li><a href="batch.htm">Batch</a> processing.
<li><a href="token.htm">Grabbing control</a>.
<li>Triple axis <a href="tasstore.htm">data files</a>.
</UL>
</p>
<h1>MAD Compatibility Commands</h1>
<p>
<ul>
<li><a href="tasmad.html#Terminology">Terminology and Conventions</a>
<li><a href="tasmad.html#Syntax">Syntax </a>
<li><a href="tasmad.html#Commands">Commands</a>
<li><a href="tasmad.html#Special_commands">Special commands</a>
<li><a href="tasmad.html#Standard_hints">Standard hints</a>
<li><a href="tasmad.html#Measurement_Modes">Measurements Modes</a>
<li><a href="tasmad.html#Variables">Variables</a>
</ul>
</p>
<h1><a href="madsim.htm">Simulation Mode</a></h1>
<h1>Advanced Topics</h1>
<p>
<UL>
<li>Handling <a href="samenv.htm">sample environment</a> devices in SICS.
<li><a href="motor.htm">Motor Parameters</a>.
<li>Dealing with the <a href="counter.htm">counter box</a>.
<li>Directly access a <a href="ctrl.htm">serial device.</a>
<li>SICS <a href="system.htm">system commands</a>.
<li>Configuring a <a href="config.htm">client connection</a> manually.
<li><a href="trouble.htm">Trouble</a> shooting.
</UL>
</p>
<h1>Download Manual</h1>
<ul>
<li><a href="sicsmad.ps">Postscript Format</a>,246KB
</ul>
<!latex-on>
</BODY>
</HTML>

93
doc/user/tascli.htm Normal file
View File

@ -0,0 +1,93 @@
<HTML>
<HEAD>
<TITLE>The TAS Client</TITLE>
</HEAD>
<BODY>
<H1>The TAS Client</H1>
<P>
The TAS client is the dedicated SICS client for the triple axis
spectrometers. It allows both to control the instrument and to view
its current status.
</P>
<h2>Step 1: Starting the TAS Client</h2>
<p>
On the LNS unix systems the TAS client can be started by typing:
<pre>
tas &
</pre>
at the unix command prompt. For PC's and proper Macintosh computers
(proper is MacOS > 10) the recommended way to start the TAS program is
to install Java Web Start and run it from the SICS Java Web Start
page. Further instructions and the applications can be found at:
http://lns00.psi.ch/sics/wstart .
</p>
<h2>Step 2: Connect to an Instrument</h2>
<p>
Due to the client server architecture, the client program alone is
only of very limited use. In order to become usefule, a connection to
a SICS server has to be established. The obvious way to do this is
through the menu selections in the Connect menu of the TAS
client. There are various entries for various triple axis
spectrometers and their simulation programs. With the Custom Connect
option the connection parameters, the computer running the SICS server
and the server port where the SICS server listens, can be entered
manually. This is only necessary when SICS had to be relocated due to a
hardware outage.
</p>
<h2>Step 3: Use The TAS Client</h2>
<p>
The TAS client consists of a menubar, a row of buttons beneath and a
central activity area. The central activity area can display three
different sub panels. These sub panels are selected through the
buttons underneath the menubar. The following sub panels are
available:
<ul>
<li>A Command Panel for entering commands.
<li>A Status panel displaying the current values of interesting
instrument parameters, most notably the positions of the 6 magic
triple axis motors.
<li>A Plot panel showing the data collected in the currently running
scan and some auxiliary information about the scan.
</ul>
At the very bottom of the screen is a yellow line displaying the
current status of a pending counting operation. Below that is a text
line displaying the current status of the instrument.
</p>
<h3>The Command Panel</h3>
<p>
The command panel consists mainly of a text area in which the
communication between the TAS client and the SICS server is logged. A
text entry field at the bottom serves to enter commands to the SICS
server. The little red button, labelled Interrupt, besides the text
entry field can be used to interrupt the currently running
measurement.
</p>
<p>
The Command Panel has a menu associated with it. Through this menu
logging to a file can be enabled. This log file is written locally on
the machine running the TAS client. Submenu entries are available for
opening and closing such log files. SICS has various levels of user
rights. When connecting to the SICS server you are logged in with
lowest possible privilege. In order to change your privilege, enter a
username and a password through the Command/User Rights dialog.
</p>
<h3>The Plot Panel</h3>
<p>
The Plot Panel displays the data collected in the current scan. This
display is automatically updated as soon as new data becomes available
through the progress of the scan. You may <em>zoom in</em> on details
in th plot by dragging a rectangle enclosing the interesting
region from top to bottom. You may <em>zoom out</em> by dragging a
rectangle from the bottom to the top.
</p>
<h2>Step 4: Closing the TAS Client</h2>
<p>
You can exit the TAS client through the File/Exit menu entry. You can
also disconnect from the current SICS server through the
Connect/Disconnect option and connect to another SICS server through
the menu choices provided.
</p>
</BODY>
</HTML>

1012
doc/user/tasmad.html Normal file
View File

File diff suppressed because it is too large Load Diff

54
doc/user/tasstore.htm Normal file
View File

@ -0,0 +1,54 @@
<HTML>
<HEAD>
<TITLE>TAS Data Storage</TITLE>
</HEAD>
<BODY>
<H1>TAS Data Storage</H1>
<P>
Triple axis spectrometer data is stored in ASCII files. These ASCII
files are formatted in a format compatible to the ILL's triple axis
data file format. Data files can be found in directories:
<pre>
/home/INST/data/YYYY
</pre>
on the instrument computer or in
<pre>
/data/lnslib/data/INST/data/YYYY
</pre>
on any other LNS unix system. INST is a placeholder for the instrument
name in capitals, YYYY for the year of data collection. Data files are
named according to the SINQ naming convention:
<pre>
instRRRRRYYYY.dat
</pre>
with inst being the placeholder for the instrument name in lowercase,
RRRRR the run number as a five digit number and YYYY again the year of
data collection. Example: tasp003302002.dat is data collected in run
number 330 in 2002.
</p>
<p>
The last measured data file can be discarded by typing the command:
<pre>
<em>killfile</em>
</pre>
in SICS. SICS managers privilege is required for this command.
</p>
<p>
Automatically generated log files can be found in the /home/INST/log
directory for each day. They are named according to the scheme:
<pre>
autoYYYY-MM-DD@HH-MM-SS.log
</pre>
YYYY is again the year, MM the month, DD the day, HH the hour, MM the
minute and SS the second of file creation.
</p>
</BODY>
</HTML>

3
doc/user/trouble.htm
View File

@ -111,7 +111,7 @@ mechanics or electronics people were closer to the instrument then 400 meters.
<OL> <OL>
<LI> Reboot the histogram memory. It has a tiny button labelled RST. That' s <LI> Reboot the histogram memory. It has a tiny button labelled RST. That' s
the one. Can be operated with a hairpin, a ball point pen or the like. the one. Can be operated with a hairpin, a ball point pen or the like.
<LI> Wait 5 minutes. The Macintosh may take that time to come up again. <LI> Wait 5 minutes.
<LI> Restart the SICServer. Watch for any messages about things not being <LI> Restart the SICServer. Watch for any messages about things not being
connected or configured. connected or configured.
<LI> Restart and reconnect the client programs. <LI> Restart and reconnect the client programs.
@ -206,3 +206,4 @@ will help to analyse the cause of the problem and to eventually resolve it.
</body> </body>
</html> </html>