lmfit version upgraded to 0.7.4 to 0.9.11

[Lokesh Jasrotia]

Need help on the issue.I have..post upgrading lmfit version 0.7.4 (2014) to directly 0.9.11..

So we have same dataset  where in i was getting results  before upgrading but now model results are throwing errror--raise MinimizerException error(CONF-ERR_STDERR)

Release version history  details i am getting only for 0.9 version..

Looking for some directions and help..

1-can earlier version release changes details be availed anywhere?

2-any argument to look into in new changed version ..or  i can never get back to old values with current version..

[Renee Otten]

hi Lokesh,


as stated at the top of the Google-group page, we request to include a minimal and complete example and the full traceback if you get an error - so please do so.

Most likely the change has happened between version 0.8.3 and 0.9 - so reading the 0.9 release notes might be sufficient. Additionally, you should probably read the documentation to make sure that all function calls you’re making are actually still up-to-date. Reading through the documentation and examples will probably prove helpful.

It none of that helps, please provide the actual code and some (synthetic) data so that it will run and show us the different things you tried to get it to work. With all of that information we can hopefully get you back on track.

[Matt Newville]

Hi Lokesh,

I agree with all of Renee's points.

The main change from 0.8 to 0.9 is described at https://lmfit.github.io/lmfit-py/whatsnew.html#whatsnew-090-label

Basically, the parameters passed into Minimizer or Model.fit() are no longer changed in place, but you need to look at the `params` object of the result to see the updated values.

--
You received this message because you are subscribed to the Google Groups "lmfit-py" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lmfit-py+u...@googlegroups.com.
To post to this group, send email to lmfi...@googlegroups.com.
Visit this group at https://groups.google.com/group/lmfit-py.
To view this discussion on the web visit https://groups.google.com/d/msgid/lmfit-py/9C7A3B5E-8CA5-457E-A480-EA9FD022EB76%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

--Matt Newville <newville at cars.uchicago.edu> 630-252-0431

[Lokesh Jasrotia]

Thanks Renee ,Thanks Matt,

While I was going  through documentation and lmfit page--

which says ---Requires: Python >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.* while I have been trying on python 3.7 and python 3.3

Does it mean I should  try on other versions than these two.

Regards

Lokesh

[Matt Newville]

Hi,

On Sun, Oct 28, 2018 at 2:56 AM Lokesh Jasrotia <lokesh....@gmail.com> wrote:

Thanks Renee ,Thanks Matt,

While I was going  through documentation and lmfit page--

which says ---Requires: Python >=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.* while I have been trying on python 3.7 and python 3.3

Does it mean I should  try on other versions than these two.

We don't test against Py 3.3. Like lmfit 0.7.4, it is pretty old.Python 3.4 was released in early 2014.   My view is that Python 3.0 to through 3.4 are not interesting or useful at this point. I would have no objection to dropping support for Python 3.4, and cannot be  very sympathetic to people who claim to be stuck with Python 3.4 or earlier.  FWIW, our policy is also that scipy should be newer than ~2 years old.  We don't have the manpower to support legacy systems.  Not upgrading for 4 years is not a good strategy.

That said, I am slightly sympathetic to people stuck with Python 2.7, but lmfit 1.0 will almost certainly require Python 3.5 (or perhaps even 3.6) or higher.

Python 3.7 is pretty new.  The latest release of lmfit (0.9.11) was released within a week of Python 3.7, so there was not much testing done with it at the time of the last release.   But we do test against Python 3.7 and I amn not aware of any problems.

--Matt