Update post-traverse and augmentation docs#67
Merged
Conversation
VJalili
marked this pull request as ready for review
June 10, 2026 03:41
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
1 participant
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.
The
post-traversecommand creates new nodes and edges files that contain extended features compared to the original files. Because downstream steps, such as theaugmentcommand, consume these files and subsequently create their own new files for graph importing, it is very common to mix up the filenames and use the incorrect files, which wastes computation time.Ideally, this should be handled within the method itself. However, until the methods are properly extended, this PR updates the documentation and adds commands that back up the old files and rename the newly generated files to avoid confusion.