From: Frank on

what about use the old optimization toolbox together with the new matlab release?
From: Walter Roberson on
Frank wrote:
>
> what about use the old optimization toolbox together with the new matlab
> release?

Such a thing would not be supported, at the very least, even if you
managed to get past the issue that the license manager would refuse to
see the old toolbox.
From: Frank on
Walter Roberson <roberson(a)hushmail.com> wrote in message <r_V5o.41$1v3.30(a)newsfe20.iad>...
> Frank wrote:
> >
> > what about use the old optimization toolbox together with the new matlab
> > release?
>
> Such a thing would not be supported, at the very least, even if you
> managed to get past the issue that the license manager would refuse to
> see the old toolbox.

we have two fully licenced versions, 2007b and 2010a. why wouldn't that work with the respective path setting?
From: Matt J on
"Frank " <anyone(a)oleole.com> wrote in message <i38a9s$bc8$1(a)fred.mathworks.com>...

> 2. The respective solutions are optimal for the respecitve runs (i.e. solution from 7.5 is optimal for 7.5). However, the solution from 7.5 is not optimal for 7.10 and vice versa.
================

What have you done to verify this? Did you check gradients, or something else?
From: Walter Roberson on
Frank wrote:
> Walter Roberson <roberson(a)hushmail.com> wrote in message
> <r_V5o.41$1v3.30(a)newsfe20.iad>...
>> Frank wrote:
>> > > what about use the old optimization toolbox together with the new
>> matlab > release?
>>
>> Such a thing would not be supported, at the very least, even if you
>> managed to get past the issue that the license manager would refuse to
>> see the old toolbox.
>
> we have two fully licenced versions, 2007b and 2010a. why wouldn't that
> work with the respective path setting?

MATLAB cross-checks (somehow, I don't know how) that toolboxes are the
same release as Matlab is.

For whatever reason, Mathworks requires that toolboxes be updated when
you updated Matlab. Matlab then has to check the versions in order to
prevent people from trivially by-passing that restriction by adding an
old toolbox to the matlabpath .

I won't get into _why_ Mathworks does this; I could speculate and point
out technical constraints, but I have never had "inside information"
from Mathworks about *anything*.