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

- Conescan working now

Browse Source 
- Removed old NETReadTillterm


SKIPPED:
	psi/libpsi.a
	psi/tasdriveo.c
This commit is contained in:
koennecke
2006-04-11 08:03:15 +00:00
parent da3dfd9d76
commit 38cfea4865
13 changed files with 230 additions and 124 deletions
Download Patch File Download Diff File Expand all files Collapse all files

77
doc/user/Conescan.html Normal file
View File

@ -0,0 +1,77 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html><head><title>Conescan.radi</title></head><body>
<h2>Conescan </h2>
<p>A conescan is a possibly useful procedure when setting up a single crystal
diffraction experiment. The first thing which needs to be done when
starting a single crystal experiment is the determination of the UB
matrix. In order to do that at least two reflections need to be
located through a search procedure. Now, consider the situation when
one reflection has been found and indexed. Then it is known that other
reflections can be found on a cone
with an opening angle determined by the lattice parameters and the
indices of the target reflection around the first (center)
reflection. The SICS conescan module allows to do just that, do a scan
around a given center reflection. The syntax is:
</p></p><dl><dt>conescan list
<dd> lists all the parameters of the conescan
<dt>conescan cell
<dd> prints the cell constants.
<dt>conescan cell a b c alpha beta gamma
<dd> sets new cell constants.
<dt>conescan center
<dd> prints the current values for the center reflection
<dt>conescan center h k l
<dd> uses h, k, l as the indices of the center
reflection. Motor positions are read from motors.
<dt>conescan center h k l stt om chi phi
<dd> defines a center position
complete with all angles.
<dt>conescan target
<dd> prints the current target for the conescan
<dt>conescan target h k l
<dd> defines the target indices for the conescan.
<dt>conescan qscale
<dd> prints the Q scale for the conescan. The conescan
module calculates the length of then scattering vector from the
lattice parameters and the indices. When the lattice constants are
only approximatly known it might be useful to vary the scattering
vector length for the conescan a little. This can be doen with the
qscale factor.
<dt>conescan qscale value
<dd> sets a new value for the qscale factor
<dt>conescan run step mode preset
<dd> starts a conescan with the nstep width
step, the couent mode mode and the preset preset.
<dt>conescan run
<dd> starts a conescan with defaults: step = .5,
mode = monitor, preset = 10000
<p></dl>This is the simple usage of the conescan. In fact cone is implemented
as a virtual motor. This means that arbitray scans can be performed on
cone as with any other motor. As with any other motor, cone can also
be driven to a cone angle.
</p></p><h3>Implementation Reference </h3>
<p>The conescan commands are just wrapper routines around the cone and
ubcalc module which actually work together to implement the
conescan. The ubcalc module, documented elsewhere, holds the cell
constants and the center reflection.
</p></p><p>The cone module does the actual cone calculation. Cone can be
configured with commands:
<dl></p><dt>cone center
<dd> prints the number of the reflection in ubcalc to use as
a center.
<dt>cone center num
<dd> sets the reflection in ubcalc to use a the center
for driving on the cone. Set to 0 to use the first reflection in
ubcalc.
<dt>cone target
<dd> prints the target reflection indices for the cone.
<dt>cone target h k l
<dd> sets the target reflection indices.
<dt>cone qscale
<dd> prints the current value of the scattering vector scale.
<dt>cone qscale val
<dd> sets a value for the scaling factor for the
scattering vector. Values should be close to 1.0;
</dl></body></html>

25
doc/user/tricsingle.htm
View File

@ -18,7 +18,7 @@ to be solved are:
<h3>Locate Reflections</h3>
<p>
If you know x-ray single crystal diffractometers you'll expect sophisticated
reflection search procedures here. Nothing is available in this field in
reflection search procedures here. Little is available in this field in
SICS. It was deemed inapropriate for neutron research. The first reflections
must be found by hand. Something which may help in this is a quick scan
facility which allows to run a motor and print counts while the motor is
@ -38,12 +38,27 @@ But it may help to locate the aproximate position of a peak.
</p>
<p>
Once a peak has been found, its position can be optimised and centered with the
<a href="optimise.htm">peak optimiser</a>.
<a href="optimise.htm">peak optimiser</a>. Dor not forget to put all
collimators in and to close all slits before optimizing. This is in
order to improve accuracy.
</p>
<p>
Once one reflection has been located, others might be located using the
<a href="Conescan.html">conescan</a> method when the lattice constants
are known. Do not forget to open all slits and to remove all
collimators for this.
</p>
<p>
If two reflections and the cell constants are known, a provisional UB
matrix may be <a href="ubcalc.htm">calculated</a> with the UBCALC
module. UBCALC can also calculate the UB matrix from three reflections
from scratch.
</p>
<P>
The next thing to do is to store the reflection and find other ones. Once a
few reflections have been found, the need to be written to disk. This can be
accomplished with the object rliste which has the following subcommands:
With a prvisional UB matrix determined it is advisable to locate and
optimise another 20 reflections in order to do UB matrix
refinement. During this time, reflections may be stored using the
rliste module:
<DL>
<DT>rliste clear
<DD> clears all entries from the list

4
doc/user/tricsman
View File

@ -48,6 +48,7 @@ Switzerland\\
%html system.htm 1
%html tricsingle.htm 1
%html optimise.htm 2
\section{External FORTRAN 77 Programs}
\subsection{INDEX}
@ -339,8 +340,9 @@ H H L
3 : 2H + L = 4n
\end{verbatim}
%html mesure.htm 2
%html Conescan.html 2
%html ubcalc.htm 2
%html mesure.htm 2
%html hklscan.htm 2
%html tricspsd.htm 1