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

Smoothly Embed Vector Bundles into Preexisting Code #28718

Open
DeRhamSource mannequin opened this issue Nov 11, 2019 · 5 comments
Open

Smoothly Embed Vector Bundles into Preexisting Code #28718

DeRhamSource mannequin opened this issue Nov 11, 2019 · 5 comments

Comments

@DeRhamSource
Copy link
Mannequin

DeRhamSource mannequin commented Nov 11, 2019

Though, ticket #28159 implemented vector bundles into Sage and is already merged, there are still things to do. Sections and tensor fields share similar or even identical code lines and implementation concepts. This comes in quite unhandy when further modifications are to be made, either to vector bundles or to tensor fields.

This gap should be closed in this ticket. Appropriate inheritances and removing code redundancies will be performed here.

Until this ticket is finished, I suggest one of the following procedures:

  1. Every modification either to tensor fields or to sections, should be done for both if intersections occur. This makes the following task devoted to this ticket easier and keeps the code as clean as possible.

  2. Link the ticket devoted to possible interactions in the comments of this ticket.

CC: @egourgoulhon

Component: geometry

Keywords: vector bundles

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

@DeRhamSource DeRhamSource mannequin added this to the sage-9.0 milestone Nov 11, 2019
@DeRhamSource DeRhamSource mannequin added c: geometry labels Nov 11, 2019
@DeRhamSource

This comment has been minimized.

@DeRhamSource
Copy link
Mannequin Author

DeRhamSource mannequin commented Nov 12, 2019

comment:1

#28716: Linearly independent vector fields as new frame -> Adaption to Sections

@embray
Copy link
Contributor

embray commented Jan 6, 2020

comment:2

Ticket retargeted after milestone closed

@embray embray modified the milestones: sage-9.0, sage-9.1 Jan 6, 2020
@mkoeppe
Copy link
Member

mkoeppe commented Apr 14, 2020

comment:3

Batch modifying tickets that will likely not be ready for 9.1, based on a review of the ticket title, branch/review status, and last modification date.

@mkoeppe mkoeppe modified the milestones: sage-9.1, sage-9.2 Apr 14, 2020
@mkoeppe mkoeppe modified the milestones: sage-9.2, sage-9.3 Aug 29, 2020
@mkoeppe
Copy link
Member

mkoeppe commented Feb 13, 2021

comment:5

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

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Feb 13, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.4, sage-9.5 Jul 19, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.5, sage-9.6 Dec 18, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.6, sage-9.7 Apr 1, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.7, sage-9.8 Aug 31, 2022
@mkoeppe mkoeppe removed this from the sage-9.8 milestone Jan 29, 2023
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