Cartesian Spaces and Smooth Functions
Cartesian Spaces and Smooth Functions
𝑑𝑓
1. the derivative 𝑑𝑥 𝑓: ℝ ⟶ ℝ exists;
2. and is itself a smooth function.
We write C(R) Set for the set of aaall smooth functions on R\mathbb{R}.
Definition 1.3. For n∈Nn \in \mathbb{N}, the Cartesian space Rn\mathbb{R}^n is the set
ik:R→Rni^k : R⟶R^n
Remark 1.5. But a homomorphism of Cartesian spaces in def. 1.3 is not required to be
a linear map. We do not regard the Cartesian spaces here as vector spaces.
Definition 1.6. A smooth function f:Rn1→Rn2f : \mathbb{R}^{n_1} \to
\mathbb{R}^{n_2} is called a diffeomorphism if there exists another smooth
function Rn2→Rn1\mathbb{R}^{n_2} \to \mathbb{R}^{n_1} such that the underlying
functions of sets are inverse to each other
f∘g=idf \circ g = id
and
Propositions 1.10. Abstract coordinate systems according to prop. 1.8 form a category –
to be denoted CartSp – whose
objects are the abstract coordinate systems Rn\mathbb{R}^{n} (the class of
objects is the set N\mathbb{N} of natural numbers nn);
morphisms f:Rn1→Rn2f : \mathbb{R}^{n_1} \to \mathbb{R}^{n_2} are the
abstract coordinate transformations = smooth functions.
We have that
This is the category with the same objects as CartSpCartSp, but where a
morphism Rn1→Rn2\mathbb{R}^{n_1} \to \mathbb{R}^{n_2} in CartSpopCartSp^{op} is
given by a morphism Rn1←Rn2\mathbb{R}^{n_1} \leftarrow
\mathbb{R}^{n_2} in CartSpCartSp.
We will be discussing below the idea of exploring smooth spaces by laying out abstract
coordinate systems in them in all possible ways. The reader should begin to think of the
sets that appear in the following definition as the set of ways of laying out a given abstract
coordinate systems in a given space. This is discussed in more detail below in Smooth
spaces.
such that
The special properties smooth functions that make them play an important role different
from other classes of functions are the following.
(…)
{}
Semantic Layer
In this Sem Layer we discuss the concrete general aspects of abstract coordinate
systems, def. 1.8: the fact that they naturally form:
1. an algebraic theory,
2. a site.
Propositions 1.13.
f∘(−):C∞(Rn,Rk1)→C∞(Rn,Rk2)f\circ (-)\colonC^\infty(\mathbb{R}^n,
\mathbb{R}^{k_1})\toC^\infty(\mathbb{R}^n, \mathbb{R}^{k_2})
Remark 1.16. Example 1.15 shows how we are to think of a functor A:CartSp→SetA
\colon CartSp \to Set as encoding an algebra: such a functor assigns to Rn\mathbb{R}^n a
set to be interpreted as a set of “smooth functions on something with values
in Rn\mathbb{R}^n”, only that the “something” here is not pre-defined, but is instead
indirectly characterized by this assignment.
Due to this we will often denote smooth algebras as “C∞(X)C^\infty(X)”, even if “XX” is
not a pre-defined object, and write their value
on Rn\mathbb{R}^n as C∞(X,Rn)C^\infty(X,\mathbb{R}^n).
C∞(D,Rn)≔Rn×RnC^\infty(D,\mathbb{R}^n)\coloneqq\mathbb{R}^n \times
\mathbb{R}^n
given by
(ϵ↦(x⇀+ϵv⇀))(ϵ↦f(x⇀)+(df)(v⇀))↦(ϵ↦(f(x⇀)+∑n2j=1(∑n1i=1∂fj∂xivi)e⇀j)).\begin{a
ligned}\left(\epsilon \mapsto \left(\vec x + \epsilon \vec v\right)\right)\\\left(\epsilon
\mapsto f(\vec x) + (\mathbf{d}f)(\vec v)\right)&\mapsto \left(\epsilon\mapsto
\left(f\left(\vec x\right) + \sum_{j = 1}^{n_2}\left(\sum_{i = 1}^{n_1}\frac{\partial
f^j}{\partial x^i} v^i\right)\vec e_j \right)\right)\end{aligned}\,.
Definition 1.19. For n∈Nn \in \mathbb{N} the standard open n-ball is the subset
Remark 1.22. Differentiably good covers are useful for computations. Their full impact is
however on the homotopy theory of simplicial presheaves over CartSp. This we discuss
further below, around prop.
\ref{DifferentiablyGoodCoverGivesSPlitHyperCoverOverCartSp}.
Proposition 1.23. Every open cover refines to a differentially good open cover, def. 1.21.
Remark 1.24. Despite its appearance, this is not quite a classical statement. The classical
statement is only that every open cover is refined by a topologically good open cover. See
the comments here in the references-section at open ball for the situation concerning this
statement in the literature.
Remark 1.25. The good open covers do not yet form a Grothendieck topology on CartSp.
One of the axioms of a Grothendieck topology is that for every covering family also
its pullback along any morphism in the category is a covering family. But while the
pullback of every open cover is again an open cover, and hence open covers form a
Grothendieck topology on CartSp, not every pullback of a good open cover is again good.
which sends the line to a curve in the plane that periodically goes around the circle of
radius 2 in the plane.
So the pullback of the good open cover that we started with is an open cover which is
not good anymore. But it has an evident refinement by a good open cover.
Proposition 1.27. The differentially good open covers, def. 1.21, constitute
a coverage on CartSp.
To obtain this, let {f∗Ui→Rk}\{f^* U_i \to \mathbb{R}^k\} be the pullback of the original
covering family, in that
This is evidently an open cover, albeit not necessarily a good open cover. But by
prop. 1.23 there does exist a good open cover {K˜j˜↪Rk}j˜∈J˜\{\tilde K_{\tilde j}
\hookrightarrow \mathbb{R}^k\}_{\tilde j \in \tilde J} refining it, which in turn means that
for all j˜\tilde j there is
By example 1.26 this good open cover coverage is not a Grothendieck topology. But as
any coverage, it uniquely completes to one which has the same sheaves.
Proposition 1.28. The Grothendieck topology induced on CartSp by the differentially good
open cover coverage of def. 1.27 has as covering families the ordinary open covers.
Remark 1.29. This means that for every sheaf-theoretic construction to follow we can just
as well consider the Grothendieck topology of open covers on CartSpCartSp. The
sheaves of the open cover topology are the same as those of the good open cover
coverage. But the latter is (more) useful for several computational purposes in the
following. It is the good open cover coverage that makes manifest, below, that sheaves
on CartSpCartSp form a locally connected topos and in consequence then a cohesive
topos. This kind of argument becomes all the more pronounced as we pass further
below to (∞,1)-sheaves on CartSp. This will be discussed in Smooth n-groupoids –
Semantic Layer – Local Infinity-Connectedness below.
(…)
(…)
Syntactic Layer
In this Syn Layer we discuss the abstract generals of abstract coordinate systems,
def. 1.8: the internal language of a category with products, which is type
theory with product types.
We now introduce a different notation for objects and morphisms in a category (such as
the category CartSpof def. 1.10). This notation is designed to, eventually, make more
transparent what exactly it is that happens when we reason
deductively about objects and morphisms of a category.
But before we begin to make any actual deductions about objects and morphisms in a
category below, in this section here we express the given objects and morphisms at hand
in the first place. Such basic statements of the form “There is an object called AA” are to
be called judgments, in order not to confuse these with genuine propositions that we
eventually formalize within this metalanguage.
We say that these symbols express the judgment that XX is a type. We also say
that ⊢X:Type\vdash \; X \colon Type is the syntax of which X∈CX \in \mathcal{C} is
the categorical semantics.
For instance the terminal object *∈C* \in \mathcal{C} we call the categorical
semantics of the unit type and write syntactically as
⊢Unit:Type.\vdash \; Unit \colon Type\,.
If we want to express that we do assume that a terminal object indeed exists, hence that
we want to be able to deduce the existence of a terminal object from no hypothesis, then
we write this judgment below a horizontal line
*→xX* \stackrel{x}{\to} X
⊢x:X\vdash \; x \colon X
Notice that every object X∈CX \in \mathcal{C} becomes the terminal object in the slice
category C/X\mathcal{C}_{/X}. Let A→XA \to X be any morphism in C\mathcal{C},
regarded as an object in the slice category
We declare that the syntax of which this is the categorical semantics is given by
the sequent
We say that this expresses the judgement that AA is an XX-dependent type; or a type in
the context of a free variable xx of type XX.
in C\mathcal{C}.
We say that this expresses the judgment that a(x)a(x) is a term depending on the free
variable xx of type XX.
This completes the list of judgment syntax to be considered. Notice that if the
category C\mathcal{C} has products then, even though it does not explicitly appear
above, this is sufficient to express any morphism X→fYX \stackrel{f}{\to}
Y in C\mathcal{C} as the semantics of a term: we regard this morphism naturally as being
the corresponding morphism in the slice category C/X\mathcal{C}_{/X} which as
a commuting diagram in C\mathcal{C} itself is
being the judgment which expresses that y(x)y(x) is a term in context of an XX-
dependent type YY in the special degenerate case that YY does not actually vary
with x:Xx \colon X.
With the above symbolic notation for making judgments about the presence
of objects and morphisms in a category C\mathcal{C}, we now consider a system of rule
of deduction that tells us how we may process these symbols (how to do computations)
such that the new symbols we obtain in turn express new objects and new morphisms
in C\mathcal{C} that we can build out of the given ones by universal constructions in the
sense of category theory.
This way of deducing new expressions from given ones is very basic as well as very natural
and hence goes by the technical term natural deduction. For every kind
of type (every universal construction in category theory) there is, in natural deduction,
one set of rules for how to deductively reason about it. This set of rules, in turn, always
consists of four kinds of rules, called the
be two objects in a category with products. Then there exists the product object
We now declare that the syntax of which this state of affairs is the categorical
semantics is the collection of symbols of the form
Here on top of the horizontal line we have the two judgments which express
that, syntactically, AA is a typeand BB is a type, and semantically that A∈CA \in
\mathcal{C} and B∈CB \in \mathcal{C}. Below the horizontal line is, in turn,
the judgmentwhich expresses that there is, syntactically, a product type, which
semantically is the product A×B∈CA \times B \in \mathcal{C}. The horizontal line itself is
to indicate that if we are given the (symbols of) the collection of judgments on top, then
we are entitled to also obtain the judgment on the bottom.
Remark (Computation) All this may seem, on first sight, like being a lot of fuss about
something of grandiose banality. To see what is gradually being accomplished here
despite of this appearance, as we proceed in this discussion, the reader can and should
think of this as the first steps in the definition of a programming language: the notion of
judgment is a syntactic rule for strings of symbols that a computer is to read in, and
a natural deduction-step as the type formation rule above is an operation that this
computer validates as being an allowed step of transforming a memory state with a given
collection of such strings into a new memory state to which the string below the
horizontal line is added. As we add the remaining rules below, what looks like a grandiose
banality so far will remain grandiose, but no longer be a banality. The reader feeling in
need of more motivational remarks along these lines might want to take a break here and
have a look at the entry computational trinitarianism first, that provides more pointers
to the grandiose picture which we are approaching here.
Next, the second natural deduction rule for product types is the
2. term elimination rule. The fact that A×B∈CA \times B \in \mathcal{C} is equipped with
two projection morphisms
A←p1A×B→p2B\array{A \stackrel{p_1}{\leftarrow} A \times B \stackrel{p_2}{\to} B}
means that from every element tt of A×BA \times B we may deduce the existence
of elements p1(t)p_1(t) and p2(t)p_2(t) of AAand BB, respectively. We declare now that
this is the categorical semantics of which the natural deductionsyntax is:
in C\mathcal{C}. This is now declared to be the categorical semantics of which the natural
deduction syntax is
With the elements that are the semantics of the terms appearing here made explicit, this
is the syntax for a diagram
4. computation rule. The next part of the universal property of the product in category
theory is that the resulting diagram
is in fact a commuting diagram. Syntactically this is, clearly, the rule that the following
identifications of strings of symbols are to be enforced
p1(a,b)=ap2(a,b)=b.p_1(a,b) = a \;\;\;\;\;\; p_2(a,b) = b\,.
In the next section we promote our running example category C\mathcal{C}, which
admits only very few universal constructions (just products), to a richer category,
the sheaf topos over it. That richer category then accordingly comes with a
richer syntax of natural deduction inside it, namely with full dependent type theory. This
we discuss in the Syn Layer below.
The dictionary between dependent type theory with product types and category
theory of categories with products.
\,
type theory category theory
syntax semantics
natural deduction universal construction
substitution……………………. pullback
x_2 \, f∗A↓X1→→fA↓X2\array{ f^*
x2:X2⊢A(x2):Typex1:X1⊢f(x1):X2x1:X1⊢A(f(x1)):Type\frac{
\colon X_2\; \vdash\; A(x_2) \colon Type \;\;\;\; x_1 A &\to& A \\ \downarrow &&
\colon X_1\; \vdash \; f(x_1)\colon X_2}{ x_1 \colon \downarrow \\ X_1
X_1 \;\vdash A(f(x_1)) \colon Type} &\stackrel{f}{\to}& X_2 }
\,
\,
Edit | Back in time (1 revision) | See changes | History | Views: Print | TeX | Source
This site is running on Instiki 0.19.7(MML+)
Powered by Ruby on Rails 2.3.18