You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TRANSITIONGUIDE.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,21 +2,21 @@
2
2
3
3
## Python API
4
4
5
-
This release introduces new concepts in the API and improves user experience through more automation and better DataFrame support. Python users are encouraged to review these changes and potentially upgrade their code before using 0.11 verison.
5
+
This release introduces new concepts in the API and improves user experience through more automation and better DataFrame support. Python users are encouraged to review these changes and potentially upgrade their code before using 0.11 version.
6
6
7
7
### New graph types
8
8
The Python API now has `Graph` (undirected) and `DiGraph` (directed) types. This is closer to NetworkX's API.
9
9
10
10
In the past, directed graphs were stored using the `Graph` type.
11
11
Starting in 0.11, `DiGraph` should be used for directed graphs instead. `Graph` only refers to undirected graphs now.
12
12
13
-
The `Multi(Di)Graph` types were added and more support this new structure will be added in the next releases (more details on that in issue #604).
13
+
The `Multi(Di)Graph` types were added and more support this new structure will be added in the next releases (more details in issue #604).
14
14
15
15
### Undirected graphs
16
16
cuGraph automatically "symmetrize" undirected inputs: each undirected edge (u,v) is stored as two directed edges (u,v) and (v,u).
17
17
18
18
When viewing the graph or requesting the number of edges, cuGraph will currently return this symmetrized view.
19
-
This is an implementation detail that will be hidden to the user in 0.12 (more details on that in issue #603).
19
+
This is an implementation detail that will be hidden to the user in 0.12 (more details in issue #603).
20
20
21
21
### Loading an edge list
22
22
Users are encouraged to use `from_cudf_edge_list` instead of `add_edge_list`.
@@ -26,15 +26,13 @@ In this case all analytics outputs are automatically un-renumbered before being
26
26
27
27
## C++ API
28
28
29
-
This release is the first step toward converting the former C-like API into a C++ API. Major changes have been made. C++ users should review these changes and upgrade their code before using 0.11 verison.
29
+
This release is the first step toward converting the former C-like API into a C++ API. Major changes have been made, C++ users should review these changes and upgrade their code before using 0.11 version.
30
30
31
31
- All C++ API functions are now encapsulated in namespace `cugraph`
32
32
- All functions are now processing errors through exceptions. As a result, `gdf_error` is no longer used as a return type, `void` is used instead.
33
33
-`gdf_graph` is now `Graph`. The content of the structure is still the same (will be upgraded in future releases).
34
34
-`gdf_` prefix has been removed from all C++ API functions.
35
35
36
-
The C++ API provides functions that efficiently convert between data formats and access to the efficient CUDA algorithms. Automatic conversions and decision making has been removed from the C++ layer.
The C++ API provides functions that efficiently convert between data formats and access to the efficient CUDA algorithms. In 0.11, all automatic conversions and decision making were removed from the C++ layer.
45
+
46
+
46
47
## Directory Structure and File Naming
47
48
`c_` prefix of all `.pxd` files have been removed.
0 commit comments