Want to take part in these discussions? Sign in if you have an account, or apply for one below
Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.
am working on putting some genuine detailed content into smooth groupoid. So far there is now discussion of the groupoid-enriched category of groupoid-valued presheaves, Cech nerves, and the stack condition.
Then it breaks off and some rough old material kicks in which needs to be harmonized. Will continue later, need to go offline now for a little.
have now expanded a good bit further. But there are still some loose ends…
In Remark 6 it says that one can define smooth groupoids as stacks on the site of all smooth manifolds instead of the site of Cartesian spaces. It says
Everything discussed so far goes through verbatim for [], too, but the descent condition in def. 4 is a much stronger condition. For instance the presheaves of the form from example 3 satisfy descent on , but not all .
I’m not clear on how to understand the situation. In particular, I’m not sure what the condition in def. 4 is stronger than. Here’s one possibility. On the first approach we define a pre-smooth groupoid to be a (2,1)-presheaf on . We then say that a pre-smooth groupoid is a smooth groupoid if it satisfies the stack condition. On the second approach, we do the same thing on the site . As it happens (because all of the objects in are contractible), the stack condition has a particularly simple expression on this site, and this simplified expression is given as the descent condition in def. 4. These two approaches give equivalent definitions of smooth groupoids. However, if one were to try to use the stack condition as expressed in def. 4 on the first approach (by replacing the with arbitrary objects of ), then one would not obtain the stack condition on . Rather, one would obtain something more restrictive. For example, does not satisfy this translated condition, though it does satisfy the correct stack condition on . The reason that one can’t just make the obvious replacements in def. 4 and obtain the stack condition on is that def. 4 is a simplified expression, and this simplification relies on properties of that doesn’t have.
Is something like this right?
I’m not sure what the condition in def. 4 is stronger than.
Presumably that any pre-smooth groupoid that satisfies descent for will satisfy descent for but this doesn’t hold in general vice versa.
While we’re at def. 4, the two occurrences before and in it:
…and precomposes it with the canonical map
and
given by pre-composition with
and another in the commutative diagram between these should presumably be .
So I fixed that and other typos.
Back to #3, presumably the issue is that not all smooth groupoids are pre-smooth groupoids satisfying descent on CartSp (though most are) and fewer satisfy descent on SmoothMfd (including important ones). But then
So a smooth groupoid is a stack on the site CartSp
is misleading.
David, thanks, these were indeed typos, thanks for fixing them.
John: it’s simply that is a subcategory of and hence requiring descent over the former site is only a subset of the conditions of requiring descent over the latter site.
(In terms of the localization of simplicial presheaves (called “pre-smooth groupoids” in the entry) this is counterbalanced by the fact that over the smaller site the condition for cofibrancy is stronger that that over the larger site (for the projective model structure).)
David, so it is not misleading to say that smooth groupoids are stacks over , indeed there is an equivalence of -catgeories
and either of these -categories is called in the entry, whose objects may be called smooth stacks.
Oh, I see. It was this part that confused me:
For instance the presheaves of the form (\mathbf{B}G)_\bullet = (G \stackrel{\longrightarrow}{\longrightarrow} \ast) from example 3 satisfy descent on CartSp, but not all SmoothMfd. Still, once we have defined the higher category of smooth groupoids, the definition will be equivalent for both choices of sites.
The choice of the smaller site is the one that is easier to work with, and therefore we stick with that. In fact, most every example of a pre-smooth groupoid that one runs into satisfies descent on CartSp.
From that last sentence, not every example of a pre-smooth groupoid satisfies descent on CartSp? But then what happens to such pre-smooth groupoids under localization,
which is really just the identity as a functor. Instead of doing anything to the objects, passing along this functor just means to change the definition of the hom-groupoids from the direct definition of def. 3 to the localized definition.
Yes, in general not every pre-sheaf is a sheaf, of course, and this is as true over as over any other site.
Under localization, a pre-sheaf or more generally a pre-stack becomes equivalent to its sheafification or more generally its stackification, which you may think of as being the universal way of approximating “from the right” the object that does not necessarily satisfy descent by one that does.
Thanks for these comments, I see that the entry leaves some puzzlement that should be clarified. But at the moment I am not sure what could be added to the entry to help make this clearer. But once you and John D. are content with the discussion here, you could maybe make a suggestion.
One way to make the entry a bit clearer would be to modify Remark 6 to
There is an alternative formulation of the whole theory where instead of the site one uses the site of all smooth manifolds. Everything discussed so far goes through verbatim for that site, too, but the descent condition over is a much stronger requirement than the descent condition over .
Assuming this is true (and I gather from our discussion that it is), I think I can start to see more of my confusion. Take ; it satisfies descent over , so is a stack over . Assuming that the equivalence is given by inclusion, is a stack over . But doesn’t satisfy descent over , so it’s not a stack over .
I think the problem with that reasoning is that I’m not accounting for localization correctly, but I don’t know where exactly my problem is. Definition 4 gives the stack condition. Remark 5 claims that a smooth groupoid is a stack on . Proposition 3 refers to “a smooth groupoid in the sense of def. 4”, but def. 4 doesn’t define smooth groupoids. I assumed that I was supposed to take “smooth groupoid” to mean “pre-smooth groupoid that satisfies descent (as defined in def. 4)”.
Now I think that was a mistake on my part. Smooth groupoids are defined in def. 8 as objects of the simplicial localization of . The canonical localization functor acts on objects as the identity, and so every pre-smooth groupoid is a smooth groupoid, when considered as an object of via the localization functor. If that’s right, then I was mistaken when I started thinking that (i) “smooth groupoid” meant (ii) “stack on CartSp” meant (iii) “pre-smooth groupoid satisfying the stack condition”. If “stack on CartSp” means “object of the -category ”, then I think (i) and (ii) mean the same thing, but I don’t know how (iii) fits in. After all, a pre-smooth groupoid that doesn’t satisfy the stack condition is still an object of the -category by application of the localization functor. So what does the stack condition do here?
That’s a very clear way of expressing the confusion, John.
I think the problem with that reasoning is that I’m not accounting for localization correctly,
I think that’s right, and hence we need to understand
Under localization, a pre-sheaf or more generally a pre-stack becomes equivalent to its sheafification or more generally its stackification
This kind of statement confuses us as poor philosophers brought up on a diet of set theory. There’s something in a collection undergoing a process, and we’re told no member of the collection changes, but that miraculously that thing becomes equivalent to a kind of thing it wasn’t before localisation.
A colourful comparison might be that it’s like London becoming rail-connected to Paris on building the Channel Tunnel. London hasn’t changed, but it’s now connected.
Of course, a Bradleian metaphysician would probably want to say that London has changed, since everything is defined by its internal relations. Russell couldn’t seem to fathom that kind of thinking.
Strange how so often parallel discussions have common themes. Compare #10 with this.
John,
yes, so just as David says, there is something happening as one sends an object through this equivalence:
The presheaf of groupoids given by does NOT go, under this equivalence, to the presheaf on the site of manifolds which would be given by sending to the groupoid , but goes to the stackification of the latter, which is the stack of -principal bundles.
Even if this further stackification seems like a drastic operation, it gives here an equivalence of -categories.
There’s something in a collection undergoing a process, and we’re told no member of the collection changes, but that miraculously that thing becomes equivalent to a kind of thing it wasn’t before localisation.
Interesting observation! It’s not fundamentally different from the process of forming the quotient of an equivalence relation in set theory: elements of a set which were not equal become equal after quotienting. In that case we usually call the image in the quotient the “equivalence class” rather than the object itself. But even in the case of localization, I don’t think it’s really correct to say that “no member of the collection changes”. From a structural point of view, a thing is a thing only insofar as it is a member of some set/type (this sounds kind of like your Bradleian), so it doesn’t make sense to say that a pre-stack “is the same thing as” its image in the localization. It’s true that when we analyze categories in terms of sets of objects and morphisms, one construction of the localization takes its set of objects to be the same as the set of objects of the original category, but even in set theory that isn’t the only way to construct a localization, and of course there are more things in heaven and earth than set theory. (-:
Thanks all, my confusion has been pretty much resolved. I was quite happy to say that localization made a pre-stack equivalent to its stackification even though it acted as the identity on the objects. I took it to be just another instance of the importance of keeping track of types. I just didn’t see how localization was related to the equivalence, and I wasn’t sure what type to assign to in different sentences. But now that I get it, I can’t quite see why I was confused, so I unfortunately don’t have a concrete suggestion for an edit to the entry.
1 to 17 of 17