vitess codes

Kristian Nielsen kristian.nielsen at risoe.dk
Thu Jun 15 16:00:22 CEST 2000


> Date: Wed, 14 Jun 2000 17:52:15 +0200
> From: Geza Zsigmond <zsigmond at hmi.de>

> Since you know better the McStass standard, it would be easyer for you
> to write the translation programme, I guess.  So I would like too that
> you continue with these efforts, if you can find some time for it. So
> please let us know where we can help.

I am happy to write the translation program, it will not be too much
work for me since I am intimately familiar with the McStas side of
things, as you say. However I will need some help on the VITESS side of
things.

The code I send you demonstrates the use of McStas-translated modules in
a VITESS command-line pipe. However, it will also be necessary I think
to make a translation into the VITESS graphical user interface. I tried
to look at the code, but I am not familiar with Tcl/Tk and I am unsure
about how to proceed.

More specifically, I need to know what code I should generate for a
component to make it integrate with the graphical user
interface. Perhaps if you could send me a file containing just the code
needed for the sampleinelast module in the graphical user interface, and
I could try to generate similar code for the McStas modules.

There is also the issue of how to generate the names of the module
option parameters of the translated components. I see three
possibilities:

1. V_sample_Linux -i0.01 -o0.02 -h0.03 ...
2. V_sample_Linux -radius_i=0.01 -radius_o=0.02 -h=0.03 ...
3. V_sample_Linux -a0.01 -b0.02 -c0.03 ...

Number 1 resembles the current VITESS modules the most, but it requires
human intervention to define the translation from McStas parameter names
to VITESS one-letter names. Number 2 would use the original McStas
names. Number 3 would use arbitrary VITESS-like one-letter names (ie. a,
b, c, d, ...), and so not require human intervention. I think I prefer
option 2, but it really depends on what will work best for VITESS.

Could you let me know how to proceed on the translation into the
graphical user interface and on the issue of selection option parameter
names?

I would suggest that you take a look at the list of McStas components on
http://neutron.risoe.dk/mcstas/mcdoc/components/ and see which of these
(if any) that would be of interest for you in your work on VITESS. We
could then concentrate on getting those modules translated properly
initially.

 - Kristian.

--
Kristian Nielsen        kristian.nielsen at risoe.dk
Risø National Laboratory
Condensed Matter Physics and Chemistry Department
Tel. +45 4677 5515   Fax +45 4677 4790
Encryption PGP key http://neutron.risoe.dk/kn.txt






More information about the mcstas-users mailing list