Add Examples to Manifolds Catalog

[mjungmath]

The current catalog is nice to have but still very limited or incomplete. Constructing some examples in the current catalog also takes a lot of time.

While improving and extend this, it is also a good opportunity to expand the tutorials a little bit. Furthermore, most of our docstring examples are based on the 2-sphere. Hence we can perhaps shorten or simplify some parts of the documentation.

Step 1: rearrange folder structure (#30799)

Step 2: unification/improvement/extension of preexisting models

• More Flexible Coordinate Treatment for EuclideanSpace (More Flexible Coordinate Treatment for EuclideanSpace #30824)
• Category of connected manifolds will be joined to spheres, Euclidean spaces and open intervals (Stronger Categories for Manifold Examples: Connectedness #31243)
• Add Orientation to EuclideanSpace
• Sphere (Add Spheres smoothly embedded in Euclidean Space to Manifold Catalog #30804, Sphere: improve handling of default charts #32953)
• Kerr (some inspiration may be found in the class KerrBH of the Sage package kerrgeodesic_gw)
• Minkowski
• Torus
• Move examples from sage.geometry.riemannian_manifolds to sage.manifolds (Move examples from sage.geometry.riemannian_manifolds to sage.manifolds #32228)

Step 3: add new examples

• Real Projective Space / Real Grassmannians (Grassmann Manifolds #31249, Add example of projective space to manifold catalog #33221)
• Complex Projective Space / Complex Grassmannians (Grassmann Manifolds #31249)
• Hyperbolic space (a starting point may be this notebook)

Step 4: improve the tutorial/doctests

• simplify preexisting 2-sphere examples
• add thorough tutorial with old/new models

CC: @egourgoulhon @tscrim @tobiasdiez

Component: manifolds

Issue created by migration from https://trac.sagemath.org/ticket/30189

[egourgoulhon]

comment:1

This sounds like a very good idea!

Note that in order not to clutter the global namespace, one can let access to the sphere and the hyperbolic space via the manifold catalog. The current version of the catalog is very primitive and the function Sphere() in it should call the constructor the sphere class, as soon as the latter is ready.

[mjungmath]

comment:2

Replying to @egourgoulhon:

This sounds like a very good idea!

Note that in order not to clutter the global namespace, one can let access to the sphere and the hyperbolic space via the manifold catalog. The current version of the catalog is very primitive and the function Sphere() in it should call the constructor the sphere class, as soon as the latter is ready.

Ah, that is very nice. Actually, I was not aware that something like that exists. This should be populated somewhere more obvious. Probably in a tutorial?

So, the only thing that should be added now is the hyperbolic space, right?

[mjungmath]

comment:3

By the way, I noticed that the result coming from sage.manifolds.catalog.Sphere is not even correct:

sage: S.<th, ph> = manifolds.Sphere()
sage: S
2-dimensional Riemannian submanifold S embedded in the Euclidean
 space E^3
sage: S.atlas()
[Chart (S, (th, ph))]

This is not a correct atlas.

[egourgoulhon]

comment:4

Replying to @mjungmath:

Ah, that is very nice. Actually, I was not aware that something like that exists. This should be populated somewhere more obvious. Probably in a tutorial?

Indeed, when it is more developed.

So, the only thing that should be added now is the hyperbolic space, right?

No, there remains to introduce a proper sphere class, on the model of EuclideanSpace, with methods like stereographic_coordinates.

[egourgoulhon]

comment:5

Replying to @mjungmath:

By the way, I noticed that the result coming from sage.manifolds.catalog.Sphere is not even correct:

sage: S.<th, ph> = manifolds.Sphere()
sage: S
2-dimensional Riemannian submanifold S embedded in the Euclidean
 space E^3
sage: S.atlas()
[Chart (S, (th, ph))]

This is not a correct atlas.

Indeed. As I say in comment:1, the catalog is in a primitive stage.

[mjungmath]

comment:6

Now I see what you mean. I first thought that "primitive" was just referring to the amount of examples.

That's good: there's still work to do. :)

[mkoeppe]

comment:18

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

[mkoeppe]

comment:19

There is also some old code in sage.geometry.riemannian_manifolds that seems to provide some examples

[egourgoulhon]

comment:20

Replying to @mkoeppe:

There is also some old code in sage.geometry.riemannian_manifolds that seems to provide some examples

Indeed! These examples should be integrated into the catalog and then sage.geometry.riemannian_manifolds should be deprecated, since all the functionalities it contains are available in sage.manifolds.differentiable.pseudo_riemannian_submanifold.