vitess codes

[Geza Zsigmond]

Hello,

thank you, it would be good to have a general translation programme.
At the moment we are thinking so: to build an arbitrary external code in
the Vitess should work through a 'module' in the GUI which means simply
giving a command line for the external code containing the information
(parameters, filenames)  between 2 pipe "| " which has to be typed by
the user (this means that the user has to generate it and not the Tcl).
Then by starting, the GUI will include this command also in the entire
command and runs the programme.

The Tcl thing was made rather complicated (all compressed into the
Vitess.tcl file) but in the next future we try to make it more
accessible for the user, that is we want that the user can generate his
GUI windows for his own codes. We are working on it (mainly F.Streffer)
and then we could see how to make eventually an automatic generation of
a GUI entity if we have a code in the McStas standard.

In the command line in DOS I think that it works only(?) with one
character after "-" like -a3.567. I'm not sure. In fact, it would be
even for the Tcl irrelevant whether it is -a3.567 or -absorbtion=3.567,
because it only transforms the table  of the window into a command
sequence. If the command line runs, then everything is ok.

 So I think the most important  would be to make it possible to produce
the translation, then to compile it and then to be able to write the
corresponding command sequence between two "|" in the pipe, that is, the
user should have to be familiar with the new parameter definitions after
translation (we could give the definitions in the help-info).  So the
translation programme could be included in the package and then users
could use it for any McStas code.

At the moment it would be interesting to make some comparisons between
similar modules in McStas and Vitess, for example to compare the output
of the analysers in the two cases or others like guide, choppers, etc.
This could we do also for the SCANS ("bench marking"). So if I would
have your codes (which we also have) translated into "Vitess" I could
make such comparisons. My interest is not in eventual bugs but to
compare the different models, approaches we use. We have: source, guide,
chopper,  velocity selector, crystal monochromator/analyser,
power_sample, "sans" sample, inelastic sample, collimator, detector. It
would be good to have those McStas codes which are the most similar to
our codes.

I will also send you a zipped file containing all actual source codes of
Vitess next week.

Best regards, Geza





--
Dr. Geza Zsigmond

Hahn-Meitner-Institut Berlin          Tel: +49 (0)30 8062 3022
D-14109 Glienickerstr. 100            Fax: +49 (0)30 8062 2523
Berlin, Germany                       E-mail: zsigmond at hmi.de

http://www.hmi.de/projects/ess/vitess
http://www.hmi.de/people/zsigmond