-
-
Notifications
You must be signed in to change notification settings - Fork 570
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
giacpy_sage doctest failure and new libsingular cf.type == n_unknown ring test #21884
Comments
comment:1
I don't think that it is related to #21860 (giac update), but it is related to the singular upgrade: with sage 7.5beta2 (singular4)
but with older versions with singular3 it gives
|
comment:2
In fact the doctest was not using the result computed by giac but was recomputing everything with singular so I have changed this. I have not yet changed the output doc string because it seems not coherent with the documentation of
but
Last 10 new commits:
|
Changed dependencies from #21860 to none |
Commit: |
Branch: public/giacpy21884 |
This comment has been minimized.
This comment has been minimized.
comment:4
15 commits to change just one line of code? Please squash this to one commit :-) |
comment:5
And change the title to something which refers to Singular. |
comment:6
sorry for the messy branch, here is a new one New commits:
|
Changed branch from public/giacpy21884 to public/trac21884 |
comment:7
how about changing the doc of
is no longer true. |
comment:8
Before doing just that, my question is also about how QQ was detected in the old code and does the new condition detect any ring, because if I grep the old test I already have:
|
comment:9
So if I am right it seems that the old test ringtype != 0 was used as a trick to detect if the ring of coefficient was not a field, and seems equivalent to cf.type == one of n_Z, n_Zm, n_Zmn, n_Z2n in src/sage/rings/polynomial/multi_polynomial_libsingular.pyx in interreduced the normalisation of the head coefficient may be never executed and is not equivalent to the old code. So I suggest 2 modification.
for plural.pyx it should be OK because of the or But in src/sage/libs/singular/singular.pyx the 2 substitutions gives strange code:
for instance n_Zp had ringtype == 0 |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:11
NB: I chose solution 2 because the reduced command of multi_polynomial_sequence.py also talk of normalized polynomials and use the libgiac interred:
|
comment:12
NB: I am not confortable enough with sage and singular to modify the == n_unkown in: Does anyone plan to change it or can I switch to need review? |
Author: Frederic Han |
comment:16
Rebased to 7.6.beta6 |
comment:17
Is it good to go ? |
comment:18
I have not run the test suite for while but we should try if other doctests have been added in between |
comment:19
In 7.6.rc1 + #20523 + #21884 (present ticket) :
which is transient (i. e. pass without failure when ran standalone). ==> |
comment:20
Forgot to sign the review... |
Reviewer: Emmanuel Charpentier |
comment:21
Note : I do not understand the patchbot failure. Someone with a better understanding of the patchbot system should investigate the issue... |
Changed branch from public/trac21884 to |
Related to #21860 : one failure in ptestlong :
in fact it is related to the singular update #17254 where all the
were replaced by
but it seems not equivalent with QQ coefficients.
Remarks: The interred_libsingular function of multi_polynomial_ideal_libsingular.pyx
ends with an explicit:
and the groebner_basis function doc have still five examples giving:
so what is the best thing for the interreduced_basis command to output?
CC: @sagetrac-parisse @frederichan-IMJPRG @jpflori
Component: doctest coverage
Author: Frederic Han
Branch/Commit:
fd60c06
Reviewer: Emmanuel Charpentier
Issue created by migration from https://trac.sagemath.org/ticket/21884
The text was updated successfully, but these errors were encountered: