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

Make Dynkin diagrams coming from a Cartan type immutable and better respect edge deletion #15739

Open
tscrim opened this issue Jan 27, 2014 · 1 comment

Comments

@tscrim
Copy link
Collaborator

tscrim commented Jan 27, 2014

So we don't get behavior like this:

sage: d = DynkinDiagram(['B',3])
sage: d.edges()
[(1, 2, 1), (2, 1, 1), (2, 3, 2), (3, 2, 1)]
sage: d
O---O=>=O
1   2   3
B3
sage: d.delete_edge(1,2)
sage: d.edges()
[(2, 1, 1), (2, 3, 2), (3, 2, 1)]
sage: d    # This iswrong
O---O=>=O
1   2   3
B3
sage: CartanMatrix(d)   # So is this
[ 2 -1  0]
[ 0  2 -1]
[ 0 -2  2]

CC: @sagetrac-sage-combinat @nthiery @sagetrac-jakobkroeker

Component: combinatorics

Keywords: dynkin diagrams

Stopgaps: wrongAnswerMarker

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

@tscrim tscrim added this to the sage-6.1 milestone Jan 27, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.1, sage-6.2 Jan 30, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.2, sage-6.3 May 6, 2014
@sagetrac-vbraun-spam sagetrac-vbraun-spam mannequin modified the milestones: sage-6.3, sage-6.4 Aug 10, 2014
@sagetrac-jakobkroeker
Copy link
Mannequin

sagetrac-jakobkroeker mannequin commented Mar 3, 2017

Stopgaps: wrongAnswerMarker

@mkoeppe mkoeppe removed this from the sage-6.4 milestone Dec 29, 2022
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