Given that on the input we discuss that answers returned by msolve don't make
sense,
we should leave it in place.
IMHO msolve tries to find a univariate representation for the solutions, and so
it needs a big field to work in - and I don't even know whether there any
pitfalls with this approac
Hi Dima,
Dima Pasechnik wrote:
> So this is due to "0 < char <= 2**17 and deg != elim.degree()" - added
> by you - which does not make sense to me.
> Is this "Criterion" no longer applicable?
I don't know. This criterion was suggested to me by Mohab after I
complained that msolve -P 1 often retur
Hi Marc,
On Sun, Jun 30, 2024 at 8:04 AM Marc Mezzarobba wrote:
>
> 'Peter Mueller' via sage-devel wrote:
> > R. = GF(2)[]
> > L = [a^2+a, b^2+b]
> > I = ideal(L)
> > V = I.variety(algorithm='msolve', proof=False)
> >
> > raises a `ValueError: positive-dimensional ideal`, which of course is
> > n
On Sun, Jun 30, 2024 at 12:08 PM 'Peter Mueller' via sage-devel
wrote:
>
> OK, it apparently was a bug of the previous version of msolve: For `msolve -P
> 2 -f file.ms` with msolve 0.6.5-2 yields the wrong result claiming that the
> dimension is positive, no matter whether file.ms ends with a ne
OK, it apparently was a bug of the previous version of msolve: For `msolve
-P 2 -f file.ms` with msolve 0.6.5-2 yields the wrong result claiming that
the dimension is positive, no matter whether file.ms ends with a newline
character or or not, while msolve 0.6.6-1 yields the correct result in bo
'Peter Mueller' via sage-devel wrote:
> I guess that in your snippet, you manually typed the `enter` key after
> the `cat` command in the console.
Hmm, no, there is a newline at the end:
~$ hexdump -c /tmp/tmprcz_zw9l
000 a , b \n 2 \n a ^ 2 + a , \n b ^ 2
010
msolve apparently ignores the last line of the input file if it does not
end with a newline character. If one adds it, then it yields the correct
result. The doc of msolve ("2 Input file format") probably should be
clearer about that.
I guess that in your snippet, you manually typed the `enter`
'Peter Mueller' via sage-devel wrote:
> R. = GF(2)[]
> L = [a^2+a, b^2+b]
> I = ideal(L)
> V = I.variety(algorithm='msolve', proof=False)
>
> raises a `ValueError: positive-dimensional ideal`, which of course is
> nonsense. Exporting the system to an msolve-readable file and using
> msolve directl
