{"id":592,"date":"2008-02-05T12:17:11","date_gmt":"2008-02-05T12:17:11","guid":{"rendered":"http:\/\/scientopia.org\/blogs\/goodmath\/2008\/02\/05\/more-groupoids-and-groups\/"},"modified":"2008-02-05T12:17:11","modified_gmt":"2008-02-05T12:17:11","slug":"more-groupoids-and-groups","status":"publish","type":"post","link":"http:\/\/www.goodmath.org\/blog\/2008\/02\/05\/more-groupoids-and-groups\/","title":{"rendered":"More Groupoids and Groups"},"content":{"rendered":"<p> In my introduction to groupoids, I mentioned that if you have a groupoid, you can find<br \/>\ngroups within it. Given a groupoid in categorical form, if you take any object in the<br \/>\ngroupoid, and collect up the paths through morphisms from that object back to itself, then<br \/>\nthat collection will form a group. Today, I&#8217;m going to explore a bit more of the relationship<br \/>\nbetween groupoids and groups.<\/p>\n<p> Before I get into it, I&#8217;d like to do two things. First, a mea culpa: this stuff is out on the edge of what I really understand. My category-theory-foo isn&#8217;t great, and I&#8217;m definitely<br \/>\non thin ice here. I think that I&#8217;ve worked things out enough to get this right, but I&#8217;m<br \/>\nnot sure. So category-savvy commenters, please let me know if you see any major problems, and I&#8217;ll do my best to fix them quickly; other folks, be warned that I might have blown some of the details.<\/p>\n<p> Second, I&#8217;d like to point you at <a href=\"http:\/\/en.wikipedia.org\/wiki\/Groupoid\">Wikipedia&#8217;s page on groupoids<\/a> as a<br \/>\nreference. That article is quite good. I often look at the articles in Wikipedia and<br \/>\nMathWorld when I&#8217;m writing posts, and while wikipedia&#8217;s articles are rarely bad, they&#8217;re also<br \/>\noften not particularly <em>good<\/em>. That is, they cover the material, but often in a<br \/>\nsomewhat disorganized, hard-to-follow fashion. In the case of groupoids, I think Wikipedia&#8217;s<br \/>\narticle is the best general explanation of groupoids that I&#8217;ve seen &#8211; better than most<br \/>\ntextbooks, and better than any other web-source that I&#8217;ve found. So if you&#8217;re interested in<br \/>\nfinding out more than I&#8217;m going to write about here, that&#8217;s a good starting point.<\/p>\n<p><!--more--><\/p>\n<p> As I&#8217;ve explained before, the basic idea of a group is a mathematical structure with an<br \/>\noperation that defines a kind of immunity to transformation. Every transformation through the<br \/>\ngroup operator preserves some kind of structure. In a groupoid, you don&#8217;t have such a strong<br \/>\nsymmetry. In a groupoid, you have an operation that <em>includes<\/em> a symmetric<br \/>\ntransformation, but not all applications of it are symmetric: the groupoid operator preserves<br \/>\nstructure <em>under some conditions<\/em>: that is, there are <em>sequences<\/em> of groupoid<br \/>\noperations that result in symmetric, structure-preserving transformation, and it&#8217;s easy to<br \/>\ndefine just what those sequences of transformations are.<\/p>\n<p> In categorical terms, that idea of the <em>partially<\/em> symmetric operation of a<br \/>\ngroupoid is reflected by the fact that there are many arrows that go from an object (a<br \/>\nstructure) to a <em>different<\/em> object &#8211; transforming it into something different &#8211;<br \/>\nsomething distinguishable from the original structure. But there are sequences of operations<br \/>\nthat end back at the original object, and those sequences of operations describe symmetric<br \/>\ntransformations.<\/p>\n<p> This leads to the intuition behind the simplest relation between groupoids and groups. If<br \/>\nyou have a groupoid with a single object in it, that that groupoid is a group. In a<br \/>\nsingle-object groupoid, every application of the operation <em>must<\/em> end back at the<br \/>\nobject where it began &#8211; so every transformation in a single-object groupoid must be symmetric<br \/>\n&#8211; so the single-object groupoid is a group.<\/p>\n<p> That much already shows us some of why the categorical formulation is nice: we&#8217;ve gone from something where the relationships and structures are symbolic, to something where we can see what&#8217;s going on using a simple diagram: it&#8217;s easier to see &#8220;all paths from G end at G&#8221;<br \/>\nwhen you draw the structures, than it is to see the corresponding statement in terms of pure algebra.<\/p>\n<p> But there&#8217;s more to it. Some of the more subtle things are captured very nicely. For<br \/>\nexample, there&#8217;s a notion of <em>equivalence<\/em> in groupoids that is different from isomorphism, which tells us more about the relationship between groupoids and groups. It comes from the categorical idea of a <em>natural transformation<\/em>. I wrote about<br \/>\nnatural transformations <a href=\"http:\/\/scientopia.org\/blogs\/goodmath\/2006\/06\/category-theory-natural-transformations-and-structure\">here<\/a>. For a quick reminder, if you start with<br \/>\na category, you can define structure-preserving transformations between objects using<br \/>\nmorphisms; you can define structure-preserving transformations between morphisms using functors; and you can define structure-preserving transformations between functors using<br \/>\nnatural transformations.<\/p>\n<p> Let&#8217;s look at that notion of loose equivalence. Suppose we have a groupoid, O, which is<br \/>\nconnected &#8211; that is, where in the category for G, given any two objects a and b in O, there<br \/>\nis an arrow from a to b. We can form a group G out of the groupoid, by <em>collapsing<\/em><br \/>\nthe connected groupoid to a single object. Loosely speaking, you can pick an arbitrary object from the groupoid as a representative, and collapse the arrows &#8211; each set of arrows<br \/>\nfrom the representative to a particular other object becomes an arrow in the collapsed groupoid; those arrows become the objects of the group, and arrow composition is the group operator. The end result is a group formed from the collapsed arrows of any connected groupoid. <\/p>\n<p> What if the groupoid isn&#8217;t connected? You take the connected components of the groupoid, and each of them can be collapsed into a group &#8211; so you can collapse any groupoid into a collection of disjoint groups. <\/p>\n<p> Here&#8217;s where it gets interesting. The collapse of a groupoid isn&#8217;t unique. It&#8217;s determined by the selection of the representative objects. The collapsed groupoids are all<br \/>\nequivalent. In fact, you can define an isomorphism between them &#8211; they&#8217;re all ultimately the<br \/>\nsame structure; so you can define the isomorphic mappings between objects in the different<br \/>\ncollapsed versions.<\/p>\n<p> But suppose you don&#8217;t define the mappings between objects. Suppose all you look at are<br \/>\nthe arrows that form the groups. So you&#8217;ve discarded the objects from the original groupoid,<br \/>\nand all you have left are single objects corresponding to the different connected components, each of which is a group. What you&#8217;ve done, then, is to create a mapping from a groupoid to a collection of groups. It is <em>not<\/em> an isomorphism &#8211; but it is a mapping from the groupoid to a collection of groups that is, in  some sense, equivalent to the original groupoid. (Note that I said &#8220;collection&#8221;, <em>not<\/em> set. In fact, it&#8217;s a multiset; multiple components can collapse down to the same group, but you need to keep an instance of that group for each of the components.) The structure of that collection of groups is determined by the original groupoid. <\/p>\n<p> But it&#8217;s not an isomorphism. That transformation has discarded some information about the original structure. There are multiple groupoids that can all be collapsed into the same<br \/>\ncollection of groups. Because you didn&#8217;t keep the mappings that allow you to identify the arrows to the original groupoid objects, you can&#8217;t go back. It&#8217;s a one-way transformation.<\/p>\n<p> Category theory allows you to define that loss of information in a very convenient way. Any high-level transformation like that &#8211; where you&#8217;re basically transforming a category into a different category (in this case, from a groupoid category to a category containing a collection  of groups) can be described by categorical transformations. The structure-preserving relations between arrows in the original category &#8211; the <em>functors<\/em> of the original category &#8211; in a categorical sense define the structural information contained in the category. When you map from category to category, there<br \/>\nis a mapping between the functors that define the informational relationships between<br \/>\nthe two categories. If you can map from one category C to another category D without losing any structural information, that is reflected in category theory by the existence of<br \/>\na <em>natural transformation<\/em> from C to D. In the case of the groupoid-to-groups collapse, there is no natural transformation. The non-existence of a natural transformation<br \/>\nmeans that there is going to be a significant loss of structural information.<\/p>\n<p> What does that mean?<\/p>\n<p> It means that groupoids are <em>richer<\/em> structures that groups. There is interesting<br \/>\ninformation about symmetry which we can capture in terms of the algebraic structure of<br \/>\na groupoid which we <em>cannot<\/em> capture in terms of the groups that make up the components of a groupoid. Without understanding the groupoids, we are missing something about<br \/>\nthe meaning of symmetry!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In my introduction to groupoids, I mentioned that if you have a groupoid, you can find groups within it. Given a groupoid in categorical form, if you take any object in the groupoid, and collect up the paths through morphisms from that object back to itself, then that collection will form a group. Today, I&#8217;m [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[76,26],"tags":[],"class_list":["post-592","post","type-post","status-publish","format-standard","hentry","category-category-theory","category-group-theory"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p4lzZS-9y","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/posts\/592","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/comments?post=592"}],"version-history":[{"count":0,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/posts\/592\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/media?parent=592"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/categories?post=592"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.goodmath.org\/blog\/wp-json\/wp\/v2\/tags?post=592"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}