Not signed in (Sign In)

Discussion Feed
- RSS2
- ATOM

Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

Site Tag Cloud

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome to nForum
If you want to take part in these discussions either sign in now (if you have an account), apply for one now (if you don't).

nLab > Latest Changes: functor

201 to 221 of 221

<
1
2
3
>

- CommentRowNumber201.
- CommentAuthorEric
- CommentTimeApr 2nd 2010
- PermaLink
Author: Eric
Format: MarkdownThe nLab says: >A **diagram** in a category <latex>C</latex> is simply a functor <latex>F:J\to C</latex>. > >The category <latex>J</latex> is called the shape or index category of the diagram, and is typically understood to be a small category. Does <latex>J</latex> need to be a free category? If so, I think it would be helpful to explicitly state it like I did above: >Given a graph <latex>G</latex> and a category <latex>C</latex>, a **diagram** in <latex>C</latex> is a functor <latex>F(G)\to C</latex>. > >A **commutative diagram** is a diagram <latex>F(G)\to P\to C</latex> which factors through a preorder <latex>P</latex>. This would be much clearer to me. What do you think? Can we change the nLab? This would also lead directly to the statement: >A diagram may also be thought of (via adjunction) as a graph morphism <latex>G\to U(C)</latex>.

The nLab says:

A diagram in a category $C$ is simply a functor $F:J\to C$ .

The category $J$ is called the shape or index category of the diagram, and is typically understood to be a small category.

Does $J$ need to be a free category?

If so, I think it would be helpful to explicitly state it like I did above:

Given a graph $G$ and a category $C$ , a diagram in $C$ is a functor $F(G)\to C$ .

A commutative diagram is a diagram $F(G)\to P\to C$ which factors through a preorder $P$ .

This would be much clearer to me. What do you think? Can we change the nLab?

This would also lead directly to the statement:

A diagram may also be thought of (via adjunction) as a graph morphism $G\to U(C)$ .
- CommentRowNumber202.
- CommentAuthorHarry Gindi
- CommentTimeApr 2nd 2010
- (edited Apr 2nd 2010)
- PermaLink
Author: Harry Gindi
Format: Markdown@Eric: I apologize if that came off a bit rude. It was not my intention. The main problem that I see with using the "functors are maps of graphs" approach is that it is a lot more confusing and complicated. The real benefit from the diagram approach comes from things like limits and colimits, where the choice of index category only matters for the shape. However, in practice, it still feels a lot easier to just be careful with your definition of limit/colimit, which you can apply to arbitrary functors (provided they exist). I prefer to reserve statements about commutativity to actual diagrams that I can draw (or at least pieces of diagrams, if they're infinite). All of these statements about posets etc are interesting, but we all have an intuitive notion of what it means for a diagram to commute. I submit to you that the notion of an abstract diagram as a map on graphs, let alone any definition of what it means for such a creature to commute, is certainly more difficult to work with than saying that a functor is a map on the set of objects and the set of arrows preserving identities and composition. Even if we want to use an unbiased definition, it's still the same. That is, we just say that F preserves n-ary composites for all n in N (notably including 0, where the 0ary composite at an object is the identity). (By the way, defining the identity to be the 0-ary composite doesn't seem right, since the 0-ary composite does not have an explicit domain/codomain. This means that we have to define a notion of a 0-ary composite _at an object_, which is much less parsimonious than just splitting off the case of n=0.) Edit: Eric, I am against changing the definition of a diagram. The whole beauty of the standard approach is not that we can describe categories as graphs, but that we can describe a diagram as a functor!

@Eric: I apologize if that came off a bit rude. It was not my intention.

The main problem that I see with using the "functors are maps of graphs" approach is that it is a lot more confusing and complicated. The real benefit from the diagram approach comes from things like limits and colimits, where the choice of index category only matters for the shape. However, in practice, it still feels a lot easier to just be careful with your definition of limit/colimit, which you can apply to arbitrary functors (provided they exist).

I prefer to reserve statements about commutativity to actual diagrams that I can draw (or at least pieces of diagrams, if they're infinite). All of these statements about posets etc are interesting, but we all have an intuitive notion of what it means for a diagram to commute. I submit to you that the notion of an abstract diagram as a map on graphs, let alone any definition of what it means for such a creature to commute, is certainly more difficult to work with than saying that a functor is a map on the set of objects and the set of arrows preserving identities and composition. Even if we want to use an unbiased definition, it's still the same. That is, we just say that F preserves n-ary composites for all n in N (notably including 0, where the 0ary composite at an object is the identity).

(By the way, defining the identity to be the 0-ary composite doesn't seem right, since the 0-ary composite does not have an explicit domain/codomain. This means that we have to define a notion of a 0-ary composite at an object, which is much less parsimonious than just splitting off the case of n=0.)

Edit: Eric, I am against changing the definition of a diagram. The whole beauty of the standard approach is not that we can describe categories as graphs, but that we can describe a diagram as a functor!
- CommentRowNumber203.
- CommentAuthorEric
- CommentTimeApr 2nd 2010
- PermaLink
Author: Eric
Format: Markdown@Harry: No worries about that. The help you give more than makes up for things like that. Plus, I somewhat disagree with Todd. Being unfriendly towards engineers actually puts you in very good company in the mathematics community (present company excluded!) :) As I mentioned before, since you are not a "scientist nor engineer", you do not have a say in what they find easier :) The most you can say is that it is easier for you and that is great. I've been around long enough and I've known enough "scientists and engineers" to say with some confidence that most would be much more comfortable working with graphs, since graphs pervade almost all scientific disciplines. Besides, in my suggested modification to the nLab above, the functor aspect was front and center and was part of the definition. The relation to graph morphisms was secondary. Or are you hesitant about using the word "graph" in the definition? If that is the case, then I'd disagree. I think it is perfectly acceptable for the word graph to appear in the definition of a diagram. What I'd really like to know is whether my suggested modification is acceptable to the experts. Is it?

@Harry: No worries about that. The help you give more than makes up for things like that. Plus, I somewhat disagree with Todd. Being unfriendly towards engineers actually puts you in very good company in the mathematics community (present company excluded!) :)

As I mentioned before, since you are not a "scientist nor engineer", you do not have a say in what they find easier :) The most you can say is that it is easier for you and that is great. I've been around long enough and I've known enough "scientists and engineers" to say with some confidence that most would be much more comfortable working with graphs, since graphs pervade almost all scientific disciplines.

Besides, in my suggested modification to the nLab above, the functor aspect was front and center and was part of the definition. The relation to graph morphisms was secondary.

Or are you hesitant about using the word "graph" in the definition? If that is the case, then I'd disagree. I think it is perfectly acceptable for the word graph to appear in the definition of a diagram.

What I'd really like to know is whether my suggested modification is acceptable to the experts. Is it?
- CommentRowNumber204.
- CommentAuthorTodd_Trimble
- CommentTimeApr 2nd 2010
- (edited Apr 2nd 2010)
- PermaLink
Author: Todd_Trimble
Format: MarkdownEric: you could rephrase that way, but now that this discussion is at last converging toward consensus (yay!), I think the issue of whether to use free categories or not becomes a bit subsidiary and can be relegated to a comment. In other words, you could define a diagram as we currently have it in the Lab, as a functor <latex>F: J \to C</latex>, and say the diagram commutes if it factors through a preorder <latex>P</latex>. (This <latex>P</latex> can be taken to be the _preorder reflection_ of <latex>J</latex> -- offhand I'm not sure where that would link to.) This uses a few less words than if you brought in free categories or whatever, and is somewhat more general. But I still think Mike's earlier words on this still have a certain legitimacy and deserve to be noted as a comment in the article. I lean slightly toward the more general formulation, but either definition is okay with me; the definition you want to use Eric is certainly defensible. At this point I can bow out of the conversation. :-)

Eric: you could rephrase that way, but now that this discussion is at last converging toward consensus (yay!), I think the issue of whether to use free categories or not becomes a bit subsidiary and can be relegated to a comment.

In other words, you could define a diagram as we currently have it in the Lab, as a functor $F: J \to C$ , and say the diagram commutes if it factors through a preorder $P$ . (This $P$ can be taken to be the preorder reflection of $J$ -- offhand I'm not sure where that would link to.) This uses a few less words than if you brought in free categories or whatever, and is somewhat more general. But I still think Mike's earlier words on this still have a certain legitimacy and deserve to be noted as a comment in the article.

I lean slightly toward the more general formulation, but either definition is okay with me; the definition you want to use Eric is certainly defensible. At this point I can bow out of the conversation. :-)
- CommentRowNumber205.
- CommentAuthorEric
- CommentTimeApr 2nd 2010
- (edited Apr 2nd 2010)
- PermaLink
Author: Eric
Format: Markdown@Todd: Ok, but if <latex>J</latex> is not free, do we need to abandon the adjunction? I would like to be able to think in terms of graph morphisms, but in the more general case, would graph morphisms just be special cases?

@Todd: Ok, but if $J$ is not free, do we need to abandon the adjunction? I would like to be able to think in terms of graph morphisms, but in the more general case, would graph morphisms just be special cases?
- CommentRowNumber206.
- CommentAuthorTodd_Trimble
- CommentTimeApr 2nd 2010
- PermaLink
Author: Todd_Trimble
Format: MarkdownYes, that formulation doesn't mention that adjunction. Graph morphisms would be special cases. But those are the cases which generally arise in practice when we wave our hands and point to or draw commutative diagrams, as one can verify by opening just about any book. :-)

Yes, that formulation doesn't mention that adjunction. Graph morphisms would be special cases. But those are the cases which generally arise in practice when we wave our hands and point to or draw commutative diagrams, as one can verify by opening just about any book. :-)
- CommentRowNumber207.
- CommentAuthorEric
- CommentTimeApr 2nd 2010
- (edited Apr 2nd 2010)
- PermaLink
Author: Eric
Format: MarkdownHmm... I'm not a big fan of definitions like: <ul> <li>A [[diagram]] is simply a functor <latex>F:C\to D</latex>. Period.</li> <li>A [[representation]] is simply a functor <latex>F:C\to D</latex>. Period.</li> </ul> That makes me wonder, "Is a diagram simply a representation? Why have three words for the same thing?" In this case, I probably would prefer to restrict things just a little unless there is a good reason not to. That way I can safely keep in the back of my head "a diagram is basically a graph morphism". This is what it means for all practical purposes. Should we take a vote on it? :) Thanks again everyone for your help. I just redrew my favorite example, but now starting with a graph <latex>G</latex> given by <latex>X\stackrel{f}{\to} Y</latex> and a graph <latex>L</latex> given by <latex>\stackrel{e}{\circlearrowleft}</latex>. From here we can construct the free category of the loop <latex>F(L)</latex> and project this back down to a graph <latex>U\circ F(L)</latex> with one node and an infinite number of directed edges, one for each morphism <latex>1</latex>, <latex>e</latex>, <latex>e^2</latex>, etc. A diagram is a graph morphism <latex>G\to U\circ F(L)</latex>. Of course <latex>f\mapsto e^n</latex> for some <latex>n\ge 0</latex> and there are no hidden identities etc forcing <latex>f\mapsto 1</latex>. Mystery solved :)
Hmm... I'm not a big fan of definitions like:
- A diagram is simply a functor $F:C\to D$ . Period.
- A representation is simply a functor $F:C\to D$ . Period.
That makes me wonder, "Is a diagram simply a representation? Why have three words for the same thing?"

In this case, I probably would prefer to restrict things just a little unless there is a good reason not to. That way I can safely keep in the back of my head "a diagram is basically a graph morphism". This is what it means for all practical purposes.

Should we take a vote on it? :)

