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.
Can someone try to give me a very concrete example? I've read the nLab page, Lawvere's Toward the Description in a Smooth Topos of the Dynamically Possible Motions and Deformations of a Continuous Body and attempted a few others, all of which presented things in increasingly general ways, without giving concrete examples. (There were plenty of highly abstract examples.)
I don't mind working out details, but I need a concrete starting point. [Hint: anything start with 'topos' will fail the ELI5 criteria; if you use the word 'presheaf' you're probably thinking at too high a level still, and need to expand things out. Please.]
What is ELI5?
Ah, "explain it like I'm 5". I assumed it was some categorical axiom heh.
I know the interval (1-cube) in the category of cartesian cubical sets is supposed to be an example, though I never worked it out for myself. (I didn't say "presheaf"...)
I'm surprised it's not on the nLab page for amazing right adjoint already.
Once someone figures out an example, I can stick it on the nLab. I think Lawvere's favorite examples involve "infinitesimal spaces", - maybe like the "walking tangent vector" space in synthetic differential geometry?
I get the idea of that "walking tangent vector" or "infinitesimal arrow" pretty well, but I haven't thought about this "amazing right adjoint".
So this fails the ELI5 test, but here goes. Say is a category with an object (for "interval") such that has all products for . The exponential on has left adjoint (here is the Yoneda embedding). But , so takes representables to representables and as a left adjoint, it must be the left Kan extension along the functor on . That means that is the restriction along this functor and so it has a right adjoint, given by right Kan extension along the same functor.
It's a shame you ruled out presheaves, because they provide the easiest example in my opinion, thanks to Proposition 2.5 of the nLab page.
Let be a small category, and consider the category of functors ; this is the category of "copresheaves on ", but the essential thing is that the objects of are functors and the morphisms are natural transformations. For any object in this category, we can consider the representable functor to sets, which always has a left adjoint given by sending any set to an -indexed coproduct of copies of . On the other hand, this representable functor has a right adjoint if and only if it is a (retract of a) representable copresheaf the latter being a functor of the form for some object of .
The objects whose representable functors admit right adjoints are called "tiny objects", so the above says that we can identify the representable copresheaves on a category up to retracts as the subcategory of tiny objects.
I don't think he ruled out examples that happen to be presheaves. I think he just wanted a concrete example, not a general example of the sort you just gave. So please give an example of your example!
The category of directed graphs is the category of copresheaves on the double-arrow category . By the above, the tiny objects are the digraph consisting of a single vertex and no edges, and the graph consisting of two vertices and a single edge from one to the other. I think this is a very instructive example to work out the details of!
(Note that this is normally presented as the category of presheaves on the double arrow category, but the result is identical; for the purposes of understanding this concept, it doesn't matter.)
Aha, that last example is indeed something I can sink my teeth in to. Thank you.
And indeed, I want to work my way up to understanding why this has anything to do with "infinitesimals". But I would like to do it via seeing 'tiny' objects in a number of sufficiently different concrete settings first.
Morgan Rogers (he/him) said:
The category of directed graphs is the category of copresheaves on the double-arrow category . By the above, the tiny objects are the digraph consisting of a single vertex and no edges, and the graph consisting of two vertices and a single edge from one to the other. I think this is a very instructive example to work out the details of!
There is some problem with the terminology. On the nlab there are two things that are called tiny:
I don't know whether the two graphs that you mention are also internally tiny (I'll try to compute the exponentials).
The graph with a single vertex and no edges is the terminal object, so then the functor is the identity functor (which does preserve colimits). So this graph should be internally tiny as well. (The graph with a single vertex and no edges is not the terminal object, so this argument is wrong.)
But if is the graph with two vertices and an edge connecting them, then I believe has 4 edges, while has 32 edges... so does not preserve coproducts in this case.
Jens Hemelaer said:
But if is the graph with two vertices and an edge connecting them, then I believe has 4 edges...
I'm having trouble seeing 4 edges. What are these 4 edges? For starters, what are the vertices of ?
A vertex of corresponds to a morphism , right? And a morphism from to itself must map the one edge of this graph to itself. So I'm getting just one vertex.
Similarly, the set of edges corresponds to morphisms . The product has one edge and two isolated points and . The diagonal edge has to map to the only edge in , but the isolated points can go to either vertex, making 4 options.
Ok, I miscalculated with the vertices...
A vertex of is the same thing as a morphism . Here, is the graph with two vertices and no edges. So there are 4 morphisms which means that has four vertices.
I made a similar mistake when I said that the functor is the identity functor.
You can compute that the functor sends a graph to the complete directed graph on its vertices.
This functor does not preserve colimits (not even coproducts), so is not an internally tiny object.
Here are the directed graphs and (hopefully no miscalculations). The loops are not shown in the pictures, the first should have a loop at vertex "st", and the second should have a loop at vertices 1 and 11. exponential1.png exponential2.png
In general, exponentials in a presheaf category are hard to compute... so it is difficult to come up with an easy and interesting example where taking exponentials has a right adjoint (the amazing right adjoint).
I bet you're used to reflexive graphs, Jens. For reflexive graphs I believe is the identity functor, and other things change too.
Yes I agree. I still think it is a bit surprising intuitively that the product of a point and an edge is two points...
This whole discussion is a splendid illustration of why I wanted explicit examples!
Jacques Carette said:
This whole discussion is a splendid illustration of why I wanted explicit examples!
Yes exactly... Here is the easiest example that I could come up with. Let be the category that has as objects the triples where and are sets and is a function. We look at the object in . For this object, you can compute that the functor is given as follows: if is an object of , then is the identity map . This exponential functor has a right adjoint (the amazing right adjoint), which sends an object in to the identity function .
Some theoretical background (using the terminology and results from the nlab page here): is the topos of presheaves on the category with two objects and precisely one non-identity morphism (from one object to the other). Because is a sheaf topos, the exponential has a right adjoint if and only if it preserves colimits, so if and only if is internally tiny. Further, because is a category admitting finite products, the internally tiny and externally tiny objects in agree (Proposition 2.4). Now from Example 2.2 it follows that is tiny, because it is a representable presheaf. Conversely, you can use Theorem 2.14 here to show that and the terminal object are the only tiny objects in .
Very nice explanation! Presheaves on this particular category are like graphs, only simpler. I sometimes think of them as graphs where every edge has a source but no target.
It's cool that has finite products. One object is terminal, and the product of the other object with itself is itself.
One way to think about this is that is a poset, and a poset has finite products if every pair of objects has a greatest lower bound.
Viewed as a poset is an ordinal, the ordinal called "2", and any ordinal has finite products.
Here's a very simple example, the "cartesian cubical sets" that @Reid Barton already mentioned. Let be the category of finite , strictly bipointed sets and the cartesian cube category - which is the free finite product category on an interval . Write the objects in the form , so and . Presheaves on are called (Cartesian) cubical sets, written . There is a functor taking to , which induces by restriction, and therefore has both left and right adjoints. One can easily calculate that
so its adjoint must be
.
The further right adjoint then also exists and is therefore an "amazing right adjoint" . We write it as and call it the " root". In particular, itself is therefore "tiny".
this is essentially the same as Reid's example.
Can one exhibit / compute that further right adjoint? What does that functor actually do?
in cubical sets:
,
where is the binomial coefficient.
I think I can reconstruct all the justifications, except for to . [I'm probably missing something simple, yet I am missing it!]
It would make more sense if it were , but even then, I'm not sure.
Indeed, it should be . Then is an application of Yoneda lemma to the category of presheaves
We have where is the Yoneda embedding.
Aha, Yoneda, of course! Now, the above computation exhibits quite explicitly, and shows up in there as well -- but I was kind of hoping for to be the item being isolated, not . Or maybe it's just a typo and the very first thing should be ?
Jacques Carette said:
It would make more sense if it were , but even then, I'm not sure.
thanks - that was indeed a typo!