That looks very nice and fills a major gap in the expository literature.
You might consider changing the title to "A primer on computational group
homology and cohomology using GAP and Sage".
William
I've added a link for this cool project here:
Let me know if you want me to change anything.
Perhaps you'll want to make all the data available as a database
as part of Sage at some point?
William
Doxygen is as you know for C/C++, not Python. There are some tools
like Doxygen for Python, but in my experience they always fall apart
on something as complicated as Sage.
Sage itself can crate the class diagram associated to all objects
in any given module:
sage: g = class_graph(sage.rings.polynomial)
sage: h = Graph(g)
sage: h.plot3d_new(vertex_size=0.01, edge_size=0.001)
However the above isn't labeled (and it is stupid that one must
tweak the vertex and edge sizes to see anything).
It could be labeled though, since our
new 3d plotting code has good support for labels.
This has labels, but they size and spacing is so terrible by default
that one can't see any of them.
sage: h.plot()
-- William
Mind you , that is not very easy and requires quite a lot of Python
knowledge, as I am discovering in doing the same job on my modular
symbols C++ code.
John
--
John Cremona
That's not necessarily true. You can wrap C++ code but have it
fit nicely into the Sage class heiarchy. See, e.g., finite_field_givaro.pyx
in the Sage source tree.
> In fact, it's not so much that there is a lot of code to define an
> unstable algebra, it's rather that i don't feel i have (just now) the
> competence to merge it gracefully into Sage.
We really need to make it easier for developers to get up to speed
with Sage! Now is definitely the time...
William