<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi All,</p>
<p><br>
</p>
<p>I have followed this discussion with interest and would like to
say I agree with all the replies of being cautious about adding
more file formats to be officially supported by Nexus. It would be
a classic case of throwing the baby out with the bathwater! In
this case HDF5 is the baby and the bathwater is the infrastructure
(file system, network, etc.). Nexus/HDF5 can be seen as the
reference implementation which is the official (i.e. validated)
implementation of Nexus. Other implementations (e.g. based on zarr
etc.) are alternatives which could be shared as contributions
derived from the reference implementation.<br>
</p>
<p><br>
</p>
<p>Gabriel, I understand the need to have very high performance or
different file formats but these should be supported locally and
mapped to Nexus definitions if necessary as a local exercise. For
example we have done this at the ESRF for the ICAT database
mapping Nexus definitions to ICAT parameters. We also support
other file formats when we have to e.g. jpeg2000. The community is
there to share such developments. I would not however burden the
Nexus committee with having to officially support other file
formats and I would definitely not develop our own API which is
challenging in its own right but also a long term maintenance
issue. The current version of Nexus relies strongly on HDF5 so
moving to another format would be difficult, it would also create
confusion for users who are in the process of moving to Nexus/HDF5
if we say to them now to adopt another file format - it is
challenging enough to change their codes to read Nexus/HDF5. Most
of our problems can still be solved with HDF5 so the best is to
ask others how they solved the same problem to see if they have
been solved already.</p>
<p><br>
</p>
<p>I recommend you (and all European HDF5 users) to attend the next
HDF User Group workshop in Europe
(<a class="moz-txt-link-freetext" href="https://www.hdfgroup.org/hug/europeanhug22/">https://www.hdfgroup.org/hug/europeanhug22/</a>) which will take
place not far away from ALBA in the south of France. This is an
opportunity to discuss with the HDF5 developers and other users on
your problems and how to solve them.</p>
<p><br>
</p>
<p>Kind regards</p>
<p><br>
</p>
<p>Andy</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 12/04/2022 12:50, Watts Benjamin
(PSI) via NeXus wrote:<br>
</div>
<blockquote type="cite"
cite="mid:4f1baeac49544f80afcd105e025e2ecc@psi.ch">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;">P {margin-top:0;margin-bottom:0;}</style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
dir="ltr">
<div id="divtagdefaultwrapper" dir="ltr" style="font-size: 12pt;
color: rgb(0, 0, 0); font-family: Calibri, Helvetica,
sans-serif, "EmojiFont", "Apple Color
Emoji", "Segoe UI Emoji", NotoColorEmoji,
"Segoe UI Symbol", "Android Emoji",
EmojiSymbols;">
<p>Hi Everyone,</p>
<p> My understanding is that the core NeXus mission has only
concerned the organisation of the data. The container file
format was only within our scope for the practical reasons
of demonstrating how to implement the NeXus structures. We
recommended HDF5 because we did not see viable alternatives
for a long time. <br>
</p>
<p><br>
</p>
<p>I think that there are both practical and ideological
aspects to the discussion about file formats for NeXus and
it is a bit confronting for some of us because we see
conflict between these aspects. On the one hand, we should
encourage people using file formats other than HDF5 and XML
to organise their data using NeXus. On the other hand, we
don't want to encourage a "wild west" in file formats where
reading archived files becomes a hunt for obscure libraries.
On this point - what is the role that NeXus should play?
Certainly, NeXus should only promote file formats that are
capable of expressing the NeXus hierarchies. NeXus should
also document how the data hierarchies are expressed in each
file format (I think we can do this in a more formal way
than we currently do). If NeXus is to do any discrimination
between file formates, I would like for us to come up with a
set of criteria for file formats to meet in order to gain
NeXus approval. NeXus does not currently have the resources
to support further file formats in the NeXus libraries
(NAPI) and perhaps community support could be one of the
criteria for approval.<br>
</p>
<p><br>
</p>
<p>Cheers,</p>
<p>Ben<br>
</p>
<p><br>
</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
Osborn, Raymond <a class="moz-txt-link-rfc2396E" href="mailto:rosborn@anl.gov"><rosborn@anl.gov></a><br>
<b>Sent:</b> Thursday, 7 April 2022 9:42:50 PM<br>
<b>To:</b> Discussion forum for the NeXus data format<br>
<b>Cc:</b> Tobias Richter; <a class="moz-txt-link-abbreviated" href="mailto:nexus@nexusformat.org">nexus@nexusformat.org</a>; Watts
Benjamin (PSI); Alexander Debus; Nicolas Soler; Franz
Pöschel; Emilio Centeno Ortiz<br>
<b>Subject:</b> Re: [Nexus] HDF5 as NeXus file format</font>
<div> </div>
</div>
<div>Hi everyone,
<div class="">NeXus was originally both a standard for
defining how data should be organized in files and a unified
API for reading and writing those files, irrespective of the
physical file format, HDF4, HDF5, or XML. Thanks mainly to
the work that Mark Koennecke put into the C-API, it achieved
both goals seamlessly. I think it was a remarkable technical
achievement. To some extent, the two components were
independent of each other, but not entirely. For example,
HDF4 did not allow group attributes, so for a long time,
they were not part of the definitions. Now that HDF4 is
obsolete, the NeXus definitions have evolved to use more and
more of the features that HDF5 provides, many of which have
become an essential part of the standard. </div>
<div class=""><br class="">
</div>
<div class="">I think there are therefore two questions that
need to be clarified, preferably before we next meet. The
first is whether the proposed alternative physical file
formats will allow the same type of hierarchical data
organization and features that have now become part of the
standard. If they didn’t, this would probably be a
deal-breaker, unless there is a way of interfacing, say,
regular HDF5 NeXus files to the new file formats, in much
the same way that HDF5 handles external links. </div>
<div class=""><br class="">
</div>
<div class="">The second is whether there is a need to revive
the API to handle the new formats, so that we are not faced
with the situation that Tobias warned about with a large
fraction of the user community unable to read such files.
The reason the API became deprecated is, in my view, that we
have depended too much on one or two people (i.e., Mark in
the case of the C-API) to take all the responsibility for
maintaining it, so that supporting new HDF5 features, such
as virtual data sets or even variable-length-strings, fell
entirely on them. While an increasing number of facilities
have become dependent on NeXus, very few of them, if any,
have committed resources to maintaining it, so it has become
an activity that many of us squeeze in when we have free
time from our other responsibilities. If facilities like
Alba, and presumably others, feel that they are being held
back by technical limitations of HDF5, then it might be
necessary to rethink the NeXus support model, so that API
development is revived by being integrated into other
facility software development projects, such as Mantid or
Dials. It would probably save the facilities money in the
long term, but it would require NeXus to be less of a
part-time activity. Or we need to encourage more people to
contribute, in the way the more successful open-source
projects are run. I would certainly welcome additional
support for the Python API for the same reasons.</div>
<div class=""><br class="">
</div>
<div class="">With best regards,</div>
<div class="">Ray</div>
<div class="">
<div class="">
<div 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="">
<a href="mailto:ROsborn@anl.gov" class=""
moz-do-not-send="true">Email: ROsborn@anl.gov</a><br
class="">
<br class="">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">On Apr 7, 2022, at 12:16 PM, Watts
Benjamin (PSI) via NeXus <<a
href="mailto:nexus@shadow.nd.rl.ac.uk"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@shadow.nd.rl.ac.uk</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<div id="divtagdefaultwrapper" dir="ltr" class=""
style="font-style: normal; font-weight: normal;
letter-spacing: normal; text-align: start;
text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
text-decoration: none; font-size: 12pt;
font-family: Calibri, Helvetica, sans-serif,
"EmojiFont", "Apple Color
Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol",
"Android Emoji", EmojiSymbols;">
<div class="" style="margin-top:0px;
margin-bottom:0px">Hi Tobias,</div>
<div class="" style="margin-top:0px;
margin-bottom:0px"> I agree that we have spent
the past decade recommending HDF5, but at the
same time we have been saying that NeXus is
about the organisation of data within the
container, not the container file format itself.
I can see that you feel surprised by the sudden
discussion of other file formats, just as I was
surprised to hear the community talking about it
at the recent NFDI workshop. I am only
advocating for discussion and I would like to
hear your input.<span
class="Apple-converted-space"> </span><span
class="">I agree that multiple backends will
introduce higher support requirements that
NeXus doesn't currently have resources for.</span><span
class="Apple-converted-space"> </span>Your
preference for NeXus referring to a (small)
defined set of file formats is a valid view
point and I agree that there are practicalities
to consider. I view the next telco as just the
restart of an old discussion and nothing can
really change until a proposal is brought to a
NIAC meeting (and accepted).</div>
<div class="" style="margin-top:0px;
margin-bottom:0px"><br class="">
</div>
<div class="" style="margin-top:0px;
margin-bottom:0px">Cheers,</div>
<div class="" style="margin-top:0px;
margin-bottom:0px">Ben<br class="">
</div>
</div>
<hr tabindex="-1" class=""
style="font-family:Helvetica; font-size:12px;
font-style:normal; font-weight:normal;
letter-spacing:normal; text-align:start;
text-indent:0px; text-transform:none;
white-space:normal; word-spacing:0px;
text-decoration:none; display:inline-block;
width:1835.53125px">
<span class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none;
float:none; display:inline!important"></span>
<div id="divRplyFwdMsg" dir="ltr" class=""
style="font-family:Helvetica; font-size:12px;
font-style:normal; font-weight:normal;
letter-spacing:normal; text-align:start;
text-indent:0px; text-transform:none;
white-space:normal; word-spacing:0px;
text-decoration:none">
<font class="" style="font-size:11pt"
face="Calibri, sans-serif"><b class="">From:</b><span
class="Apple-converted-space"> </span>Tobias
Richter <<a
href="mailto:Tobias.Richter@ess.eu"
class="moz-txt-link-freetext"
moz-do-not-send="true">Tobias.Richter@ess.eu</a>><br
class="">
<b class="">Sent:</b><span
class="Apple-converted-space"> </span>Thursday,
7 April 2022 6:23:43 PM<br class="">
<b class="">To:</b><span
class="Apple-converted-space"> </span>Discussion
forum for the NeXus data format;
<a href="mailto:nexus@nexusformat.org"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@nexusformat.org</a><br
class="">
<b class="">Cc:</b><span
class="Apple-converted-space"> </span>Watts
Benjamin (PSI); Alexander Debus; Nicolas Soler;
Franz Pöschel; Emilio Centeno Ortiz<br class="">
<b class="">Subject:</b><span
class="Apple-converted-space"> </span>Re:
[Nexus] HDF5 as NeXus file format</font>
<div class=""> </div>
</div>
<div class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none">
<div class="WordSection1" style="">
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="">Hi all,</span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="">According to this discussion
from a decade ago HDF5 is singled out as the
only preferred physical file format:<span
class="Apple-converted-space"> </span><a
href="https://www.nexusformat.org/NIAC2012"
class="moz-txt-link-freetext"
style="color:blue;
text-decoration:underline"
moz-do-not-send="true">https://www.nexusformat.org/NIAC2012</a></span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<ul class="" style="margin-bottom:0cm"
type="disc">
<li class="MsoNormal" style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif;
color:rgb(81,81,81); background-color:white">
<span class="" style="font-size:13.5pt;
font-family:"PT
Sans",sans-serif">NeXus guiding
statements:</span>
<ul class="" style="margin-bottom:0cm"
type="circle">
<li class="MsoNormal" style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif;
color:rgb(81,81,81);
background-color:white">
<span class="" style="font-size:13.5pt;
font-family:"PT
Sans",sans-serif">The main focus
of the NeXus community is to further
develop the dictionaries, base classes
and application definitions.</span></li>
<li class="MsoNormal" style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif;
color:rgb(81,81,81);
background-color:white">
<span class="" style="font-size:13.5pt;
font-family:"PT
Sans",sans-serif">The NIAC is a
forum for resolving issues.</span></li>
<li class="MsoNormal" style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif;
color:rgb(81,81,81);
background-color:white">
<span class="" style="font-size:13.5pt;
font-family:"PT
Sans",sans-serif">The NIAC acts
as a custodian for NeXus: definitions,
examples, documentation, reference
implementations.</span></li>
<li class="MsoNormal" style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif;
color:rgb(81,81,81);
background-color:white">
<span class="" style="font-size:13.5pt;
font-family:"PT
Sans",sans-serif">NeXus can be
mapped to different physical file
formats:</span>
<ul class="" style="margin-bottom:0cm"
type="square">
<li class="MsoNormal"
style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif;
color:rgb(81,81,81);
background-color:white">
<span class=""
style="font-size:13.5pt;
font-family:"PT
Sans",sans-serif">HDF5 is the
preferred physical file format.</span></li>
<li class="MsoNormal"
style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif;
color:rgb(81,81,81);
background-color:white">
<span class=""
style="font-size:13.5pt;
font-family:"PT
Sans",sans-serif">NeXus-XML
is the currently supported ASCII
file format.</span></li>
</ul>
</li>
</ul>
</li>
</ul>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="">Technically you can map into
different backends. Yes. XML is still sort
of supported. At the time it was requested
that other options would get the official
blessing (YAML being specifically asked for)
but for practical exchange between
facilities the consensus was to stick with
HDF5.</span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="">There no longer is a
recommended or fully maintained abstraction
layer (like NAPI) to do an on the fly
translation between backends. Who would be
in charge of defining how the “official”
mapping into sqlite or whatever would look
like? How many backends can the community
commit to support in the long run?</span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="">When tools that are currently
developed/supported/maintained to “read”
NeXus/HDF5 fail to work with what gets
handed out, we are in a worse situation than
we are now. Note: What facilities do
internally for performance optimisations or
other reasons could be different, if it
stays internal. But I am clearly a lot less
open minded about producing non-HDF5 files
with a “NeXus” label than Ben. Maybe I
missed some decisions that were taken lately
in this direction or we’re no longer
interested in being able to read each
other’s files. Should either be the case,
I’ll be quiet.</span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="">Best wishes,</span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="">Tobias</span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<div class="" style="margin:0cm; font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""> </span></div>
<div class="" style="border-style:solid none
none; border-top-width:1pt;
border-top-color:rgb(181,196,223); padding:3pt
0cm 0cm">
<div class="" style="margin:0cm 0cm 0cm 36pt;
font-size:11pt;
font-family:Calibri,sans-serif">
<b class=""><span class=""
style="font-size:12pt">From:<span
class="Apple-converted-space"> </span></span></b><span
class="" style="font-size:12pt">NeXus <<a
href="mailto:nexus-bounces@shadow.nd.rl.ac.uk"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus-bounces@shadow.nd.rl.ac.uk</a>>
on behalf of "Watts Benjamin (PSI) via
NeXus" <<a
href="mailto:nexus@shadow.nd.rl.ac.uk"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@shadow.nd.rl.ac.uk</a>><br
class="">
<b class="">Reply to:<span
class="Apple-converted-space"> </span></b>Discussion
forum for the NeXus data format <<a
href="mailto:nexus@shadow.nd.rl.ac.uk"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@shadow.nd.rl.ac.uk</a>><br
class="">
<b class="">Date:<span
class="Apple-converted-space"> </span></b>Thursday,
7 April 2022 at 17:10<br class="">
<b class="">To:<span
class="Apple-converted-space"> </span></b>"<a
href="mailto:nexus@nexusformat.org"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@nexusformat.org</a>"
<<a href="mailto:nexus@nexusformat.org"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@nexusformat.org</a>><br
class="">
<b class="">Cc:<span
class="Apple-converted-space"> </span></b>Benjamin
Watts <<a
href="mailto:benjamin.watts@psi.ch"
class="moz-txt-link-freetext"
moz-do-not-send="true">benjamin.watts@psi.ch</a>>,
Alexander Debus <<a
href="mailto:a.debus@hzdr.de"
class="moz-txt-link-freetext"
moz-do-not-send="true">a.debus@hzdr.de</a>>,
Nicolas Soler <<a
href="mailto:nsoler@cells.es"
class="moz-txt-link-freetext"
moz-do-not-send="true">nsoler@cells.es</a>>,
Franz Pöschel <<a
href="mailto:f.poeschel@hzdr.de"
class="moz-txt-link-freetext"
moz-do-not-send="true">f.poeschel@hzdr.de</a>>,
Emilio Centeno Ortiz <<a
href="mailto:ecenteno@cells.es"
class="moz-txt-link-freetext"
moz-do-not-send="true">ecenteno@cells.es</a>><br
class="">
<b class="">Subject:<span
class="Apple-converted-space"> </span></b>Re:
[Nexus] HDF5 as NeXus file format</span></div>
</div>
<div class="">
<div class="" style="margin:0cm 0cm 0cm 36pt;
font-size:11pt;
font-family:Calibri,sans-serif">
</div>
</div>
<div id="divtagdefaultwrapper" class=""
style="font-family: Helvetica,
"EmojiFont", "Apple Color
Emoji", "Segoe UI Emoji",
NotoColorEmoji, "Segoe UI Symbol",
"Android Emoji", EmojiSymbols;">
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Hi
Gabriel,</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt"> NeXus
is officially not dependent on HDF5 and we
are definitely open minded about
implementing the NeXus<span
class="Apple-converted-space"> </span><i
class="">data format</i><span
class="Apple-converted-space"> </span>on<span
class="Apple-converted-space"> </span><i
class="">file formats</i><span
class="Apple-converted-space"> </span>other
than HDF5. We plan to discuss such issues
at our<span class="Apple-converted-space"> </span><a
href="https://www.nexusformat.org/Telco_20220426.html" class=""
style="color:blue;
text-decoration:underline"
moz-do-not-send="true">next
teleconference</a><span
class="Apple-converted-space"> </span>on
April 26th and I invite you to join us.
Are there specific container file formats
that you are interested in?</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt"> </span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Cheers,</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Ben</span></div>
<p class="MsoNormal" style="margin:0cm 0cm
12pt 36pt; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="" style="font-size:12pt"> </span></p>
<div class="">
<div class="MsoNormal" style="margin:0cm 0cm
0cm 36pt; font-size:11pt;
font-family:Calibri,sans-serif;
text-align:center" align="center">
<span class="" style="font-size:12pt">
<hr class="" width="100%" size="0"
align="center">
</span></div>
<div id="divRplyFwdMsg" class="">
<div class="" style="margin:0cm 0cm 0cm
36pt; font-size:11pt;
font-family:Calibri,sans-serif">
<b class=""><span class="" style="">From:</span></b><span
class="" style=""><span
class="Apple-converted-space"> </span>NeXus
<<a
href="mailto:nexus-bounces@shadow.nd.rl.ac.uk"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus-bounces@shadow.nd.rl.ac.uk</a>>
on behalf of Gabriel Jover Manas via
NeXus <<a
href="mailto:nexus@shadow.nd.rl.ac.uk"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@shadow.nd.rl.ac.uk</a>><br
class="">
<b class="">Sent:</b><span
class="Apple-converted-space"> </span>Thursday,
7 April 2022 4:47 PM<br class="">
<b class="">To:</b><span
class="Apple-converted-space"> </span><a
href="mailto:nexus@nexusformat.org"
class="moz-txt-link-freetext"
moz-do-not-send="true">nexus@nexusformat.org</a><br
class="">
<b class="">Cc:</b><span
class="Apple-converted-space"> </span>Gabriel
Jover Manas; Nicolas Soler; Emilio
Centeno Ortiz<br class="">
<b class="">Subject:</b><span
class="Apple-converted-space"> </span>[Nexus]
HDF5 as NeXus file format</span><span
class="" style="font-size:12pt"></span></div>
<div class="">
<div class="" style="margin:0cm 0cm 0cm
36pt; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="" style="font-size:12pt"> </span></div>
</div>
</div>
<div class="">
<div class="" style="margin:0cm 0cm 0cm
36pt; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="" style="font-size:12pt">Dear
NeXus Users Community,</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Last
NFDI NeXus Workshop was a great
opportunity to meet the community and
learn from the experience of other
scientists and institutions.</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Here
at ALBA we are working on the
integration of NeXus files in our data
analysis workflows.</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">In
this scope we are interested on
investigating alternatives to hdf5 as
NeXus file format, in terms of slice
read/write performance,
read-write-many capabilities and
convenient reading.</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Would
the community be open to decoupling
the data format (NeXus) from the file
format (HDF5)?<br class="">
Is there already any effort in the
community in this direction?<br
class="">
Is anyone else also interested?</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt"> </span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Best
regards,</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt">Gabriel</span></div>
<div class="" style="margin-top:0px;
margin-bottom:0px; margin-left:36pt"><span
class="" style="font-size:12pt"> </span></div>
<div class="">
<div class="" style="margin:0cm 0cm 0cm
36pt; font-size:11pt;
font-family:Calibri,sans-serif">
<span class="" style="font-size:12pt">--</span></div>
<div class="">
<div class="">
<table class="MsoNormalTable"
style="width:468pt;
margin-left:36pt" width="624"
cellspacing="0" cellpadding="0"
border="0">
<tbody class="">
<tr class="">
<td rowspan="2" class=""
style="width:94.9pt;
padding:0cm" width="127">
<div class=""
style="margin-top:0px;
margin-bottom:0px"><a
href="http://www.albasynchrotron.es/"
target="_blank" class=""
style="color:blue;
text-decoration:underline"
moz-do-not-send="true"><span
class=""
style="color:windowtext;
text-decoration:none"><span
class=""
style="color:blue;
border:1pt solid
windowtext;
padding:0cm"><img
id="_x0000_i1025"
alt="Image removed
by sender. ALBA
Synchrotron"
class=""
style="width:1.2291in;
height:0.5729in"
src="cid:~WRD0000.jpg"
moz-do-not-send="true" width="118" height="55" border="0"></span></span></a></div>
</td>
<td class=""
style="width:373.1pt;
padding:3.75pt 0cm 0cm"
width="497" valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
<b class=""><span class=""
style="font-size:12pt;
font-family:Arial,sans-serif; color:rgb(17,46,80)">Gabriel Jover-Mañas</span></b></div>
</td>
</tr>
<tr class="">
<td class=""
style="width:373.1pt;
padding:3.75pt 0cm 0cm"
width="497" valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""
style="font-size:9pt;
font-family:Arial,sans-serif">Scientific
Data Management<br
class="">
Computing Division<span
class="Apple-converted-space"> </span></span></div>
</td>
</tr>
<tr class="">
<td colspan="2" class=""
style="padding:3.75pt 0cm
0cm" valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
</div>
</td>
</tr>
<tr class="">
<td colspan="2" class=""
style="padding:3.75pt 0cm
0cm" valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
<b class=""><span class=""
style="font-size:10pt;
font-family:Arial,sans-serif">ALBA SYNCHROTRON LIGHT SOURCE</span></b></div>
</td>
</tr>
<tr class="">
<td colspan="2" class=""
style="padding:3.75pt 0cm
0cm" valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
<span class=""
style="font-size:9pt;
font-family:Arial,sans-serif"><a
href="http://www.albasynchrotron.es/en/about/coming-to-alba"
target="_blank"
class=""
style="color:blue;
text-decoration:underline"
moz-do-not-send="true">Carrer
de la Llum 2-26 |
08290 | Cerdanyola del
Vallès| Barcelona |
Spain<span
class="Apple-converted-space"> </span></a><br
class="">
(+34) 93 592 4471<span
class="Apple-converted-space"> </span></span></div>
</td>
</tr>
<tr class="">
<td colspan="2" class=""
style="padding:3.75pt 0cm
0cm" valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
<b class=""><span class=""
style="font-size:9pt;
color:rgb(17,46,80)"><a
href="http://www.albasynchrotron.es/" target="_blank" class=""
style="color:blue;
text-decoration:underline"
moz-do-not-send="true">www.albasynchrotron.es</a></span></b><b class=""><span
class=""
style="font-size:7.5pt;
color:rgb(17,46,80)"><span
class="Apple-converted-space"> </span>|<span
class="Apple-converted-space"> </span></span></b><b
class=""><span class=""
style="font-size:9pt;
color:rgb(17,46,80)"><a
href="mailto:Gabriel.Jover@cells.es" class="" style="color:blue;
text-decoration:underline"
moz-do-not-send="true">Gabriel.Jover@cells.es<span
class="Apple-converted-space"> </span></a>|<span
class="Apple-converted-space"> </span><a
href="https://www.albasynchrotron.es/en/about/legal-notice"
target="_blank"
class=""
style="color:blue;
text-decoration:underline"
moz-do-not-send="true">legal notice</a></span></b></div>
</td>
</tr>
<tr class="">
<td colspan="2" class=""
style="padding:3.75pt 0cm
0cm" valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
<span
class="Apple-converted-space"> </span></div>
</td>
</tr>
<tr class="">
<td colspan="2" class=""
style="padding:6pt 0cm 0cm"
valign="top">
<div class=""
style="margin:0cm;
font-size:11pt;
font-family:Calibri,sans-serif">
<b class=""><span class=""
style="font-size:8pt;
color:rgb(138,138,138)">Please, do not print this e-mail unless it is
absolutely necessary.<span
class="Apple-converted-space"> </span><br class="">
</span></b><span
class=""
style="font-size:8pt;
color:rgb(138,138,138)">Si
heu rebut aquest correu
per error, us informo
que pot contenir
informació confidencial
i privada i que està
prohibit el seu ús. Us
agrairíem que ho
comuniqueu al remitent i
l'elimineu. Gràcies.<br
class="">
Si ha recibido este
correo por error, le
informo de que puede
contener información
confidencial y privada y
que está prohibido su
uso. Le agradeceré que
lo comunique a su
remitente y lo elimine.
Gracias.<br class="">
If you have received
this e-mail in error,
please note that it may
contain confidential and
private information,
therefore, the use of
this information is
strictly forbidden.
Please inform the sender
of the error and delete
the information
received. Thank you.</span></div>
</td>
</tr>
</tbody>
</table>
<div class="" style="margin:0cm 0cm
0cm 36pt; font-size:11pt;
font-family:Calibri,sans-serif">
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<span class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none;
float:none; display:inline!important">_______________________________________________</span><br
class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none">
<span class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none;
float:none; display:inline!important">NeXus
mailing list</span><br class=""
style="font-family:Helvetica; font-size:12px;
font-style:normal; font-weight:normal;
letter-spacing:normal; text-align:start;
text-indent:0px; text-transform:none;
white-space:normal; word-spacing:0px;
text-decoration:none">
<span class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none;
float:none; display:inline!important"><a
href="mailto:NeXus@nexusformat.org"
class="moz-txt-link-freetext"
moz-do-not-send="true">NeXus@nexusformat.org</a></span><br
class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none">
<span class="" style="font-family:Helvetica;
font-size:12px; font-style:normal;
font-weight:normal; letter-spacing:normal;
text-align:start; text-indent:0px;
text-transform:none; white-space:normal;
word-spacing:0px; text-decoration:none;
float:none; display:inline!important"><a
href="https://lists.nexusformat.org/mailman/listinfo/nexus"
class="moz-txt-link-freetext"
moz-do-not-send="true">https://lists.nexusformat.org/mailman/listinfo/nexus</a></span></div>
</blockquote>
</div>
<br class="">
</div>
</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
NeXus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:NeXus@nexusformat.org">NeXus@nexusformat.org</a>
<a class="moz-txt-link-freetext" href="https://lists.nexusformat.org/mailman/listinfo/nexus">https://lists.nexusformat.org/mailman/listinfo/nexus</a>
</pre>
</blockquote>
</body>
</html>