[NeXus-committee] Is NeXus strictly one-based?

[Benjamin Watts]

Hi Tobias,
    To be clear, I'm not advocating any change and I don't care either 
way (although zero-based fits nicely with Python). I just want to make 
sure we all agree because I can't find a definitive statement anywhere. 
I have a file from Mark Koennecke from 2012 that labels the axes 
counting from 1 - so I think we will have some conflict here. Perhaps we 
will need a compromise where the old axes labeling scheme is one-based 
and the new scheme is zero-based? Anyway, lets wait and see what other 
responses we get from the mailing list over the next week to see what 
people think the situation is/should be.

Cheers,
Ben


On 10/04/15 15:37, Tobias Richter wrote:
> Hi Ben,
>
> All the HDF indexing is zero based and that’s what canSAS picked. We’re compatible and got that in use already, so it’s a bit late to change.
>
> Cheers,
>
> Tobias
>
>
>
>> On 10 Apr 2015, at 15:13, Benjamin Watts <Benjamin.Watts at psi.ch> wrote:
>>
>> Hi Everyone,
>>    I have been looking closer at the new NXdata axes labelling scheme:
>> http://wiki.nexusformat.org/2014_axes_and_uncertainties
>> and I notice that it is zero-based (i.e. the axes are numbered starting from zero). Isn't NeXus supposed to be one-based? I can't find anything specific in the manual, but the old axes labelling scheme I had implemented as one-based and I don't recall ever seeing an "entry0".
>>
>> Should I update the above wiki page to count from one?
>>
>> Cheers,
>> Ben
>> _______________________________________________
>> NeXus-committee mailing list
>> NeXus-committee at nexusformat.org
>> http://lists.nexusformat.org/mailman/listinfo/nexus-committee