different attributes in different installations about gpfit HOT 5 CLOSED

Hi @iclucho ! Both objects are created with the same code?

If so my guess it's that they're different versions of gpfit; we added the FitConstraintSet class pretty recently, and it looks like that's what you're seeing in the former, while the latter is probably a standard ArrayConstraintSet. What does type(smafit) show for each of them?

from gpfit.

Hi bqpd. Thanks for your reply.

Indeed, both objects are generated with the same code. At the moment I only have access to the "bad" machine. There, when typing type(smafit), I get:

<class 'gpfit.fit_constraintset.FitCS'>

I recloned the gpfit version today to see if it would make a difference but so far nothing.

EDIT: Nevermind, I started python in a different terminal and the newly cloned version also contains the fitdata attribute.

from gpfit.

Great! Yeah, looks like that's the newest version: https://github.com/hoburg/gpfit/blob/master/gpfit/fit_constraintset.py#L15

It might not be on pypi yet, so if you installed the 'bad' version with pip install gpfit, that could explain it.

from gpfit.

Sorry for the version confusion! GPfit hasn't had a proper owner/maintainer for a year; I'll hopefully be stepping to get it better documented /organized / etc this Fall.

from gpfit.

Created #92 to add to PyPI

from gpfit.