<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
As discussed in last NIAC meeting, I have asked my colleague Manuel
Sanchez (<a class="moz-txt-link-abbreviated" href="mailto:srio@esrf.fr">srio@esrf.fr</a>) to take a look at the NeXus classes
concerning optical elements. Manuel is a physicist, a programmer and
a specialist on X-ray tracing (he is a SHADOW maintainer). He has
started to take a look and he has sent the mail below to several
colleagues from different facilities. I just forward his mail to
this private list to let you now he has started to take a look. I
will let you know if he reaches to any conclusion but from his mail
I deduce you can also ask him directly.<br>
<br>
Best regards,<br>
<br>
Armando<br>
-------------------------------------------------------------------------------<br>
<div class="moz-forward-container">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Hello, <br>
<br>
After several discussions with some of you, it seems convenient to
define a glossary of variables and terms for beamline optics to be
used in future software with applications in: <br>
<br>
- standarize input/output for optics simulations software<br>
- write GUIs<br>
- use standard data format (HDF5)<br>
- exchange input/output among different codes<br>
- synchronize our activity with people in other domains
(accelerators, data acquisition, data analysis)<br>
<br>
after looking to some existing glossaries (e.g., Nexus
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="http://download.nexusformat.org/doc/html/ClassDefinitions-Base.html#NXattenuator">http://download.nexusformat.org/doc/html/ClassDefinitions-Base.html#NXattenuator</a>
), I found that nothing is really suitable for us, so I propose to
discuss among us how to do it in a better way.<br>
<br>
As a starting point, I have created a very preliminary draft
document with a list of what I think could be a list of terms and
parameters, and how to classify them. I am sure many things are
missing, other not well adapted, etc. I volunteer to coordinate
this work and get all your comments with the aim of creating a
dictionary suitable for us. So, please send me your comments,
suggestions and ideas in any format, I'll try to merge them in a
new document. You may also reply to the whole list if wanted. <br>
<br>
Thanks a lot for your collaboration, <br>
<br>
Manuel<br>
<br>
PS: Please pass this email to other people that may be interested.
And let me know if you want to be removed from this list. <br>
<br>
<pre class="moz-signature" cols="72">--
____
Manuel Sanchez del Rio
European Synchrotron Radiation Facility
BP 220
38043 Grenoble-Cedex 9 (France)
email: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:srio@esrf.eu">srio@esrf.eu</a>
Tel +33-476 882513 Fax +33-476 882542 <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.esrf.eu">http://www.esrf.eu</a>
</pre>
<br>
<br>
</div>
<br>
</body>
</html>