[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [h5md-user] Update
From: |
Pierre de Buyl |
Subject: |
Re: [h5md-user] Update |
Date: |
Fri, 6 Dec 2013 14:56:41 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hi Felix,
On Fri, Dec 06, 2013 at 02:50:47PM +0100, Felix Höfling wrote:
> Am 23.11.2013, 11:46 Uhr, schrieb Konrad Hinsen
> <address@hidden>:
>
> >Peter Colberg writes:
> >
> > > It would probably be reasonable to view the unit strings as a data
> > > format, and less as a display format; i.e. choose a single format
> > > based on ASCII, with a single representation of each unit. The data
> > > format can be converted to a display format using udunits2.
> >
> >+1
> >
> > > > The other one is that is may frighten potential users/developers?
> >
> >+1
> >
> > > I am more frightened of all the published work that is based on
> > > simulations that are based on non-peer-reviewed source code ;-).
> >
> >+1
> >
> >No contradiction here: different people are frightened by different
> >things ;-)
> >
> > > At this point, it seems better not to finalize the specification of
> > > the units module. We could keep it at a version 0.*, and add a note
> > > which clarifies that this is a preliminary version. To finalize the
> > > units module, we need proof of some applications; both for writing
> > > (simulation programs) and reading (analysis programs).
> >
> >+1
> >
> >That makes +4 in total :-)
> >
> >Konrad.
>
> Sorry for the late reply.
>
> In conclusion, I suggest to drop all UTF8 related stuff from the
> units module (thanks to Git these things are not lost completely),
> making the module really simple. I would prefer version numer 1.0 as
> it is the first working version along with the release of H5MD.
> Adding UTF8 later would increase the major version number (no
> backwards compatibility), which helps potential reader software
> agnostic of UTF8 to distinguish the two cases. I will prepare a
> patch for this.
Slow news from me too.
I would prefer (actually, I need time to modify the spec but I am preparing and
thinking this since my last message) to do the following:
1. within the spec, mention that all h5md_elements and physically relevant
datasets may carry a "units" attribute.
2. drop the inclusion of "units" and "thermodynamics" from the spec.
Actually, having the modules within the spec does not make sense as they carry
their own version numbers.
Cheers,
Pierre