octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pending interval-3.0.0 release


From: Oliver Heimlich
Subject: Re: pending interval-3.0.0 release
Date: Mon, 21 Aug 2017 19:09:02 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

On 21.08.2017 18:37, Mike Miller wrote:
> On Mon, Aug 21, 2017 at 17:57:30 +0200, Oliver Heimlich wrote:
>> We are not even talking about software.  It's static data.  We are
>> talking about the data format which you don't like.  A data format which
>> is perfect for an Octave user (.mat).
> 
> Does the data change over time or is it pretty much a constant table of
> data that might as well have been copied from a book?

The existing data mainly comes from free software projects, which are no
longer actively maintained.

  * https://scm.gforge.inria.fr/anonscm/git/metalibm/crlibm.git/
  * https://github.com/nehmeier/libieeep1788
  * https://gforge.inria.fr/frs/?group_id=157

I don't expect to get any updates from them.  Also, I haven't yet
successfully convinced others to contribute test data.  Probably the
existing test data is quite comprehensive already.

So if I want to update / extend the test data, I am pretty much on my own.

> FWIW, in previous projects where I have had to create or build large
> test vectors, where the test data doesn't actually change at all or
> often, I have usually written a script or set of comments to describe
> how the data was generated, but commit the test vectors themselves to
> version control to avoid having to regenerate the constant data on every
> build. Also to avoid adding build dependencies on unrelated tools.

That's pretty much the same reason why I decided to put the test data
under version control (plus the build dependencies would be very exotic
in this case).

Oliver



reply via email to

[Prev in Thread] Current Thread [Next in Thread]