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.
I've been working on better understanding limits (in my ongoing quest to understand how limits are preserved by certain representable functors!). My current understanding is that a limit of a diagram consists of two pieces of data , where:
Here sends an object to the set of cones over with apex of . And is a function which acts by precomposition "at the apex", so for each "leg" of a cone with apex .
If we view as a diagram with one object, I think that is very similar to the functor . That is because a cone over a diagram with a single object is just a morphism to .
Inspired by this, I was wondering if it could be interesting to consider the concept of a "diagram limit". A diagram limit for a diagram of "shape" would consist of two pieces of data , where:
My hope is that even if a diagram doesn't have a limit (in the standard sense), it might have a diagram limit with respect to some where is much "smaller" then . Intuitively, this might allow one to "compress" one's understanding of cones over to be in terms of cones over a smaller diagram .
Is this something that people do sometimes?
I'd also be interested in finding examples of diagrams that don't have a limit, but have a "diagram limit" ( where is "smaller" than . (To determine if is "smaller" than , we might ask if has fewer morphisms than , for example).
You and I had begun discussing the preservation of limits by representable functors, and also the connection between this and the Yoneda lemma, but the discussion was dropped at some point.
In any case, let me encourage you to look more closely into how " is very similar to the functor ". (Did you mean to write ?) More precisely, let me encourage you to understand exactly how is defined in terms of categories, functors, and natural transformations. A cone is a certain natural transformation, but between which functors?
With regard to your idea of diagram limits, you might also be interested in the notion of "final functor", if you haven't bumped into this already.
Todd Trimble said:
You and I had begun discussing the preservation of limits by representable functors, and also the connection between this and the Yoneda lemma, but the discussion was dropped at some point.
Yes, and I am still interested in talking about this! I've been slowly working on better understanding some of these things before posting again in that thread. (And I've also been distracted by other things!) But I'm happy to connect this conversation to that one.
Todd Trimble said:
In any case, let me encourage you to look more closely into how " is very similar to the functor ". (Did you mean to write ?) More precisely, let me encourage you to understand exactly how is defined in terms of categories, functors, and natural transformations. A cone is a certain natural transformation, but between which functors?
Thanks for the suggestion! It will take me some time to think about this.
Although I can immediately clear this up: I did mean to write , and not . The idea is that is shorthand for where is the diagram that picks out the element . (Here is a category with a single object and just the identity morphism).
I think I can start to clarify my understanding of how is defined in terms of categories, functors, and natural transformations. A cone over with apex is a natural transformation from a functor that is constant at to the functor . We might call the constant functor .
So, we can consider the category of functors from to and the natural transformations between them, . The set of cones over is I think then the set of morphisms from to . So, .
We still have to consider how acts on morphisms. It is tempting at this point to guess that is , where is some functor that sends an object to the functor that is constant at .
However, it will take me some work to properly figure this out!
In that case, looks pretty tautological, if your shape category is the category with exactly one object and morphism.
Your understanding of cones as natural transformations is correct!
Todd Trimble said:
In that case, looks pretty tautological, if your shape category is the category with exactly one object and morphism.
To be honest, I hadn't thought about the role that the shape category plays here. I mostly just wanted the diagram corresponding to to only have the object and its identity morphism.
So if has a limit, then .
We would say in that case that "represents" the functor .
Yes, that all makes sense!
There's a good chance you know this already, but if every diagram of shape in has a limit, then the natural isomorphism
says that has for its right adjoint. But there's a nice little bit of categorical wisdom lurking there:
Namely, that even though we haven't quite defined how is defined as a functor, the effect of on morphisms is automatically determined by exploiting universal properties. More generally, the wisdom is that in order for a functor to have a right adjoint , it is sufficient that every functor be representable (by an object of ). It's highly recommended that every student of category theory goes through this at one time in their life!
I think I have seen the natural isomorphism you describe above (in Leinster's book "Basic Category Theory"), although I did not understand it. I still don't understand why the isomorphism is natural in , or exactly how is a functor.
But I see that you indicate below that there is a way to figure out how needs to act on morphisms using universal properties! That sounds pretty cool! The more general insight you share also sounds interesting. (Although I don't quite see how the pieces fit together though, just yet.)
Take your time with this! It's really worthwhile fitting all these pieces together. I don't remember how long it took me; I only remember that it was well worth the effort.
I will plan to chip away at this then! If I figure things out or get too stuck I'll hopefully post here about that.
(And thanks again for your comments in both this thread and the previous one on representable functors. Once I get a bit further with understanding preservation of limits, I am hopeful that I'll be able to post a bit again in that other thread too!)
Not sure if I should let you make that step on your own, but your question at the start (which I find quite interesting) essentially amounts to finding another diagram such that
This makes sense when and are small and is locally small (otherwise the functor categories involved might not be locally small). When has a limit, you can pick to be the constant functor at . Otherwise, what does it mean for and to have the same cones?
There are some trivial cases. For instance when is a diagram with one or more instances of a terminal object from , you can remove them to get a diagram , and cones over both diagrams will be the same thing (because a morphism from the tip of the cone to a terminal object adds no information EDIT: I was too quick en besogne, see James' answer below).
I am sure there are interesting cases, but I don't see any at the moment.
When D is itself a cone, it has the apex as a limit, but if it's a limiting cone you can also remove the apex and get a "diagram limit".
In fact whenever there's a limiting cone contained in D you can "safely" remove its apex; the above fact about terminal objects is a special case as by itself is a limiting cone.
There's kind of a trick to the sense of "contains" though. You can remove arrows into the apex, and you can remove arrows out of the apex that are part of the limiting cone, but arrows out of the apex that are not part of the limiting cone can't always be removed; a simple example is the diagram (either one) where the can't be removed; with it the limit is and without it is .
Thanks @Ralph Sarkis and @James Deikun for your comments! I don't yet understand the point that James Deikun is making though.
The situation I'm imagining at the moment, while trying to understand your comments, is the following:
adding or removing a terminal object
On the right, we have some cone with apex over a diagram . I have denoted this cone using . On the left, we have augmented the diagram with a terminal object . This requires us to augment the cone by adding in a (uniquely specified) morphism to the terminal object.
Above, I have drawn to facilitate thinking about the naturality square below. We get this square by evaluating each cone functor (which goes from to ) on a morphism , which has a corresponding morphism in .
Here means "the diagram on the left" (in the picture above, it is the diagram augmented with the terminal object 1) and means "the diagram on the right", which is in this case. By I mean the function that produces a new cone by precomposing each leg of cone by . And by I mean the function that takes a cone over the augmented version of and deletes the leg going to the terminal object, so that we get a cone over the un-augmented version of .
It seems like the naturality square should commute, and that each of the vertical morphisms are isomorphisms. So I am thinking that .
However, you both seem to be indicating there is some additional subtlety here, so I suspect I am missing something!
Setting aside my confusion on this point for the moment, I am wondering if we can get interesting examples of "diagram limits" in a certain way. (The way I describe below might be what James Deikun mentioned above, but I am not sure).
The idea is that if you have a subdiagram in that has a limit, then you can replace that subdiagram by (the object part of) its limit. Then it intuitively seems like the cones over the original diagram and over the smaller resulting diagram should be in bijection with one another.
Here is an illustration of the idea:
two diagrams with "equivalent" cones
The picture above shows two cones, each with apex . I think there should be a bijection between the cones over the diagram with on the left and the cones over the diagram with on the right. I haven't checked, but I am guessing this is a natural bijection so that the cone functors over these two diagrams are naturally isomorphic. That is, where means the discrete diagram with objects ,, and ; and means the discrete diagram with objects and .
The subtlety can arise only when the terminal object you remove has some morphisms going out of it in the diagram (which is not the case in your ). The example James gave is below is in green and is in purple. A cone over is not the same thing as a cone over . It is true that the morphism is uniquely determined (by terminality), but the morphism (which is the left coprejction) enforces that the morphism must be whereas it could be anything for the cone over .
Your example with works again because there are no morphisms going out of or .
Ah, thanks for explaining @Ralph Sarkis ! That makes a lot of sense. So things become more tricky when our subdiagram of interest has morphisms coming out of it that land in other parts of the diagram!