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
and distinguish between singly-partitioned vs. more nested partitionings. Having a function that flattens nested partitioned network into a single ITensorNetwork would be helpful as well.
A related function we have for dealing with nested partitioned tensor networks is nested_graph_leaf_vertices, which works like this:
vertex_groups =nested_graph_leaf_vertices(tnpp)
for finding groups of vertices but maybe the API should be rethought since it's a confusing name.
The text was updated successfully, but these errors were encountered:
Another idea would be to add a way to call partition and specify that you want to make sure that certain vertices are grouped together. An interface could be:
to make sure that vertices (1, 1), (2, 1) are grouped together and [(3, 4), (4, 4)] are grouped together. This could be implemented by first partitioning the graph according to the grouping (treating unspecified vertices as groups of 1), partitioning that partitioned graph, and then regrouping based on the functionality in the first post of this issue.
For example, something we want to do is be able to flatten a doubly-partitioned tensor network into a singly-partitioned tensor network:
It would be nice to define a function that flattens a partitioned ITensorNetwork:
and then make sure
map_vertex_data
works for this case (which currently errors if the vertex data type changes), so we can do:map_vertex_data(ITensorNetwork, tnpp)
Other ideas would be to define a
PartitionedITensorNetwork
so we can dispatch on that type:and distinguish between singly-partitioned vs. more nested partitionings. Having a function that flattens nested partitioned network into a single
ITensorNetwork
would be helpful as well.A related function we have for dealing with nested partitioned tensor networks is
nested_graph_leaf_vertices
, which works like this:for finding groups of vertices but maybe the API should be rethought since it's a confusing name.
The text was updated successfully, but these errors were encountered: