56 lines
2.0 KiB
HTML
56 lines
2.0 KiB
HTML
<html>
|
|
<head>
|
|
<title> General SICS commands </title>
|
|
</head>
|
|
<body>
|
|
<h1>General SICS commands</h1>
|
|
<hr size=4 width="66%">
|
|
<p>
|
|
This section describes general SICS concepts and SICS commands available to all instruments.</p>
|
|
<h2>Chapter Overview</h2>
|
|
<p>
|
|
<ul>
|
|
<li> This chapter starts with an overview of some <a href="basic.htm">basic</a> SICS concepts.
|
|
<li> Than there are <a href="system.htm">system</a> commands for closing the server, requesting status information etc.
|
|
<li> The <a href="token.htm">Token command</a>is for managing control access to
|
|
the SICS server.
|
|
<li> A few commands <a href="config.htm">change</a> user rights, set output files and the like.
|
|
<li> SICS has a built in <a href="macro.htm">macro</a> facility which is accessible through a few commands.
|
|
<li> Then there is the <a href="buffer.htm">famous</a> LNS-Rünbuffer system.
|
|
<li> The new <a href="exeman.htm">batch file</a> processing system.
|
|
<li> Motors and parameters need to be <a href="drive.htm">drive</a>n.
|
|
<li> SICS has a facility to <a href=optimise.htm>optimise</a> a peak with respect to several
|
|
parameters.
|
|
</ul>
|
|
</p>
|
|
<p>
|
|
SICS has various ways (to many!) to log the I/O from and to an
|
|
instrument control server. This has devolped over time and may need a
|
|
cleanup.
|
|
<ul>
|
|
<li>There exists a server log where all I/O and internal
|
|
messages is written to automatically. As this can get quite large the
|
|
files
|
|
for this
|
|
are cyclically reused. This is log aimed at debugging problems with
|
|
the SICS server.
|
|
<li> Logging of client output to a file can be performed with the <a
|
|
href=logbook.htm>LogBook</a> command. This is a wrapper around the
|
|
config file command. This is obsolete.
|
|
<li>Then there is a <a
|
|
href="commandlog.htm">commandlog </a> which writes all I/O coming from
|
|
clients with user or manager privilege. These log files are kept under
|
|
/home/INSTRUMENT/log for each day. With this log file all important
|
|
operations on an instrument can be reconstructed. This gets written
|
|
automatically without user intervention.
|
|
</ul>
|
|
</p>
|
|
</body>
|
|
</html>
|
|
|
|
|
|
|
|
|
|
|
|
|