[Nexus] problems with current stable of nxbrowse and nxdir

[Pete Jemian]

Aside from matters of variable-length string attributes, monochromator 
design, and the capabilities of X-ray scientists...

Did anyone point out that you are missing the required signal=1 
attribute on your dataset (/entry/data/data)?  Here is what you need to 
be compliant:

tstfile_00012.h5:NXroot
   entry:NXentry
     data:NXdata
       data:dataset
         @signal=1

Pete



On 9/10/2013 3:54 AM, Wintersberger, Eugen wrote:
> Hi folks
>    I got some reports that nxbrowse and nxdir do not work with the Nexus
> files we produce here at DESY. I can confirm this on my Debian system
> where libnexus0 is installed in version 4.2.1.
>
> I suspect that this still has a problem that we are using variable
> length strings and thus cannot read attribute data correctly. I have
> attached a file for testing. By the way can someone may have a look at
> the file if we got it at least a bit right ;)
>
> @Benjamin - this file does not collect non-standard fields into
> NXcollection as we discussed in Warwick. However, our new setups do. I
> am still working on the draft for a kind of 'best-practice' paper and I
> hope I can submit it to this mailing list this week.
>
> regards
>    Eugen
>
>
>
> _______________________________________________
> NeXus mailing list
> NeXus at nexusformat.org
> http://lists.nexusformat.org/mailman/listinfo/nexus
>