Re: Working with a huge Graph object

The way you prune a Graph depends on what you want to do with it. If you only need to look at local properties, you can look at clusters around a single node. Frequently you can collapse a completely connected set of nodes into a single composite one. Another strategy is cook up a way to classify nodes by purpose and restrict the graph to a subset by class.

What are you trying to extract from the graph?

After Compline,
Zaxo

Comment on Re: Working with a huge Graph object

Replies are listed 'Best First'.
Re: Re: Working with a huge Graph object by sgifford (Prior) on Dec 02, 2003 at 05:08 UTC
We're not sure yet what we want to extract. It's a bit of exploratory programming for a research group, and we won't really know what will turn out to be interesting until we've got a first draft implementation. We'd like to be able to do things like find the shortest path between two Web pages, find the longest shortest path between Web pages, find how many pages link to a page, how many links a page contains; standard graph theory sort of stuff, which is why we started with the Graph class.	[reply]

Replies are listed 'Best First'.

Re: Re: Working with a huge Graph object
by sgifford (Prior) on Dec 02, 2003 at 05:08 UTC

We're not sure yet what we want to extract. It's a bit of exploratory programming for a research group, and we won't really know what will turn out to be interesting until we've got a first draft implementation. We'd like to be able to do things like find the shortest path between two Web pages, find the longest shortest path between Web pages, find how many pages link to a page, how many links a page contains; standard graph theory sort of stuff, which is why we started with the Graph class.

[reply]