microsoft / microsoft/Graphormer

Feature Requests & Voting Hub

Open
#63 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Python
Stars
2.5k
Forks
374
PR merge metrics
No merged PRs in 30d

Description

This issue is to maintain all features request on one page.

Note to contributors: If you want to work for a requested feature, re-open the linked issue. Everyone is welcome to work on any of the issues below.

Note to maintainers: All feature requests should be consolidated to this page. When there are new feature request issues, close them and create the new entries, with the link to the issues, in this page. The one exception is issues marked good first issue. these should be left open so they are discoverable by new contributors.


Call for voting

we would like to call the voting here, to prioritize these requests.
If you think a feature request is very necessary for you, you can vote for it by the following process:

got the issue (feature request) number.
search the number in this issue, check the voting of it exists or not.
if the voting exists, you can add 👍 to that voting
if the voting doesn't exist, you can create a new voting by replying to this thread, and add the number in the it.


Efficiency related

  • High efficient shortest path implementation (#69 )
  • Compact Pre-trained Graphormer-base on PCQM4M (#80 )

New features:

  • Molecule Feature Extraction by RDKit (#71 )

  • Package Graphormer to PyPI (#72)

  • Windows support (#144)

New algorithms:

  • Examples of node classification and link prediction (#75 )

Objective and metric functions:

New pre-trained models:

  • Pre-trained Graphormer v2.0 for ogbg-molpcba (#70 )
  • Pre-trained Graphormer v2.0 on OC20 (#73 )
  • Pre-trained Graphormer-large v2.0 on PCAM4M (#74 )

Input enhancements:

  • Sparse Graph Representation (#82 )

Bug fixs:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked feature issues listed here, including #69, #71, #72, #75, and #82, and compare their status with the checklist. The issue provides no implementation file, test, or single change to make; completion would require deciding how this voting hub should be maintained and updating its entries consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.