[Nexus-developers] NX_BINARY

[Peterson, Peter F.]

Mark,

I thought that the way NX_BINARY was supposed to be handled (in HDF4/5) was to place it as NX_UINT8. That is what the minutes from NIAC 2003 say anyhow. However, I do not know any of the technical consequences of this.

P^2

-----Original Message-----
From: nexus-developers-bounces at anl.gov on behalf of Mark Koennecke
Sent: Tue 11/16/2004 4:39 AM
To: nexus-developers at anl.gov
Subject: [Nexus-developers] NX_BINARY
 


  High,

  I'am mostly finished fixing the NAPI issues resulting from the October
  NIAC meeting. In the meantime a new version of mxml was released which
  contains the changes necessary to make XML NeXus-API work. There is
  a little bug in mxml there though.. 

  NX_BINARY: there are two ways to do it:
  - cheap: just map NX_BINARY to NX_UINT8 and forget
  - good: handle NX_BINARY properly: i.e. read it correctly, allow only
    0,1 as values. This is a problem as HDF does not have a native boolean
    type. A workaround would be to have an attribute boolean=1 on boolean
    datasets which flags the condition. 

  Which one is the preferred solution? Better suggestions?

			Best Regards,

				Mark Koennecke




_______________________________________________
NeXus-developers mailing list
NeXus-developers at anl.gov
http://www.neutron.anl.gov/mailman/listinfo/nexus-developers