Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interface for computing errors #51

Open
dwysocki opened this issue Dec 14, 2014 · 1 comment
Open

Interface for computing errors #51

dwysocki opened this issue Dec 14, 2014 · 1 comment

Comments

@dwysocki
Copy link
Member

We should consider how we want to handle computing errors from an API perspective. For Lasso regression, we will need to use bootstrapping, but for OLS, we can compute standard error. I propose we somehow provide an error function to get_lightcurve, or create a new function, get_lightcurve_with_error, which takes that function. The bootstrapping function would need to call get_lightcurve many times, while the standard error function would call get_lightcurve a single time. Our current behavior could be recreated by passing in an error function which only computes the SDM of the light curve.

Any ideas or concerns about this topic?

@dwysocki
Copy link
Member Author

One more thing, this also leaves open the possibility of passing an error function which is essentially a no-op, for when you only want a quickly fitted light curve, with no errors. Bootstrapping is going to be very time consuming, and so you probably only want to use it for publishable results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant