Better Specific Pimms Outputs

[36000]

Once GroupAFQ or ParticipantAFQ is instantiated, you can:
1. Make a dependency graph picture
2. See all things that are potential to export, for this instance only
3. And for a representative GroupAFQ, we can make a docs page of # 2

[arokem]

I'd suggest using pygraphviz to lay out the graphs. Seems to me like something that belongs in Pimm's itself? Cc: @noahbenson

[noahbenson]

The new pimms is immlib (here, and preliminary documentation here), which will probably have its v1 release by mid-June.

pygraphviz is so full-featured (so many ways to render a graph) that I'd need to think hard about how to write something appropriately useful-yet-flexible into immlib, but for now I'll be sure to add a method that returns a clear / easy-to-use graph representation so that anyone who wants to can quickly make a pygraphviz object from an immlib.plan object.

In immlib, unlike in pimms, the immutable-object type is called a planobject and has a member obj.__plan__ that is just its calculation plan. In pimms, you'd need to write a separate version of this for plans and immutable classes, which have separate backends despite being basically the same thing.

Right now, are you mostly using the pimms calcs and plans or immutable classes? I can at least send you a bit of code to extract the graph representation from the internals.

[36000]

We use pimms calcs and plans. That would be good, but no rush!