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.
@Jonathan Beardsley or anyone else, can you tell me what a properad is?
Sure, so let's think about one way to define an operad: as a functor from a category of trees to the category of sets (or spaces, if you want topological operads or something)
And by tree here, I mean a rooted tree.
Like this: Y
So one "downward root" and then some collection of leaves.
Let's see... to actually give this in any reasonable detail I'd have to probably think/read for a little bit...
I'd also have to tell you about the morphisms in the category of trees.
I guess one important thing to know is that the category of trees actually extends the classical simplex category $\Delta$
Hm, that didn't work.
Where we can think of as being the category of linear trees.
There are a lot of morphisms between the trees, but they're generated by a nice collection of morphisms, just like you have with
Basically, you can "contract a branch" and you can "insert a degenerate node" into a branch.
(the only place I know that this stuff is written down is in Moerdijk's stuff on dendroidal sets)
And so if we call this category then an operad is a presheaf on satisfying certain conditions.
Reading along as I make a salad :salad:
Haha, I think you're also reading a (word) salad.
Are you familiar with this way of describing operads?
Like, basically, your presheaf takes the one-vertex tree with n leaves, call it , to your set of n-ary operations.
Not exactly, but I'm liking it so far.
But then you have to know what to do with all the other trees, and the maps between them.
But so let's take a simple example.
Let's say I've got the binary tree Y, and then I've got another tree which is the binary tree Y with its root stuck into its top right leaf
I guess I should say
And so then I have another tree which looks like plugged in to itself. Let's call it maybe for obvious reasons.
Well it's hard to say without drawing a picture, but by "contracting" the branch on which was originally the root of the upper , we can create
This all makes sense. I think this formalizes the basic way I describe operads to people pictorially.
So, in there's this morphism , which when we take a functor out of turns into "composition."
I.e. the set of operations of "shape" needs to come equipped with some kind of map to the set of operations of shape
Sorry, my daughter just came in and started pushing buttons on my computer.
So right, maybe you can see how the above goes. There are "face" and "degeneracy" maps in and then you can talk about a "dendroidal set" or "dendroidal object" wherever you like.
(it turns out that is a generalized Reedy category, so functors out of it into, e.g., Quillen model categories, have nice properties)
Okay so anyway, the EXTREMELY brief description of properads is: do all of that again, but with graphs instead of trees.
Now, you have to be careful about what you mean by "graphs" of course, just as we had to be careful about what we meant by "trees."
So the way that it extends is that you can think of an finite ordinal as a line graph?
Ah right but we have to be careful I think.
Let me see here.
There's some subtlety here that I usually mess up.
So in this framework, the "branches" are the "colors" I think, for instance if you wanted to do a colored operad.
And the vertices of the trees are the "operations"
So I think, for instance, we want to think of, in , the object as the "tree" that looks like
And as the "tree" that looks like
Now there are two injections of into which become "face maps" in simplicial sets
And in the context of simplicial sets we think of them as "projecting down onto a face of the 1-simplex," i.e. telling us which of all the 0-simplices in a simplicial set "belong" to that particular 1-simplex.
But here, we want to think of the morphism (in ) as being something like "the two ways to contract a branch to get from , if I'm recalling correctly.
So there are sort of... ALMOST dual geometric interpretations
As a tree, the face maps are contracting branches, as a simplicial set, they're projecting to a face.
But so anyway, you can see in that there's something special about the trees .
And for something to actually be an operad, you need it to satisfy a sort of "Segal condition." This corresponds to the fact that a functor out of satisfying the Segal condition is a monoid. I.e. it has a reasonable notion of "composition."
In that case, the Segal condition says that the image of needs to be the n-fold Cartesian product of the image of .
And then magically the face and degeneracy maps turn into the structure maps of a monoid.
(this is, of course, assuming that , without which you just get a category!)
So yeah, maybe a better way to say this is that with the Segal condition, a simplicial set is a category.
(and a Simplicial space is an -category)
(and a category with one object is a monoid)
But so now, okay, in that case, the object goes to the "set of objects of the category."
In the case that we're thinking of as being in , we want to go to the "set of colors of the operad."
(or equivalently, the set of objects of the multicategory)
And then you have a whole bunch of trees that can, in many different ways, "contract their branches" to end up just giving you a single branch, i.e. a single "color."
So given a tree, there are a whole bunch of "face maps" that tell me what its output and input colors are.
And basically what the Segal condition is doing here is saying that the image of some arbitrary tree needs to be able to be constructed by "gluing together" the basic trees .
And so then in the properad situation, we replace the trees with the "corollas" , each of which looks like a single vertex with n inputs and m outputs.
And these have the obvious "edge contraction" and "vertex insertion" maps.
I know what a properad is
But, again, the functor out of our category of graphs has to take to the "set of operations with n inputs and m outputs" and then we have all kinds of "composition" things to do.
Well yeah @philip hackney is a FAR better resource for this stuff than I am.
He literally wrote a book on properads.
And all I'm really doing is regurgitating all the reading I did three years ago in preparation for going to Australia to talk to him and Marcy Robertson.
haha I didn't jump in just to make jb feel self-conscious
It's okay. Also I have no idea if anyone is even reading anymore.
And my "work time" is almost up now anyway. Gotta go be a dad. I was "supposed" to be grading a quiz. Whoops.
I'll try to pop back in later on today to see if @Joe Moeller came back
I'm certainly still reading :)
Oh! OKay well I'll come back a bit later today when I have more time
I'm just butting into the conversation here, but can a properad be described as a special kind of dioperad, or are they not related like that?
@Nathanael Arkor dioperads are a special kind of properad
oh, is there a specific name for a coloured properad, analogous to a polycateory for a dioperad?
where, if I recall correctly, you can only "compose by attaching two edges at a time"
@philip hackney Ah, please don't inconvenience yourself for my sake. I'm happy sucking up whatever knowledge falls off between you, Jonathan and Joe.
in a properad, you can attach any collection of outputs to any collection of inputs
also, properads are generally always "colored"
@philip hackney is there a special name for a properad with one color?
so you've got "operad = 1-colored multicategory" and "dioperad = 1-colored polycategory" and then "properad = properad"
I think.
where, if I recall correctly, you can only "compose by attaching two edges at a time"
oh, is this analogous to the situation where you can present operads in either a "partial" or "full" style?
I'm not sure.
I think there are properads that are NOT dioperads.
Like, basically you can attach one edge at a time in a dioperad, but I sort of think there are properads with composition operations that cannot be built up in this way
"properad = properad"
ah, it's sad if the naming convention isn't "-ad" = one-coloured
sort of think there are properads with composition operations that cannot be built up in this way
oh, I'd be very interested to see an example
I was under the impression that the partial and full styles of operads were equivalent, at least
Yeah, I'm not 100% sure off the top of my head. Again, @philip hackney really would be the guy to ask here.
(but that may not be the analogous situation anyway)
The Segal condition for is what I normally call " is the Lawvere theory for monoids."
I finished my salad, so now I'm back.
So I'm sorta confused what the difference between a properad and a prop is.
I think this distinction is especially important for me, because I actually construct my operads from symmetric monoidal categories, which happen to be props/colored props.
I've found conflicting information about the relationship: on the nLab it says that PROPs are more general than properads, but in the Handbook of Algebra, it says that every PROP is a properad
You gotta be careful about this "more general" business, because for example every Lawvere theory gives a prop, and every prop gives a Lawvere theory, but it's just an adjunction.
what's the nonrepresentable version of a PROP?
I don't know. Maybe a "strict symmetric polycategory"???
I don't know if people have even defined symmetric polycategories yet, but they will someday if not today.
polycategories only allow composition along single objects at a time, whereas we need something that allows multiple composition
Richard Garner defines symmetric polycategories in https://arxiv.org/abs/math/0606735
"polycategories only allow composition along single objects at a time, whereas we need something that allows multiple composition" - oh, okay.
How about a "properad", then? I'm trying to grok the elegant definition here:
https://ncatlab.org/nlab/show/properad
yes, we've been struggling to decipher what it is :big_smile:
Phil will straighten us out as soon as he returns. I wonder how far we can get before then though.
There is an alternative description of properads as algebras for a monad on the category of presheaves on elementary graphs. It's a Segal-condition-style nerve theorem just like the ones quoted above for operads.
Can you just tell me what a properad is in one sentence as if I were a five-year-old? :slight_smile:
It's a bunch of things with inputs and outputs, where you can glue together all (? some?) of the outputs of one thing with the inputs of the next.... something like that.
It's an algebraic rule that allow you to contract acyclic connected graph configurations of operations to a single operation. Operations are many-in/many-out. Sorry, that was two sentences. Argh now we up to four sentences :-(
how does this differ from how you would describe a PROP in the same language?
Okay, I get it now. So if I have an operation A with 2 inputs and 2 outputs, and an operation B with 2 inputs and 2 outputs, I cannot, in a properad, compose them by attaching both outputs of A to inputs of B. Right, @Joachim Kock?
In a prop, you are also allowed to contract nonconnected (acyclic, directed) graphs.
....
Also.... Wheeled properads?
How can I reply to a specific message?
@Joachim Kock: there's a drop-down menu if you hover over the right side of a message — and there's an option "Quote and reply"
The best you can do is click on it, at right, and quote it.
"Quote and reply".
I think in some ways we are still behind the technology of "usenet" discussions back in 1989, where we could have arbitrary discussion trees.
John Baez said:
Okay, I get it now. So if I have an operation A with 2 inputs and 2 outputs, and an operation B with 2 inputs and 2 outputs, I cannot, in a properad, compose them by attaching both outputs of A to inputs of B. Right, Joachim Kock?
Yes, you are allowed to connect those pairs of wires, because even if it's slightly loopy, it's not a directed loop. By acyclic, I meant 'no directed cycles'.
Oh, wow. Hmm.
Oh, and props do let you do that. Right?
Just as you would with any symmetric monoidal category.
So Joachim's "yes" means "you're wrong, Baez, you can do that".
oh whoops. So what's the difference then?
I feel young with all this technology.
I think someone needs to make a chart of all different variations on these ideas.
In a prop, you can take for example the disjoint union of seven (1,1) operations and contract the whole thing to a (7,7)-corolla.
ahh
And this is just "tensoring the morphisms", right?
so in a properad, you just have the notion of composition; but in a prop, you also have a notion of concatenation (given by functoriality of the tensor product)
There is a nice survey by Markl.
Joe Moeller said:
And this is just "tensoring the morphisms", right?
Right.
A prop is just a strict symmetric monoidal category with as objects, so there's no mystery about them.
Oh, this is making sense now. Right, this is precisely what you don't have in operads too. Should've known. :upside_down:
so is a (coloured) dioperad the same as a (coloured) properad?
or is one the "partial composition" version of the other?
or something else entirely?
Dioperads are definitely not the same as properads!
I want to establish how polycategories are different from coloured properads
because they seem very similar to me at the moment
(Actually I what I described should be called a graphical prop. It is not precisely the same thing as a prop in the symmetric-monoidal-category sense of Mac Lane. The difference was spotted only recently by Michael Batanin: the difference is that in a Mac Lane prop, the (0,0) operations form a
commutative monoid, by the Eckmann-Hilton argument. In a graphical prop it can be any monoid.)
In a dioperad you are only allowed to contract contractible graphs. That is, John's example is not allowed. I think this is the same thing as polycategory. (For me everything is always coloured.)
Nathanael said that polycategories only let you attach one output to one input; Joachim just said that colored properads let you attach multiple outputs to multiple inputs. So, they can't be the same.
okay, so if this is the case, then dioperads are to properads what operads with partial composition are to operads with multiple composition
I was under the impression that operads with partial and operads with multiple composition were equivalent
Yes, they are.
and so I would have imagined dioperads and properads to be similarly equivalent?
Joachim explained how they're not, in response to my question.
Joachim Kock said:
contract contractible graphs
OK, that sounded funny. By contractible graph I meant simply-connected geometric realisation.
So now I have also been able to reply to myself. Now I can continue the conversation even when all you other go to bed.
Joachim explained how they're not, in response to my question.
ah, of course!
everything feels like it's fitting into place now — thank you for explaining, everyone!
to me, coloured properads seem more deserving of the name "polycategory" than coloured dioperads
Wheeled properads? You just allow yourself directed cycles (but still connected). Sounds easy, but that's really a can of worms :-( because of the nodeless loop. Philip and his friends wrote a whole book about it...
Sorry, that was not a proper attribution (I just mentioned Philip because he was around in this chat). I meant: Hackney-Robertson-Yau.
Yeah I'm the only one of us around in the chat. :-)
But since someone else who has written about properads appeared in the chat while I was gone, I'm not sure there's anything I should add.
@Nathanael Arkor did you feel like you got a good understanding of why there where properads that could not be dioperads?
I wish someone would make a like... hierarchy
yes, @John Baez gave an example of a properad that was not a polycategory here: https://categorytheory.zulipchat.com/#narrow/stream/229199-basic-questions/topic/Properads/near/191809947
I think the hierarchy goes like this: coloured PROPs > coloured properads > polycategories > multicompositional multicategories ~ partial-compositional multicategories > categories
where >
means "generalises" and ~
means "is equivalent to"
(and then wheeled properads sound even more general than properads)
Right I'm actually wondering if wheeled properads are PROPS or not
And then you've got modular (pr)operads and cyclic (pr)operads haha
And then you can do everything but with ∞ in front of it
it's easy to see how categorifying everything will affect the hierarchy
I would be surprised if wheeled properads could be expressed as PROPs
I would imagine they're two different generalisations
Yeah I'm getting that feeling as well
but I don't yet have an intuition for wheeled properads
Maybe it's worth pointing out some examples of properads: bialgebras, Lie bialgebras are two that I can think of off the top my head.
Maybe there's some notion of, like, a Poisson bialgebra or something
cyclic operads also seem like a different generalisation: you no longer have a strict divide between input and output
so they don't seem like operads or dioperads
Oh yeah cyclic and modular are going in a different direction completely
(personally, I think many of these names are very misleading)
I STILL don't really know wtf is going on with modular operads
I hadn't come across modular operads before
I've tried to read the Getzler paper introducing them a couple of times, never seriously, but I've never been able to grok it
Oh and of course coöperads are an example of properads
I like your use of the diaeresis :grinning_face_with_smiling_eyes:
it would be really nice if all these examples could be captured in some general framework, like Cruttwell–Shulman's approach to multicategories
maybe. i suspect that would be a rather thankless task.
there's also the possibility of messing around with the group acting on the inputs. so you've got non-symmetric operads and symmetric operads, but you can also have _braided_ operads, where the symmetries of the inputs are coming from the braid group
there's certainly an interesting question of what the right generalisation of input and output is
https://arxiv.org/pdf/0907.2460.pdf captures braided operads already
(and really anything that is "some structured input" and a single output)
a good person to ask about this could be Mike Shulman, who appears to be in the Zulip server
whoa mike's here, cool! also... whoa there are a LOT of people here!
It's a little weird stepping outside of the homotopy theory bubble and all of the sudden seeing all these people whose names I don't recognize.
I STILL don't really know wtf is going on with modular operads
For those you have to be somewhat comfortable with Riemann surfaces (or maybe algebraic curves). Are you? I forget.
Eh, somewhat. I've spent a little time with the Grothendieck-T*****r group.
I just think about spheres and tori and stuff.
And that seems to get me close enough.
But that does jar my memory a little bit I guess. You've got marked Riemann surfaces and you can like, glue them together along markings, or delete a marking, or something?
Yes. I'm not an expert on modular operads by any means, but looking over the Getzler-Kapranov paper again I see this:
The concept of modular operad is described purely combinatorially: it's a cyclic operad with extra structure. But this extra structure reflects things you can do with Riemann surface with marked points. You can think of a Riemann surface with n+1 labelled marked points as an n-ary operation. You can compose these as usual for operations in an operad, or even a cyclic operad. But you can also take two marked points and glue your Riemann surface to itself by identifying these points. This idea is incorporated into the definition of modular operad: for example, I guess you get ways to take an n-ary operation and produce an (n-2)-ary operation.
Are the marked points supposed to be like a divisor?
Yes.
The "gluing" business is a bit subtle.
right so "cyclic" here means that you can permute the inputs
(or the "labels" on the "input" markings)
oh no sorry
cyclic means you can rotate an input to an output
gah it's too late i need to go to bed
No prob. Yes, cyclic means you can rotate an input to be an output.
There's no fundamental distinction between the n inputs and the 1 output of an operation in a cyclic operad.
On top of all the structures we've been discussing, I want to understand how they relate to hypergraph categories, because they're giving me the same vibes.
I also want to know about the graph complex stuff that comes up w/r/t GT and all that stuff.
What's GT?
Grothendieck-Teichmuller.
There's a book about operads and that stuff by Benoit Fresse.
Yeah, an enormous book.
@Joe Moeller the Grothendieck-T* group (I don't like writing his name b/c he's an actual Nazi) is related to Riemann surfaces and all that jazz, but it also happens to be the homotopy automorphisms of the little 2-discs operad (this isn't SUPER surprising once you learn what GT is), but there's a lot of stuff going on there
I would be happy to talk about something like this GT stuff. I'd have to read stuff to get up to speed and remember what I once knew.
Jonathan Beardsley said:
I wish someone would make a like... hierarchy
Here's such a thing from the preface of "A Foundation for PROPs, Algebras, and Modules" (but only dealing with "directed" contexts)
Screen-Shot-2020-03-25-at-8.01.56-PM.png
So this idea of having distinguished points in a surface reminds me of modular tensor categories. Is it the same modular as modular operads?
Yes. "Modular" just means "like stuff you can do with Riemann surfaces".
That is, in this context that's what it means. The "modular group" and "modular curves" use the word in a more specific way... but they too are connected to Riemann surfaces.
Great. So what does the operad look like here?
Which operad? As I said, there's not just one "modular operad": a modular operad is a kind of operad, whose properties I sketched.
I meant the one you get for a fixed surface. How do you glue the surface to itself? I'm confused what exactly the operations are.
I didn't say a fixed surface gives an operad.
The concept of modular operad is described purely combinatorially: it's a cyclic operad with extra structure. But this extra structure reflects things you can do with Riemann surfaces with marked points. You can think of a Riemann surface with n+1 labelled marked points as an n-ary operation. You can compose these as usual for operations in an operad, or even a cyclic operad. But you can also take two marked points and glue your Riemann surface to itself by identifying these points. This idea is incorporated into the definition of modular operad: for example, I guess you get ways to take an n-ary operation and produce an (n-2)-ary operation.
I guess it wasn't clear from this that a modular operad is a kind of operad: a cyclic operad with extra structure that's a bit hard for me to explain because I don't understand it very well.
Right, so I read this and I'm confused by it.
I was sorta guessing that a surface gives an example of one of these operads, where the operations are the n+1 points.
No.
In an ordinary operad you can take a bunch of operations, visualize them as trees, and do things with them that you'd do with trees.
So what is a Riemann surface doing here?
I'm saying that in a modular operad, which is a kind of operad, you can take a bunch of operations, visualize them as Riemann surfaces with marked points, and do thigns with them that you'd do with Riemann surfaces with marked points.
So the analogy is "trees are to operads as Riemann surfaces are to modular operads".
You don't get an operad from a specific tree, and you don't get a modular operad from a specific Riemann surface with marked points.
Right, I was misunderstanding what you were saying before.
Great. What's one specific one?
I deleted some stuff that I said that was wrong.
Let me try to give an example of a modular operad.
I'm looking at the paper by Getzler and Kapranov.
This stuff is pretty complicated....
I don't think I can get it right and also be comprehensible - it'll be hard to even get things right!
But the most important idea in this general vicinity is the moduli space of Riemann surfaces with genus g and n marked points.
There are lots of Riemann surfaces with genus g and n marked points (i.e. points labelled 1, 2, ... n).
The set of isomorphism class of these things, roughly, forms a space called M(g,n).
It's incredibly important and people have spend a lot of time trying to understand its topology (it's a topological space) and geometry (it's something like an algebraic variety).
It's a fundamental player in string theory, since you can think of it as the "set of strings of genus g with n inputs/outputs".
Roughly speaking, there's a modular operad whose set of (n-1)-ary operations is the union of all the M(g,n)'s over all g.
This is probably the one to understand.
One operation is some surface with the right number of distinguished points. How does the tree analogy come into play here?
A tree has a certain number of leaves and a root. These are the points where you're allowed to attach one tree to another!
In an ordinary operad you can only attach an output of one operation (root) to an input of another (leaf).
In a cyclic operad, operations should instead be visualized as unrooted trees!
They are just trees in the sense of graph theory, with a bunch of leaves.
In a cyclic operad there's no real distinction between "inputs" and "output" - an operation just has a bunch of "puts". (Nobody calls them that.)
You can attach a "put" of one operation to a "put" of another operation.
A modular operad is more like that... as I mentioned, it's a cyclic operad with extra structure.
So are you supposed to thing of the unrooted tree as embedded in a Riemann surface?
And the leaves are the distinguished points?
Nathanael Arkor said:
it would be really nice if all these examples could be captured in some general framework, like Cruttwell–Shulman's approach to multicategories
Try the operadic categories of Batanin and Markl.
Nathanael Arkor said:
but I don't yet have an intuition for wheeled properads
Did you read this tweet: https://categorytheory.zulipchat.com/#narrow/stream/229199-basic-questions/topic/Properads/near/191812919
I can expand on it if necessary.
Regarding modular operads, the one of marked Riemann surfaces is of course the most famous one, because Riemann surfaces are so famous anyway. But just to grasp the notion, I would stick to graphs, saying that a modular operad is a structure where the operations indexed by corollas (but without distinction between in and out), and where you can contract any (connected) graph of operations to a single operation.
If you want to talk about Riemann surfaces, you have to realise that they are allowed to have singular points. It is cleaner to deal with this in the setting of stable algebraic curves in the sense of Deligne and Mumford: these are algebraic curve allowed to have ordinary double points (but not cusps or worse singularities). (I ignore the actual stability condition, a technical condition to limit the number of automorphisms.)
They also have marked points.
Given a stable curve, consider the dual graph: for each irreducible component, draw a node, and for each double point, draw an edge between the two irreducible components meeting at that point. Since a double point could be that of a component intersecting itself (like in an irreducible nodal plane cubic y^2=x^2(x-1)), the graph can have loops. Finally for each marked point, draw a dangling edge from the node corresponding to the irreducible component. Altogether you get a (non-oriented) graph with open-ended edges allowed. (If you really want to follow the original Getzler-Kapranov definition of modular operad, your graphs should also have a genus decoration at each node, namely the genus of the corresponding irreducible component. But nowadays many users have stripped off this data from the definition, and regard it as further decoration you can add if really needed.)
The overview of all these different kinds of operad-like structures can be made in terms of which graph-like configurations of operations you are allowed to contract.
For a category, you contract linear rooted trees to linear rooted trees with only one node.
For an operad, you contract rooted trees to rooted trees with only one node.
(For a nonsymmetric operad, you contract planar rooted trees to planar rooted trees with only one node.)
For properads, you contract connected directed acyclic graphs to ones with only one node.
For wheeled properads, you also allow directed cycles, and contract to directed acyclic graphs without inner edges.
For (graphical) props, you contract (not-necessarily-connected) directed acyclic graphs to directed acyclic graphs with only one node.
For cyclic operads you contract non-rooted trees to non-rooted trees with only one node.
For modular operads, you contract connected graphs to connected graphs without inner edges.
(For wheeled and modular it is not good enough to say "with only one node". A loop with a single node should not count as an operation.)
In each case, the contracted graph must have the same arity as the graph you contract. (This condition essentially tells you that the structures are algebras for a cartesian monad, but for this to be true you need to upgrade from sets to groupoids.)
In each case there is an operadic category whose objects are the graphs in question, and whose morphisms are contractions of inner edges. I am not an expert in this, so please look at the papers of Batanin and Markl for precise statements and details.
I am talking about the coloured version of these notions. This means that it is important to allow the graph which is just an edge without any nodes. This graph indexes the 'colours'. So 'graph-like configuration of operations' means that each node is decorated by an operation, and each edge by a colour -- in a compatible way.
To actually formalise the intuitions listed above, a main task is to make precise the notions of trees and graphs, and have a good formalism for them. (In particular, they should admit open-ended edges. For trees, these are the leaves and the root.) That's a longer story. I think I should not bend the discussion in that direction, although it is one of my favourite topics.
I am a little late to the discussion. Are (coloured) properads the same thing as "compact polycategories" defined by Ross Duncan in his PhD thesis (some slides about those: http://www.cs.ox.ac.uk/people/ross.duncan/ckc-21-jul-2006.pdf)?
These are basically polycategories with multicuts (composition along multiple elements).
@Joachim Kock: that's a really helpful explanation, thank you!
To actually formalise the intuitions listed above, a main task is to make precise the notions of trees and graphs, and have a good formalism for them.
is this to say that this is not what Batanin–Markl do?
that indeed sounds like a fascinating topic — I shall look at operadic categories; thank you for the reference!
Joachim Kock said:
Nathanael Arkor said:
but I don't yet have an intuition for wheeled properads
Did you read this tweet: https://categorytheory.zulipchat.com/#narrow/stream/229199-basic-questions/topic/Properads/near/191812919
I can expand on it if necessary.
ah, I did read it — but what I meant was that to feel I properly understood what was going on, I would have to think of some examples, as I don't think I've seen such a structure before
@Nicolas Blanco: they do sound like the same thing to me
operadic categories seem like a nice abstraction, but it's a bit hard for me to tell exactly what kinds of "generalised multicategory" structures they capture — are all generalised multicategories (in either the Leinster or Cruttwell–Shulman sense) examples of operadic categories?
Nathanael Arkor said:
To actually formalise the intuitions listed above, a main task is to make precise the notions of trees and graphs, and have a good formalism for them.
is this to say that this is not what Batanin–Markl do?
I did not say anything in that direction.
the graph-focused view seemed particularly espoused by Markl's Operads and PROPs
But maybe I can clarify this: for each of the examples in the list, it can be tricky to get the combinatorics right. This goes for the situation where you just want to develop your own 'ad hoc' theory for the kind of operad in question, and it also goes for the situation where you want to prove that your trees or graphs form an operadic category. In both cases, care and precision is required.
(The theory of operadic categories is abstract. In principle, it could be developed without ever seeing a tree or a graph.)
(The theory of operadic categories is abstract. In principle, it could be developed without ever seeing a tree or a graph.)
the definition doesn't seem to indicate of an graph/tree-based intuition, certainly
it also goes for the situation where you want to prove that your trees or graphs form an operadic category
would it be reading too much into your comments to take it that there might be a more "direct" way to go from these kinds of descriptions of operations on graphs to the corresponding kinds of operadic categories (or another, similarly-inclined categorical structure)?
Nathanael Arkor
Yes, that would be reading to much into my comments.
The operadic-category axioms are very powerful. It is normal that it takes some work to check them in a given situation, perhaps a bit like Quillen model structures.
I advertised operadic categories because I recommend them.
okay, that makes sense, thank you :)
Nicolas Blanco said:
I am a little late to the discussion. Are (coloured) properads the same thing as "compact polycategories" defined by Ross Duncan in his PhD thesis (some slides about those: http://www.cs.ox.ac.uk/people/ross.duncan/ckc-21-jul-2006.pdf)?
These are basically polycategories with multicuts (composition along multiple elements).
The pictures in these slides certainly seem promising! I hadn't heard of this thesis before, so can't say for sure. But thanks for the pointer
Joachim Kock said:
The operadic-category axioms are very powerful. It is normal that it takes some work to check them in a given situation, perhaps a bit like Quillen model structures.
I advertised operadic categories because I recommend them.
Sorry if this is a digression. I've been wondering if the operadic category definition can be modified to allow for finitely presentable presheaves (on some small category) rather than finite sets to be the "cardinalities". @Nathanael Arkor this is an approach I've been thinking about to get dependently coloured operads/dependent multicategories. In particular, one might hope that globular operads become examples. Note that the (opposite) category of globes is a finitely branching inverse category.
I had also been wondering if there were operadic categories whose operads were "dependent multicategories" (in whichever particular sense)
but I need to become more familiar with the intuition behind operadic categories first
are you sure that globular operads are not already examples covered by operadic categories?
(the existing papers on operadic categories don't mention enough examples or non-examples to really give a good idea of what's covered and what isn't)
Nathanael Arkor said:
are you sure that globular operads are not already examples covered by operadic categories?
I'm not sure but I would be surprised. The arities of operations of globular operads are not finite sets but rather finite globular sets.
it's not clear to me that the cardinality functor should be thought of as an arity functor; it reminds me a little of the length function in a C-system
as long as the dependency itself is encoded somewhere, a length function can be a reasonable operation, even when it doesn't capture all the information
I don't yet understand why operadic categories are the right notion — they seem to capture many existing notions, but the definition itself isn't suggestive to me of the graph-like intuition, for instance
(compared to, say, generalised multicategories, the formulation of which feels very intuitive)
Nathanael Arkor said:
it's not clear to me that the cardinality functor should be thought of as an arity functor; it reminds me a little of the length function in a C-system
I believe the moral is that objects in an operadic category are contexts that "look like" finite sets (of "variables" if you like), and that the morphisms (context morphisms) have a "descent-like" property in that they can be chopped up into fibres and glued back together. It's easy to understand what this means for usual coloured operads seen as operadic categories. (Look at the example of the operadic category of "bouquets"). It's precisely this "descent-like" property that one would like to understand for morphisms between dependently-typed contexts.
I would say that the cardinality functor describes the "shape" of a context.
I see what you mean; I think Lack's reformulation makes this slightly clearer, now that I look at it again — but I still don't have enough of an intuition to see precisely what the obstruction is in thinking about a simple dependent operad — I'll try playing around with some examples to get a better understanding
if operadic categories are insufficent, then considering finitely presentable presheaves seems like a promising idea to try
Nathanael Arkor said:
I don't yet understand why operadic categories are the right notion — they seem to capture many existing notions, but the definition itself isn't suggestive to me of the graph-like intuition, for instance
To grasp the intuition, I think the best example to look at is the operadic category Delta (the monoidal delta, including the empty ordinal), which is the operadic category for nonsymmetric operads. This means that a nonsymmetric operad (in a symmetric monoidal category V) is a strictly monoidal lax functor Delta -> Sigma V. Here Sigma V is the one-object 2-category with V as Hom cat. If you spell out the conditions, you get precisely the operad axioms. (This is due to Day and Street, and was one of the motivating examples for the notion of operadic category.)
@Joachim Kock: yes, I think it would be helpful for me to explicitly work through that example — one can often only get so far in understanding without going through a construction step-by-step
that correspondence (Lemma 1.13 in the original paper on operadic categories) seems quite helpful
I think there are quite a few steps of understanding to make here — I've only just taken a look at your paper with Batanin and Weber, and the result that Feynman categories, which can describe many operadic notions that intuitively seem much richer than just operads, are biequivalent to coloured operads seems very surprising at first sight
also, the note relating regular patterns and substitutes to generalised species is also very interesting, as I feel slightly more familiar with that work, so I can hopefully draw some more connections to things I understand
it seems like a delightful area to start exploring