<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
Eugen,
<div class="">I filled in the poll and, of course, stated that Python was important to me. However, my personal view is that we should deprecate the Python bindings in the NAPI release, and refer people to the nexusformat package (<a href="https://pypi.python.org/pypi/nexusformat" class="">https://pypi.python.org/pypi/nexusformat</a>),
which contains the underlying API without the NeXpy GUI. This API does not have a dependency on the NAPI, since it uses h5py directly, so it doesn’t have to be installed at the same time. The old Python binding may need to be kept for legacy reasons, since
the new one doesn’t read HDF4 or XML, but such files could probably be easily converted to HDF5 if nxconvert is maintained.</div>
<div class=""><br class="">
</div>
<div class="">Ray</div>
<div class="">P.S. The DISCUS simulation package is written in F90 and was recently converted to output NeXus files, so there is still a need for it. I don’t think the DISCUS author wants to have to learn how to use HDF5 when a simple NAPI example showed all
that he needed to do.</div>
<div class=""><br class="">
</div>
<div class="">
<div>
<blockquote type="cite" class="">
<div class="">On Jun 22, 2015, at 10:11 AM, Eugen Wintersberger <<a href="mailto:eugen.wintersberger@desy.de" class="">eugen.wintersberger@desy.de</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">Hi folks, <br class="">
my last mail concerning the required build targets for the NAPI build<br class="">
seems to have started a quite interesting discussion about the NAPIs<br class="">
status. Unfortunately, none of the contributions, as interesting they<br class="">
were, really solved my problem. <br class="">
<br class="">
So I've set up a doodle poll which I would like to ask you to<br class="">
participate in. You find the poll here<br class="">
<br class="">
<a href="http://doodle.com/b7bi6nh5rggc5mw4" class="">http://doodle.com/b7bi6nh5rggc5mw4</a><br class="">
<br class="">
This will hopefully answer my questions. Let me make one remark: the<br class="">
list of selections in the poll was assembled after a quick look at the<br class="">
current source tree. I have no glue what's the current development<br class="">
status of some of the bindings. Anyhow, the poll may answer the question<br class="">
what people expect from NAPI. <br class="">
<br class="">
Concerning the status of NAPI: from my interpretation of what has been<br class="">
agreed on during the NAIC meeting in Abington, the NAPI will only be<br class="">
maintained in order to keep old programs, which are using it, running. <br class="">
However, it is not recommended to use NAPI for new projects. <br class="">
<br class="">
regards<br class="">
Eugen<br class="">
<br class="">
-- <br class="">
------------------------------------<br class="">
DI. Dr. Eugen Wintersberger <br class="">
<br class="">
FS-EC <br class="">
DESY <br class="">
Notkestrasse 85 <br class="">
D-22607 Hamburg <br class="">
Germany <br class="">
<br class="">
E-Mail: eugen.wintersberger@desy.de<br class="">
Telefon: +49-40-8998-1917 <br class="">
-----------------------------------<br class="">
_______________________________________________<br class="">
NeXus mailing list<br class="">
NeXus@nexusformat.org<br class="">
http://lists.nexusformat.org/mailman/listinfo/nexus<br class="">
</div>
</blockquote>
</div>
<br class="">
<div apple-content-edited="true" class="">-- <br class="">
Ray Osborn, Senior Scientist<br class="">
Materials Science Division<br class="">
Argonne National Laboratory<br class="">
Argonne, IL 60439, USA<br class="">
Phone: +1 (630) 252-9011<br class="">
Email: <a href="mailto:ROsborn@anl.gov" class="">ROsborn@anl.gov</a><br class="">
<br class="">
</div>
<br class="">
</div>
</body>
</html>