-
Notifications
You must be signed in to change notification settings - Fork 25
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
Refactored and redid backend #111
Conversation
Review away |
@ReyhaneAskari can we test travis integration on this PR? |
@rdevon yes we should. @joeljpoulin should be working on this. |
@joeljpoulin This is apparently because there is no "script" entry in .travis.yml. How to fix? |
Why do we have so many CIs? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's hard for me to follow what has happened specially because there is no test and there are many changes. I'm OK but you should be rebasing instead of merging when you want to bring the changes of another branch. With rebase you will not have the additional commit that appears in the PR which is basically empty.
This PR has 0 flake8 errors.
Backend now uses aliases to handle keyword differences in routines and the model.
For example, a routine or build might reference a network "a_net", but this reference is only useful in the context of the routine or build. The model owns a dictionary of all the networks, and the routine simply has an alias (can be thought of a sort of pointer) to that network. That way, the routine can reference "a_net" without knowing how the model is using it.
Updated classifier, gan, vae, and ali to follow this framework.
Cleaned up code and fixed some small errors.
Cleaned up noise.py
Removed global network handler.
Now, routines and builds "own" their kwargs and help. These are containers of aliases which point to the model kwargs and help.
All models "train" correctly, but no tests are implemented. This is the next step.
cortex-config does not work (this script is not yet compatible with cortex.)
Note / TODO:
The interface for building models works, but it can be tricky to debug. This needs to be stressed tested as well as include more informative errors.