Closed dlcole3 closed 1 year ago
Merging #36 (da95ea3) into main (136750a) will decrease coverage by
0.04%
. The diff coverage is100.00%
.
@@ Coverage Diff @@
## main #36 +/- ##
==========================================
- Coverage 93.58% 93.55% -0.04%
==========================================
Files 9 9
Lines 1716 1692 -24
==========================================
- Hits 1606 1583 -23
+ Misses 110 109 -1
Impacted Files | Coverage Δ | |
---|---|---|
src/DataGraphs.jl | 100.00% <ø> (ø) |
|
src/datadigraphs/interface.jl | 100.00% <ø> (ø) |
|
src/datagraphs/interface.jl | 100.00% <ø> (ø) |
|
src/datadigraphs/core.jl | 95.20% <100.00%> (-0.84%) |
:arrow_down: |
src/datadigraphs/utils.jl | 97.21% <100.00%> (ø) |
|
src/datagraphs/core.jl | 87.25% <100.00%> (-2.44%) |
:arrow_down: |
src/datagraphs/utils.jl | 91.79% <100.00%> (ø) |
|
src/functions.jl | 94.24% <100.00%> (+1.71%) |
:arrow_up: |
src/interface.jl | 97.67% <100.00%> (+0.70%) |
:arrow_up: |
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.
Addd
get_node_data
andget_edge_data
functions for getting full matrices or vectors of data from theNodeData
andEdgeData
.Currently, edges are added to the
dg.edges
vector in the order they are passed to theadd_edge!
function. However, in some cases, it is valuable to sort the edges by what node they correspond to (i.e., edges connected todg.nodes[1]
show up first, followed bydg.nodes[2]
, etc.). For example, this is useful in GNNs, which might take a SimpleGraph object and construct the edges in the order they appear. I added functionsorder_edges! which rearranges the order of the edges in place, and I added a
get_ordered_edge_data` set of functions for returning the matrix/vector in the desired order.