[NeXus-definitions-tickets] [NeXusDefinitions] #64: Revise NXmonopd per emails

[NeXus Base Classes and Instrument Definitions]

#64: Revise NXmonopd per emails
------------------------+---------------------------------------------------
Reporter:  Pete Jemian  |      Owner:  Pete Jemian
    Type:  defect       |     Status:  new        
Priority:  major        |   Keywords:  NXmonopd   
------------------------+---------------------------------------------------
 Recently, an email exchange took place regarding NXmonopd.  The main point
 is

   ''NIAC is examining the rules for validating NeXus data files and
   NXmonopd serves as a good (and only) first example of an application
 definition''

 == Identification of the defining NXDL ==

 {{{
 > Pete wrote:
 >
 > Also, in the data file, you have used a /NXroot/NXentry/definitions
 element
 > to associate this data file with a specific NXDL.  This is key
 information for
 > automatic recognition and validation.  Freddie & I may decide to
 relocate this
 > information in the standard structure but the idea of having this
 information is
 > correct.  For now, I will add the "definitions" field to the
 NXmonopd.nxdl.xml file.
 }}}

 Some mechanism needs to exist within the '''NXroot''' base class to
 identify the use of an application definition to use instead of the
 standard '''NXentry'''.

 == Items to repair ==

 ... as described by Mark Koennecke:

 {{{
 > Pete wrote:
 >
 > Also, some of the groups used in NXmonopd.nxdl.xml contain only standard
 fields
 > from the base_class (such as in NXmonitor) so I will remove the extra
 specifications.
 }}}
  * Oops, I do not understand this. Did you make this change already in
 NXmonopd.xml? I looked at it now and it looked OK. One of the points of
 having an application definition is to say which of the fields form the
 base classes are required.
     * From Pete:  This will be addressed in a new TRAC ticket

  * Being at it: somebody put the detector efficiency into the NXdetector
 group.  I wonder if this MUST be there. In a data file for exchange should
 the source not already have performed this correction?

-- 
Ticket URL: <http://trac.nexusformat.org/definitions/ticket/64>
NeXus Base Classes and Instrument Definitions <http://www.nexusformat.org/>
NeXus Base Classes and Instrument Definitions