categories - Category Theory list
 help / color / mirror / Atom feed
From: grandis@dima.unige.it (Marco Grandis)
To: categories@mta.ca
Subject: Preprint available
Date: Thu, 12 Nov 1998 15:26:28 +0100	[thread overview]
Message-ID: <v02140b00b27092eb69cb@[130.251.60.168]> (raw)

The following preprint:

M. Grandis,
"An intrinsic homotopy theory for simplicial complexes
with applications to image processing"

is available at:

ftp://pitagora.dima.unige.it/WWW/FTP/GRANDIS/

as:   Lnk.Nov98.ps

***

Abstract. A simplicial complex is a set equipped with a down-closed family
of distinguished finite subsets; this structure is mostly viewed as
codifying a triangulated space. Here, this structure is used directly to
describe "spaces" of interest in various applications, where the associated
triangulated space would be misleading. An intrinsic homotopy theory, not
based on topological realisation, is introduced.
        The applications considered here are aimed at metric spaces and
digital topology; concretely, at image processing and computer graphics. A
metric space  X  has a structure  t_e(X)  of simplicial complex at each
"resolution"  e > 0;  the resulting n-homotopy group  \pi_n(t_e(X))  detects
those singularities which can be captured by an n-dimensional grid, with
edges bound by  e;  this works equally well for continuous or discrete
regions of euclidean spaces.

***

Comments would be appreciated.

In particular, I am uneasy about a question of terminology.

In my opinion, the term "simplicial complex", quite appropriate when the
structure is viewed as codifying a triangulated space, is unfit when such
objects are treated as "spaces" in themselves (somewhat close to
bornological spaces, which have similar axioms on objects and maps).

In other words, "simplicial complex" should not refer to the category
itself, say  C,  but to its usual embedding in  Top,  the simplicial
realisation. The two aspects may clash, e.g. with respect to initial or
final structures: the coarse C-object on three points (final structure, all
parts are distinguished) is realised as a euclidean triangle; a C-subobject
is sufficient to produce a topological subspace (a regular subobject in
Top), but a C-subspace (a regular subobject in  C)  is a stronger notion.
Moreover, from a more concrete point of view, the simplicial realisation is
quite inappropriate in most of the applications considered in this work.

The opposition  "C-object / simplicial complex" is in part similar to
"sequence / series": the second term refers to a more specific view & use
of the same data; the clashing of the opposition is particularly evident in
the notions of convergence, for a sequence or a series.

That's why I am calling a C-object a "combinatorial space". (The term
"combinatorial complex" has also been used for simplicial complex; and I
wanted a term of the form "attribute + space", to use freely of topological
terms like discrete, coarse, subspace...)
But of course it is embarassing to propose a new term for a classical notion.

Marco Grandis





             reply	other threads:[~1998-11-12 14:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-12 14:26 Marco Grandis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-05 16:05 preprint available claudio pisani
2013-10-22  8:03 Preprint available Anders Kock
2010-03-29 15:44 preprint available Anders Kock
2009-12-10 12:14 Anders Kock
2009-04-29 14:59 JONATHON FUNK
2008-11-03  5:54 zackluo
2007-05-31  7:16 Anders Kock
1999-10-12 13:18 kock
1998-12-14 22:51 Preprint available F W Lawvere
1998-11-18 16:09 preprint available Martin Escardo
1998-06-24 14:49 Susan Niefield
1998-05-06 22:15 Steve Awodey
1997-09-02 12:19 categories
1997-07-30 16:39 Preprint available categories
1997-07-01 18:12 categories
1997-04-24 18:24 preprint available categories
1997-04-10 19:34 Preprint available categories

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='v02140b00b27092eb69cb@[130.251.60.168]' \
    --to=grandis@dima.unige.it \
    --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).