Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
OpenDAS
dgl
Commits
17f86356
Unverified
Commit
17f86356
authored
Mar 21, 2021
by
Da Zheng
Committed by
GitHub
Mar 21, 2021
Browse files
fix (#2744)
parent
74c38a1f
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
3 deletions
+5
-3
docs/source/guide/distributed-preprocessing.rst
docs/source/guide/distributed-preprocessing.rst
+5
-3
No files found.
docs/source/guide/distributed-preprocessing.rst
View file @
17f86356
...
@@ -22,9 +22,11 @@ in a format that is easy to load during the training.
...
@@ -22,9 +22,11 @@ in a format that is easy to load during the training.
By default, the partition API assigns new IDs to the nodes and edges in the input graph to help locate
By default, the partition API assigns new IDs to the nodes and edges in the input graph to help locate
nodes/edges during distributed training/inference. After assigning IDs, the partition API shuffles
nodes/edges during distributed training/inference. After assigning IDs, the partition API shuffles
all node data and edge data accordingly. During the training, users just use the new node/edge IDs.
all node data and edge data accordingly. After generating partitioned subgraphs, each subgraph is stored
However, the original IDs are still accessible through ``g.ndata['orig_id']`` and ``g.edata['orig_id']``,
as a ``DGLGraph`` object. The original node/edge IDs before reshuffling are stored in the field of
where ``g`` is a DistGraph object (see the section of DistGraph).
'orig_id' in the node/edge data of the subgraphs. The node data `dgl.NID` and the edge data `dgl.EID`
of the subgraphs store new node/edge IDs of the full graph after nodes/edges reshuffle.
During the training, users just use the new node/edge IDs.
The partitioned results are stored in multiple files in the output directory. It always contains
The partitioned results are stored in multiple files in the output directory. It always contains
a JSON file called xxx.json, where xxx is the graph name provided to the partition API. The JSON file
a JSON file called xxx.json, where xxx is the graph name provided to the partition API. The JSON file
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment