[sage-devel] Re: A Sage interface for FGb (Gröbner bases)

Am Samstag, 24. November 2018 23:11:26 UTC+1 schrieb parisse: > > > Giac supports double revlex ordering, this is the order used by the > eliminate command of Giac. Geogebra has many examples of eliminate commands > there https://dev.geogebra.org/trac/browser/trunk/geogebra/giac/src/test >

[sage-devel] Re: A Sage interface for FGb (Gröbner bases)

Am Freitag, 7. Dezember 2018 13:07:45 UTC+1 schrieb Bill Hart: > > How many physical cores do you have on the machine (not logical cores), > and how many CPU sockets and what is the cache structure? (I assume it is > at least 16 physical cores, but I'm asking more because this sort of thing >

[sage-devel] Re: A Sage interface for FGb (Gröbner bases)

Am Donnerstag, 6. Dezember 2018 11:41:23 UTC+1 schrieb Bill Hart: > All the other systems are using modular methods here, so Roman use the > modstd library (the command is modStd) in Singular to get those timings. > Indeed cyclic7 over Q takes about 20s on my laptop in Singular using this >

[sage-devel] A Sage interface for FGb (Gröbner bases)

Hi everyone. I created a Sage wrapper for the C interface of FGb, which makes it easy to call FGb from within Sage. The sources are available on Github [1] and can be installed as a Python package into Sage: [1] https://github.com/mwageringel/fgb_sage FGb is a C-library by J. C. Faugère for

[sage-devel] Re: A Sage interface for FGb (Gröbner bases)

Thanks for the feedback everyone. Am Donnerstag, 22. November 2018 09:53:43 UTC+1 schrieb parisse: > > Did you make some comparisons with Giac ? > > Some benchmarks from Roman Pearce and my own tests, about 2 years old. > I have not done any comparisons, mainly because I cannot do anything about

[sage-devel] Build problem when copying __pycache__, Sage 8.5.beta4

When I try to compile Sage 8.5.beta4 using `make distclean && make build` on OS X 10.13.6, I get an error as below. It fails at copying the directory "src/bin/__pycache__". Manually copying over the directory solves the problem, so this is probably easy to fix, but I am not sure where this `cp`

[sage-devel] Re: issues (memory leak + slowness) with multivariate polynomials

If I compute a Gröbner basis using libSingular, it is much slower than using the Singular interface. Could this be related to the memory leaks or is it a different issue? sage: I = sage.rings.ideal.Katsura(PolynomialRing(QQ, 'x', 9)) sage: %time gb1 = I.groebner_basis(algorithm='singular') CPU

[sage-devel] Re: giacpy_sage fails to install

Oh, I do that for developing. Yet, although I am looking forward to using Python 3, I prefer to have a reliable stable install as well. I had some trouble with compiling the betas a few times in the past when I ended up without a working copy of Sage. The full compilation process takes hours on

Re: [sage-devel] giacpy_sage fails to install

Thanks for the explanation. This is now #28082 . -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[sage-devel] Re: How to use spkg-install in a travis-ci script?

I think it would be good to keep the install script for Travis-CI as close as possible to what you would normally do to install a package in Sage, that is, create an updated tarball of your repository and copy it to upstream/, update the checksums and then install it with sage -i. This way,

[sage-devel] Re: A Sage interface for FGb (Gröbner bases)

Hi David, my bad, I had forgotten to update the gist. I have just updated it, see [1]. There I used Singular (not libSingular), which usually should not make much of a difference for this kind of computation. However, note that there are some concerning speed issues with Singular/libSingular

Re: [sage-devel] docker images "latest" and "develop" are old

There also appears to be a problem with the credentials, causing the last step, pushing the image to DockerHub, to silently fail. For example, this is the log for the last run on the develop branch [1], which last ran for 8.8.rc1. $ sh .ci/push-dockerhub.sh sagemath + sh .ci/push-dockerhub.sh

[sage-devel] Re: Possible to use current Sage version in travis-ci?

Usually, the latest beta should be available as sagemath/sagemath:develop at DockerHub. However, for some reason this tag has not been updated in a while, so it still points to 8.8.beta5. See also https://groups.google.com/forum/#!topic/sage-devel/hHWlOluXtos. It is also possible to use the

[sage-devel] giacpy_sage fails to install

I have just tried to upgrade my main Sage install from 8.7 to 8.8, but the optional package Giacpy_sage fails to build. The logs mention several errors reported by gcc – the log file is attached. This is on OS X 10.13.6 with Clang 10.0.0, but I have observed this problem on a Linux machine as

[sage-devel] Re: issues (memory leak + slowness) with multivariate polynomials

If I understand the documentation correctly, both cases should call the same Singular function (`groebner` in this case), with the only difference that one is called through the C interface and the other via the Pexpect interface. When I enable the protocol by passing `prot=True`, I get the

[sage-devel] Sporadic build failure of zope_interface-4.6.0 and entrypoints-0.3

When building 9.0beta3 (or 9.0beta2) in parallel on two CentOS machines, I once got the following two build failures that I do not know how to resolve. Starting the build process again made the build complete successfully, so it looks like these packages do not list all their dependencies.

[sage-devel] Re: Escape sequence in doctest output using Xterm/readline

Thank you for the explanation. I confirm that adding set enable-meta-key off to my .inputrc file solves the problem. Am Samstag, 16. November 2019 23:03:32 UTC+1 schrieb dic...@invisible-island.net: > > That 1034 stuff turns on *meta-mode*, which is not a new feature (about > twelve years). >

[sage-devel] Escape sequence in doctest output using Xterm/readline

On CentOS 7.7, I see a large number of doctest failures due to the escape sequence appearing in the output. For example: ./sage -t --long src/sage/combinat/tableau.py ** File "src/sage/combinat/tableau.py", line 2850, in

Re: [sage-devel] macOS build failure (Singular/mpfr)

That worked. The build has finished successfully. Thanks. > Am 14.12.2019 um 12:47 schrieb Dima Pasechnik > > as a quick fix, try > > export LDFLAGS="-L/usr/local/lib" > make > > > > On Sat, 14 Dec 2019, 11:37 Markus Wageringel, <

Re: [sage-devel] macOS build failure (Singular/mpfr)

right. > > > On Sat, 14 Dec 2019, 11:07 Markus Wageringel, > wrote: > >> Hi everyone, >> >> trying to build 9.0.beta9 from scratch on macOS 13.6, the build fails for >> me while building Singular. There seems to be a problem with linking to the >> s

[sage-devel] How to deal with cross-references to Sphinx documentation of other projects

This came up in #29231 , and #27164 is related. Several packages included with Sage use Sphinx for their documentation (such as numpy, scipy, sympy, matplotlib, pplpy, cypari, cysignals). For the quality of our

Re: [sage-devel] How to deal with cross-references to Sphinx documentation of other projects

This is an interesting suggestion. How would this work with non-interactive builds like on the patchbots or in CI? Would the user be asked right before downloading, i.e. during the docbuild phase, or perhaps when running configure, so it can fail early? > Am 27.02.2020 um 03:30 schrieb Kwankyu

Re: [sage-devel] How to deal with cross-references to Sphinx documentation of other projects

, resolving cross-references can only work if we download missing inventory files or include them with Sage. > Am 27.02.2020 um 04:06 schrieb Michael Orlitzky : > > On 2/26/20 2:46 PM, Markus Wageringel wrote: >> >> This raises the question of how Sage should deal with thes

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

> Am 30.01.2020 um 23:10 schrieb Michael Orlitzky : > > This is a good point, but it's a problem we already have. We don't make > any promises about the precise message contained in e.g. a ValueError, > but we still frequently test the contents. You just update it when you > change the message.

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

Rather than distinguishing the different backends, I was more worried about how to keep what related doctests currently give us. For example, in src/doc/fr/tutorial/latex.rst, pretty_print is advertised as a way to obtain nicely formatted MathJax output: sage: pretty_print(x^12)

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

I have opened https://trac.sagemath.org/ticket/29136 proposing to change the default text display preference to "plain" for the text-based backends. > Am 30.01.2020 um 22:17 schrieb Nils Bruin : > > I do not think that's an issue at all. Presently, on

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

Am Dienstag, 28. Januar 2020 00:41:55 UTC+1 schrieb Michael Orlitzky: > > The insertion order is part of the language as of python-3.7, and can't > be changed: > > * https://mail.python.org/pipermail/python-dev/2017-December/151283.html > *

[sage-devel] Re: Poll: make giacpy_sage a standard package

Giacpy_sage provides C-bindings for Giac which is already a standard package. So making Giacpy_sage a standard package as well would allow to replace pexpect calls to Giac by C-calls, which is the overarching goal of #16688. Giac is currently used as fallback for symbolic integration where

Re: [sage-devel] Error building Sage 9.0 on CentOS 7.5

Rather than unsetting TERM, you could add set enable-meta-key off to your .inputrc file to solve this. I had the same problem here . Am Freitag, 31. Januar 2020 23:26:17 UTC+1 schrieb Josh Bevan: > > I "unset TERM" and that

Re: [sage-devel] 9.1.beta0: build problem using Homebrew's openblas

. > Am 12.01.2020 um 10:58 schrieb Dima Pasechnik : > > On Sun, Jan 12, 2020 at 12:10 AM Markus Wageringel > mailto:markus.wagerin...@gmail.com>> wrote: >> >> On macOS 10.13.6, trying to make use of #27870 using Homebrew's openblas, >> the build fails for

[sage-devel] Re: What should happen when we solve a linear system?

Over inexact rings, it is generally impossible to determine the rank or to check whether a square matrix is singular, so such a check should not be done at all, IMO. This implies that the `check` keyword should be ignored. This is also what https://trac.sagemath.org/ticket/13932 is about. For

[sage-devel] Re: Possible bug regarding the mod() method for multi-variable polynomials

There is also #27508 about this problem. It looks like a possible solution was suggested by upstream, but has not been implemented in Sage yet. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Re: Possible bug regarding the mod() method for multi-variable polynomials

Oh, you are right. Sorry for the noise. > Am 09.04.2020 um 19:32 schrieb Dima Pasechnik : > > On Fri, Apr 10, 2020 at 1:20 AM Markus Wageringel > wrote: >> >> There is also #27508 about this problem. It looks like a possible solution >> was suggested by upstream

[sage-devel] Re: Segmentation fault factoring a multivariate polynomial over IntegerModRing

It looks like this problem is going to be fixed by the upgrade to Singular 4.1.3 (#25993). sage: R. = Integers(7)[] sage: p = x**2-1 sage: p.factor() (x + 1) * (x + 6) There is another segmentation fault related to the non-commutative subsystem Plural, though, causing a doctest

[sage-devel] Re: Is this a bug?

Am Donnerstag, 16. April 2020 13:39:39 UTC+2 schrieb Mihai: > > fn = diff(FN(x,n), x) > mean(n) = integral(fn(x, n), (x, 0, oo)) > The main problem with this is that `fn` is just an expression, not a function of `(x, n)`. The call `fn(x, n)` switches the position of x and n, as apparently the

[sage-devel] Re: Efficient algorithm to express symmetric polynomial in terms of elementary ones

The bottleneck in `from_polynomial` is the check to test whether the input is actually a symmetric polynomial. If you disable the check, the computation is moderately fast, although not quite as fast as Vincent's code. Sym.e().from_polynomial(P(seq_taylor), check=False) -- You received

[sage-devel] Re: doc for web server installation

Hi Denis, I am not sure if this helps with your use case, but something I occasionally use to run Jupyter on a remote machine is a command like this: ssh -L localhost::localhost: REMOTE -t sage -n jupyter --no-browser --port= -- You received this message because you are subscribed

Re: [sage-devel] Re: solve() yields an expression rather than an equation/inequality

.net/p/maxima/bugs/>? I searched for it, and it appears > to be new. > > Thanks, > Evan > > > On Sun, Mar 29, 2020 at 5:36 PM Markus Wageringel > mailto:markus.wagerin...@gmail.com>> wrote: > Thank you for the report. This seems to be a problem in Maxima itself:

[sage-devel] Re: solve() yields an expression rather than an equation/inequality

Thank you for the report. This seems to be a problem in Maxima itself: sage -maxima (%i1) load(to_poly_solve)$ (%i2) to_poly_solve([x > 0, x <= 2*y, x <= 2 - 2*y], x); (%o2) %union([0 < x, x < min(2 y, 2 - 2 y), 2 y > 0, - 2 (y - 1) > 0], [x = 2 - 2 y, - 2 (y - 1) > 0, 2 (2 y - 1) > 0], [x = 2 y,

[sage-devel] Re: Polarization of Homogeneous Polynomials

Hi Michael, I do not know about preimplemented algorithms outside Sage itself, but it would not be so difficult to define this map directly. For example, as a map to the free algebra: sage: T. = FreeAlgebra(QQ) sage: R. = PolynomialRing(QQ) sage: def _polarize(f): : M = T.indices()

[sage-devel] Re: Polarization of Homogeneous Polynomials

Am Dienstag, 28. April 2020 20:23:01 UTC+2 schrieb Markus Wageringel: > > T = TensorFreeModule(V, (0, n)) > t = T([], name='t', sym=range(n)) > There is an error in this code. Here, `n` needs to be replaced by `f.degree()`. -- You received this message because you ar

[sage-devel] Re: Assumptions with complex variables (possible BUG)

You are probably using Sage with Python 2. In Python 2, a list expression involving an index variable `a` like assume([U_asm[a] for a in [0, 1, 3]]) overwrites the previous content of the variable `a`. At the end of the loop, `a` will have the value `3`, which leads to the output you

Re: [sage-devel] remove log_html() and other log_*()

Am Freitag, 8. Mai 2020 09:03:08 UTC+2 schrieb Sebastian Oehms: > > But if we talk about users who are not interested in code and strings, > wouldn't it be more useful for them to have a function that searches > through the global name space? Do we have such a one? > We do indeed. It is an

Re: [sage-devel] bug in matrix solve over inexact coefficients?

Indeed, instead of ignoring the `check` keyword altogether over inexact fields, it would be useful to verify the solution when that is possible, such as for exact input over SR and for ball and intervall fields. I have opened #29729 for this. For

Re: [sage-devel] bug in matrix solve over inexact coefficients?

Don't get me wrong. I would greatly prefer if RR would detect the ill-conditioned cases as well, but, as it stands, this is not implemented. Neither LU nor QR decompositions are supported for RR, so it is not easy to change this. The default implementation for solve_right just computes an

[sage-devel] Generalized eigenvalues with GUPTRI

Hello everyone. In Sage 9.2.beta11, Sage's functionality for eigenvalues and eigenvectors has been extended in two directions: • In #30393 , Marc Mezzarobba has added wrappers for arb's new support for arbitrary precision computation of eigenvalues and

Re: [sage-devel] check merge failure on Trac

Another option is to use git worktree to create a second copy of the source tree in the repository. $ git worktree add my_worktree $ cd my_worktree/ $ ln -s ../upstream/ . This creates a subdirectory with a copy of all source files, where one can merge the branches without touching the main

[sage-devel] Re: inconsistencies when computing eigenvectors over a number field and over QQbar

Hello Paul, thank you for the report. I can confirm that the problem is still present in the current version of Sage and have opened https://trac.sagemath.org/ticket/30518 for it. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] Re: Generalized eigenvalues with GUPTRI

Thank you for the link. I am a bit surprised I did not find that myself. I have been planning to add something to the release notes and will do so soon. I do not have a legacy trac account yet, but I have just sent a request for one. -- You received this message because you are subscribed to

[sage-devel] Re: Preparser is seriously broken!

I have also noticed this problem. It seems to be caused by the upgrade to IPython 7 https://trac.sagemath.org/ticket/28197. I have opened https://trac.sagemath.org/ticket/30417 for this. Andrey Novoseltsev schrieb am Donnerstag, 20. August 2020 um 23:54:52 UTC+2: > It interferes with multiline

[sage-devel] Re: cd /Documents/course-123/ fails because of preparser

This issue is difficult to solve. A similar problem was discussed in https://trac.sagemath.org/ticket/29391#comment:4. Using `cd` instead of `%cd` is an IPython "feature" called automagic which is not guaranteed to always work – for example, if there is a variable named `cd` in scope. The

[sage-devel] Re: Get source (??) bug

This is not related to the init.sage file, but to the fact that TriangleNumbers is a class. You can reproduce the problem like this sage: class TriangleNumbers: : pass sage: import inspect sage: inspect.getsourcelines(TriangleNumbers) ... TypeError: is a built-in class which is what

Re: [sage-devel] Definite Integral wrong

Even if there are two possible choices, the result of the definite integral should be ±8, not 0. It is rather strange to pick the positive square root for half the integral and then (discontinuously) the negative one for the other half. There is a ticket for exactly this integral, by the way:

Re: [sage-devel] Making executables available to Sage

One example is https://github.com/mwageringel/fgb_sage, which is a small wrapper for an external C binary and which uses sage_sample as a template. The relevant part is the setup.py file, which downloads the external files and makes them available for compiling the Cython code. It does not use

Re: [sage-devel] Re: Wrong matrix of Permutation

Am Dienstag, 16. Juni 2020 13:40:45 UTC+2 schrieb kcrisman: > > > so, "Permutation" objects aren't really meant to be a group: >> > > I think this is the salient point. Is there any documentation that > already has matrix(Permutation(...)) ? > The documentation of Permutation.to_matrix

Re: [sage-devel] Re: Wrong matrix of Permutation

Am Dienstag, 16. Juni 2020 19:03:40 UTC+2 schrieb Nils Bruin: > > That's quite a thread. One thing I'd like to highlight from there that > didn't seem to get so much traction is a point Marco Streng made about > possible notations for right actions: > > If G is a group acting on the right on a

[sage-devel] Re: Bug in category_singleton.__contains__ or in CombinatorialFreeModule

I think the problem here is that enumerating over a disjoint union of an infinite set and a finite set will never reach the elements in the finite set. There is this comment in the documentation of DisjointUnionEnumeratedSets Possible extensions: the current enumeration order is not

Re: [sage-devel] Re: Wrong matrix of Permutation

Am Freitag, 19. Juni 2020 18:40:34 UTC+2 schrieb Nils Bruin: > > All this disappears once we are happy using functions with two parameters > as "action operation": > > left = G.acting_on_the_left_on(M) # or left = M.left_action_by(G) > > left(g,m) > > left = G.acting_on_the_right_on(M) # or left

Re: [sage-devel] Re: Wrong matrix of Permutation

Am 18.06.2020 um 19:47 schrieb Nils Bruin : > > On Thursday, June 18, 2020 at 5:00:00 AM UTC-7, kcrisman wrote: > > I assume that would need a pretty major change in the preparser? Does other > mathematical software use this as a convention? (Just asking, no > presuppositions here.) > >

Re: [sage-devel] Re: Patchbot r640 fails with "disk full"

Yes, I will give that a try. Thanks. By searching through the patchbot logs in reverse, I also found the ticket that was causing the infinite print loop: https://trac.sagemath.org/ticket/19025 . -- You received this message because you are subscribed to

[sage-devel] Re: Patchbot r640 fails with "disk full"

Thank you for the note. I have disabled this patchbot client for now. The problem seems to be that the /tmp directory gets flooded with thousands of little files that do not get removed automatically. It has been less than two weeks since I have last cleared the /tmp directory, and now there

[sage-devel] Re: multi-polynomial subs memory leak

vdelecroix schrieb am Freitag, 7. Mai 2021 um 10:09:59 UTC+2: > I propose to switch to naive symbolic > evaluation. This is infinitely slower but at least does not > leak memory. > Recently, I have looked into performance problems of multivariate power series. One of the bottlenecks is the

Re: [sage-devel] possible bug: kernel of ring homomorphism

Thank you for reporting this problem. I have opened https://trac.sagemath.org/ticket/31367 for it and will provide a fix there shortly. Akos M schrieb am Montag, 8. Februar 2021 um 11:42:59 UTC+1: > It seems that unfortunately the problem persists for multivariate rings as > well: > > A. =

Re: [sage-devel] Re: Vector spaces with immutable vectors by default

Generally, I would be in favor of having an option for immutable vectors by default, as I had similar uses before. Usually, I just convert everything to tuples. However, I am not sure if having an additional flag on the parent is worth the extra burden on maintenance. Already the sparsity flag

[sage-devel] Re: Bug computing kernel of ring homomorphism GCA

Hi Trevor, thank you for reporting this bug. This is indeed a problem, as the implementation is written only with the commutative case in mind. We should make sure that it is called in that case only. As for your proposed fix, I am afraid I am not so familiar with the non-commutative theory

[sage-devel] Parallel docbuild

Currently, the html docs are not built in parallel when running `MAKE='make -j10' make ptestlong`, even when SAGE_NUM_THREADS is set. Is there a way to enable it again? This also limits the throughput of the patchbots. -- You received this message because you are subscribed to the Google

Re: [sage-devel] trouble pushing to a ticket

> > OpenSSH 8.8 (recently stable on Gentoo) disables RSA with SHA-1. You > can work around it, but probably the best long-term solution is to > replace your RSA key with an ECDSA one (ssh-keygen -t ecdsa) and re- > upload it to trac. By the way, the trac server seems to be using an old

[sage-devel] Re: VOTE: move Sage development to Github

+1 for Github David Roe schrieb am Mittwoch, 21. September 2022 um 19:23:36 UTC+2: > Dear Sage developers, > Following extensive discussion, both recently > > (prompted > by issues upgrading the trac server) and over >