- New batch file management module
- New oscillator module - Bug fixes SKIPPED: psi/buffer.c psi/el734hp.c psi/el737hpdriv.c psi/make_gen psi/nextrics.c psi/nxamor.c psi/pimotor.c psi/polterwrite.c psi/psi.c psi/swmotor2.c psi/tasscan.c psi/tricssupport.c psi/tricssupport.h psi/tecs/make_gen psi/utils/ecb_load_new/ecb_load.c psi/utils/ecb_load_new/ecb_load.h psi/utils/ecb_load_new/ecbdriv_els.c psi/utils/ecb_load_new/gpib_els.c psi/utils/ecb_load_new/makefile psi/utils/ecb_load_new/makefile_EGPIB psi/utils/ecb_load_new/makefile_GPIB
This commit is contained in:
59
doc/user/exeman.html
Normal file
59
doc/user/exeman.html
Normal file
@ -0,0 +1,59 @@
|
||||
<HTML>
|
||||
<HEAD>
|
||||
<TITLE>The Batch Buffer Manager</TITLE>
|
||||
</HEAD>
|
||||
<BODY>
|
||||
<H1>The Batch Buffer Manager</H1>
|
||||
<P>
|
||||
The batch buffer manager handles the execution of batch files. It can
|
||||
execute batch files directly. Additionally, batch files can be added
|
||||
into a queue for later processing. The batch buffer manager supports
|
||||
the following command described below. Please note, that the examples
|
||||
assume that the batch manager has been configured into SICS under the
|
||||
name of exe.
|
||||
<dl>
|
||||
<dt>exe buffername
|
||||
<dd>directly load the buffer stored in the file buffername and execute
|
||||
it. The file is searched in the batch buffer search path.
|
||||
<dt>exe batchpath [newpath]
|
||||
<dd>Without an argument, this command lists the directories which are
|
||||
searched for batch files. With an argument, a new search path is
|
||||
set. It is possible to specify multiple directories by separating them
|
||||
with colons.
|
||||
<dt>exe syspath [newpath]
|
||||
<dd>Without an argument, this command lists the system directories which are
|
||||
searched for batch files. With an argument, a new system search path is
|
||||
set. It is possible to specify multiple directories by separating them
|
||||
with colons.
|
||||
<dt>exe info
|
||||
<dd>prints the name of the currently executing batch buffer
|
||||
<dt>exe info stack
|
||||
<dd>prints the stack of nested batch files (i.e. batch files calling
|
||||
each other).
|
||||
<dt>exe info range [name]
|
||||
<dd>Without an argument prints the range of code currently being
|
||||
executed. With a parameter, prints the range of code executing in
|
||||
named buffer within the stack of nested buffers. The reply looks like:
|
||||
number of start character = number of end character = line number.
|
||||
<dt>exe info text [name]
|
||||
<dd>Without an argument prints the code text currently being
|
||||
executed. With a parameter, prints the range of code text executing in the
|
||||
named buffer within the stack of nested buffers.
|
||||
<dt>exe enqueue buffername
|
||||
<dd>Appends buffername to the queue of batch buffers to execute.
|
||||
<dt>exe clear
|
||||
<dt>Clears the queue of batch buffers
|
||||
<dt>exe queue
|
||||
<dd>Prints the content of the batch buffer queue.
|
||||
<dt>exe run
|
||||
<dd>Starts executing the batch buffers in the queue.
|
||||
<dt>exe print buffername
|
||||
<dd>Prints the content of the batch buffer buffername to the screen.
|
||||
<dt>exe interest
|
||||
<dd>Switches on automatic notification about starting batch files,
|
||||
executing a new bit of code or for finishing a batch file. This is
|
||||
most useful for SICS clients watching the progress of the experiment.
|
||||
</dl>
|
||||
</P>
|
||||
</BODY>
|
||||
</HTML>
|
@ -14,23 +14,7 @@ to be solved are:
|
||||
<li>Measure a couple of reflections.
|
||||
<li>Furthermore there are some specialities.
|
||||
</ul>
|
||||
There are two ways to achieve all this:
|
||||
The older way uses some built in SICS functionality plus some external
|
||||
programs inherited from the ILL. This is called the ILL operation.
|
||||
Then a complete
|
||||
four circle package called DIFRAC from P. White and Eric Gabe was
|
||||
integrated into SICS.
|
||||
This is The Difrac way of operation.
|
||||
</p>
|
||||
<h2>DIFRAC</h2>
|
||||
<p>
|
||||
The DIFRAC commands are accessed by prepending the difrac commands
|
||||
with <b>dif</b>. For example: "dif td" calls the difrac td
|
||||
command. For more information on DIFRAC commands see the separate
|
||||
<a href="diftrics.htm">DIFRAC manual</a>.
|
||||
</p>
|
||||
|
||||
<h2>ILL operation</h2>
|
||||
<h3>Locate Reflections</h3>
|
||||
<p>
|
||||
If you know x-ray single crystal diffractometers you'll expect sophisticated
|
||||
|
@ -26,7 +26,23 @@ Two special commands have been defined for TRICS with a PSD:
|
||||
<dd>reads reflection HKL values from file filename and performs
|
||||
tricsscans for each reflection. These will be done eith step width
|
||||
step, the number of steps np with counting mode mode and a preset of
|
||||
preset. These parameters have the same meaning as described above.
|
||||
preset. These parameters have the same meaning as described above. If the
|
||||
{\bf hkl nb 1} command has been given before the invocation of this scan,
|
||||
reflections will be searched in normal beam geometry. psdrefscan, however,
|
||||
will only print the normal four circle angles, though.
|
||||
<dt>detscan start step np mode preset
|
||||
<dd>Detscan performs a scan in two theta. This may be useful for detector
|
||||
calibrations. Arguments as described above.
|
||||
<dt>phscan start step np mode preset
|
||||
<dd>Phscan performs a scan in phi. This can be usefule for orienting a
|
||||
crystal. Arguments as described above.
|
||||
<dt>o2tscan2d start step np mode preset
|
||||
<dd>O2tscan2d performs a omega - two-theta scan with the PSD.
|
||||
Arguments as described above.
|
||||
<dt>hklscan2d
|
||||
<dd> For a scan in reciprocal space with the PSD, see the
|
||||
documentation for <a href="hklscan.htm">hklscan</a>. Please note that
|
||||
for a PSD HKL scan, all commans have to start with hklscan2d.
|
||||
</dl>
|
||||
</P>
|
||||
|
||||
|
Reference in New Issue
Block a user