Hi J.B and the list.
Please accept my apology for a much delayed response. Was ill for last few days
and did not access my email.
Thanks for your detailed response.
> What does "performing better" mean in this case? How are you defining
> performance? A particular metric such as MCC, PPV, or
I'm pushing to get py-earth ready for a release, but I'm having an issue
with the check_estimator function on 32 bit windows machines. Here is a
link to the failing build on appveyor:
https://ci.appveyor.com/project/jcrudy/py-earth/build/job/21r6838yh1bgwxw4
It appears that array conversion is p
> I'll probably have to set up a 32 bit environment with a debugger and drill
> down to find the bug,
Must not be a bug but can simply be due to floating point imprecision. If you
checked that this is expected behavior, you could you do sth like
import numpy.distutils.system_info as sysinfo
if
Thanks, Sebastian. I'll consider using that platform check trick to
disable the test for 32 bit windows. It is a small difference, and perhaps
not worth all the effort of tracking down. It's part of check_estimator,
so I'd have to disable the entirety of check_estimator I think. However,
testin
Hm, I am actually not sure; could be a bug. When I see it correctly, the
problem is in
https://github.com/scikit-learn/scikit-learn/blob/master/sklearn/utils/estimator_checks.py#L1519
which could be related to the 'astype' calls in
https://github.com/scikit-learn/scikit-learn/blob/master/sklear
