microsoft / microsoft/Graphormer

Simple/Basic tutorial

Open
#120 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hello,

Perhaps a very simple question despite having dug into the graphormer documentation: Assume given a csv training file containing tens of thousands of SMILES and their corresponding properties, say just 2 properties. For example the training .csv file will look like

SMILES, Property 1, Property 2
SMILE1, some_number11, some_number21 
SMILE2, some_number12, some_number22
SMILE3, some_number13, some_number23
...

At this point, I only know that I will have to invoke the command fairseq-train --user-dir path/to/graphormer with a lot of settings from the fairseq page (https://fairseq.readthedocs.io/en/latest/command_line_tools.html#fairseq-train) and Graphormer's documentation. On the website, I could just roughly make sense of the oc20 (Train a New Model) example that uses lmdb files. So for the very simple case mentioned above (1 huge training csv file, and a separate test csv file), how do I go about using Graphormer?

I would appreciate if someone could give some pointers or direct me to the correct destination in the documentation that I might have overlooked.

Thank you.

Best,
Jacey

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 with the existing OC20 “Train a New Model” example and the fairseq-train command-line documentation linked in the issue. Determine whether the project already supports CSV input for SMILES and two properties, then document the required workflow for separate training and test CSV files. Done means a newcomer can follow the documented commands without relying on LMDB examples.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation, machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.