Thanks again everyone for your help. I just redrew my favorite example, but now starting with a graph $G$ given by

and a graph $L$ given by

$\stackrel{e}{\circlearrowleft}$ .

From here we can construct the free category of the loop $F(L)$ and project this back down to a graph $U\circ F(L)$ with one node and an infinite number of directed edges, one for each morphism $1$ , $e$ , $e^2$ , etc.

A diagram is a graph morphism $G\to U\circ F(L)$ . Of course $f\mapsto e^n$ for some $n\ge 0$ and there are no hidden identities etc forcing $f\mapsto 1$ .

Mystery solved :)
- CommentRowNumber208.
- CommentAuthorMike Shulman
- CommentTimeApr 2nd 2010
- PermaLink
Author: Mike Shulman
Format: MarkdownWhat about "A diagram is a functor. When we ask whether a diagram *commutes*, we are usually thinking only of diagrams whose source is the free category on a graph, in which case we say the diagram commutes iff it factors through the free preorder on that graph (or, equivalently, through any preorder). Note that by adjunction, a functor <latex>Free(G) \to C</latex> is the same as a graph morphism <latex>G\to Underlying(C)</latex>, i.e. a 'labeling' of the vertices and edges of G by objects and morphisms in C. This labeling is what we usually draw on the page when we talk about commutative diagrams."

What about "A diagram is a functor. When we ask whether a diagram commutes, we are usually thinking only of diagrams whose source is the free category on a graph, in which case we say the diagram commutes iff it factors through the free preorder on that graph (or, equivalently, through any preorder). Note that by adjunction, a functor $Free(G) \to C$ is the same as a graph morphism $G\to Underlying(C)$ , i.e. a 'labeling' of the vertices and edges of G by objects and morphisms in C. This labeling is what we usually draw on the page when we talk about commutative diagrams."
- CommentRowNumber209.
- CommentAuthorTodd_Trimble
- CommentTimeApr 3rd 2010
- PermaLink
Author: Todd_Trimble
Format: MarkdownThat sounds good to me, Mike. Eric, my own take is that different terms for (roughly) the same concept can convey slightly different senses or "moods" or emphases, just as in ordinary language use. For example, I would sooner say "a diagram in <latex>D</latex> is a functor <latex>F: J \to D</latex>, where <latex>J</latex> is small. A representation of <latex>C</latex> is a functor whose domain is <latex>C</latex>." There's a difference in sense.

That sounds good to me, Mike.

Eric, my own take is that different terms for (roughly) the same concept can convey slightly different senses or "moods" or emphases, just as in ordinary language use. For example, I would sooner say "a diagram in $D$ is a functor $F: J \to D$ , where $J$ is small. A representation of $C$ is a functor whose domain is $C$ ." There's a difference in sense.
- CommentRowNumber210.
- CommentAuthorEric
- CommentTimeApr 3rd 2010
- PermaLink
Author: Eric
Format: MarkdownI should go through these 200+ comments and pick out pearls of wisdom and add them to the nLab. That is a small project and, time permitting, I will do my best. But for now, I thought I would summarize some of the key mental stumbling blocks that I think point to ways we can improve the nLab to help future "scientists and engineers" avoid the same problems I had. First, although this probably sounds silly, one thing that really hung me up was thinking that the image <latex>F(C)</latex> was a subcategory of <latex>D</latex>. This one factoid caused me immeasurable mental duress. This should be stated clearly somewhere on [[functor]] I think. Because of this, I thought every diagram was a category. This should also be repeated on [[diagram]], i.e. a diagram is not necessarily a subcategory. For instance, since a diagram does not need to be a category, we can have diagrams like this <latex>\bullet\stackrel{e}{\to}\bullet</latex> without hidden antiparallel identity morphisms stretched between the two copies of <latex>\bullet</latex>. If this were a category, I would probably insist that there should be hidden antiparallel identity morphisms. Second, when talking about commuting diagrams, we are almost always talking about functors from a free category, in which case we can mentally switch to thinking about graph morphisms due to the adjunction. This is pretty cool. Commuting diagrams in terms of graph morphisms is something I think "scientists and engineers" could really internalize easily, so this gives a nice segue to adjunctions. For the record, I think most scientists and engineers can easily internalize commuting diagrams in terms of functors too as long as they avoid the trap of thinking a diagram has to be a category (like I did!). A part of me still wishes we could define a diagram as follows: >Given a graph <latex>G</latex> and a category <latex>C</latex>, a **diagram** in <latex>C</latex> is a functor <latex>F(G)\to C</latex>. > >A **commutative diagram** is a diagram <latex>F(G)\to P\to C</latex> which factors through a preorder <latex>P</latex>. I like this because diagrams are almost always (I can't think of a counter example) functors from free categories for some graph. Defining it this way allows the equivalent definition stated via the adjunction: >Given a graph <latex>G</latex> and a category <latex>C</latex>, a **diagram** in <latex>U(C)</latex> is a graph morphism <latex>G\to U(C)</latex>. > >A **commutative diagram** is a diagram <latex>F(G)\to P\to C</latex> which factors through a preorder <latex>P</latex>. In fact, that last sentence could probably be improved, because I'm willing to bet that any preorder is a quiver for some graph, so it could probably be recast as a special kind of graph morphism. There is one more worry on my mind though... Back <a href="http://www.math.ntnu.no/~stacey/Vanilla/nForum/comments.php?DiscussionID=332&Focus=7112#Comment_7112">here</a>, I gave two definitions: *** **Definition #1:** Given categories <latex>C</latex> and <latex>D</latex>, a **functor** <latex>F:C\to D</latex> is a map that sends each object <latex>x</latex> in <latex>C</latex> to an object <latex>F(x)</latex> in <latex>D</latex> and each morphism <latex>f:x\to y</latex> in <latex>C</latex> to a morphism <latex>F(f):F(x)\to F(y)</latex> in <latex>D</latex> such that: <ol> <li><latex>F</latex> preserves compositions,</li> <li><latex>F</latex> preserves identities. </ol> **Definition #2:** Given categories <latex>C</latex> and <latex>D</latex>, a **functor** <latex>F:C\to D</latex> is a map that sends each object <latex>x</latex> in <latex>C</latex> to an object <latex>F(x)</latex> in <latex>D</latex> and each morphism <latex>f:x\to y</latex> in <latex>C</latex> to a morphism <latex>F(f):F(x)\to F(y)</latex> in <latex>D</latex> such that each commuting diagram in <latex>C</latex> maps to a commuting diagram in <latex>D</latex>. *** Mike responded <a href="http://www.math.ntnu.no/~stacey/Vanilla/nForum/comments.php?DiscussionID=332&Focus=7140#Comment_7140">here</a>: >@Eric: I would consider your definition #2 to be unbiased, and to include definition #1. The two axioms in definition #1 are both particular sorts of commuting diagrams: a composition of arrows is a commuting triangle, and an identity is a commuting loop. I interpreted Mike's response to mean Definition #1 and Definition #2 were the same, but all Mike really said was #2 includes #1. For them to be the same, #1 would also have to include #2. I'm afraid that might not be the case. I'm afraid #2 might be stronger than #1. I'm not sure, but I think with #2, we WOULD have the image always being a subcategory. What do you think?
This comment is invalid XML; displaying source. <p>I should go through these 200+ comments and pick out pearls of wisdom and add them to the nLab. That is a small project and, time permitting, I will do my best.</p> <p>But for now, I thought I would summarize some of the key mental stumbling blocks that I think point to ways we can improve the nLab to help future "scientists and engineers" avoid the same problems I had.</p> <p>First, although this probably sounds silly, one thing that really hung me up was thinking that the image <img src="/extensions/vLaTeX/cache/latex_dc3fcd71eea8cc9d58dab8ea82eae894.png" title="F(C)" style="vertical-align:-20%;" class="tex" alt="F(C)" /> was a subcategory of <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" />. This one factoid caused me immeasurable mental duress. This should be stated clearly somewhere on <a href="https://ncatlab.org/nlab/show/functor">functor</a> I think. Because of this, I thought every diagram was a category. This should also be repeated on <a href="https://ncatlab.org/nlab/show/diagram">diagram</a>, i.e. a diagram is not necessarily a subcategory.</p> <p>For instance, since a diagram does not need to be a category, we can have diagrams like this</p> <img src="/extensions/vLaTeX/cache/latex_4d662ed5ce56aeded1feedc49769df6f.png" title="\bullet\stackrel{e}{\to}\bullet" style="vertical-align:-20%;" class="tex" alt="\bullet\stackrel{e}{\to}\bullet" /> <p>without hidden antiparallel identity morphisms stretched between the two copies of <img src="/extensions/vLaTeX/cache/latex_2668009033d84cdc8d16f29c11ae03fd.png" title="\bullet" style="vertical-align:-20%;" class="tex" alt="\bullet" />. If this were a category, I would probably insist that there should be hidden antiparallel identity morphisms.</p> <p>Second, when talking about commuting diagrams, we are almost always talking about functors from a free category, in which case we can mentally switch to thinking about graph morphisms due to the adjunction. This is pretty cool. Commuting diagrams in terms of graph morphisms is something I think "scientists and engineers" could really internalize easily, so this gives a nice segue to adjunctions. For the record, I think most scientists and engineers can easily internalize commuting diagrams in terms of functors too as long as they avoid the trap of thinking a diagram has to be a category (like I did!).</p> <p>A part of me still wishes we could define a diagram as follows:</p> <blockquote> <p>Given a graph <img src="/extensions/vLaTeX/cache/latex_0643966166b879e3e23697a6b846efd7.png" title="G" style="vertical-align:-20%;" class="tex" alt="G" /> and a category <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" />, a <strong>diagram</strong> in <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> is a functor <img src="/extensions/vLaTeX/cache/latex_0d1483327531dd4153e5ea333e6a3753.png" title="F(G)\to C" style="vertical-align:-20%;" class="tex" alt="F(G)\to C" />.</p> <p>A <strong>commutative diagram</strong> is a diagram <img src="/extensions/vLaTeX/cache/latex_09ac822acf7c1965b64c285756e7b0a9.png" title="F(G)\to P\to C" style="vertical-align:-20%;" class="tex" alt="F(G)\to P\to C" /> which factors through a preorder <img src="/extensions/vLaTeX/cache/latex_0827b2155898e7e29e51b4330f4c0e75.png" title="P" style="vertical-align:-20%;" class="tex" alt="P" />.</p> </blockquote> <p>I like this because diagrams are almost always (I can't think of a counter example) functors from free categories for some graph. Defining it this way allows the equivalent definition stated via the adjunction:</p> <blockquote> <p>Given a graph <img src="/extensions/vLaTeX/cache/latex_0643966166b879e3e23697a6b846efd7.png" title="G" style="vertical-align:-20%;" class="tex" alt="G" /> and a category <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" />, a <strong>diagram</strong> in <img src="/extensions/vLaTeX/cache/latex_6b9aaf533fd24793040c8ec9ce302c75.png" title="U(C)" style="vertical-align:-20%;" class="tex" alt="U(C)" /> is a graph morphism <img src="/extensions/vLaTeX/cache/latex_27cc390aec1b1c61f926a3fbe835813e.png" title="G\to U(C)" style="vertical-align:-20%;" class="tex" alt="G\to U(C)" />.</p> <p>A <strong>commutative diagram</strong> is a diagram <img src="/extensions/vLaTeX/cache/latex_09ac822acf7c1965b64c285756e7b0a9.png" title="F(G)\to P\to C" style="vertical-align:-20%;" class="tex" alt="F(G)\to P\to C" /> which factors through a preorder <img src="/extensions/vLaTeX/cache/latex_0827b2155898e7e29e51b4330f4c0e75.png" title="P" style="vertical-align:-20%;" class="tex" alt="P" />.</p> </blockquote> <p>In fact, that last sentence could probably be improved, because I'm willing to bet that any preorder is a quiver for some graph, so it could probably be recast as a special kind of graph morphism.</p> <p>There is one more worry on my mind though...</p> <p>Back <a href="http://www.math.ntnu.no/~stacey/Vanilla/nForum/comments.php?DiscussionID=332&Focus=7112#Comment_7112">here</a>, I gave two definitions:</p> <hr /> <p><strong>Definition #1:</strong></p> <p>Given categories <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> and <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" />, a <strong>functor</strong> <img src="/extensions/vLaTeX/cache/latex_4ab4a8e1b1343def201689148996e8cd.png" title="F:C\to D" style="vertical-align:-20%;" class="tex" alt="F:C\to D" /> is a map that sends each object <img src="/extensions/vLaTeX/cache/latex_0e29540f708ca8b32bde8e2c33e97582.png" title="x" style="vertical-align:-20%;" class="tex" alt="x" /> in <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> to an object <img src="/extensions/vLaTeX/cache/latex_91281b8b55384164c30dff8ad67a7219.png" title="F(x)" style="vertical-align:-20%;" class="tex" alt="F(x)" /> in <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" /> and each morphism <img src="/extensions/vLaTeX/cache/latex_fda7a63267491b34b45b8d7b684bb1f8.png" title="f:x\to y" style="vertical-align:-20%;" class="tex" alt="f:x\to y" /> in <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> to a morphism <img src="/extensions/vLaTeX/cache/latex_ddd586710e765e3df32ec4ac5dfb8f2c.png" title="F(f):F(x)\to F(y)" style="vertical-align:-20%;" class="tex" alt="F(f):F(x)\to F(y)" /> in <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" /> such that:</p> <ol> <li><img src="/extensions/vLaTeX/cache/latex_5ec3dcd4fa96727f6008946ebbeebfa2.png" title="F" style="vertical-align:-20%;" class="tex" alt="F" /> preserves compositions,</li> <li><img src="/extensions/vLaTeX/cache/latex_5ec3dcd4fa96727f6008946ebbeebfa2.png" title="F" style="vertical-align:-20%;" class="tex" alt="F" /> preserves identities. </ol> <p><strong>Definition #2:</strong></p> <p>Given categories <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> and <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" />, a <strong>functor</strong> <img src="/extensions/vLaTeX/cache/latex_4ab4a8e1b1343def201689148996e8cd.png" title="F:C\to D" style="vertical-align:-20%;" class="tex" alt="F:C\to D" /> is a map that sends each object <img src="/extensions/vLaTeX/cache/latex_0e29540f708ca8b32bde8e2c33e97582.png" title="x" style="vertical-align:-20%;" class="tex" alt="x" /> in <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> to an object <img src="/extensions/vLaTeX/cache/latex_91281b8b55384164c30dff8ad67a7219.png" title="F(x)" style="vertical-align:-20%;" class="tex" alt="F(x)" /> in <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" /> and each morphism <img src="/extensions/vLaTeX/cache/latex_fda7a63267491b34b45b8d7b684bb1f8.png" title="f:x\to y" style="vertical-align:-20%;" class="tex" alt="f:x\to y" /> in <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> to a morphism <img src="/extensions/vLaTeX/cache/latex_ddd586710e765e3df32ec4ac5dfb8f2c.png" title="F(f):F(x)\to F(y)" style="vertical-align:-20%;" class="tex" alt="F(f):F(x)\to F(y)" /> in <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" /> such that each commuting diagram in <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align:-20%;" class="tex" alt="C" /> maps to a commuting diagram in <img src="/extensions/vLaTeX/cache/latex_2741ee6cf4a5aa48b2ee29b3b0fee62e.png" title="D" style="vertical-align:-20%;" class="tex" alt="D" />.</p> <hr /> <p>Mike responded <a href="http://www.math.ntnu.no/~stacey/Vanilla/nForum/comments.php?DiscussionID=332&Focus=7140#Comment_7140">here</a>:</p> <blockquote> <p>@Eric: I would consider your definition #2 to be unbiased, and to include definition #1. The two axioms in definition #1 are both particular sorts of commuting diagrams: a composition of arrows is a commuting triangle, and an identity is a commuting loop.</p> </blockquote> <p>I interpreted Mike's response to mean Definition #1 and Definition #2 were the same, but all Mike really said was #2 includes #1. For them to be the same, #1 would also have to include #2. I'm afraid that might not be the case. I'm afraid #2 might be stronger than #1. I'm not sure, but I think with #2, we WOULD have the image always being a subcategory. What do you think?</p>
- CommentRowNumber211.
- CommentAuthorMike Shulman
- CommentTimeApr 3rd 2010
- PermaLink
Author: Mike Shulman
Format: MarkdownThey are the same. If <latex>G:C\to D</latex> is a functor in the usual sense (i.e. definition #1), and <latex>Free(G) \to P \to C</latex> is a commuting diagram factoring through a preorder <latex>P</latex>, then since functor composition (in the usual sense) is associative, the induced diagram <latex>Free(G) \to C\to D</latex> also factors through <latex>P</latex>. Diagrams in the sense of "diagrams-we-draw-on-a-page" are basically always functors from a free category or equivalently graph maps. I think the point is that there is a *different meaning* of "diagram" which refers to an arbitrary functor. It is fairly common, for instance, to talk about <latex>D^C</latex> as "the category of diagrams in <latex>D</latex> of shape <latex>C</latex>" for arbitrary categories <latex>C</latex> and <latex>D</latex>. Not every preorder is free on a graph, in fact very few are. For instance, the commuting square is not.

They are the same. If $G:C\to D$ is a functor in the usual sense (i.e. definition #1), and $Free(G) \to P \to C$ is a commuting diagram factoring through a preorder $P$ , then since functor composition (in the usual sense) is associative, the induced diagram $Free(G) \to C\to D$ also factors through $P$ .

Diagrams in the sense of "diagrams-we-draw-on-a-page" are basically always functors from a free category or equivalently graph maps. I think the point is that there is a different meaning of "diagram" which refers to an arbitrary functor. It is fairly common, for instance, to talk about $D^C$ as "the category of diagrams in $D$ of shape $C$ " for arbitrary categories $C$ and $D$ .

Not every preorder is free on a graph, in fact very few are. For instance, the commuting square is not.
- CommentRowNumber212.
- CommentAuthorTodd_Trimble
- CommentTimeApr 3rd 2010
- (edited Apr 3rd 2010)
- PermaLink
Author: Todd_Trimble
Format: Markdown[Edit: I'm covering much the same ground as Mike just did] <blockquote> A part of me still wishes we could define a diagram as follows ... </blockquote> Again, I personally don't mind our doing that. <blockquote> I like this because diagrams are almost always (I can't think of a counter example) functors from free categories for some graph. </blockquote> A counterexample would be a functor whose domain has just one object and exactly two morphisms. The non-identity morphism could be either idempotent or involutive. This category is not a free category. However, in the context of speaking of commutative diagrams, this sort of thing is arguably a little bit artificial. <blockquote> In fact, that last sentence could probably be improved, because I'm willing to bet that any preorder is a quiver for some graph. </blockquote> Sorry, not true. The commuting square, i.e., the poset consisting of subsets of $\{0, 1\}$ ordered by inclusion, is not a quiver (free category). Do you see why? (In fact, here's a little factoid I rather enjoy: if the free category on a directed graph has a terminal object, then the graph is a tree.) <blockquote> I interpreted Mike's response to mean Definition #1 and Definition #2 were the same, but all Mike really said was #2 includes #1. For them to be the same, #1 would also have to include #2. I'm afraid that might not be the case. I'm afraid #2 might be stronger than #1. I'm not sure, but I think with #2, we WOULD have the image always being a subcategory. What do you think? </blockquote> The two statements are equivalent. Definition # 1 is the standard definition of functor. It implies definition #2, because functors preserve commuting diagrams. Definition # 2 could be considered an axiom scheme, since you are quantifying over all diagrams in <latex>C</latex>. Probably you see definition #1 more often because there are only two axioms. The image of a category <latex>F(C)</latex> not necessarily being a subcategory has nothing to do with preservation of commuting diagrams. It has to do with the image not necessarily being closed under compositions. I gave an example a while back.
This comment is invalid XHTML+MathML+SVG; displaying source. <div> <p>[Edit: I'm covering much the same ground as Mike just did]</p> <blockquote> A part of me still wishes we could define a diagram as follows ... </blockquote> <p>Again, I personally don't mind our doing that.</p> <blockquote> I like this because diagrams are almost always (I can't think of a counter example) functors from free categories for some graph. </blockquote> <p>A counterexample would be a functor whose domain has just one object and exactly two morphisms. The non-identity morphism could be either idempotent or involutive. This category is not a free category.</p> <p>However, in the context of speaking of commutative diagrams, this sort of thing is arguably a little bit artificial.</p> <blockquote> In fact, that last sentence could probably be improved, because I'm willing to bet that any preorder is a quiver for some graph. </blockquote> <p>Sorry, not true. The commuting square, i.e., the poset consisting of subsets of ${0, 1}$ ordered by inclusion, is not a quiver (free category). Do you see why?</p> <p>(In fact, here's a little factoid I rather enjoy: if the free category on a directed graph has a terminal object, then the graph is a tree.)</p> <blockquote> I interpreted Mike's response to mean Definition #1 and Definition #2 were the same, but all Mike really said was #2 includes #1. For them to be the same, #1 would also have to include #2. I'm afraid that might not be the case. I'm afraid #2 might be stronger than #1. I'm not sure, but I think with #2, we WOULD have the image always being a subcategory. What do you think? </blockquote> <p>The two statements are equivalent. Definition # 1 is the standard definition of functor. It implies definition #2, because functors preserve commuting diagrams.</p> <p>Definition # 2 could be considered an axiom scheme, since you are quantifying over all diagrams in <img src="/extensions/vLaTeX/cache/latex_ca43fb5496104dcafda44acbe4014b0e.png" title="C" style="vertical-align: -20%;" class="tex" alt="C"/>. Probably you see definition #1 more often because there are only two axioms.</p> <p>The image of a category <img src="/extensions/vLaTeX/cache/latex_dc3fcd71eea8cc9d58dab8ea82eae894.png" title="F(C)" style="vertical-align: -20%;" class="tex" alt="F(C)"/> not necessarily being a subcategory has nothing to do with preservation of commuting diagrams. It has to do with the image not necessarily being closed under compositions. I gave an example a while back.</p> </div>
- CommentRowNumber213.
- CommentAuthorEric
- CommentTimeApr 3rd 2010
- (edited Apr 3rd 2010)
- PermaLink
Author: Eric
Format: MarkdownNice! Thanks Mike.If no one beats me to it, I'll add your suggestions to the nLab. Edit: And thanks Todd! Yes. Thanks so much. That all makes perfect sense. All my fears are gone :)

Nice! Thanks Mike.If no one beats me to it, I'll add your suggestions to the nLab.

Edit: And thanks Todd! Yes. Thanks so much. That all makes perfect sense. All my fears are gone :)
- CommentRowNumber214.
- CommentAuthornLab edit announcer
- CommentTimeFeb 5th 2019
- PermaLink
Author: nLab edit announcer
Format: MarkdownItexAdded preservation of identity to ideas section. It is misleading to think that a functor does this automatically. Take the terminal category $\mathbf{1}$ and an idempotent monoid $D$. A functor $F : \mathbf{1} \to D$ has the following: $F(f) = F(f \circ 1_{\mathbf{1}}) = F(f) \circ F(1_{\mathbf{1}})$ but if $F$ does not preserve identity then $F(1)$ may be the idempotent. I think when these are groupoids, preservation of identity can be dropped but idempotent categories require the restriction. Anonymous <a href="https://ncatlab.org/nlab/revision/diff/functor/57">diff</a>, <a href="https://ncatlab.org/nlab/revision/functor/57">v57</a>, <a href="https://ncatlab.org/nlab/show/functor">current</a>

Added preservation of identity to ideas section. It is misleading to think that a functor does this automatically. Take the terminal category $\mathbf{1}$ and an idempotent monoid $D$ . A functor $F : \mathbf{1} \to D$ has the following: $F(f) = F(f \circ 1_{\mathbf{1}}) = F(f) \circ F(1_{\mathbf{1}})$ but if $F$ does not preserve identity then $F(1)$ may be the idempotent. I think when these are groupoids, preservation of identity can be dropped but idempotent categories require the restriction.

Anonymous

diff, v57, current
- CommentRowNumber215.
- CommentAuthorMike Shulman
- CommentTimeFeb 5th 2019
- PermaLink
Author: Mike Shulman
Format: MarkdownItexIn fact, I would say that both preservation of identities and composition are "the functoriality condition". <a href="https://ncatlab.org/nlab/revision/diff/functor/58">diff</a>, <a href="https://ncatlab.org/nlab/revision/functor/58">v58</a>, <a href="https://ncatlab.org/nlab/show/functor">current</a>

In fact, I would say that both preservation of identities and composition are “the functoriality condition”.

diff, v58, current
- CommentRowNumber216.
- CommentAuthorAli Caglayan
- CommentTimeFeb 5th 2019
- PermaLink
Author: Ali Caglayan
Format: MarkdownItexAlso the "categorification" should be of the notion of "identity preserving homomorphisms"?

Also the “categorification” should be of the notion of “identity preserving homomorphisms”?
- CommentRowNumber217.
- CommentAuthorMike Shulman
- CommentTimeFeb 5th 2019
- PermaLink
Author: Mike Shulman
Format: MarkdownItexA homomorphism (between structures with identities, like monoids or groups) always preserves identities.

A homomorphism (between structures with identities, like monoids or groups) always preserves identities.
- CommentRowNumber218.
- CommentAuthorDmitri Pavlov
- CommentTimeNov 21st 2020
- PermaLink
Author: Dmitri Pavlov
Format: MarkdownItexAdded a reference to Joyal's CatLab. <a href="https://ncatlab.org/nlab/revision/diff/functor/63">diff</a>, <a href="https://ncatlab.org/nlab/revision/functor/63">v63</a>, <a href="https://ncatlab.org/nlab/show/functor">current</a>

Added a reference to Joyal’s CatLab.

diff, v63, current
- CommentRowNumber219.
- CommentAuthorUrs
- CommentTimeJul 12th 2021
- PermaLink
Author: Urs
Format: MarkdownItexWanted to point to the component function $F_{x,y} \;\colon\; C(x,y) \xrightarrow{\;\;} D(F(x), F(y))$ of a functor, but it wasn't mentioned here. Have added it now to the first lines of the Idea-section, making some small adjustments in the course. This ancient entry would need a bit of a clean-up... <a href="https://ncatlab.org/nlab/revision/diff/functor/64">diff</a>, <a href="https://ncatlab.org/nlab/revision/functor/64">v64</a>, <a href="https://ncatlab.org/nlab/show/functor">current</a>

Wanted to point to the component function $F_{x,y} \;\colon\; C(x,y) \xrightarrow{\;\;} D(F(x), F(y))$ of a functor, but it wasn’t mentioned here. Have added it now to the first lines of the Idea-section, making some small adjustments in the course.

This ancient entry would need a bit of a clean-up…

diff, v64, current
- CommentRowNumber220.
- CommentAuthornLab edit announcer
- CommentTimeJun 7th 2022
- PermaLink
Author: nLab edit announcer
Format: MarkdownItexadding text from HoTT wiki Anonymous <a href="https://ncatlab.org/nlab/revision/diff/functor/65">diff</a>, <a href="https://ncatlab.org/nlab/revision/functor/65">v65</a>, <a href="https://ncatlab.org/nlab/show/functor">current</a>

adding text from HoTT wiki

Anonymous

diff, v65, current
- CommentRowNumber221.
- CommentAuthorUrs
- CommentTimeMay 20th 2023
- PermaLink
Author: Urs
Format: MarkdownItexadded pointer to: * [[Saunders MacLane]], §I.3 of: *[[Categories for the Working Mathematician]]*, Graduate Texts in Mathematics **5** Springer (1971, second ed. 1997) [[doi:10.1007/978-1-4757-4721-8](https://link.springer.com/book/10.1007/978-1-4757-4721-8)] <a href="https://ncatlab.org/nlab/revision/diff/functor/68">diff</a>, <a href="https://ncatlab.org/nlab/revision/functor/68">v68</a>, <a href="https://ncatlab.org/nlab/show/functor">current</a>
added pointer to:
- Saunders MacLane, §I.3 of: Categories for the Working Mathematician, Graduate Texts in Mathematics 5 Springer (1971, second ed. 1997) [doi:10.1007/978-1-4757-4721-8]
diff, v68, current

201 to 221 of 221

<
1
2
3
>