<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hy Kristian
<p>I'm now writing the documentation for components Source_Optimizer, Monitor_Optimizer
and Monitor_nD. Hope it will be clear and usefull.
<br>I was wondering what you think about neutron spin. I mean the fact
that you have s1 and s2 [ STATE PARAMETERS (x,y,z,vx,vy,vz,t,s1,s2,p) ]
in all components,
<br>but you do not have (sx, sy, sz) except if you really ask for it [
POLARISATION PARAMETERS (sx,sy,sz) ]. In this latter case, one usually
get huge amounts of warning from other components. This is very starnge
as s1 and s2 should contain the same information as sx sy sz, but in a
different way.
<p>What about writing a MACRO that would compute sx, sy sz from s1 and
s2, according to the component orientation, and possibly neutron direction,
and an other one that would do the reverse operation ?
<p>This would make all component beeing able to handle polarisation, and
would thus avoid warnings.
<p>Also, I just point out that writing a component that does or does not
handle polarisation with POLARISATION PARAMETERS symbol makes two way of
programming : in one hand you will use s1 s2, in the other, sx sy sz....
<p>Cheers. EF.
<pre>--
Emmanuel FARHI, <A HREF="http://www.ill.fr/tas/people/Farhi.html">http://www.ill.fr/tas/people/Farhi.html</A> \|/ ____ \|/
TAS-Group, Institut Laue-Langevin (ILL) Grenoble ~@-/ oO \-@~
Avenue J. Horowitz, BP 156, 38042 Grenoble Cedex 9,France /_( \__/ )_\
Work :Tel (33/0) 4 76 20 71 83. Fax (33/0) 4 76 48 39 06 \__U_/
La Grande Arche, Chateau d'Uriage, 38410 Saint Martin d'Uriage 04 76 59 73 94</pre>
</html>