Category Theory
Zulip Server
Archive

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.


Stream: learning: questions

Topic: defining a "diagram limit" for a diagram


view this post on Zulip David Egolf (Nov 04 2023 at 18:13):

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 D:JCD: J \to C consists of two pieces of data (x,f)(x,f), where:

view this post on Zulip David Egolf (Nov 04 2023 at 18:13):

Here Cone(,D):CopSetCone(-,D): C^{\textrm{op}} \to \mathsf{Set} sends an object cCc \in C to the set of cones over DD with apex of cc. And Cone(,D)(f:cd)Cone(-,D)(f: c \to d) is a function f:Cone(d,D)Cone(c,D)f^*:Cone(d,D) \to Cone(c,D) which acts by precomposition "at the apex", so ggfg \mapsto g \circ f for each "leg" gg of a cone with apex dd.

If we view xx as a diagram with one object, I think that Cone(,x)Cone(-,x) is very similar to the functor C(,x)C(-,x). That is because a cone over a diagram with a single object xx is just a morphism to xx.

view this post on Zulip David Egolf (Nov 04 2023 at 18:13):

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 D:JCD: J \to C of "shape" F:ICF: I \to C would consist of two pieces of data (F,f)(F,f), where:

view this post on Zulip David Egolf (Nov 04 2023 at 18:13):

My hope is that even if a diagram D:JCD: J \to C doesn't have a limit (in the standard sense), it might have a diagram limit with respect to some F:ICF: I \to C where II is much "smaller" then JJ. Intuitively, this might allow one to "compress" one's understanding of cones over D:JCD: J \to C to be in terms of cones over a smaller diagram F:ICF: I \to C.

Is this something that people do sometimes?

I'd also be interested in finding examples of diagrams D:JCD: J \to C that don't have a limit, but have a "diagram limit" (F:IC,f)F: I \to C,f) where II is "smaller" than JJ. (To determine if II is "smaller" than JJ, we might ask if II has fewer morphisms than JJ, for example).

view this post on Zulip Todd Trimble (Nov 04 2023 at 18:47):

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.

view this post on Zulip Todd Trimble (Nov 04 2023 at 18:47):

In any case, let me encourage you to look more closely into how "Cone(,x)Cone(-, x) is very similar to the functor C(,x)C(-, x)". (Did you mean to write Cone(,D)Cone(-, D)?) More precisely, let me encourage you to understand exactly how Cone(,D)Cone(-, D) is defined in terms of categories, functors, and natural transformations. A cone is a certain natural transformation, but between which functors?

view this post on Zulip Todd Trimble (Nov 04 2023 at 18:49):

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.

view this post on Zulip David Egolf (Nov 04 2023 at 18:57):

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.

view this post on Zulip David Egolf (Nov 04 2023 at 19:03):

Todd Trimble said:

In any case, let me encourage you to look more closely into how "Cone(,x)Cone(-, x) is very similar to the functor C(,x)C(-, x)". (Did you mean to write Cone(,D)Cone(-, D)?) More precisely, let me encourage you to understand exactly how Cone(,D)Cone(-, D) 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 Cone(,x)Cone(-,x), and not Cone(,D)Cone(-,D). The idea is that Cone(,x)Cone(-,x) is shorthand for Cone(,F)Cone(-,F) where F:1CF: 1 \to C is the diagram that picks out the element xCx \in C. (Here 11 is a category with a single object and just the identity morphism).

view this post on Zulip David Egolf (Nov 04 2023 at 19:08):

I think I can start to clarify my understanding of how Cone(,D)Cone(-,D) is defined in terms of categories, functors, and natural transformations. A cone over DD with apex cc is a natural transformation from a functor that is constant at cc to the functor D:JCD: J \to C. We might call the constant functor Δc:JC\Delta_c: J \to C.

So, we can consider the category of functors from JJ to CC and the natural transformations between them, [J,C][J,C]. The set of cones over DD is I think then the set of morphisms from Δc:JC\Delta_c: J \to C to D:JCD: J \to C. So, Cone(c,D)[J,C](Δc,D)Cone(c,D) \cong [J,C](\Delta_c, D).

view this post on Zulip David Egolf (Nov 04 2023 at 19:12):

We still have to consider how Cone(,D)Cone(-,D) acts on morphisms. It is tempting at this point to guess that Cone(,D)Cone(-,D) is [J,C](Δ,D)[J,C](\Delta-, D), where Δ:C[J,C]\Delta:C \to [J,C] is some functor that sends an object cc to the functor Δc:JC\Delta_c: J \to C that is constant at cc.

However, it will take me some work to properly figure this out!

view this post on Zulip Todd Trimble (Nov 04 2023 at 19:15):

In that case, Cone(,x)C(,x)Cone(-, x) \cong C(-, x) looks pretty tautological, if your shape category is the category 11 with exactly one object and morphism.

view this post on Zulip Todd Trimble (Nov 04 2023 at 19:17):

Your understanding of cones as natural transformations is correct!

view this post on Zulip David Egolf (Nov 04 2023 at 19:19):

Todd Trimble said:

In that case, Cone(,x)C(,x)Cone(-, x) \cong C(-, x) looks pretty tautological, if your shape category is the category 11 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 xx to only have the object xx and its identity morphism.

view this post on Zulip Todd Trimble (Nov 04 2023 at 19:20):

So if DD has a limit, then [J,C](Δ,D)C(,limD)[J, C](\Delta-, D) \cong C(-, \lim D).

view this post on Zulip Todd Trimble (Nov 04 2023 at 19:22):

We would say in that case that limD\lim D "represents" the functor [J,C](Δ,D)[J, C](\Delta -, D).

