Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in Chart.__init__ regarding the determination of top charts #32112

Closed
egourgoulhon opened this issue Jul 3, 2021 · 12 comments
Closed

Bug in Chart.__init__ regarding the determination of top charts #32112

egourgoulhon opened this issue Jul 3, 2021 · 12 comments

Comments

@egourgoulhon
Copy link
Member

As noticed in #31901 comment:28, there is an issue when constructing two charts sharing the same coordinate symbols but not being otherwise related:

sage: M = Manifold(2, 'M', structure='topological')
sage: U = M.open_subset('U')
sage: V = M.open_subset('V')
sage: XU = U.chart('x y')
sage: XV = V.chart('x y')
sage: M.top_charts()
[Chart (U, (x, y))]

The chart XV should also appear as a top chart on M.

CC: @mkoeppe @tscrim @mjungmath @vbraun

Component: manifolds

Keywords: coordinate chart

Author: Eric Gourgoulhon

Branch/Commit: public/manifolds/top_charts_32112 @ 4e316e9

Reviewer: Matthias Koeppe

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

@egourgoulhon egourgoulhon added this to the sage-9.4 milestone Jul 3, 2021
@egourgoulhon
Copy link
Member Author

New commits:

4e316e9Fix bug in Chart.__init__ regarding the determination of top charts (Trac #32112)

@egourgoulhon
Copy link
Member Author

Author: Eric Gourgoulhon

@egourgoulhon
Copy link
Member Author

Commit: 4e316e9

@egourgoulhon
Copy link
Member Author

Branch: public/manifolds/top_charts_32112

@mkoeppe
Copy link
Contributor

mkoeppe commented Jul 3, 2021

Reviewer: Matthias Koeppe

@mkoeppe
Copy link
Contributor

mkoeppe commented Jul 3, 2021

comment:2

Thanks! This is working well.

@mkoeppe
Copy link
Contributor

mkoeppe commented Jul 3, 2021

comment:3

It would have been good to do this on top of #32009 though

@egourgoulhon
Copy link
Member Author

comment:4

Thanks for the review.

Replying to @mkoeppe:

It would have been good to do this on top of #32009 though

Could you explain why? I mean, why _domain should become a Cython attribute?

@mkoeppe
Copy link
Contributor

mkoeppe commented Jul 4, 2021

comment:5

In #31894 I hope to make Chart a subclass of sage.categories.map.Map so that all functionalities of morphisms such as composition etc. become available. Map is a Cython class in which _domain happens to be a Cython attribute.

@mkoeppe
Copy link
Contributor

mkoeppe commented Jul 4, 2021

comment:6

As #32009 came back with a bug, I have made the present ticket a dependency of #32009 instead.

@egourgoulhon
Copy link
Member Author

comment:7

Replying to @mkoeppe:

In #31894 I hope to make Chart a subclass of sage.categories.map.Map so that all functionalities of morphisms such as composition etc. become available. Map is a Cython class in which _domain happens to be a Cython attribute.

Thanks for the explanation.

@mkoeppe
Copy link
Contributor

mkoeppe commented Jul 24, 2021

comment:8

Apparently this has been merged as part of #32089.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants