-
Notifications
You must be signed in to change notification settings - Fork 1
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
Initial graph #5
Merged
Merged
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This creates a graph that is not ideal (see issue #4 for more details), but does work for most machine learning use cases anyways. The approach in the PR initially is to represent all of the available ops that all backends can execute using an enum called
Op
. This approach is likely not what we ultimately intend to use since it doesn't support adding ops downstream, but this PR will be open to discuss this.The
deep
crate contains the core graph logic and tensor logic. It also contains what defines a backend.The
deep-native
crate defines the backend for native Rust implemented operations. It specifically chooses to usendarray
to represent its tensors. It allows ops to be plugged into it at runtime.The
deep-backend-tools
crate was created becausedeep-native
had several pieces of code that likely apply to all backends. This crate is intended to make the development of future backends easier by allowing the reuse of code. This crate performs the graph forward and backward propogation using aTape
struct that remembers previous outputs to avoid re-computation when gradients need to be applied.