It looks like you're new here. If you want to get involved, click one of these buttons!

- All Categories 2.3K
- Programming with Categories Course 33
- Exercises - Programming with Categories Course 21
- Mini-Talks - Programming with Categories Course 3
- Applied Category Theory Course 341
- Applied Category Theory Seminar 4
- Exercises - Applied Category Theory Course 149
- Discussion Groups 50
- How to Use MathJax 15
- Chat 487
- Azimuth Code Project 108
- News and Information 147
- Azimuth Blog 149
- Azimuth Forum 29
- Azimuth Project 189
- - Strategy 108
- - Conventions and Policies 21
- - Questions 43
- Azimuth Wiki 711
- - Latest Changes 701
- - - Action 14
- - - Biodiversity 8
- - - Books 2
- - - Carbon 9
- - - Computational methods 38
- - - Climate 53
- - - Earth science 23
- - - Ecology 43
- - - Energy 29
- - - Experiments 30
- - - Geoengineering 0
- - - Mathematical methods 69
- - - Meta 9
- - - Methodology 16
- - - Natural resources 7
- - - Oceans 4
- - - Organizations 34
- - - People 6
- - - Publishing 4
- - - Reports 3
- - - Software 21
- - - Statistical methods 2
- - - Sustainability 4
- - - Things to do 2
- - - Visualisation 1
- General 42

Options

*Revision history:*

*- 2018 06 18: Removed an unhelpful paragraph.*

*- 2018 05 26 : First version.*

## Comments

`![picture](https://i.imgur.com/qTEaVos.png)`

I find that the "light cone" visualization helps to fix some of the inconsistencies:

This uses the Hasse diagram "smaller on bottom" order, but remains consistent with the standard symbols for "meet" and "join": the future light cone looks like a \(\vee\) for "least upper bound", and the past light cone looks like a \(\wedge\) for "greatest lower bound"). I still have to remember which symbol goes with which word, but things aren't quite so inconsistent from here.

(In other words, I don't interpret \(\vee\) and \(wedge\) as arrows, but as cones of light emanating from a flashlight. Think about the negative space around the symbol, rather than the symbol itself!)

This comes down to the defining property, where if "f" is a left adjoint to "g", then "f" appears on the

leftof the \(\le\): \(f(x) \le y \Leftrightarrow x \le g(y)\).`I find that the ["light cone"](https://en.wikipedia.org/wiki/Light_cone) visualization helps to fix some of the inconsistencies: <center>![](https://upload.wikimedia.org/wikipedia/commons/thumb/1/16/World_line.svg/470px-World_line.svg.png)</center> This uses the Hasse diagram "smaller on bottom" order, but remains consistent with the standard symbols for "meet" and "join": the future light cone looks like a \\(\vee\\) for "least upper bound", and the past light cone looks like a \\(\wedge\\) for "greatest lower bound"). I still have to remember which symbol goes with which word, but things aren't quite so inconsistent from here. (In other words, I don't interpret \\(\vee\\) and \\(wedge\\) as arrows, but as cones of light emanating from a flashlight. Think about the negative space around the symbol, rather than the symbol itself!) > I had a lousy time trying to memorize what made a "left adjoint" different from a "right adjoint". This comes down to the defining property, where if "f" is a left adjoint to "g", then "f" appears on the _left_ of the \\(\le\\): \\(f(x) \le y \Leftrightarrow x \le g(y)\\).`