Hi,

I have a question about the order of motifs, their counts and maps returned
by clustering.motifs.

I have a graph in which vertices and edges have some properties:

(Pdb) grafo
<Graph object, undirected, with 23 vertices and 19 edges at 0xb06088c>

I asked the motifs of this graph, with the following instruction:

(Pdb) motivos, counts, vm = gt.motifs(grafo, k, return_maps=True)

And I got the motifs, counts an vertex mappings as described below:

*** 6 mofits
(Pdb) motivos
[<Graph object, undirected, with 4 vertices and 3 edges at 0xb066cec>,
<Graph object, undirected, with 4 vertices and 3 edges at 0xb066cac>, <Graph
object, undirected, with 4 vertices and 3 edges at 0xb066aec>, <Graph
object, undirected, with 4 vertices and 3 edges at 0xb066bcc>, <Graph
object, undirected, with 4 vertices and 3 edges at 0xb066d8c>, <Graph
object, undirected, with 4 vertices and 3 edges at 0xb066e2c>]

(Pdb) len(motivos)
6

*** The counts of these motifs
(Pdb) counts
[6, 1, 7, 9, 2, 2]

***The vertex mappings
(Pdb) len(vm)
6

(Pdb) len(vm[0])
7
(Pdb) len(vm[1])
6
(Pdb) len(vm[2])
9
(Pdb) len(vm[3])
1
(Pdb) len(vm[4])
2
(Pdb) len(vm[5])
2

I thougth that there was a correspondence between the positions of motifs,
counts and vertex mappings. For instance: The motif in the position
motivos[0] occurs counts[0] times (which means 6 times) and the 6
occurrences of this motif is in vm[0].

Inspecting the length of vm, I realized that it is according to values in
the counts, but not in the same order. 

Is it the expected behavior of  clustering.motifs?


Thank you for any help you can provide.

Sabrina



--
View this message in context: 
http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com/Order-of-motifs-counts-and-vertex-mappings-in-clustering-motifs-tp4025641.html
Sent from the Main discussion list for the graph-tool project mailing list 
archive at Nabble.com.
_______________________________________________
graph-tool mailing list
[email protected]
http://lists.skewed.de/mailman/listinfo/graph-tool

Reply via email to