view this post on Zulip David Egolf (Nov 04 2023 at 19:25):

Yes, that all makes sense!

view this post on Zulip Todd Trimble (Nov 04 2023 at 19:29):

There's a good chance you know this already, but if every diagram DD of shape JJ in CC has a limit, then the natural isomorphism

[J,C](Δx,D)C(x,limD)[J, C](\Delta x, D) \cong C(x, \lim D)

says that Δ:C[J,C]\Delta: C \to [J, C] has lim:[J,C]C\lim: [J, C] \to C for its right adjoint. But there's a nice little bit of categorical wisdom lurking there:

view this post on Zulip Todd Trimble (Nov 04 2023 at 19:37):

Namely, that even though we haven't quite defined how lim\lim is defined as a functor, the effect of lim\lim on morphisms is automatically determined by exploiting universal properties. More generally, the wisdom is that in order for a functor F:CDF: C \to D to have a right adjoint G:DCG: D \to C, it is sufficient that every functor D(F,d)D(F-, d) be representable (by an object of CC). It's highly recommended that every student of category theory goes through this at one time in their life!

view this post on Zulip David Egolf (Nov 04 2023 at 19:42):

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 DD, or exactly how lim\lim is a functor.

But I see that you indicate below that there is a way to figure out how lim\lim 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.)

view this post on Zulip Todd Trimble (Nov 04 2023 at 19:49):

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.

view this post on Zulip David Egolf (Nov 04 2023 at 20:00):

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!)

view this post on Zulip Ralph Sarkis (Nov 04 2023 at 20:50):

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 F:ICF:I \to C such that

[J,C](ΔJ,D)[I,C](ΔI,F)[J, C](\Delta^J-, D) \cong [I, C](\Delta^I-, F)

This makes sense when JJ and II are small and CC is locally small (otherwise the functor categories involved might not be locally small). When DD has a limit, you can pick F:1CF: \mathbf{1} \to C to be the constant functor at limD\lim D. Otherwise, what does it mean for FF and DD to have the same cones?

There are some trivial cases. For instance when DD is a diagram with one or more instances of a terminal object from CC, you can remove them to get a diagram FF, 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.

view this post on Zulip James Deikun (Nov 05 2023 at 03:49):

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".

view this post on Zulip James Deikun (Nov 05 2023 at 03:54):

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 1\bold{1} by itself is a limiting cone.

view this post on Zulip James Deikun (Nov 05 2023 at 04:10):

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 11+1\bold{1} \to \bold{1} + \bold{1} (either one) where the 1\bold{1} can't be removed; with it the limit is 1\bold{1} and without it is 1+1\bold{1} + \bold{1}.

view this post on Zulip David Egolf (Nov 06 2023 at 20:02):

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 xx over a diagram DD'. I have denoted this cone using a:xDa: x \to D'. On the left, we have augmented the diagram DD' with a terminal object 11. This requires us to augment the cone by adding in a (uniquely specified) morphism to the terminal object.

Above, I have drawn f:yxf:y \to x to facilitate thinking about the naturality square below. We get this square by evaluating each cone functor (which goes from CopC^{\mathrm{op}} to Set\mathsf{Set}) on a morphism fop:xyf^{op}: x \to y, which has a corresponding morphism f:yxf: y\to x in CC.

naturality square

view this post on Zulip David Egolf (Nov 06 2023 at 20:05):

Here DLD_L means "the diagram on the left" (in the picture above, it is the diagram DD' augmented with the terminal object 1) and DRD_R means "the diagram on the right", which is DD' in this case. By ff^* I mean the function that produces a new cone by precomposing each leg of cone by ff. And by (!,a)a(!,a) \mapsto a I mean the function that takes a cone over the augmented version of DD' and deletes the leg going to the terminal object, so that we get a cone over the un-augmented version of DD'.

It seems like the naturality square should commute, and that each of the vertical morphisms are isomorphisms. So I am thinking that Cone(,DR)Cone(,DL)Cone(-,D_R) \cong Cone(-,D_L).

However, you both seem to be indicating there is some additional subtlety here, so I suspect I am missing something!

view this post on Zulip David Egolf (Nov 06 2023 at 20:17):

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 DD 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 DD and over the smaller resulting diagram FF 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 xx. I think there should be a bijection between the cones over the diagram with a,b,ca,b,c on the left and the cones over the diagram with a×b,ca \times b,c 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, Cone(,{a,b,c})Cone({a×b,c})Cone(-,\{a,b,c\}) \cong Cone(-\{a \times b, c\}) where {a,b,c}\{a,b,c\} means the discrete diagram with objects aa ,bb, and cc; and {a×b,c}\{a \times b, c\} means the discrete diagram with objects a×ba \times b and cc.

view this post on Zulip Ralph Sarkis (Nov 06 2023 at 20:21):

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 DLD_L). The example James gave is below DLD_L is in green and DRD_R is in purple. A cone over DLD_L is not the same thing as a cone over DRD_R. It is true that the morphism !:X1{!}: X \to \mathbf{1} is uniquely determined (by terminality), but the morphism inl:11+1\mathsf{inl}:\mathbf{1} \to \mathbf{1}+\mathbf{1} (which is the left coprejction) enforces that the morphism X1+1X \to \mathbf{1}+\mathbf{1} must be inl!\mathsf{inl} \circ {!} whereas it could be anything for the cone over DRD_R.

image.png

view this post on Zulip Ralph Sarkis (Nov 06 2023 at 20:23):

Your example with a×ba \times b works again because there are no morphisms going out of aa or bb.

view this post on Zulip David Egolf (Nov 06 2023 at 20:25):

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!