As far as measures on diamond spaces and Leinster weights are concerned:
I feel rather uneasy about this approach for various reasons—which probably just shows I don’t understand what you’re trying to do. But I’ll mindlessly articulate two of my concerns anyway and see where it leads …
First: if the weighting or coweighting is supposed to be some sort of ‘curvature’ which one integrates over the space to get the Euler characteristic as a total curvature, one would expect the weighting or coweighting of an -diamond space to be everywhere (except perhaps at boundaries), seeing as these are surely supposed to be flat spaces.
Second: in an -diamond space, why would we include only the underlying graph of 0-cells and 1-cells, and leave out the faces, -cells, etc?
Starting by very naively applying this philosophy to -diamond spaces, we say we have a vertex, contributing to its local Euler characteristic (or ‘curvature’), incoming (or outgoing) edges contributing each, and one incoming face giving a contribution of Totalling we get as expected.
Less naively, lets try and do this properly.
Consider a -category with objects and with two morphisms and one -morphism,
We’ll consider this to be a -graph, and try to generalise the algorithm we developed for -graphs. Hopefully this should instantiate something sensibly algebraic on the -graph’s -category, though I haven’t tried to work this out yet.
So we try a 2-step procedure. First, assign weights (or co-weights) to the edges, according to the rule “weight = -number of incoming (or outgoing) -edges”. Then we assign weights (or co-weights) to the vertices, taking the weights on the edges into account.
I’ll go with co-weights (based on incoming -edges) since that’s what I’m used to. Step 1 assigns a weight of 1 (no incoming -edges), and assigns a weight of (1 incoming -edge).
Then step 2 assigns vertex the value 1 (no incoming edges), and assigns a weight of … well, let’s see … So the vertex total is which is correct, since our -graph is topologically a disc.
So lets add a second -edge parallel to the first, so we get a sphere. Then is still assigned a weight of and , with incoming -edges, gets assigned a weight of Now, checking the vertices, still has a weight of and has a weight of So totalling the weight of and we get which, for a sphere, is right.
I wanted to show some pictures of more complicated -graphs but, gads, the graphics capabilities of this interface are worse than ASCII-art, so I just drew some pictures on paper. You may imagine me looking at them now …
A couple of issues arise in the more general situation. What exactly are the -edges? The reasonable answer, I think, is that we make them polygons whose boundaries are made up of the (-)edges. In fact, just to simplify things, I only considered the case where every -edge is part of the boundary of at least one -edge, though I sincerely hope this isn’t essential for the process to make sense. Since the -edges and vertices generate a poset, each polygonal boundary has a single ‘source’ and a single ‘target’ vertex, with respectively two edges of the polygon leaving and two edges entering; all other vertices will have one leaving and one entering. So there is no doubt which morphisms (that is, which catenations of edges) act as source and target of the polygonal -morphism; the only decision to make is which is source and which is target: we need an orientation. In keeping with the situation with edges and vertices, we want the -morphisms to organise the edges as a poset; we want to avoid cycles.
However, the way we are proceeding, we are trying to assign weights to edges, not to morphisms. Hopefully this will fall in some nice inclusion-exclusion way out of the algebra, but at the moment I don’t have an algebra, just a candidate algorithm. Since the -morphism acts between two -morphisms which may well be catenations of edges, we need to decide how the weight gets shared out. A bit of thinking and playing around makes me reasonably confident that we assign -1 to an edge for each incoming (or, dually, outgoing) -morphism whose target morphism has the same target vertex as the edge itself; in other words, to the last edge in the catenation making up the morphism. The other edges don’t get any contribution to their weight due to that -morphism (i.e. polygon).
At this point, I would draw a cube, with its vertices, edges and faces, and start assigning orientations and weights, but I can’t face trying to draw one here, so I will leave this as a slightly fiddly but interesting exercise for the reader, and simply report what I found. The end result is that the edge weights are somewhat opaque in their significance (at least to me) but the vertex weights are of crystalline clarity. I have just one vertex with only outgoing edges, and one vertex with only incoming edges, and each of these gets assigned a weight of 1; the remaining vertices all get assigned a weight of 0. This gives an Euler characteristic of 2, which is right, since the cube is topologically a sphere.
This is now starting to look increasingly Morse-like, so I tried one more configuration equivalent to a sphere: the ‘pair of pants’ (or, as Terry Pratchett likes to call them, the ‘trousers of time’) with the three holes capped off with -cells.
This is how I did it, in case you want to check:
I started by hanging the trousers upside-down, and drew a seam down the outside of the left leg all the way to the waist. I put vertices at the top (on the hem of the trouser-leg), at the bottom (on the waistband) and halfway down. That gives two edges, which I directed to point down. I did the same on the right side. Then I put a seam down the inside of each leg, meeting in a vertex at the crotch, and put another vertex at the top of each of them. Again, the edges are directed downward. At the end of each leg, we now have two vertices, and I put two edges in, directed from the outside vertex to the inside vertex, one around each side of the hem. I ran two edges around the waistward end of each trouser leg from the outside vertex (the one halfway down the outer seam) to the vertex at the crotch, again one edge on the front of each trouser leg and one edge around the back. All these edges I directed from left to right. I also put left-to-right-directed edges around the front and back of the waistband. I closed off the waist end ends of the trouser-legs with -cell caps.
The -cells consist of three bigons (the leg and waist caps), four rectangles, (the front and back panels of each leg), and two pentagons (the front and back of the waist).
Then I assigned edge weights and vertex weights.
The edge weights were again a bit opaque but the vertex weights were: on the outer vertex on the hem of each trouser leg—i.e. the vertices with only outgoing edges; on the right vertex on the waistband—i.e. the vertex with only incoming edges; on the vertex at the crotch; on all other vertices. This correctly gives a total of Interestingly, the picture was essentially unchanged when I reversed the direction of all the -edges (while keeping the orientation of the -edges the same). Or rather, unchanged in an interesting way: the edge weights changed a lot, but the vertices still got assigned weights of if their edges were all incoming or all outgoing, at the crotch, and elsewhere.
This selection doesn’t involve much variety (only spheres! Oops!) but it does tend to confirm that the Leinster weights (or coweights) and the partial ordering are doing something analogous the work of Morse functions on a manifold, i.e. detecting singular behaviour or something like that, and picking out odd and even indices. Except we have something a bit more general: not only analogies to the singular behaviour on slices through smooth manifolds (as determined by contours of a Morse function), but also handling manifolds with boundaries, and spaces made of manifolds glued together along boundaries. Since triangulations, or other ways of chopping spaces into contractible polytopic pieces, are of exactly this sort, the Leinster approach seems to mediate between the Morse function approach and the triangulation approach to calculating Euler characteristics.
I guess it’s likely this stuff is already well-known; but not to me …
Re: Isham on Arrow Fields
I’ll incorporate the following comments tomorrow, when I am less tired:
The entire discussion in section 4.3 of Chris Isham’s paper amounts to saying that with the morphisms of regarded as paths between its objects (which is the relevant interpretation for Isham’s purposes), a functor is a hermitean vector bundle with connection on .
However, this is not the way Chris Isham puts it. The connection part he calls a “multiplier” and instead of thinking of a parallel transport functor he thinks of this functor as a presheaf.
I don’t really follow the reasoning behind this. Thinking of the above functor as a presheaf would imply thinking of as a site. But this is not the role played by in the rest of the discussion:
rather plays the role of the configuration space of some physical system (and not of a site of open sets on that configuration space).
The discussion around equation (83) then amounts to noticing that a transformation is not just a section of this bundle, but a flat section.
This is a general issue, which I also do discuss for instance in that Rosetta stone section 1.2:
when we want to form the space of states in our arrow-theoretic formulation of quantum mechanics, we need to pass from the category of “configurations and paths between configurations”, which in my terminology is the category of functors from parameter space into target space (for the present case the parameter space is simply the point so that )
to the subcategory the true configuration space, which contains only morphism between configurations that we want to regard as physically equivalent.
That’s the difference between all “cobordisms” (processes) between configurations (morphisms in ) and the morphisms in , which are the processes that are “pure gauge”.
So, this is why I keep going on about why specifying a physical system arrow-theoretically involves not just choosing a target space and a bundle with connection on that, but also a sub-category of the category of all processes in target space. That’s why I define # a physical system as a situation of the form and then give a prescription for computing the space of states which involves first pulling back (Isham’s “multiplier”!) back to configuration space and then taking its sections.
All this is, secretly, the issue discussed around equations (83)-(84) in Chris Isham’s paper.
It’s a not a particularly complicated issue, but I think it pays to try to extract a clear picture here.
I am making this comparison with Isham’s ideas here also in the hope that it will help our mutual understanding, in the light of John’s remarks at the end of this comment.