Initial HIT-Leiden implementation (CPU-first baseline)#1
Merged
randomvariable merged 4 commits intomainfrom Feb 21, 2026
Merged
Initial HIT-Leiden implementation (CPU-first baseline)#1randomvariable merged 4 commits intomainfrom
randomvariable merged 4 commits intomainfrom
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
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.
Summary\n- deliver initial HIT-Leiden implementation with deterministic and throughput execution paths\n- add incremental benchmark comparison flow for uk-2007-05@100000 with paper-style split (80% initial + 9 batches of 1000)\n- export incremental benchmark outputs to CSV/JSON and add cargo-make tasks\n- remove untested GPU/native acceleration and SIMD-specific branches from this first PR\n\n## Scope Decisions\n- first PR is CPU-only for reliability and reviewability\n- benchmark/release-gate and acceleration qualification evidence are explicitly marked deferred in spec/plan/tasks\n\n## Validation\n- cargo check\n- cargo test --test integration_tests --test contract_tests\n- targeted unit test for paper split behavior\n\n## Follow-ups\n- reintroduce acceleration targets (native/CUDA/ROCm) in dedicated PRs with parity/fallback tests and release-gate evidence\n