[NeXus-committee] NeXus paper v12

[Herbert J. Bernstein]

My wife did a copyedit pass, so here are a few small changes.  They
have been committed
to the repository.  The main changes were to add "e.g." to the last
line of figure 2 and NIH
to the list of primary US funders.  Except for the figure 2 change,
the full diff is appended.
  -- Herbert

--- nexus14aip.tex    (revision 93)
+++ nexus14aip.tex    (working copy)
@@ -184,7 +184,7 @@

 \section{File Hierarchies}
 NeXus data files are organized into a hierarchy of groups which, in
turn, can contain further groups or fields,
-very much like an internal file system. The content of each NeXus
group is defined by either a base class,
+very much like an internal file system. The content of each NeXus
group is defined by a base class, or
 an application definition, or a contributed definition.


@@ -197,7 +197,7 @@
 \end{figure}

 The major focus of NeXus has been the recording of \emph{raw}
experimental data, i.e. information taken directly from the
experimental
-equipment, or processed only as required to provide physically
meaningful values.
+equipment or processed only as required to provide physically
meaningful values.
 The NeXus raw data file hierarchy is the consequence of some
practical considerations.
 An overview of the NeXus data file structure for raw experimental
data is shown in FIG.~\ref{rawfile}.

@@ -245,7 +245,7 @@
 is linked  into a \texttt{NXsubentry}. The \texttt{NXsubentry}
follows the hierarchy of
 \texttt{NXentry}. But it will typically only link to the data required by the
 application definition for the specific experimental technique. The
point of this scheme
-is that both humans and computerized users can easily locate method
specific data while
+is that both humans and computerized users can easily locate
method-specific data while
 maintaining the full view of the experiment.

 \begin{figure}
@@ -273,7 +273,7 @@
 \begin{itemize}
 \item Each variable varied or collected in the scan is stored at its
appropriate place in the NeXus beamline
  hierarchy as an array. The array's first dimension is the scan axis.
This is the unlimited dimension in
- the implementation and data is appended at each scan point to the array.
+ the implementation and data at each scan point is appended to the array.
 \item The \texttt{NXdata} group holds links to all the variables
varied or collected during the scan.
  This creates something equivalent to or better than the tabular
representation people are used to for scans.
  The main detector data can be plotted against any scanned parameter
as well as against everything that was
@@ -320,10 +320,10 @@
 \section{Coordinate Systems, Positioning of Components and Further Rules}

 For data reduction, it is often necessary to know the exact position
and orientation of beamline components.
-The first thing needed is a reference coordinate system. NeXus chose
to use same coordinate system as the
+The first thing needed is a reference coordinate system. NeXus chose
to the use same coordinate system as the
 neutron beamline simulation software McStas\cite{mcstas}.

-For describing the placement and orientation of components, NeXus
stores the same information as used for the
+For describing the placement and orientation of components, NeXus
stores the same information as is used for the
 same purpose in the Crystallographic Interchange Format
(CIF)\cite{ITCVG}. CIF (and NeXus) stores the details
 of the translations and rotations necessary to move a given component
from the zero point of the coordinate
 system to its actual position. As coordinate transformations are not
commutative, the order of transformations
@@ -473,7 +473,7 @@

 \begin{acknowledgments}
 The NIAC acknowledges the support of all the institutions
contributing to NeXus and their respective
-funding agencies. Most notably DOE and NSF in the US. The development
of the muSR NeXus data format was partly
+funding agencies, most notably DOE, NIH and NSF in the US. The
development of the muSR NeXus data format was partly
 funded by the European Commission within the sixth Framework Programme.
 \end{acknowledgments}

On Tue, Sep 9, 2014 at 8:49 AM, Mark Könnecke <mark.koennecke at psi.ch> wrote:
> Hi,
>
> sorry for yet another version but I missed some changes by Pete Jemian which resided in a
> separate branch. This is now merged in.
>
>
> Regards,
>
>     Mark Koennecke
>
>
> _______________________________________________
> NeXus-committee mailing list
> NeXus-committee at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus-committee
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nexus14aip.pdf
Type: application/pdf
Size: 730297 bytes
Desc: not available
URL: <http://lists.nexusformat.org/pipermail/nexus-committee/attachments/20140909/ed8c0571/attachment.pdf>