From: henry@phare.normalesup.org
To: "Richard Garner" <richard.garner@mq.edu.au>
Cc: "Categories list" <categories@mta.ca>
Subject: Re: Tensor product of left exact morphisms
Date: Fri, 27 Mar 2015 14:08:18 +0100 [thread overview]
Message-ID: <E1YbdPt-0000g0-PH@mlist.mta.ca> (raw)
In-Reply-To: <E1YbTai-0002cg-87@mlist.mta.ca>
Dear Richard,
If I'm not mistaken, the distinction between inhabited and non-inhabited
torsors does not change much : your initial answer is correct.
To connect with Andr?'s answer, inhabited free G-sets are inhabited
collection of G-torsors, his construction produces a topos over [set,Set]
(the classyfing topos for object, i.e. the bagdomain construction for the
topos of sets) while what you want is a topos over [set+,Set] where set
denote the category of finite set and set+ the category of inhabited
finite set.
But this corresponds to the functor from finitely generated free right
$G$-Set to set which send an object to its (finite) set of orbits. Because
it is a fibration it is easy to construct the pullback along the geometric
morphism from [set+,Set] to [set,Set] corresponding to the inclusion of
set+ in set : it will give the topos of inhabited free finitely generated
G-set as you first found (the weak pullback of category).
Also, as you are probably aware, once you know that the classyfing topos
you want to construct is a topos of presheaf over a category C, it is a
general fact that C can be taken to be the opposite of the category of
finitely presented model of your theory, hence finitely generated free
inhabited G-set, and what you said for the case of groupoids.
Best wishes,
Simon Henry
> Thanks, Andr?, that's helpful. This:
>
>> In general, if a topos $mathcal{E}$
>> classifies the models of a geometric theory T, there is
>> another topos $mathcal{E}$ which classifies variable families
>> of models of T: it is the *bagdomain* of $mathcal{E}$
>> introduced by Johnstone. See the Elephant vol. I Proposition 4.4.16.
>
> is particularly good. I knew about the bagdomain, but didn't connect it
> to my question.
>
> However, I think I want a non-transitive torsor to be a right G-set with
> a free action, but which is also inhabited. This means passing to a
> subtopos of [X, Set], where X is as before the category of finitely
> generated free G^op sets.
>
> Looking at the calculation I made before, I think I got it wrong. I must
> pass to the topology generated by making 0 ----> G into a cocover in X.
> But then I must also make every pushout of this into a cocover, and
> every composite of such pushouts into a cocover. So, in the end, I think
> the classifying topos should be Sh(X^op) for the topology whose cocovers
> are the coproduct injections in X. In other words, I take the Lawvere
> theory of G^op-sets, and take sheaves on it for the topology given by
> the project projections.
>
> Richard
>
[For admin and other information see: http://www.mta.ca/~cat-dist/ ]
next prev parent reply other threads:[~2015-03-27 13:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 1:27 Richard Garner
2015-03-26 15:00 ` Joyal, André
[not found] ` <8C57894C7413F04A98DDF5629FEC90B1137B097E@Pli.gst.uqam.ca>
2015-03-26 23:08 ` Richard Garner
2015-03-27 13:08 ` henry [this message]
2015-03-28 8:40 ` Richard Garner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1YbdPt-0000g0-PH@mlist.mta.ca \
--to=henry@phare.normalesup.org \
--cc=categories@mta.ca \
--cc=richard.garner@mq.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).