[Os-project-managers] NaN in xs:double (OSrL)

[Horand Gassmann]

Kipp Martin <kmartin at chicagobooth.edu> wrote:

> Hi Gus:
>
> It seems to me that by definition of an optimal, indeed even feasible
> solution, cannot contain a NaN.  If the solver does return NaN my first
> inclination is in the <optimization> child <status> set type = "error"
> and under description say "solver returned a NaN."  In  such a case we
> would not print a <solution>. I would argue that having a NaN as a
> solution value is an oxymoron.

But even then, I think, the diagnostics would be helped greatly if we  
provide tools to *pinpoint* where the NaN occurred. We allow NaN to be  
provided as a *starting value*, so why not as a terminating value? We  
seem to be breaking the symmetry here.

Just my Can$ 0.02

Cheers

gus