HigherOrderGraph / modified MultiOrderModel - #329
Open
vineetbansal wants to merge 27 commits into
Open
Conversation
… namespace); continuations method removed from EventGraph
…lable from package root
…legating to MultiOrderModel
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
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.
A
HigherOrderGraphclass of arbitrary order, constructable from temporal_graph/event_graph/path_data. It delegates most of the work to theMultiOrderModelclass which does the iterations on the lifting (withcached=False). It is also constructable usingfrom_aggregated, and has its own.liftmethod.The
MultiOrderModelclass now hasHigherOrderGraphs in its layers.None of the tests for
MultiOrderModelneeded modifications and still pass, which is reassuring. Tests forHigherOrderModelandMultiOrderModelthat assumeHigherOrderModelin layers are coming next.This PR assumes that the
EventGraphbranch is merged, as it builds on top of it.Typical workflow using these new classes: