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
OA(7,66), OA(7,68), OA(8,69), OA(7,74) and OA(8,76) #16361
Comments
Branch: u/ncohen/16361 |
Author: Nathann Cohen |
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
comment:5
Hi Nathann, The function Vincent |
comment:6
Hellooooooooo !!
Indeed. And sensitive to the labelling of the design, which I guess is what bothers you.
First, it is not true that "this can change and that I cannot rely on that" because there is a doctest. So if the constructions for which we need Secondly, you are right that the least we can do is solve this problem "up to relabelling" of the original design. This is what is being done in #16391 (it depends on #16370), which also implements another technique to find
Sooooooooooo given that
ittttttt would be cool if you could consider that this problem does not matter as it is already fixed above. It just comes from the fact that I write all my code in the same file but that I try to split it into small bits that are easier to review... And in this case I probably removed the call to Nathann |
comment:8
EDIT: post removed |
comment:9
Hello,
see the changes on the branch Do you have further remarks? Otherwise it deserves a positive review. Vincent |
comment:10
Hello !
+1
See [1]
+1
See below
+1
Well... Actually, I think that you should not intercept all exceptions in order to return specific error messages... I believe that you should let the subfunction raise its own exception. That's going too far I think If the user requests a construction that requires other construction, let the other constructions raise an exception ! The user will see a message like "Impossible to build a OA(....)", meaning that the function needed one and it did not exist.
In the first two situations, you return manually the exception that should be raised by incomplete_orthogonal_array. Why do it again manually ? Why not just call it ? Same here
The line you removed was doing the very same job, i.e. forwarding the non-existence results ! All you did was rewrite the exception, and the user sees : "There is no OA(k,n) and this no OA(k,n)-xOA(k,1)" instead of "There is no OA(k,n)" I believe that you should let the subfunction raise its exception. What do you think ? Nathann |
comment:11
Replying to @nathanncohen:
What is
All right, but then you should put #16388 as a dependency and adapt the doctests... Vincent |
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:14
Here it is ! Nathann |
comment:15
Hi, Looks good to me. All test pass and documentation builds! Do you know if there is an Vincent |
comment:16
Yo !
I hope that Volker will merge it soon... I had not noticed that some tickets had been closed already in an unreleased beta
HMmmm.... No idea, but there is a partial answer as Theorem III.3.32 in the handbook. Looks like we will call "is_sum_of_squares" again Nathann |
comment:18
Reviewer name Whats up with the TODO? |
comment:19
Sorry, it was a "note to self". I did that when I rebased everything above. Nathann |
Reviewer: Vincent Delecroix |
This comment has been minimized.
This comment has been minimized.
Changed branch from u/ncohen/16361 to |
New designs, and a new "TD from PBD" construction ! Too bad this construction cannot be called automatically (yet)
:-P
Nathann
Depends on #16461
Depends on #16388
CC: @videlec @KPanComputes @dimpase @brettpim
Component: combinatorial designs
Author: Nathann Cohen
Branch/Commit:
5d4607a
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/16361
The text was updated successfully, but these errors were encountered: