Take the 2-minute tour ×
Mathematics Stack Exchange is a question and answer site for people studying math at any level and professionals in related fields. It's 100% free, no registration required.

I'm teaching myself some category theory, and I find that I'm very slow with diagram chasing. It takes me some times a very long time to decide whether adding an arrow to a diagram preserves the diagram's commutativity, or that a given arrow exists, or is unique, or that two opposing arrows are actually inverses of each other, etc. Conversely, more than once I've been led down a blind alley as a result of careless diagram reasoning.

I'm looking for a "student's guide to diagram chasing", or the equivalent. I.e. a collection of tips, rules-of-thumb, dos-and-donts, etc., aimed at novices. E.g. rules like: "any two commuting diagrams may be pasted along a common edge".

If you happen to know of such a guide$^{1}$, please let me know of it.

Thanks!

$^{1}$IOW, please don't Google it for me. I have already done so, and found nothing that fits the description given above. My only hope is that such a guide exists as an appendix to a book, or maybe some unpublished classroom notes.


UPDATE

I thought that some readers will find this cautionary tale instructive.

While working through an arrow-pushing/diagram-chasing exercise, I drew this diagram

Innocent-looking, but wrong

(FWIW, all these diagrams are in good ol' Set.)

Here, $U\;\Pi_{\gamma,\delta}\;V$ is the binary relation

$$ \{(u, v) | \gamma(u) = \delta(v) \} \subseteq U \times V = U \;\Pi\; V, $$

and $\rho_U, \rho_V$ are given by $\rho_U((u, v)) = u, \rho_V((u, v)) = v$. The maps $\pi_U, \pi_V$, of course, are the canonical projections of the product $U \;\Pi\; V$. (Two-headed arrows denote epimorphisms, and "tailed" arrows, like the one for $\delta$, denote monomorphisms.)

The diagram sure looked innocent enough at first: nothing more than the usual categorical pullback (which here I'm calling $U\;\Pi_{\gamma,\delta}\;V$, to suggest a "fibered product"):

The usual categorical pullback

...conveniently outfitted with its inclusion $\iota_{\gamma,\delta}$ into the usual categorical product:

Inclusion into the usual categorical product

Needless to say, I soon began deriving (from the first diagram above, that is) some obviously nonsensical conclusions, such as "$\delta$ is monic $\Rightarrow \pi_U$ is monic $\Rightarrow U\;\Pi\; V \cong U$".

It took me a looong time to figure out that the source of the errors was incorrectly treating this subdiagram as commutative:

This is very wrong!

Of course, except for special cases (e.g. $V \cong W \cong \mathbf{1}$, the singleton), this last diagram is wrong.

I'm sure there's a moral to this story (other than "Diagrams are trickier than they look" and "Don't be stupid!"), but I have not quite figured it out yet.

share|improve this question

3 Answers 3

up vote 5 down vote accepted

Well, the first problem is that there aren't strict conventions on the use and meaning of diagrams. Although a formal definition exists—a diagram of objects and arrows in a category $\mathbf{C}$ is a functor $\mathscr{F} : \mathbf{J} \to \mathbf{C}$, for some (small) indexing category $\mathbf{J}$—in practice, a printed diagram, without clarifying remarks, may not be sufficient to determine what $\mathbf{J}$ is. For example, consider the traditional equaliser diagram $$\bullet \rightarrow \bullet \rightrightarrows \bullet$$ It is ‘obvious’ that the two parallel arrows are not equal. So this is an exception to the usual rule that every path through a diagram between a pair of vertices should be equal. Yet it is precisely this convention which is in force when it is ‘obvious’ that the composite arrows are equal. But I digress.

It is true that pasting two commutative diagrams along a matching pair of paths yields a commutative diagram. This is essentially by a discrete deformation of paths. For example, consider the diagrams

$$\begin{matrix} \bullet & \xrightarrow{f} & \bullet \newline {\scriptstyle g} \downarrow & & \downarrow {\scriptstyle h} \newline \bullet & \xrightarrow{k} & \bullet \end{matrix} \qquad \begin{matrix} \bullet & \xrightarrow{f'} & \bullet \newline {\scriptstyle g'} \downarrow & & \downarrow {\scriptstyle h'} \newline \bullet & \xrightarrow{k'} & \bullet \end{matrix} $$ Suppose $h = g'$. In order to verify that the diagram $$\begin{matrix} \bullet & \xrightarrow{f} & \bullet & \xrightarrow{f'} & \bullet \newline {\scriptstyle g} \downarrow & & \scriptstyle{g'} \downarrow {\scriptstyle h} & & \downarrow {\scriptstyle h'} \newline \bullet & \xrightarrow{k} & \bullet & \xrightarrow{k'} & \bullet \end{matrix} $$ also commutes, we need to show that the three paths between the top-left and bottom-right corners are equal. But this is obvious, since $k' \circ k \circ g = k' \circ h \circ f = k' \circ g' \circ f = h' \circ f' \circ f $.

The troublesome operation is adding in new arrows, since commutativity is not quite a local property. But it is possible to make life a little bit easier, by observing that we can subdivide the diagram into fragments, add in the arrow in each fragment and checking commutativity, then pasting the fragments back together.

As for existence and uniqueness: the only arrows which are guaranteed to exist are those obtained by composing arrows. Anything more than that requires specific knowledge of the objects and arrows in question.

share|improve this answer

I think diagram chasing is nothing but using injective and surjective homomorphism and exact sequences. If you learn those well, you can find those in diagrams. Try to reduce diagrams into simpler diagrams, morphisms or previously proved lemmas.

share|improve this answer

Part of the problem is that a lot of mathematicans who are heavy into categorical constructions and thinking think that most of it is just obvious if you look at the diagrams-just follow the arrows,they say. I think most beginners would disagree, but for some reason it never penetrates.

For relatively simple constructions-like commutative triangles and squares-it's easy to say it's obvious since you can just reexpress them in terms of good old fashioned functional arguments( write out the compositions explicitly). But in the real world, you can't really get far with this machinery if you can't read much more complicated diagrams. Even the proof of the Snake Lemma in homological algebra-which confuses the crap out of many graduate students-is baby stuff compared to some of the diagrams you'll see other areas of this subject. Including a number of 3-dimensional arrow chases.

So I agree-there's a need for a good practice source on this material for beginners.Until someone writes one,you'll need to do some digging around and putting together a patchwork source. Paulo Aluffi's Algebra:Chapter 0 has probably the best introduction to diagram chasing and its relation to categories that currently exists. It's really designed as a presentation for complete beginners-it does a very good job and has many good exercises for practice. A more general and equally helpful introduction can be found in Harold Simmons' An Introduction To Category Theory. 2 other,less comprehensive,but equally helpful sources are Chapter 4 of Ash's Basic Abstract Algebra ,which is available online at Ash's website and pages 43-53 of P.M. Cohn's An Introduction To Ring Theory. I think you'll find all these sources to be helpful.

share|improve this answer
2  
"...is baby stuff compared to the diagrams you'll see in higher category theory..." There is actually very little diagram chasing in higher category theory. This comes up more often (but still not as often as this question or this answer make it seem) in homological algebra, and some stuff with triangulated categories. For example, I think probably the biggest diagram written down in all of Higher Topos Theory involves at most 6 to 8 objects- most involve 4. –  Dylan Wilson Dec 18 '12 at 19:50
1  
@Dylan Ok,fair enough,I don't know much about higher category theory. I edited the statement accordingly. –  Mathemagician1234 Dec 18 '12 at 21:41

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.