<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
Jeff,
<div>That’s an extremely interesting question that doesn’t really have an easy answer. NeXus represents a way of organizing HDF5 files that could inspire similar efforts in other fields. Essentially, we try to represent objects, in our case the sample being
measured, components of a beamline, etc. by collecting their metadata into groups of a particular class (which is defined by an HDF5 group attribute). We also collect all the data representing the results of an experiment in separate groups of class NXdata
so that they are automatically plottable. Both of those aspects of the format could be transferable to other techniques. Indeed, we already have one example, in that muon spin resonance is now part of the standard. There is also some interest in the electron
microscopy community. The advantage is that there could be some generic tools that could work in multiple fields, e.g., the NXDL language for defining class structures and the Python API for manipulating HDF5 files.</div>
<div><br>
</div>
<div>On the other hand, the specific classes defined within the format and the glossary of field names that can go in those classes are clearly specific to scattering, and there is probably insufficient overlap in our scientific fields for it to make sense
to merge. We would have to document the neurophysiology classes separately from the neutron and x-ray classes so as not to cause confusion. That could perhaps be achieved through having completely separate branches of the format.</div>
<div><br>
</div>
<div>In a way, NeXus is just a way of adding semantics to HDF5, making the files self-describing in a way that HDF5 files are not guaranteed to be. There may be value in multiple groups using the same design philosophy and sharing similar tools, and we would
probably benefit if the community were enlarged. I’m sure we would be happy to give further advice if you decide to pursue this further.</div>
<div><br>
</div>
<div>With regards,</div>
<div>Ray</div>
<div><br>
<div>
<div>On Oct 1, 2014, at 4:56 PM, Jeff Teeters <<a href="mailto:jteeters@berkeley.edu">jteeters@berkeley.edu</a>> wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Hi,<br>
I'm helping to coordinate a project (called "Neurodata Without Borders", described below), which has the goal to develop a standard file format for neurophysiology data. It seems likely that HDF5 will be used as the basis for the standard format, but the
organization of data and metadata within the HDF5 file still must be determined. I'm interested in any opinions or input about the following:<br>
a. Is NeXus potentially useful for domains unrelated to particle physics experiments?<br>
b. Are there any examples of NeXus being used in other domains?<br>
</div>
c. What other methods of specifying the organization of data in an HDF5 file might be applicable for this project?<br>
</div>
<div>Thanks,<br>
</div>
<div>Jeff Teeters<br>
Redwood Center for Theoretical Neuroscience<br>
UC Berkeley<br>
</div>
<br>
<div><br>
<span>---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Jeff Teeters</b> <span dir="ltr"><<a href="mailto:jteeters@berkeley.edu" target="_blank">jteeters@berkeley.edu</a>></span><br>
Date: Mon, Aug 11, 2014 at 11:47 PM<br>
Subject: Seeking community input for Neurodata Without Borders<br>
To: Jeff Teeters <<a href="mailto:jteeters@berkeley.edu" target="_blank">jteeters@berkeley.edu</a>><br>
Cc: Fritz Sommer <<a href="mailto:fsommer@berkeley.edu" target="_blank">fsommer@berkeley.edu</a>><br>
<br>
<br>
</span>Dear Colleague,<br>
<br>
The Neurodata Without Borders (NWB) project has just started. The project goal is to build a common data format for neurophysiology data from Allen Brain Institute, Janelia Farm and two labs from NYU and Caltech. Although focusing on a limited set of use cases,
the project also aims to develop products that will serve the broader community.
<br>
<br>
At this point we would like to solicit community input about ideas/approaches for designing a generalizable neurophysiology data format. If you are interested in contributing to this project, please review the project description at:<br>
<a href="https://crcns.org/NWB" target="_blank">https://crcns.org/NWB</a><br>
and fill out the questionnaire:<br>
<a href="https://docs.google.com/forms/d/1CNTd4M-8kQ_WhEZc7n7WxpTa0LOupt_q3z21E1fRxjM/viewform" target="_blank">https://docs.google.com/forms/d/1CNTd4M-8kQ_WhEZc7n7WxpTa0LOupt_q3z21E1fRxjM/viewform</a><br>
<br>
On the basis of the questionnaire responses and ensuing communication, we will organize the first hackathon meeting of the project, to be held November 20 – 22, 2014 (just after SfN) at Janelia Farm, in Ashburn, Virginia. At this hackathon we will discuss
in detail the requirements for a common format based on the project use cases and also discuss, compare and evaluate alternative techniques for implementing the common format.
<br>
<br>
More information about the project is available in a recent press release: <a href="http://www.kavlifoundation.org/kavli-news/prominent-us-research-institutions-announce-collaboration-toward-sharing-and" target="_blank">
http://www.kavlifoundation.org/kavli-news/prominent-us-research-institutions-announce-collaboration-toward-sharing-and</a><br>
<br>
Please forward this email to anyone you know with relevant expertise who may be interested in contributing to this project.<br>
<br>
Thank you,<br>
Fritz Sommer and Jeff Teeters<br>
Redwood Center for Theoretical Neuroscience<br>
UC Berkeley<br>
</div>
</div>
_______________________________________________<br>
NeXus mailing list<br>
<a href="mailto:NeXus@nexusformat.org">NeXus@nexusformat.org</a><br>
http://lists.nexusformat.org/mailman/listinfo/nexus<br>
</blockquote>
</div>
<br>
<div>-- <br>
Ray Osborn, Senior Scientist<br>
Materials Science Division<br>
Argonne National Laboratory<br>
Argonne, IL 60439, USA<br>
Phone: +1 (630) 252-9011<br>
Email: <a href="mailto:ROsborn@anl.gov">ROsborn@anl.gov</a><br>
<br>
</div>
<br>
</div>
</body>
</html>