vitess codes

[Kristian Nielsen]

> Date: Mon, 29 May 2000 12:15:01 +0200
> From: Geza Zsigmond <zsigmond at hmi.de>

Thanks for the source code to the VITESS inelastic sample module. I have
now had the chance to take a thorough look at it. It was very useful to
see the details of how VITESS modules are implemented in order to assess
the possibility of sharing module code.

I have made good progress in terms of translating a McStas component
into a VITESS module. This seems to be feasible, and an automatic
translation should be fairly easy to do. The only thing that cannot be
automatic is to invent short option names (-a, -k, -x, etc.) to replace
the long names used by McStas; alternatively, the translated components
could use long option names (-height=x, -radius=x, etc.) if that will
work with the VITESS concept. Also, some specialized McStas components
communicate with each other, and this seems difficult to do in VITESS
where modules run in seperate programs.

I wonder if you and the other VITESS developers are interesting in
pursuing this further (the automatic translation of McStas components
into VITESS)? If so, I could work further on this, if not I will spend
my time in some other way...

For the other direction, translating VITESS modules into McStas
components, this should also be feasible. However, there seems to be no
way to do automatic translation since there is no formalized standard
for writing VITESS modules. The underlying concepts of the two programs
are sufficiently simular that manual rewriting seems to be not too
difficult, though the heavy use of global variables in VITESS modules
could make it difficult to use code from several VITESS modules in the
same program. There is also the problem that each time a VITESS module
is updated, the manual translation into a McStas component would have to
be repeated.

Just for information, I have included the code I produced so far to
translate a McStas component into a VITESS module. It consists of a
small instrument definition, two modules to convert between VITESS and
McStas unit conversions, and a file with some general VITESS/McStas
library code.

Let me know what you think of this, and whether you consider it worth it
to work further along these lines.

 - 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: V_sample-vitess.instr
Type: application/octet-stream
Size: 1305 bytes
Desc: not available
URL: <http://mailman2.mcstas.org/pipermail/mcstas-users/attachments/20000613/487bdd19/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Vitess_input.comp
Type: application/octet-stream
Size: 3021 bytes
Desc: not available
URL: <http://mailman2.mcstas.org/pipermail/mcstas-users/attachments/20000613/487bdd19/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Vitess_output.comp
Type: application/octet-stream
Size: 3013 bytes
Desc: not available
URL: <http://mailman2.mcstas.org/pipermail/mcstas-users/attachments/20000613/487bdd19/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vitess-lib.c
Type: application/octet-stream
Size: 4136 bytes
Desc: not available
URL: <http://mailman2.mcstas.org/pipermail/mcstas-users/attachments/20000613/487bdd19/attachment-0003.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vitess-lib.h
Type: application/octet-stream
Size: 1278 bytes
Desc: not available
URL: <http://mailman2.mcstas.org/pipermail/mcstas-users/attachments/20000613/487bdd19/attachment-0004.obj>
-------------- next part --------------