Boost logo

Boost :

Subject: Re: [boost] library proposal : odeint
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2010-07-11 05:56:03

> -----Original Message-----
> From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]] On Behalf Of Matthias Troyer
> Sent: Sunday, July 11, 2010 5:26 AM
> To: boost_at_[hidden]
> Subject: Re: [boost] library proposal : odeint
> On 9 Jul 2010, at 15:46, Karsten Ahnert wrote:
> >
> >> I have one question - have you considered if your library will 'play nicely' with the Boost.Units library? If it
> >> the units error detection and convenience of output with units, would seem to make it much more attractive.
> >
> > At the moment it is not possible to use Boost.Units. We are redesigning
> > the library and it might be possible to enable Boost.Units at some
> > point. But I suspect, that Boost.Units will not work in general with
> > odeint. I can go in details if you like.
> I would be very interested in why it would not work with Boost.Units since I might be interested in using such a
library with my own
> datatypes instead of double or std::complex<double>

I have also have some interest in using a user defined 'uncertain type' - one that includes not just a value but also an
uncertainty - a sort of 'plus or minus' (and calculation operators propagate the uncertainties).

Can you see any reason why it would not work with a user-defined type like that?

(Leaving aside downsides like much longer compute time).

But perhaps there are other better ways of estimating uncertainties of the final result?


Paul A. Bristow
Prizet Farmhouse
Kendal, UK   LA8 8AB
+44 1539 561830, mobile +44 7714330204

Boost list run by bdawes at, gregod at, cpdaniel at, john at