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
Stupid waste of time in graphs 1 #15704
Comments
Branch: u/ncohen/15604 |
comment:2
This is the kind of patches that breaks code everywhere in Sage. We better wait for the patchbot to say it passes tests before getting it in. Nathann |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
comment:4
I think you should have something documenting what happens with the old "bad" behavior. I assume it raises a well-formed error that tells people exactly what to do? Also, it's not clear from the diff whether there are now no examples of adding edges with 2-tuples, which I assume is still supported. |
comment:5
Yo !
Well, it raises the same error as
I hope it will be explicit enough for the users, and that they will notice they feed the loop with heterogeneous data. As for testing I added a commit. Nathann |
Changed branch from u/ncohen/15604 to u/ncohen/15704 |
Changed commit from |
Commit: |
comment:8
A commit to haul what we sow. Nathann |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
OOps. Perhaps I should change the commit message |
comment:13
Hi Nathann, my branch: u/vdelecroix/15704 I simplified the |
comment:14
Can you provide timings for this change ? If it is not that bad it is good to have indeed. Nathann |
comment:15
Replying to @nathanncohen:
Here they are. Your version
mine
(Be careful the branch is not yet merged with 6.2.rc0 and |
comment:16
Hmmm.... 10%... I'd vote for the first version. What do you think ? Yours handles more case, but it would mean that input is a bit messy ?... Nathann |
comment:17
Replying to @nathanncohen:
The main question: is this function critical? Is there any piece of code that uses it intensively? |
comment:18
Well, I began to write those patches because Jernej was not able to build a Graph with Sage .... I do not think that it really is the bottleneck in any code, but if the error message is clear, I don't think anybody can really complain that Sage refuses inputs like So well. I'd go for the most efficient way to do it, given that I do not see this being a real problem for anybody.... I don't like to know that everybody loses 10% to prevent several users from cleaning their input a bit Nathann |
comment:19
Then leeeeet's go! Vincent |
comment:20
Thaaaaaanks ! Nathann |
comment:22
Reviewer name |
Reviewer: Vincent Delecroix |
comment:24
doctest failures after merge |
comment:25
turns out some combinat code was feeding the function with non-uniform input. Testing the whole Sage code... It would be cool if I could set up a patchbot on my office's computer, really Nathann |
comment:27
Passes all long tests. |
Changed branch from u/ncohen/15704 to |
............
The point is that MY computations are never long because of the add/remove edge functions. I should pay more attention
T_T
Before
After
Nathann
CC: @sagetrac-azi
Component: graph theory
Author: Nathann Cohen
Branch/Commit:
297b1b3
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/15704
The text was updated successfully, but these errors were encountered: