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

Custom optimisation criterion functions #84

Open
mitchelloharawild opened this issue Jan 2, 2019 · 4 comments
Open

Custom optimisation criterion functions #84

mitchelloharawild opened this issue Jan 2, 2019 · 4 comments
Labels
enhancement New feature or request
Milestone

Comments

@mitchelloharawild
Copy link
Member

Where possible, models should allow custom optimisation criterions. This is appropriate as a control parameter for models.

from: robjhyndman/forecast#744

@dclengacher
Copy link

Thank you! Any idea when it will be included?

@mitchelloharawild
Copy link
Member Author

Hard to say. Control parameters for models have not yet been implemented, but this will be done for the first release of the package (#73). I'm hoping to release the package soon (https://github.com/tidyverts/fable/milestone/1), but I'm not sure if this feature will make it into the first release. If not included in v0.1.0, it will definitely be in v0.2.0.

@mitchelloharawild mitchelloharawild added the enhancement New feature or request label Jan 4, 2019
@mitchelloharawild mitchelloharawild added this to the v0.2.0 milestone Feb 21, 2019
@bonddr
Copy link

bonddr commented Apr 12, 2022

Has this enhancement been released?

@mitchelloharawild
Copy link
Member Author

Unfortunately not, this was pushed back a lot since it involves a rewrite of the underlying model code on an individual basis. When I first raised this issue, I was hopeful that it would be reasonable to specify the optimisation criterion more generally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants