-
Notifications
You must be signed in to change notification settings - Fork 4.4k
Remove graph scope #1205
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
Merged
Merged
Remove graph scope #1205
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
awjuliani
reviewed
Sep 12, 2018
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.
Changes look good. Just remove dead code and comments.
* Documentation changes * removed the keep checkpoint printing
awjuliani
approved these changes
Sep 14, 2018
mmattar
reviewed
Sep 17, 2018
@@ -1,9 +1,12 @@ | |||
import logging | |||
import numpy as np | |||
import tensorflow as tf |
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.
@vincentpierre - I thought we were aiming to remove TF dependency from the Policy class?
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature : Remove Graph Scopes
Abstract
As part of our work to make inference within the Unity Engine easier to use, we propose to generate one graph per brain when training with multi-brain rather than a single graph with multiple graphs scopes.
Background
A key project we want to integrate in v0.6 is around inference within Unity. As such, there are several pieces that are required in order to make inference in Unity more intuitive. The first step is to ensure the graphs we generate through our training process are always formatted the same way. This is currently not the case when a model is trained through multi-brain since the graph generated contains multiple inference sub-graphs with different graph scopes.
Goals
action
node per.bytes
file)bytes
file per brain when training with multi-brainNon-Goals
Plan
The graph generated with multi-brain goes under :
models/<run-id>/<env-name>_<run-id>.bytes
withbrain-name
for graph scopeWe propose to genetate multiple graphs without graph scopes under
models/<run-id>/<brain-name>.bytes
.The policy will be responsible for serializing, saving and loading the models and will be called from the
trainer_controller
through trainer base class method calls.Acceptance criteria
Single model per brain when training with multi-brain
Design aligns with long term plan
Milestones
Graph Scope
property from Internal Brain PR here