Neural Updates: PolicyDataLoader replaced with the old dataloading scheme and Quad terms added #780
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.
hi @MUCDK,
I have added support for quad terms while replacing the old dataloader with something more efficient and more extendable. Currently quad terms will work in a meaningful way if in the policy this is satisfied for the policy graph
for all a,b,c,d in nodes, for every (a,b) in edges there is no (c,a) or no (b,d) present
. I.e., a src node should stay a source node and tgt node should stay a tgt node throughout the plan. Currently I handled it like thisAnother problem is that I could've assume an adata has both src_quad and tgt_quad. For this we'd also need to assume there is no second adata. These assumptions can make it a bit easier but it depends on our main goal with adding quad support. For now it makes sense to me that all adata will have the
aug
andflow
. This quad problem actually exists in non-Neural version right? How do we solve that?How reasonable are these?