Upgrade dependency stack - #54
Merged
Merged
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
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.
Summary
uv.lockWhy
The previous dependency stack and installation path were increasingly difficult to install on current Python and accelerator environments. This update establishes a current, locked baseline while retaining the benchmark's existing runtime behavior.
Validation
install.sh, includingpip checknrm_rankcomparison: all 31 non-runtime result fields exactly equal across the old and new stacksppo_dual_gat+smoke training and inference: one epoch completed and 10/10 inference requests succeededuv lock --check, shell syntax check, and source/wheel builds passedNotes
pyg_libas the optional compiled extension; the complete test suite passes with the supported pure/PyG paths.