categories - Category Theory list
 help / color / mirror / Atom feed
From: Jens Hemelaer <Jens.Hemelaer@uantwerpen.be>
To: "categories@mta.ca" <categories@mta.ca>
Subject: Re: Does essential entail locally connected for hyperconnected geometric morphisms?
Date: Mon, 28 Sep 2020 07:50:19 +0000	[thread overview]
Message-ID: <E1kN3c4-0001PB-SC@rr.mta.ca> (raw)
In-Reply-To: <CAJUcr-_n3h3d3QkDffcg_r87JAZYyz6O-8GqPdKx0sLBTQVv4g@mail.gmail.com>

Morgan Rogers and I were able to construct a counterexample of the form PSh(M) --> PSh(N) where M and N are monoids. It arises from our joint work-in-progress in which we study exactly these kind of geometric morphisms, in a systematic way. After talking about it with Thomas Streicher, we have now written up the counterexample in more detail. You can find it here:
https://arxiv.org/abs/2009.12241 (3 pages).

Jens

________________________________

From: <streicher@mathematik.tu-darmstadt.de<mailto:streicher@mathematik.tu-darmstadt.de>>
Date: Sat, 19 Sep 2020 at 14:28
Subject: categories: Does essential entail locally connected for hyperconnected geometric morphisms?
To: <categories@mta.ca<mailto:categories@mta.ca>>


Consider the functor F from the site for the topos of graphs to the site
for the Sierpinski topos such that the object part of F is a bijection.
Let f be the geometric morphism whose inverse image part is given by
change of base along F. It is the inclusion of graphs with loops only into
the category of graphs.
Of course, p is essential and one easily sees that it is hyperconnected.
One can show that p is not locally connected. However, p is not local
since p_* does not preserve coequalizers.

My attempts to come up with an example of a hyperconnected local geometric
morphism which is is essential but not locally connected have failed so
far.
But all my instincts tell me that there should be a counterexample!

The question came up in discussions with Matias Menni. He told me that one
can prove that essential entails locally connected for hyperconnected
local geometric morphisms. But his argument uses (ii) => (i) of Lemma 3.2
of Peter Johnstone's paper "Calibrated Toposes" whose proof I, however,
find very cryptic. In any case, it would entail a result which I,
personally, would find very surprising...

I would be grateful for any clarification of this puzzling question. My
hope is that someone comes up (with an idea for) a counterexample. But, of
course, I also would highly appreciate any argument that such a
counterexample cannot exist.

Thomas



[For admin and other information see: http://www.mta.ca/~cat-dist/ ]


  parent reply	other threads:[~2020-09-28  7:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  6:57 streicher
     [not found] ` <CAJUcr-_n3h3d3QkDffcg_r87JAZYyz6O-8GqPdKx0sLBTQVv4g@mail.gmail.com>
2020-09-28  7:50   ` Jens Hemelaer [this message]
     [not found] ` <499e9e5440f6457d92349be543c9b280@uantwerpen.be>
2020-09-28 11:36   ` Thomas Streicher
     [not found] ` <20200928113603.GB17526@mathematik.tu-darmstadt.de>
2020-09-29  0:40   ` Jens Hemelaer
2020-09-29  8:53     ` Thomas Streicher

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=E1kN3c4-0001PB-SC@rr.mta.ca \
    --to=jens.hemelaer@uantwerpen.be \
    --cc=categories@mta.ca \
    /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).