-
Notifications
You must be signed in to change notification settings - Fork 119
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
[Internal] Performance Consistency Check Leaderboard #53
Comments
[DGL] Homogeneous Node ClassificationStarting cmd:
Environment: Tesla V100S-PCIE-32GB
|
[PYG] Homogeneous Node ClassificationStarting cmd:
Environment: Tesla V100S-PCIE-32GB
|
[DGL] Heterogeneous Node ClassificationStarting cmd:
Environment: [fill this env]
|
[PyG] Homogeneous Graph ClassificationStarting cmd:
Environment: Tesla V100S-PCIE-32GB
Environment: Tesla V100S-PCIE-32GB
|
[PyG] NASEnvironment: GeForce GTX TITAN X
|
[DGL] Homogeneous Graph ClassificationStarting cmd:
Environment: Tesla V100S-PCIE-32GB
|
[PYG] Homogeneous Link PredictionStarting cmd:
Environment: Tesla V100S-PCIE-32GB
|
[DGL] Link PredictionStarting cmd:
Environment: Tesla V100S-PCIE-32GB
|
[PYG] Robust Model under MettackStarting cmd:
[PYG] Robust Model under MettackStarting cmd:
|
SSL Test train set performance
valid set performance
test set performance
|
This issue is created to check whether the library has the same performance features with the native implemented models.
WARNING: This is not the evaluation results of this library. For benchmarking of AutoGL, please see the examples provided.
Guide to developers
What do we mean when we are checking performance?
First, remember that the performance inconsistency may not be because of our implementations. Sometimes you need to increase the repeat number, or change the range of seeds to see whether the performances match with each other under the "same" setting.
If the rules above do not apply, you need to carefully check whether there are some unwanted implementations in your code. Also, there are still chances that the performance check codes are incorrect, in which case you should point out to @Frozenmad .
Note
All the performance check results are listed below. All the performances inconsistencies are represented as bold in the Table.
The text was updated successfully, but these errors were encountered: