David Sagan

So I propose that basePath can be any absolute (must begin with "/") directory specification. If basePath does not have a "%T" then there is no more than one messes...

My apologies. I was vague. In the standard, under the section "Scalar, Vector and Tensor Records", the following or something like it should be added (and the existing first three...

@ax3l > in general, openPMD is totally open to store more information in form of attributes or even other groups in data files. You can always add program-specific attributes or...

@ax3l Consider these use cases: A) When a person who maintains program X interfaces reader code to read in openPMD files, if he/she sees that program Y stores some extra...

@ax3l > I am not entirely sure if such information should just be part of the specific application's documentation. Another comment on this: My plan is to put information in...

@ax3l > Currently, only attributes can be freely added at any place (well, it's recommended to name them comment). Groups and data sets are restricted inside those paths. I would...

@mccoys >and we cannot rely on labels to be chosen among mandatory options. And why not? For example, if cylindrical coords are being used why cannot the Standard mandate that...

@mccoys What could be done is to have two attributes for the component sub-records. One attribute unambiguously identifies that component. For example, (`r` , `z` and `theta`) for cylindrical coordinates....

OK with me.

And I too agree