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

Purpose #1

Open
pkofod opened this issue Mar 17, 2017 · 0 comments
Open

Purpose #1

pkofod opened this issue Mar 17, 2017 · 0 comments

Comments

@pkofod
Copy link
Member

pkofod commented Mar 17, 2017

So, the idea here is to have a lot of the "intelligent" stuff in this package (autodiff constructors, gradient checkers, etc). This allows Optim and NLsolve to have a more lean code base, that is potentially much easier to maintain. One reason this would be the case, is the fewer direct dependencies.

I think the name might need a bit of bikeshedding. Maybe have an OptimTools and an NLsolveTools (LsqFitTools?). I'm mostly concerned about refactoring Optim right now, but it would be great if the packages could be organized in somewhat the same way.

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

No branches or pull requests

1 participant