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.
(This is more an algebra question than category theory.)
The nLab alleges that the automorphism group of a 1-sorted torsor is the closure under composition of in . (See point 3. under section 3, to which I linked)
Here, must obey (in case you don't want to visit nlab):
and
using standard .
Anyway, this surprises me. For a group , there is similarly a conjugation operation , but the Moore closure of this operation (say, starting from generators) only gives the "Inner" automorphisms . There is no operation that generally yields also the "outer" automorphisms , at least that I know of; how nice that would be!!
So I'm very surprised by this claim, that ! Can anyone confirm whether this is actually true, or provide some insight as to why/how?
(FWIW nlab calls the 1-sorted theory a "heap" after the translation of груда itself a pun on the Russian for group... but heap is already something much more common in compsci; wikipedia also suggests "groud")
If it helps, the 1-sorted torsor operation in terms of an adjoint group operation is:
where takes the inverse.
And specifically it is claimed that for all combinations of , the closure under composition of these maps
yields all of .
I'll start poking through the literature but if anybody has any leads, would certainly appreciate them.
I think you're confusing automorphisms of the heap with automorphisms of the group! An analogy is that every group arises as the automorphism group of its Cayley graph. We wrote a section on heaps (/grouds) in the symmetry book, Sec. 4.17. (Don't call them torsors: they are equivalently pairs of a group G and a G-torsor, as also mentioned on the nLab page.
Thanks -- That's a very cool book!
FWIW, the nLab seems to be confused/inconsistent about this issue as well;
"""
More precisely, a torsor (also known as a heap when stated in a single-sorted form) is a set
equipped with a ternary operation ...
"""
from [[torsor]] -- This is the first time I have read about heaps, so I admit I just took the nLab at its word, and only skimmed the page on heaps; will suggest an update once things are clearer to me.
Again, really cool book! I know it's still in production, but still exciting to see HoTT making its way into abstract algebra books! The standard curriculum sure could use a shake-up. ("What's a monoid? What's a rig?" "They are things we do not speak of, now go write Sylow's theorems on the board times!")
As Ulrik hinted, the usual concept of a torsor is: you've got a group G, and then a G-torsor is a nonempty set X with a free and transitive action of G. Another way to say it, which cleverly hides the annoying 'nonempty' condition, is to say a G-torsor is a set X with an action of G:
but also a 'division' operation
obeying
I list about a dozen extremely familiar examples of torsors here:
For example: dates in a calendar, notes in the chromatic scale, points in the plane, electrical potentials, etc.
If we want to package a group G and a G-torsor X into a single structure, we can use X, but we need to use a ternary operation: we can divide two elements of X and get an element of G, but if we're trying to avoid talking about G we should then have it act on another element of X! So we can call this ternary operation
and we can figure out the axioms this operation obeys from the axioms of a group and those of a G-torsor. This gives the definition of a heap.
If someone could read the nLab article 'heap' and not learn all this stuff, there's something missing from it.
Okay, I looked at the article and everything I said is there - but maybe not so easy to absorb?
In particular, a heap is essentially the same as a group G and a torsor of this group. In particular, from a heap, no matter how you define it, you can extract a group G and a G-torsor.
For some reason the nLab calls this group the automorphism group of the heap. I'm not at all convinced that this is a good name. The automorphism group of a heap $H$ should be the group of all bijections $H \to H$ that preserve the ternary operation. Is that isomorphic to what the nLab is calling the automorphism group???
Thanks to you both!! I'll mark this topic resolved.
Well, please don't yet.
oh ok!
I realize I haven't really proved that what the nLab calls the automorphism group of the heap is not really the automorphism group!
But we can prove that it is the group now that I look at it
So unless the group is ... :)
What do you mean 'the group'? Which group?
It would be nice to be a bit clearer.
Anyway, if we can prove that what the nLab calls the automorphism group of a heap is not the group of all bijections of the heap preserving the ternary operation on the heap, then I can add a remark to the nLab saying the term 'automorphism group' is being used in a misleading way here.
Sorry.
The closure under recursion/composition of this operation will clearly generate a group, which must be the group of the heap, by definitions. And as we know that generally we can see that calling that closure the automorphism group is potentially misleading.
I'll write it up formally.
Okay, thanks. I added a bunch of material to the section Heap: relation to torsors saying most of what I just said here on that subject.
John Baez said:
I realize I haven't really proved that what the nLab calls the automorphism group of the heap is not really the automorphism group!
Yes, of course that's a terrible name. If is a heap, then should be the automorphism group of as a heap. Using the model of heaps as pairs of a group and a -torsor , an automorphism of is a pair of an automorphism of , , and an isomorphism of -torsors . It's only when we look at automorphisms over the identity automorphism of that we get a group that (merely) identifies with (since any automorphism group of -torsors is merely isomorphic to ).
So while this is related to one of the two retractions of , it is in fact neither.
Thanks. I'm wondering if there's a heap of heap theorists who use "automorphism group" in this terrible sense, and whether they'll be mortally offended if I change the nLab to improve the name of this particular group.
I say: go for it! And while you're at it, it would be great to point out that we have two natural functors from heaps to groups that return when given the pair of and the principal -torsor. (From we can take either or twisted by , i.e., ) I guess it depends on conventions which one is currently Prop. 3.1. Also: Under examples, you could put the set of homotopy classes of paths from point to point in a connected topological space. (I would do this myself, but I'm short on time this week.)
I don't have the energy right now to do anything for this article that is not absolutely necessary to preserve the sanity of the mathematical community. However, I've clarified the relation between heaps and torsors, and asked on the nLab if I can go ahead and change the term "automorphism group" to "underlying group".
There's still a mess in the article: at present, all sections except "Automorphism groups of heaps" relate a heap to a left torsor for a group, while that one section uses a right torsor.
Would having a page that collected non-canonical patterns of -terminology make these kinds of editing jobs easier?
I expect this one (Moore closure over an "obvious" set of bijections on a set) will be very common for old algebraic literature.
For this article, I might say for instance "The heap literature uses and 'automorphism group' to describe this concept, see Pattern 2 on non-canonical-aut-link, here we use instead ____ to avoid confusion with what has since become the more restrictive categorical usage [[automorphism]]".
Some people will never be happy, but I hope there's less of a sense that we are erasing or nostrifying the contributions of non-category-centric mathematicians that way...
In case I come back to this, I'm noting this diagram summarizes the heap in terms of the -torsor and group inverse ; the coherence diagrams for all follow from the familiar behavior for those.
Ideally there is a second diagram, as described by Ulrik above, explicating the relationship of the non-canonical "Aut" functor to the closure over the curried right-actions via delooping, to , and to the canonical . But I have not been able to draw this yet.
The page [[heap]] is now much improved:
Eric M Downes said:
Would having a page that collected non-canonical patterns of Aut-terminology make these kinds of editing jobs easier?
Do you know more than one?
Some people will never be happy, but I hope there's less of a sense that we are erasing or nostrifying the contributions of non-category-centric mathematicians that way...
As I mentioned, Urs just stepped in and replace "Aut" with "Str" everywhere. But I have a question: do a bunch of heap theorists (assuming such exist) say "Aut" here?
Eric M Downes said:
Ideally there is a second diagram, as described by Ulrik above, explicating the relationship of the non-canonical "Aut" functor to ...
Do you mean ? There's no category on the nLab page called . And again, the functor once called is now called . So what I now see on the nLab paper is a discussion of the functor .
I don't know what a "non-canonical functor" is, but seems plenty canonical to me. The person who wrote this page gave 3 descriptions of it; one involved an arbitrary choice of "identity element" for the heap, but the other two, don't involve any arbitrary choice. It's (implicitly) claimed all these functors are naturally isomorphic, but if there's any doubt of that, or if one just wants to avoid fussing with arbitrary choices, I'd use one of the other two.
My note was written prior to the updates, which I think addresses them; I have no complaints about .
Yes, I have encountered people using to mean a closure of in some obvious way that turns out not to be , (also for some closure of appropriate maps in a monoid); it is often mostly pre-category theory algebra in obscure topics like semigroups, quasigroups, etc. If its important I can find them; that's why I was asking.
As to wether there's anyone who will be annoyed or who even use Aut canonically -- I'm looking for a 2017 book on Wagner's theory of Heaps to see exactly what terminology is used there, as it would presumably be the most up to date. I do not know any heap theorists, and I doubt you have anything to be concerned about, but please use your own judgement. I'll post back when I find what terminology is used for this in the most-up-to-date book(s).
By "non-canonical" I meant that (now ) is not . To me the only canonical use of "Aut" should be the automorphisms within a category. So, the symmetries of the heap, as a heap, which could be different from its structure group or the automorphisms of said structure group etc etc. Again, nothing you and Ulrick haven't said, and now its fixed; my earlier comment is now outdated.
Re "Prin", sorry. I meant to write Heap, but was thinking of principal fiber bundles while writing. I often make such mistakes, and don't wish to waste your time worrying about them. Those were notes to myself when I thought I might have to fix the page.
Ok found it.
One interesting mathematical note in the book I'm reading is the claim that "the automorphism group of a heap" (back when they were called "Scharen", evidently) is the [[holomorph]] "of the corresponding group".. Not yet 100% sure its the same concept but sounds pretty damn close.
Okay evidently this is the paper:
Baer, R.: Zur Einführung des Scharbegriffs. J. reine angew. Math. 163, 199–207 (1929)
here in German
I definitely don't have access, but I'll check with a small non-abelian group to see if it checks out.
So, yes people have referred to the procedure used as "the automorphism group", and "Aut"; the papers I have found are from 70-100 years ago by Russian and German authors in algebra. Baer did important work here, as did Mal'cev. I expect anyone still using such terminology are just quoting the original, which of course we should not expect to coincide with nLab!
FWIW The people I have met who cite those algebraists and know about obscure algebra stuff, often work on loops (the algebra kind, not topological loops), and or Lie algebras.
I am happy to help out if anything more is needed here, but I consider the matter resolved!
Thanks to both of you.
Okay, people often use "canonical" in a quasi-mathematical way, and people argue about its meaning, e.g. what Grothendieck meant by it, so I thought "non-canonical functor" might have some technical meaning for you that I didn't understand - like a functor which required some arbitrary choice for its definition. But you just meant "using the word Aut to mean something that ain't what it should mean". (You put it more politely.)
"them thar functors aint right I tella ya"
Bill Messing has pointed out publicly a couple of times that Bourbaki had a technical working definition of a "canonical" mapping in their first edition of ch4 of Théorie des Ensembles, but they took it out of subsequent editions, with no explanation. From what I can tell, it seems sensible, but you have to understand things like how Bourbaki defines theories in terms of signatures and structures and whatnot. More or less it's "core natural" (as on the nLab [[core-natural transformation]]) plus a condition linked to how the context is specified as a theory: let's say something like it should exist in the free model of the theory).
For those not in the know "core-natural" = "natural with respect to isomorphisms". I find the latter is a bit more self-explanatory.
James Dolan uses "canonical" to mean "natural with respect to isomorphisms", which is roughly what you're saying Bourbaki was saying - but simpler in that we can take any transformation between functors, possibly an unnatural transformation, and check to see if it's canonical in this sense - without the stuff about signatures and structures and free models and stuff.
My only concern is that there seem to be maps Bourbaki (and in fact most people) call canonical that aren't any kind of transformations between functors, like the inclusion function of a subset in ZFC. But this is off-topic for this thread!
If you don't mind, I'd like to understand your comment better, @David Michael Roberts.
Why doesn't the following (phrased using topos-theoretic language) work in ZFC? Subset relations and powersets are primitive or close-to-primitive notions, so I'd have expected it to all "just work out".
The "natural inclusion" acts functorially to give the indicator function as a pushout.
( is the subobject classifier in ) and there are quite a few constructions preserved by using the powerset monad, which equivalently form commuting diagrams that preserves; here is one:
You know all this of course, though maybe you'd phrase it differently. I'm just trying to set the stage for you to explain why this shouldn't be considered natural in ZFC.
(FWIW, this is all pretty related to anything involving group (or other) actions , because moore closures and working in for some is where a lot of algebra lives when you concretize it... so I think its probably ok to discuss here. Or if you'd prefer to open a new topic please at me.)
How does that pushout work? I'm not sure I see it. It feels more like it should be , not .
If is a literal subset inclusion in ZFC, what are the functors that there is supposedly a isomorphism-natural transformation between? I can imagine that if you replace by something isomorphic (as a set), then there is a subset of it that is in bijection with , via the restriction of the original bijection. But what are the functors?
Note that a characteristic function does determine a literal subset in ZFC via a pullback, but it's not the usual construction of the pullback using the Kuratowski ordered pairs construction of the product (which is really just a convention).
I'm not sure what you mean by me explaining why something shouldn't be considered natural. I'm raising the possibility that there are things we want to consider as natural morphisms that are not captured by the definition by "core-natural transformation".
Easy question first. and
where as you noted.
So, because these are material sets, we need to be evil and demand literal equality , so the unique isomorphism between (built as a lookup table using ) and is determined by the following: we can only draw that arrow when we have element-wise agreement .
We require the same of all the powersets (elements are subsets that agree element-wise with their containing sets) and functions use the definition. These are specific material sets, not sets unique up to unique isomorphism, because in ZFC they have to be.
This significantly weakens this approach, and introduces all kinds of annoying checks and the construction of explicit isomorphisms if we want to map into say, , but the diagrams I drew still commute. preserves certain commuting diagrams involving functions and their direct images etc. using material sets. So is a natural transformation within in ZFC.
It might be evil from a CT sense, and terribly weakened compared to standard CT practice, but it seems to me this still works internal to a ZFC model of , and this is what I have always understood people to mean. Tom Leinster talks briefly about things like choosing specific privileged sets etc. in his ETCS preprint, and claims it works. I admit though that I have not looked carefully at the internals, and am no expert at set theory, so maybe losing "unique up to unique iso" isn't just annoying and inconvenient, but actually breaks something.
I agree with products it gets dicier, but strictly-set-theory people don't tend to use the term "categorical product" as much, while I have heard them use the term "natural inclusion".
It was less a demand that you demonstrate something doesn't work, and more an invitation to say something about what breaks if it was convenient to do so.
I want to be clear that I am not advocating working this way!! I just want to be more sure that if I say something categorical to a programmer new to category theory at work, who only knows naive set theory, that I'm not actually saying something badly wrong.
Regarding the "easy question", did you check the universal property? Note that to be a pushout you need 1) a commutative square (you can make one by factoring your through , and putting that singleton in the bottom left corner, opposite ); and 2) the universal property.
Now suppose you have some with at least one element and , for some chosen . The commuting square made from , , and picking out 1 should induce a unique function , if what you describe is the pushout, such that . But this is only possible if is injective. And hence that .
I don't know what you mean about elements of being isomorphic, what I'm talking about is independent of the cartesian closed structure of Set.
What I'm after is a nontrivial functor with codomain Set (for now, the category of ZFC sets) that takes the value on some object , another functor that takes the value on that same object, and also an isomorphism natural transformation from the second functor to the first. This means that if I have , then contains as a literal subset, and then we have as functions.
One can get this in a stupid way by saying the domain of and is the trivial, single object, single arrow category. But then this would imply that every single morphism in any category is 'canonical'.
David Michael Roberts said:
Now suppose you have some with at least one element and , for some chosen . The commuting square made from , , and picking out 1 should induce a unique function , if what you describe is the pushout, such that . But this is only possible if is injective. And hence that .
You're right its not a pushout, thank you. A pullback over inclusions is closer to what I mean, but even that isn't quite right. I was trying to say subsets of both and will also have indicator functions that factor through . And because a map into is isomorphic to a powerset on the domain of that map, we obtain many other commuting diagrams.
Thanks for communicating what you're looking for! That's very clear and I'll have to think about it.
Yes, the square is a pullback, by the defining nature of the subobject classifier. We have in the category of ZFC sets a canonical choice of pullback of any injection, by taking any pullback, and then taking the canonical inclusion of the image of the resulting injection instead (which also satisfies the universal property of the pullback).
Thanks for giving the idea some thought!