-
Notifications
You must be signed in to change notification settings - Fork 68
Category: A1; Team name: Guris; Dataset: ogbn-arxiv and ogbn-products #232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
alexsandro-santos
wants to merge
21
commits into
geometric-intelligence:main
Choose a base branch
from
giovanni-br:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Up to date with main repo
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.
Checklist
Description
This pull request integrates two datasets from the Open Graph Benchmark (OGB) into the TopoBench framework:
ogbn-arxivandogbn-products. Both datasets are homogeneous, single-label node classification tasks, which makes them fully compatible with TopoBench’s current graph pipeline.The first dataset,
ogbn-arxiv, is a directed citation network of computer science papers, where each node corresponds to a paper described by a 128-dimensional word-embedding feature vector, and the task is to predict one of forty subject areas. The second dataset,ogbn-products, is a large co-purchase graph where nodes represent Amazon products with 100-dimensional semantic features, and the task is to classify each product into one of forty-seven categories.To support these datasets, this PR adds a unified dataset loader that handles feature casting and label formatting. Corresponding dataset configuration files have been added under configs/dataset/graph/, following the same structure and conventions used by the existing TopoBench datasets. Although this PR adds full support for ogbn-products, it is intentionally not used in test/pipeline/test_pipeline.py, because of its size.
Additional context
Although the OGBN collection contains five datasets in total, only
ogbn-arxivandogbn-productsare included in this PR. The remaining three datasets require functionality that is beyond TopoBench’s current architecture.ogbn-magis a heterogeneous graph containing multiple node and edge types, which would require dedicated hetero-graph support to integrate properly.ogbn-proteinsis a multi-label regression task with no node features, which does not align with TopoBench’s assumption of single-label node classification on feature-bearing graphs. Finally,ogbn-papers100Mis extremely large and cannot be feasibly downloaded or tested in the CI environment. Because these datasets would require substantial structural additions or special-case handling, they are intentionally omitted from this PR to keep the scope clean and maintain alignment with the existing pipeline.Co-authored by: @giovanni-br and @alexsandro-santos