[sage-devel] Error installing package gap_packages-4.10.2.p1

2020-10-27 Thread 'Peter Mueller' via sage-devel
On a Lenovo ThinkPad with an up to date Manjaro Linux OS and Sage 9.2 successfully compiled from source I failed to install gap_packages-4.10.2.p1, while many other optional packages (like the huge cbc) installed perfectly. Below I append the (hopefully) relevant piece of the log file. -- Pet

[sage-devel] git clone git://github.com/sagemath/sage.git didn't do what I expected

2020-10-28 Thread 'Peter Mueller' via sage-devel
I'm sorry if the following is more appropriate for sage-support. I just tried to follow the first few steps from the Developer's Guide v9.2. From that I would have expected that after running "git clone git://github.com/sagemath/sage.git" I would find two branches of the source code, namely sag

[sage-devel] Wrong degree limit in PrimitiveGroup()

2021-05-03 Thread 'Peter Mueller' via sage-devel
Still in SageMath version 9.3.rc5, the call "PrimitiveGroup(2500, 1)" raises a "NotImplementedError: Only the primitive groups of degree less than 2500 are available in GAP's database", even though the primitive groups are available up to degree 4095. The exception is raised by the wrong degree

Re: [sage-devel] Wrong degree limit in PrimitiveGroup()

2021-05-03 Thread 'Peter Mueller' via sage-devel
ady a trac ticket opened about > that? > > Vincent > > Le 03/05/2021 à 17:53, 'Peter Mueller' via sage-devel a écrit : > > Still in SageMath version 9.3.rc5, the call "PrimitiveGroup(2500, 1)" > > raises a "NotImplementedError: Only the primiti

[sage-devel] Strange bug connected to GAP as a backend

2022-11-21 Thread 'Peter Mueller' via sage-devel
The following lines do what is to be expected: sage: g = SymmetricGroup(3) : u = g.subgroup([]) : x1 = u.trivial_character().induct(g) : dummy = g.conjugacy_classes_subgroups() : x2 = u.trivial_character().induct(g) : print(x1 == x2) : print(x1.scalar_product(x1)) : pri

[sage-devel] Bug in representative_action()

2023-03-28 Thread 'Peter Mueller' via sage-devel
The method representative_action() for Sage permutation groups erroneously returns the identity element when it actually should either fail or return something which makes clear if no representative exists. The corresponding method for libgap groups behaves as expected: sage: g = PermutationGr

[sage-devel] SingularError in rational_parameterization

2024-04-17 Thread 'Peter Mueller' via sage-devel
The following code raises a SingularError in SageMath version 10.4.beta3 (with system singular enabled), and the same at https://sagecell.sagemath.org/ : R. = QQ[] f = -2*x^2*y^2 - x^3 - x^2*y + x*y^2 + y^3 + 2*x^2 + 2*y^2 - 2 C = Curve(f) assert C.genus() == 0 print(C.rational_parameterization(

[sage-devel] Re: SingularError in rational_parameterization

2024-04-19 Thread 'Peter Mueller' via sage-devel
I just figured out that the installation from source (even with the explicit configure option `--with-system-singular`) on an up to date arch linux machine ignores the installed singular (`pacman -Q singular` returns `singular 4.3.2.p16-1`). Not sure if it is a path problem that makes the conf

Re: [sage-devel] Re: SingularError in rational_parameterization

2024-04-19 Thread 'Peter Mueller' via sage-devel
am Freitag, 19. April 2024 um 12:08:01 UTC+2: > On Fri, Apr 19, 2024 at 02:28:13AM -0700, 'Peter Mueller' via sage-devel > wrote: > > I just figured out that the installation from source (even with the > > explicit configure option `--with-system-singular`) on an u

Re: [sage-devel] Re: SingularError in rational_parameterization

2024-04-20 Thread 'Peter Mueller' via sage-devel
Dima Pasechnik schrieb am Samstag, 20. April 2024 um 17:57:05 UTC+2: [...] well, this looks relevant. "any of gmp ntl flint readline mpfr cddlib is installed as or will be installed as SPKG" these are Singular's dependencies, and possibly not all of them are on your OS. In particular, flint is

[sage-devel] Error in I.variety(algorithm='msolve', proof=False)

2024-06-29 Thread 'Peter Mueller' via sage-devel
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 directly (with the -P 2 flag) returns the correct result.

[sage-devel] Re: Error in I.variety(algorithm='msolve', proof=False)

2024-06-30 Thread 'Peter Mueller' via sage-devel
the `enter` key after the `cat` command in the console. -- Peter Mueller Marc Mezzarobba schrieb am Sonntag, 30. Juni 2024 um 09:04:28 UTC+2: > 'Peter Mueller' via sage-devel wrote: > > R. = GF(2)[] > > L = [a^2+a, b^2+b] > > I = ideal(L) > > V = I.variety(alg

[sage-devel] Re: Error in I.variety(algorithm='msolve', proof=False)

2024-06-30 Thread 'Peter Mueller' via sage-devel
both cases. Still, from within Sage, I get the wrong result. So I guess I need to force Sage to use the system msolve rather the one which Sage built during installation. -- Peter Mueller Marc Mezzarobba schrieb am Sonntag, 30. Juni 2024 um 12:27:25 UTC+2: > 'Peter Mueller' via sag

[sage-devel] Bug in `factor` for multivariate polynomials over QQbar

2024-08-02 Thread 'Peter Mueller' via sage-devel
The line `R. = QQbar[]; factor(a^2 - 2*c^2)` raises a ValueError: variable name '@c' is not alphanumeric while the same line with `c` replaced with `b` works fine. This happens in a local installation of Sage 10.4 (and 10.5.beta0), but also on the SageCell. -- Peter Mueller -- You received t