Output parameters

[Farhi]

Hy

I have adopted a solution for the numerous output parameters I had in my
components : I put all of them into structures. Thus there is only one
symbol than contains all the data. Then, the Monitor_Optimizer uses the
same principle as your Adapt_check for getting the information :
MC_GETPAR with the optimizer name from the instrument definition. This
adds an input parameter to Monitor_Optimizer. I updated this fact in the
doc attached.

Cheers.
EF.

--
Emmanuel FARHI, http://www.ill.fr/tas/people/Farhi.html     \|/ ____ \|/
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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman2.mcstas.org/pipermail/mcstas-users/attachments/20000310/d5dfacd6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Source_Optimizer.tex
Type: application/x-tex
Size: 13979 bytes
Desc: not available
URL: <http://mailman2.mcstas.org/pipermail/mcstas-users/attachments/20000310/d5dfacd6/attachment.tex>