Hi Tiago, It seemed reasonable that one might want to review the results of a MixedMeasuredBlockState with respect to the original graph. For instance, perhaps I have certain vertex or edge properties within my original graph object I want to review for association to this model's collected eprobs. Another example, perhaps I want to run both the Measured and MixedMeasured and compare/contrast the eprobs from the marginals stored as separate edge properties on the graph. Is there a way to marry up these results of the MixedMeasuredBlockState eprob back to the original graph? Unless intuitive syntax within GraphTool I am not aware of, I suppose it would be a case of pulling out the edge list from the original and the model, then taking the union of that. Thanks, James
On 15 Jun 2020, at 13:04, Tiago de Paula Peixoto <tiago@skewed.de> wrote:
Am 15.06.20 um 13:36 schrieb James Ruffle:
How do you manage to get around this issue? Presumably there is a simpler way with the graph-tool syntax than forlooping everything and matching edges up between the two graphs…?
Obviously, the reconstructed graph is different from what has been measured. Before we talk about how to do anything efficiently, can you first explain what "get around" this issue means? How do you expect two graphs with a different set of edges to share the same edge property map?
-- Tiago de Paula Peixoto <tiago@skewed.de>
_______________________________________________ graph-tool mailing list graph-tool@skewed.de https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.skewed.de%2Fmailman%2Flistinfo%2Fgraph-tool&data=02%7C01%7C%7Ca40eb653a66d4a13b1de08d811243b7d%7C569df091b01340e386eebd9cb9e25814%7C0%7C0%7C637278194597163832&sdata=%2FpT2HHNjjf9gGIOIkx8LzmDPwkNALPJibGjEvInJoag%3D&reserved=0