- Added tabledrive: table driven path for MARS

- Initial MARS development
- Upgraded Manager Manual


SKIPPED:
	psi/make_gen
	psi/psi.c
	psi/tabledrive.c
	psi/tabledrive.h
	psi/tabledrive.w
	psi/utils/SerPortServer.c

doc/manager/nxscript.htm

@@ -57,6 +57,9 @@ nexusFile. The dictionary file dictFile is used.
 <dt>nxscript create4 nexusFile dictFile
 <dd>Creates a new NeXus file based on HDF-4 with the name
 nexusFile. The dictionary file dictFile is used.
+<dt>nxscript createxml nexusFile dictFile
+<dd>Creates a new NeXus file based on XML with the name
+nexusFile. The dictionary file dictFile is used.
 <dt>nxscript reopen nexusFile dictFile
 <dd>Reopens  an existing NeXus with the name
 nexusFile for modification or appending. 
@@ -112,7 +115,7 @@ values requested make sense to the histogram memory. In the case of
 subset writing, the dimensions have to be specified in the definition
 string belonging to the alias. Nxscript sets a variable timedim in the
 dictionary though which contains the length of a time binning if
-appropriate. This is a special help for writing extra detectors at
+appropriate. This is a special feauture for writing extra detectors at
 SANS and AMOR.
 <dt>nxscript puttimebinning aliasName hmName
 <dd>Writes the time binning at histogram memory hmName to file using
@@ -132,5 +135,69 @@ attribute.
 designated by targetAlias. 
 </dl>
 </p>
+<H1>Automatic Updating of NeXus Files</H1>
+<P>
+Some instruments perform measurements for quite long counting
+times. In such cases it is advisable to save the data measured so far
+to file in order to protect against hardware or software failures. To
+this purpose an automatic file upgrade manager is provided. On
+installation the automatic update object is connected wth a counting
+device through the the callback interface. This makes sure that the
+update manager is automatically notified when counting starts or
+finishes.  
+</P>
+<h2>Prerequisites for Using the Automatic Update Manager</h2>
+<p>
+In order to use automatic updating, three programs must be
+provided. Each of these programs can be a script which uses the
+nxscript facility. It can also be a SICS command. 
+<dl>
+<dt>startScript
+<dd>This program is supposed to write the static part of the file. It
+is called once when the file is created.
+<dt>updateScript
+<dd>This program is supposed to create and update the variable data
+elements in the NeXus file. This is called frequently.
+<dt>linkScript
+<dd>This program is supposed to create the links within the NeXus
+file. This is called once after startscript and updateScript have been
+run. 
+</dl>
+</p>
+<h2>Installing Automatic Update</h2>
+<p>
+An automatic update object is installed into SICS with:
+<pre>
+updatefactory name countername
+</pre>
+name is a placeholder for the name under which SICS knows the
+automatic update object. name is available as a SICS command later on.
+ countername is a placeholder for a counter
+object (counter or HM) which triggers automatic updating of NeXus
+files. This object has to support both the countable and callback
+interfaces of SICS. Suitable SICS objects include counter and
+histogram memory objects. 
+</p>
+<h2>Configuring Automatic Update</h2>
+<p>
+The SICS command created with updatefactory (see above) supports a few
+parameters which allow for the configuration of the whole
+process. Parameters follow the normal SICS syntax. Futhermore there is
+a subcommand list, which lists all configuration
+parameters. Supported parameters are:
+<dl>
+<dt>startScript
+<dd>The program supposed to write the static part of the file. 
+<dt>updateScript
+<dd>The program supposed to create and update the variable data
+elements in the NeXus file. 
+<dt>linkScript
+<dd>This program supposed to create the links within the NeXus
+file. 
+<dt>updateintervall
+<dd>The time intervall in seconds between updates. The defualt is
+1200, eg. 20 minutes. 
+</dl>
+</p>
 </BODY>
 </HTML>