-
-
Notifications
You must be signed in to change notification settings - Fork 552
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
Errors with graph complement #15669
Comments
comment:1
Hello Travis ! Well, I guess you can fix this one yourself ! You should just add a Nathann |
comment:2
Replying to @nathanncohen:
Done and NR. Although making an immutable copy destroys the name of the graph, so a slightly different question is do we want that behavior.
Ah, I see. I also understand why you want to keep the same layout as the original graph too. Thanks, Travis New commits:
|
Branch: public/graphs/complement-15699 |
This comment has been minimized.
This comment has been minimized.
Author: Travis Scrimshaw |
Commit: |
comment:3
Hello !
O_o Destroys the name of the graph ? Why ? Well if it does I guess it's a bug, isn't it ? Besides : shouldn't the complement of an immutable graph be immutable ? There are so many functions that will react oddly to immutable graphs....
Yep. It's just unfortunate for this graph Nathann |
comment:4
Replying to @nathanncohen:
I agree that it is a bug:
What's the "canonical" way to check if a graph
We'll just keep fixing them as we come across them I guess. Best, Travis |
comment:5
Yoooooooo !
Hmmmmmmm.... Well, we have been using
Yepyepyep But the graph products. The unions. The subgraphs. The orientations... pffffff Nathann |
comment:7
Okay, the names issue is actually something with the graph constructor:
Nathann, you're likely to know best how to fix that, do you think you could do it? |
comment:8
Yoooooooooo !
Oh sorry, I thought that you would only deal with this Nathann |
comment:9
The |
comment:10
Okay, done in #15681 ! Nathann |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
comment:12
Okay, immutable graph complements now return immutable graphs with the correct name. |
comment:13
I may have mentionned a couple of times that seeing the commits of the ticket's dependencies was a pain. So let's say it another time : it is a pain. Nathann |
comment:14
Okay, good to go ! I set it to positive review and add the dependency with #15681. A request, though : could you add the ticket number to the commit message ? This helps a lot with tickets like that. If all the other commits did not contain the number, there would be no way to know what belong to this ticket easily Thaaaaaaaaaanks for this ticket ! Nathann |
Dependencies: #15681 |
Reviewer: Nathann Cohen |
comment:16
I thought I added the dependency...shrugs I'll take the commit message under advisement. Thank you for doing the review. |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. New commits:
|
comment:19
I just realized the ticket number is wrong... whoops |
comment:20
I don't get it Why did you change this hasattr line, and why did you add to the branch ? Nathann |
comment:21
Can't we just remove the last 3 commits ? They undo what they do Nathann |
comment:22
|
comment:23
Okayokay Nathann |
Changed branch from public/graphs/complement-15699 to public/graphs/complement-15669 |
comment:24
Rebased branch. New commits:
|
comment:27
The trac reference in the doctest added in this ticket had a typo. |
We can't take the complement of an immutable graph:
which is because
copy(Gamma)
doesn't return a mutable copy.Depends on #15681
CC: @nathanncohen
Component: graph theory
Author: Travis Scrimshaw
Branch/Commit: public/graphs/complement-15669 @
c393b58
Reviewer: Nathann Cohen
Issue created by migration from https://trac.sagemath.org/ticket/15669
The text was updated successfully, but these errors were encountered: