categories - Category Theory list
 help / color / mirror / Atom feed
From: Jason Erbele <erbele@math.ucr.edu>
To: Tom Hirschowitz <tom.hirschowitz@univ-savoie.fr>,
	"categories@mta.ca" <categories@mta.ca>
Subject: Re: Reference search: new categories by replacing morphisms with diagrams
Date: Wed, 24 Sep 2014 11:49:09 -0700	[thread overview]
Message-ID: <E1XXDpu-000263-J6@mlist.mta.ca> (raw)
In-Reply-To: <87iokdf9u7.fsf@hirscho.lama.univ-savoie.fr>

Ah, it figures I would leave something out in my first post here.  My
apologies to all of you that were scratching your heads over the
missing rules for composition.  At least five of you have responded
with essentially the same question, so this will be sort of a blanket
response.

Composition of (f,g,h): A --> B through X and (f',g',h'): B --> C
through Y will go through the biproduct X (+) Y with (f'f, [f'g, g'],
[h, h'(f+gh)]^T): A --> C.  That is, the first component composes in
the usual way, the second component is a row matrix, and the third
component is a column matrix.  In the original category, the various
morphisms in the composed triple correspond to A --> B --> C,
directly; X --> B --> C and Y --> C; and A --> X and A --> B --> Y,
where this A --> B is f+gh rather than f.

Identity morphisms in the new category are those with f=id and the
zero object for X, which uniquely determines g and h.  The embedding I
mentioned of the original category into the new category is a functor,
after all.

Best,
Jason

On Wednesday, September 24, 2014, Tom Hirschowitz
<tom.hirschowitz@univ-savoie.fr> wrote:
>
>
> Dear Jason,
>
> How do your triples compose?
>
> Best,
> Tom
>
> Jason Erbele <erbele@math.ucr.edu> writes:
>
>> Dear all,
>>
>> I built a category from another category by keeping "the same" objects
>> and taking the morphisms to be diagrams from the old category that
>> satisfy certain properties.  The closest thing to what I'm doing that
>> I have been able to find is factorization systems, but there are some
>> major differences.
>>
>> To be more specific, I am starting with an Abelian category.  If there
>> are morphisms f: A --> B, g: X --> B, and h: A --> X, it makes sense
>> to talk about the morphism f+gh: A --> B, which can be represented
>> with a non-commutative triangle.  I don't know how to draw that in
>> plain text, so I will depict it as the ordered triple (f,g,h).  The
>> category I built takes this type of non-commutative triangle as a
>> morphism (f,g,h): A --> B.
>>
>> That is, the new category is storing extra information in the
>> morphisms by distinguishing between the part that goes directly from A
>> to B and the part that takes a detour through an intermediate object,
>> X.  So while it may be possible for f+gh = f'+g'h' in the original
>> category, (f,g,h) and (f',g',h') would be different morphisms in the
>> new category unless f=f', g=g', and h=h'.  One nice feature of this
>> construction is the original category can be embedded in the new
>> category by taking X to be the zero object.
>>
>> The people I have shown this to have told me they have never seen
>> anything like my construction.  I am at a loss for search terms --
>> everything I have tried either turns up nothing or thousands of
>> unrelated articles.  The closest I've found is factorization systems,
>> which involve a commutative triangle, f=gh, for some g and h with
>> certain properties.
>>
>> If any of you know a reference or keyword associated with expanding a
>> category by replacing the morphisms with diagrams (with a specified
>> property/shape), I would greatly appreciate the assistance.
>>
>> Sincerely,
>> Jason Erbele
>>

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


  parent reply	other threads:[~2014-09-24 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 22:56 Jason Erbele
     [not found] ` <87iokdf9u7.fsf@hirscho.lama.univ-savoie.fr>
2014-09-24 18:49   ` Jason Erbele [this message]
2014-09-25 19:52     ` Steve Lack
2014-09-26 21:14       ` Robin Cockett

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=E1XXDpu-000263-J6@mlist.mta.ca \
    --to=erbele@math.ucr.edu \
    --cc=categories@mta.ca \
    --cc=tom.hirschowitz@univ-savoie.fr \
    /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).