You're reading the public-facing archive of the Category Theory Zulip server.
To join the server you need an invite. Anybody can get an invite by contacting Matteo Capucci at name dot surname at gmail dot com.
For all things related to this archive refer to the same person.
Very basic question. According to the definition here: http://math.ucr.edu/home/baez/structured/,
given a functor , a structured cospan is a diagram in of the form .
At first this looks like a co-cone with apex , but obviously it's not, because is a functor from , not from a two-element discrete (shape) category (except when itself is that). Nevertheless, is there a way of seeing it as a co-cone?
(I felt this would be out of place in the post-talk discussion, since it's quite basic and probably moves away from the actual focus of the talk, so I'm asking it now)
If is the discrete category with 2 elements, and is the diagram that picks out and then a cocone under is a diagram of the form .
I'm not sure if that really answers your question though.
Ah, that's perfect. I thought a composition might work, but I kept thinking (even now after seeing your answer) that would be somehow lost in the process
Not exactly, but the information from . Hm, I see it now. Thank you!
There are different things to say about this but here's one: given any functor there's a category of structured cospans, i.e. diagrams and the sort of obvious morphisms between such diagrams. Moreover this category is a comma category. Daniel Cicala showed this category under some conditions is a topos:
Notice this is a category where structured cospans are objects, whereas I'm more interested in treating them as morphisms. But both viewpoints are reconciled in the double category I'll discuss in my talk!
This is another question about structured cospans, so I thought it might fit here. Let me know if it should be moved to a new topic.
(Disclaimer: I'm very new to category theory...any corrections/insights are much appreciated)
If I understand correctly, a structured cospan can be thought of as some object together with "allowed connections" or "connection interfaces" given by and . We can then stick these objects together along their interfaces (provided they have compatible interfaces) by working in a category where these cospans are morphisms and composition corresponds to taking a pushout.
In applications, some objects have more than two allowed connections. For example, consider an electrical circuit that has the following three connections: input, output, and reset. Does this structured cospan approach support modelling of these kinds of networks?
(My initial guess is "yes, but it gets more complicated": I guess the new morphisms would consist of a circuit object together with three maps , and, . Maybe composition would work in the same way (using a pushout with respect to the connecting interface), although we do have the additional wrinkle that the number of interfaces a circuit has can change upon being composed with another circuit. For example, if circuit A has input, output and reset interfaces, and circuit B also has input, output and reset interfaces, then connecting the output of circuit A to the input of circuit B yields a new circuit with four interfaces: input_A, reset_A, output_B, reset_B. So, I guess if we want to support flexible connections between circuits with three interfaces, we need to be able to support connection between circuits with any finite number of interfaces (?).)
This is a good place for talking about structured cospans, I'd say!
If I understand correctly, a structured cospan can be thought of as some object together with "allowed connections" or "connection interfaces" given by and . We can then stick these objects together along their interfaces (provided they have compatible interfaces) by working in a category where these cospans are morphisms and composition corresponds to taking a pushout.
That's exactly right.
In applications, some objects have more than two allowed connections. For example, consider an electrical circuit that has the following three connections: input, output, and reset. Does this structured cospan approach support modelling of these kinds of network?
Yes! And that's crucial, because for almost any kind of network that comes up in practice we need to allow objects with more than two connections.
We handle this using the fact that when and have finite colimits and is a left adjoint (the case worth keeping in mind), the structured cospan category is a monoidal category. This lets talk about morphisms from a finite set of objects to a finite set of objects.
Furthermore, this category is compact closed. This lets us change our mind and reinterpret some inputs as outputs or vice versa if we feel like it, and also permute the order of inputs or outputs.
Even better this category is a hypergraph category. This lets us do even more fun things that we often want to do with networks!
All this is proved in the paper Structured cospans.
Thanks! (I'll have to do some reading to more fully understand.)
All these concepts (which I just added links to, so now they're in blue) are really important for understanding categories where the morphisms are networks. Brendan Fong's thesis is a good introduction to all of them, I think - he defines them all and explains why they're important.
That's two talks on 1 April I need to watch, then (the other is Kevin Buzzard's, advertised in the Lean and HoTT Zulip chat rooms/spaces/etc). All this ability to watch seminars from around the world is taking up so much time! ;-)
If I succeed in recording my talk and putting it on YouTube, I'll record my talk and put it on YouTube.