categories - Category Theory list
 help / color / mirror / Atom feed
From: Jens Hemelaer <Jens.Hemelaer@uantwerpen.be>
To: Thomas Streicher <streicher@mathematik.tu-darmstadt.de>
Cc: "categories@mta.ca" <categories@mta.ca>
Subject: Re: Does essential entail locally connected for hyperconnected geometric morphisms?
Date: Mon, 28 Sep 2020 21:40:32 -0300	[thread overview]
Message-ID: <E1kN3h2-0001Vy-32@rr.mta.ca> (raw)
In-Reply-To: <20200928113603.GB17526@mathematik.tu-darmstadt.de>

Dear Thomas,


At the moment, we do not have a counterexample to the statement that pre-cohesive geometric morphisms are locally connected. We think we can construct  one of the form PSh(M) --> PSh(N) with M and N monoids, but it will take some more work.

All the best,
Jens

________________________________
From: Thomas Streicher <streicher@mathematik.tu-darmstadt.de>
Sent: Monday, September 28, 2020 1:36 PM
To: Jens Hemelaer
Cc: categories@mta.ca; Morgan Rogers
Subject: Re: categories: Does essential entail locally connected for hyperconnected geometric morphisms?

> 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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Farxiv.org%2Fabs%2F2009.12241&amp;data=02%7C01%7CJens.Hemelaer%40uantwerpen.be%7C4e384645e45b483168dc08d863a2af9d%7C792e08fb2d544a8eaf72202548136ef6%7C0%7C0%7C637368898108545753&amp;sdata=o5jz9Hahe4VdYGGKQObOulsZH6HIdoh7IXqCAlV9uew%3D&amp;reserved=0> https://arxiv.org/abs/2009.12241 (3 pages).

Dear Jens and Morgan,

thanks a lot for your very nice counterexample which I never would
have found on my own!

Alas, it leaves open Lawvere and Menni's question whether precohesive
geometric morphisms are always also locally connected. Does your
toolbox also provide a counterexample to this implication. The current
one does not do this job since you show the leftmost adjoint does not
preserve binary products. (By Lemma 2.7 of Johnstone's 2011 TAC paper
preservation of binary products by the leftmost adjoint is equivalent
to preservation of exponentials by the inverse image part for hyperconnected
and local geometric morphisms.)

BTW I think that locally connected, hyperconnected and local is the
correct generalization of essential, 2-valued and local from base Set
to arbitrary base toposes from the point of view of fibered categories.

Best, Thomas


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


  parent reply	other threads:[~2020-09-29  0:40 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
     [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 [this message]
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=E1kN3h2-0001Vy-32@rr.mta.ca \
    --to=jens.hemelaer@uantwerpen.be \
    --cc=categories@mta.ca \
    --cc=streicher@mathematik.tu-darmstadt.de \
    /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).