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

Hierarchy change: take Black-box optimization out of RL #3

Closed
schaul opened this issue Jul 3, 2009 · 3 comments
Closed

Hierarchy change: take Black-box optimization out of RL #3

schaul opened this issue Jul 3, 2009 · 3 comments

Comments

@schaul
Copy link
Collaborator

schaul commented Jul 3, 2009

Although it technically fits there, it is a bit confusing.
I think the split should be along the difference of ontogenetic/phylogenetic with on one side optimization, evolution, pso, etc. (coevolution methods should fit here, but how about multi-objective optimization?) and on the other side policy gradients, and other RL algos.

@schaul
Copy link
Collaborator Author

schaul commented Jul 3, 2009

Thomas says:

There was a class "Learner", which we thought of as being the RL-equivalent of "Trainer" for supervised learning. Then it was changed to "RLLearner" and another class "Learner" was created that does optimization now. For me it always felt like the blackbox optimization code was just dumped in there because some functionality was similar to the existing RL methods. We should clean this up or work out a proper common framework for RL and optimization.

@schaul
Copy link
Collaborator Author

schaul commented Jul 25, 2009

Additionally, we could change the directory hierarchy a bit more: merge the tools and auxiliary folders, put datasets in there too, and move the test folder one level up.

@schaul
Copy link
Collaborator Author

schaul commented Jul 25, 2009

I've started doing those changes in a new branch: http://github.com/schaul/pybrain/commits/learnerstucture ...

x75 added a commit to x75/pybrain that referenced this issue May 22, 2015
This issue was closed.
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