GitLab

* fix

* improve

* fix lint

* upd

* fix

* upd

* Fix outdated example

* Hot fix

* [Doc] Small graphs readme.txt, edit pass

Edit for grammar and style. Should this be an .rst on .txt?

* Update README.txt

* upd

* fig edgebatch edges

* add test

* trigger

* add graphwriter pytorch example

* fix line break in graphwriter README

* upd

* fix

* [Doc] Generative models, edit pass

Edit for grammar and style. Can you clarify "Instead of and/or"?

* Update tutorials/models/3_generative_model/5_dgmg.py

* Update tutorials/models/3_generative_model/5_dgmg.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/models/3_generative_model/5_dgmg.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/models/3_generative_model/5_dgmg.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/models/3_generative_model/5_dgmg.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

Edit pass for grammar and style

* Add L2 distance score for TransE

* Update README.md

* Use linalg.gemm to speedup mx l2 dist

* Fix

Edited for grammar and style.

Edit pass for grammar and style

* upd

* rm redundancy:

* upd

* Edit for readability

* giant_graph_readme edit for grammar

* NodeFlow and Sampling edit pass for grammar

* Update tutorials/models/1_gnn/9_gat.py

* Update tutorials/models/1_gnn/9_gat.py

Revisions for grammar and style

* Update contribute.rst

* Update contribute.rst

* Update contribute.rst

* Update contribute.rst

* Edit pass

Updates for grammar and readability

* Update tutorials/models/1_gnn/6_line_graph.py

* Update tutorials/models/1_gnn/6_line_graph.py

* Update tutorials/models/1_gnn/6_line_graph.py

* fix

* unit test

Grammar and style updates

* To(device) should return updated object

* Add test case and doc

* Add another doc

* Add descriptions  and a test

* Pass test

* Edit for grammar and style

Improve readability

* Update tutorials/models/1_gnn/README.txt
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/models/1_gnn/README.txt
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Edit for grammar and style

Improve the flow and readability

* Update docs/source/features/nn.rst

Better now? NN Modules as a title is vague

* grammatical updates

Edit pass for readability. 
Can you clarify: "are of different, but shapes that can be broadcast." Are they of different shapes, but both can be broadcast?

* Update docs/source/features/builtin.rst

Okay now? Check this for logic.

* Edit for grammar and style

As with other tutorials, it would help the reader if you add a paragraph in the opening section about assumptions or prerequisites.

Does this refer to SageMaker Ground Truth feature? "...assigns its ground truth label..." If yes, phrase it thus: assigns its Amazon SageMaker Ground Truth label

* Update tutorials/basics/4_batch.py

* Update tutorials/basics/4_batch.py

* Update tutorials/basics/4_batch.py

topologies

* Update tutorials/basics/4_batch.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Grammar and style edit pass

In the opening, it would be great to provide some rationale for why you recommend conda or pip.

* Update docs/source/install/index.rst
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update docs/source/install/index.rst
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update docs/source/install/index.rst
Co-Authored-By: Aaron Markham <markhama@amazon.com>

fix minor error: GCNLayerSAGE->GraphSAGELayer

* Update

* Update

* Update

* Fix

* CI style fix

* CI fix style

* Fix

* Try CI

* Fix test

* Update

* Update

* Update

* Update

* [Example] Finish adaptive sampling

* refactor code and use argparse for command-line usage

* Update README.md

* add node_per_layer command-line argument

* Update

* Try CI

* Edit for readability

Edit pass for grammar and style. 
* A great value-add would be to provide assumptions and prerequisites in the opening section. This helps readers understand what they need to have in place in order to make use of your tutorial steps.
* The wikidata knowledge graph could be improved with a smaller font for the Zuckerberg circle.

* Update tutorials/hetero/1_basics.py

* Update tutorials/hetero/1_basics.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/hetero/1_basics.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/hetero/1_basics.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/hetero/1_basics.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

* Update tutorials/hetero/1_basics.py
Co-Authored-By: Aaron Markham <markhama@amazon.com>

Can you add a link for the download to this sentence: You can also `download <location?>` and run the different code examples...
As with other tutorial topics, it would be helpful to add your assumptions or information in the opening section about prerequisites.

* Edit for grammar and style

In the opening paragraph, it would be helpful to provide some overall scenario and the prerequisites you expect readers to have completed before they start here. "This tutorial assumes you have already..." Add a link to Install DGL topic perhaps and any other framework or IDE or even specialized knowledge. With this context, you help readers to succeed by setting expectations.

Better to group all tutorials (this, PageRank with, Batched Graph, Working with) at the same level in the left navigation rail and all as subsections of DGL Basics.

* Update tutorials/basics/2_basics.py

Add RotatE support for KGE (apps/kg)
Performance Result:
Dataset FB15k:
Result from Paper:
MR: 40
MRR: 0.797
HIT@1: 74.6
HIT@3: 83.0
HIT@10: 88.4

Our Impl:
MR: 39.6
MRR: 0.725
HIT@1: 62.8
HIT@3: 80.2
HIT@10: 87.5