You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 6, 2023. It is now read-only.
Hi:
I am trying to use the parameter check_every to control my fitting time, but I found it didn't make any differences when I change the init parameter check_every.
So I wonder whether the parameter check_every is useful now?
The text was updated successfully, but these errors were encountered:
Thanks for your answer!
So here comes a question:
What does the parameter check_every exactly do.
I found the fitting results(both predict accuracy and basis) are always the same when I change the parameter check_every.
I think if you set check_every sufficiently high, you should eventually see a worse fit (and maybe a very slight speed up). I think it speaks to the usefulness of check_every that I actually had to look in the code to make sure it's even still implemented. All it does is reduce the number of candidate knot locations during knot search. One reason to do this would be to make sure you don't end up with knots too close together. However, the minspan argument takes care of that in a much nicer way. I think I originally put check_every in in order to duplicate the behavior of the R earth package, which implements minspan the way py-earth implements check_every (or at least that was my understanding at the time). Basically, I'd say there's no good reason to use check_every at this point, unless you want to make your model worse for some reason (testing or something).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi:
I am trying to use the parameter check_every to control my fitting time, but I found it didn't make any differences when I change the init parameter check_every.
So I wonder whether the parameter check_every is useful now?
The text was updated successfully, but these errors were encountered: