Re: [sage-support] Bug/problem evaluating infinite sum

2025-01-16 Thread 'OHappyDay' via sage-support
After contacting the Maxima team it turns out that Maxima indeed can evaluate the inifinite sum (at least a numerical value but not a closed form which probably does not exist) Sage: k=var('k'); sum(log(1-2^-k),k,1,20) results in an error message ending with "Sum is divergent". Maxima: load

Re: [sage-support] Bug/problem evaluating infinite sum

2024-12-12 Thread Emmanuel Charpentier
A bit of exploration in the respective interpreters show that neither Maxima, Sage, Giac, Fricas, Sympy nor Mathematica can give an expression for this sum. Wolfram Alpha gives the numerical answer the OP reported, but I have been unable to get any explanation about the process used ; graphics

Re: [sage-support] Bug/problem evaluating infinite sum

2024-12-10 Thread Nils Bruin
Investigating the error shows that sympy didn't do anything with this sum: 671 try: --> 672 return result._sage_() 673 except AttributeError: 674 raise AttributeError("Unable to convert SymPy result (={}) into" ipdb> p result Sum(log(1 - 1/2**

Re: [sage-support] Bug/problem evaluating infinite sum

2024-12-10 Thread 'OHappyDay' via sage-support
Thanks for investigating. I tried to use sympy this way: sum(log(1-2^-k),k,1,oo,algorithm="sympy") but this failed for other reasons (NotImplementedError: conversion to SageMath is not implemented) wdjo...@gmail.com schrieb am Dienstag, 10. Dezember 2024 um 14:58:49 UTC+1: > On Tue, Dec

Re: [sage-support] Bug/problem evaluating infinite sum

2024-12-10 Thread David Joyner
On Tue, Dec 10, 2024 at 8:43 AM 'OHappyDay' via sage-support < sage-support@googlegroups.com> wrote: > I tried to evaluate the infinite product: > > prod((2^n-1)/2^n) (n=1,oo) > > by converting the product to a sum via logarithm: > > sum(log(1-2^-k),k,1,oo) > > The sum (and thus the product) shoul

[sage-support] Bug/problem evaluating infinite sum

2024-12-10 Thread 'OHappyDay' via sage-support
I tried to evaluate the infinite product: prod((2^n-1)/2^n) (n=1,oo) by converting the product to a sum via logarithm: sum(log(1-2^-k),k,1,oo) The sum (and thus the product) should, according to WolframAlpha, converge with a final value of about -1.24206 This video (https://www.youtube.com/w

Re: [sage-support] Bug?

2024-09-17 Thread 'OHappyDay' via sage-support
For the curious: the Maxima team opened a third bug report: https://sourceforge.net/p/maxima/bugs/4373/ which discusses a possible fix (evaluating conjugate(li[n](x)) does not consider that li[n](x) can also be complex :-( ). OHappyDay schrieb am Montag, 9. September 2024 um 11:13:18 UTC+2:

Re: [sage-support] Bug?

2024-09-09 Thread 'OHappyDay' via sage-support
The Maxima team has opened two bug reports about this issue: incorrect dilogarithm limit in definite integral & incorrect trig substitution: https://sourceforge.net/p/maxima/bugs/4368/ and https://sourceforge.net/p/maxima/bugs/4369 OHappyDay schrieb am Samstag, 7. September 2024 um 17:20:08

Re: [sage-support] Bug?

2024-09-07 Thread 'OHappyDay' via sage-support
I have reported this to the Maxima team. wdjo...@gmail.com schrieb am Donnerstag, 5. September 2024 um 15:19:02 UTC+2: > On Thu, Sep 5, 2024 at 9:16 AM 'OHappyDay' via sage-support < > sage-s...@googlegroups.com> wrote: > >> I recently stumbled upon something that looks like a bug: >> >> Try to

Re: [sage-support] Bug?

2024-09-05 Thread David Joyner
On Thu, Sep 5, 2024 at 9:16 AM 'OHappyDay' via sage-support < sage-support@googlegroups.com> wrote: > I recently stumbled upon something that looks like a bug: > > Try to integrate the following function: > > f(x)=log(1-4*cos(x)+4) > integrate(f,x,0,pi) > > According to the following video ( > htt

[sage-support] Bug?

2024-09-05 Thread 'OHappyDay' via sage-support
I recently stumbled upon something that looks like a bug: Try to integrate the following function: f(x)=log(1-4*cos(x)+4) integrate(f,x,0,pi) According to the following video (https://www.youtube.com/watch?v=nscSDYApAjM) the result should be 2*pi*log(2) But my local Sage as well as online I g

Re: [sage-support] bug in plot?

2024-03-16 Thread kcrisman
I'd think that matplotlib's defaults are defaults for a good reason. Agreed, but not a good *mathematical* reason. It is a good *data analysis* reason (appropriate for mpl), which is not the same thing. I can't think of a single mathematics textbook, talk, or other purely mathematical setti

Re: [sage-support] bug in plot?

2024-03-16 Thread Dima Pasechnik
On Fri, Mar 15, 2024 at 9:44 PM Nils Bruin wrote: > On Friday 15 March 2024 at 12:42:49 UTC-7 kcrisman wrote: > > Or rather, should the default be useoffset False? > > > Yes, I think that would be reasonable to do. Clearly, offsets being used > without the user knowing they exist can easily lead

Re: [sage-support] bug in plot?

2024-03-15 Thread Nils Bruin
On Friday 15 March 2024 at 12:42:49 UTC-7 kcrisman wrote: Or rather, should the default be useoffset False? Yes, I think that would be reasonable to do. Clearly, offsets being used without the user knowing they exist can easily lead to confusion and misinterpreting the graph, as had been demon

Re: [sage-support] bug in plot?

2024-03-15 Thread Dima Pasechnik
On 15 March 2024 19:42:48 GMT, kcrisman wrote: > > >it's not a bug, it's a feature. :-) >https://discourse.matplotlib.org/t/default-format-of-axis-offset-label/23162/2 > > >Correct. > >import matplotlib as mpl >mpl.rcParams['axes.formatter.useoffset'] = False >plot((x^2+0.0001)/(x^2+0.00010

Re: [sage-support] bug in plot?

2024-03-15 Thread kcrisman
it's not a bug, it's a feature. :-) https://discourse.matplotlib.org/t/default-format-of-axis-offset-label/23162/2 Correct. import matplotlib as mpl mpl.rcParams['axes.formatter.useoffset'] = False plot((x^2+0.0001)/(x^2+0.000101), (x,-0.1,0.1)) produces the normal labelling of y-axes, wi

Re: [sage-support] bug in plot?

2024-03-15 Thread Dima Pasechnik
On Fri, Mar 15, 2024 at 9:13 AM David Joyner wrote: > > > On Thu, Mar 14, 2024 at 8:17 PM Dima Pasechnik wrote: > >> >> >> On Fri, Mar 15, 2024 at 12:15 AM Dima Pasechnik >> wrote: >> >>> >>> >>> On Thu, Mar 14, 2024 at 9:32 PM Dima Pasechnik >>> wrote: >>> On 14 March 2024 21:0

Re: [sage-support] bug in plot?

2024-03-15 Thread David Joyner
On Thu, Mar 14, 2024 at 8:17 PM Dima Pasechnik wrote: > > > On Fri, Mar 15, 2024 at 12:15 AM Dima Pasechnik wrote: > >> >> >> On Thu, Mar 14, 2024 at 9:32 PM Dima Pasechnik wrote: >> >>> >>> >>> On 14 March 2024 21:09:22 GMT, Nils Bruin wrote: >>> >I get the impression that without setting ymi

Re: [sage-support] bug in plot?

2024-03-14 Thread Dima Pasechnik
On Fri, Mar 15, 2024 at 12:15 AM Dima Pasechnik wrote: > > > On Thu, Mar 14, 2024 at 9:32 PM Dima Pasechnik wrote: > >> >> >> On 14 March 2024 21:09:22 GMT, Nils Bruin wrote: >> >I get the impression that without setting ymin,ymax you just end up with >> a >> >tiny range for the y-axis and its

Re: [sage-support] bug in plot?

2024-03-14 Thread Dima Pasechnik
On Thu, Mar 14, 2024 at 9:32 PM Dima Pasechnik wrote: > > > On 14 March 2024 21:09:22 GMT, Nils Bruin wrote: > >I get the impression that without setting ymin,ymax you just end up with > a > >tiny range for the y-axis and its labelling is just very weird. I think > the > >labels displayed are sh

Re: [sage-support] bug in plot?

2024-03-14 Thread Dima Pasechnik
On 14 March 2024 21:09:22 GMT, Nils Bruin wrote: >I get the impression that without setting ymin,ymax you just end up with a >tiny range for the y-axis and its labelling is just very weird. I think the >labels displayed are shifted and scaled. So the error is just how the >labels are printed

Re: [sage-support] bug in plot?

2024-03-14 Thread Nils Bruin
I get the impression that without setting ymin,ymax you just end up with a tiny range for the y-axis and its labelling is just very weird. I think the labels displayed are shifted and scaled. So the error is just how the labels are printed. That looks the same as https://github.com/sagemath/sag

Re: [sage-support] bug in plot?

2024-03-14 Thread David Joyner
On Thu, Mar 14, 2024 at 10:35 AM Dima Pasechnik wrote: > It might help seeing your graphs here, too. > It is attached, Dima. Note that the correct graph should be (for all practical purposes) simply the plot of the constant function 1 for all x. [image: bug-in-plot-of-rational-function.jpg]

Re: [sage-support] bug in plot?

2024-03-14 Thread David Joyner
On Thu, Mar 14, 2024 at 1:51 PM kcrisman wrote: > > > On Thursday, March 14, 2024 at 10:35:50 AM UTC-4 dim...@gmail.com wrote: > > It might help seeing your graphs here, too. > > > Try this: > > > https://sagecell.sagemath.org/?z=eJxL06jQVLBV0KiIM9I20DMwMDDU1EfiGBiAhXi5fICKojUq9IEiOgppEIampkJafpF

Re: [sage-support] bug in plot?

2024-03-14 Thread kcrisman
On Thursday, March 14, 2024 at 10:35:50 AM UTC-4 dim...@gmail.com wrote: It might help seeing your graphs here, too. Try this: https://sagecell.sagemath.org/?z=eJxL06jQVLBV0KiIM9I20DMwMDDU1EfiGBiAhXi5fICKojUq9IEiOgppEIampkJafpFChUJmnkJRYl56qoYuWBokFcvLlZNZXBJfkJNfouGjqYAVKCsklabb83IpIynVUajMz

Re: [sage-support] bug in plot?

2024-03-14 Thread Dima Pasechnik
It might help seeing your graphs here, too. On Thu, Mar 14, 2024 at 10:04 AM David Joyner wrote: > Hi: > > I'm trying to show my students a plot of > a rational function whose graph is basically 1, > so I plotted > f(x) = (x^2+0.0001)/(x^2+0.000101) > However, there is a problem: Note the di

[sage-support] bug in plot?

2024-03-14 Thread David Joyner
Hi: I'm trying to show my students a plot of a rational function whose graph is basically 1, so I plotted f(x) = (x^2+0.0001)/(x^2+0.000101) However, there is a problem: Note the difference between plot((x^2+0.0001)/(x^2+0.000101), (x,-10,10)) (which dips down near x=0) and plot((x^2+0.000

[sage-support] Bug in canonical_height for dynamical systems?

2023-06-06 Thread dkrumm
The following few lines lead to a crash in Sage 10.0, with error message "TypeError: Not an element of the order." Is this an error on my part? K. = NumberField(3*x^2 + 1) P. = ProjectiveSpace(K, 1) phi = DynamicalSystem_projective([a*(z^2 + w^2),z*w]) phi.canonical_height(P(a,1)) -- David --

Re: [sage-support] Bug in GAP installation provided by SageMath?

2023-04-18 Thread 'Peter Mueller' via sage-support
Thanks, the following line resolves the issue in Sage 10.0.beta6 (but not in 9.8, but I don't care): `libgap.SetUserPreference("AtlasRep", "AtlasRepAccessRemoteFiles", true )` Dima Pasechnik schrieb am Dienstag, 18. April 2023 um 12:50:49 UTC+2: [...] So you can either go and edit the file abov

Re: [sage-support] Bug in GAP installation provided by SageMath?

2023-04-18 Thread Dima Pasechnik
That's because by default Sage's installation of AtlasRep does not fetch data from the internet: we patch local/lib/gap/pkg/atlasrep/gap/userpref.g so that it says default:= false; The reason is that our release manager runs build tests in an no internet mode, and something breaks without this pat

[sage-support] Bug in GAP installation provided by SageMath?

2023-04-18 Thread 'Peter Mueller' via sage-support
While `libgap.SimpleGroup("J2")` yields the expected result, `libgap.SimpleGroup("J3")` raises a `GAPError: Error, The AtlasRep package could not load a group with parameters [ "J3" ]`. Calling `libgap.LoadPackage("AtlasRep")` returns without errors, but the problem persists. The same happens

Re: [sage-support] bug column_space for IntegerModRing matrices with Sagemath9.6

2023-03-15 Thread Dima Pasechnik
On Wed, Mar 15, 2023 at 8:41 AM Rafael Robles wrote: > > I have encountered the following bug with version 9.6 of SageMath under > Ubuntu. This works perfectly in SageMath 9.1 > > Example: > > A = matrix(IntegerModRing(2) , 2, 2, [1, 0, 1, 1]) > A.column_space() > > -> The kernel appears to have

[sage-support] bug column_space for IntegerModRing matrices with Sagemath9.6

2023-03-15 Thread Rafael Robles
I have encountered the following bug with version 9.6 of SageMath under Ubuntu. This works perfectly in SageMath 9.1 Example: A = matrix(IntegerModRing(2) , 2, 2, [1, 0, 1, 1]) A.column_space() -> The kernel appears to have died. It will restart automatically. -- You received this message b

Re: [sage-support] Bug in qepcad?

2022-07-12 Thread 'Peter Mueller' via sage-support
Dear Dima, thanks for your input. Three additions: (i) I had overlooked that, but in fact one can directly call the qepcad shell within sage by 'qepcad_console()'. (ii) The described error results from the frontend, it apparently misinterprets the result returned by the qepcad backend if it fa

Re: [sage-support] Bug in qepcad?

2022-07-12 Thread Dima Pasechnik
On Mon, Jul 11, 2022 at 8:24 PM 'Peter Mueller' via sage-support wrote: > > OK, calling "sage -sh" and setting "export qe="~/local/sage/local" allows to > start qepcad without relocating files. However, qepcad fails for this rather > small example , telling "Failure occurred in:GCSI (final c

Re: [sage-support] Bug in qepcad?

2022-07-11 Thread 'Peter Mueller' via sage-support
OK, calling "sage -sh" and setting "export qe="~/local/sage/local" allows to start qepcad without relocating files. However, qepcad fails for this rather small example , telling "Failure occurred in:GCSI (final check) Reason for the failure: Too few cells reclaimed." So either (i) qepcad has

Re: [sage-support] Bug in qepcad?

2022-07-11 Thread Dima Pasechnik
On Mon, 11 Jul 2022, 17:04 'Peter Mueller' via sage-support, < sage-support@googlegroups.com> wrote: > Thanks for the suggestion, I wasn't aware of this feature. However, here > it results in "Error HELPFRD: Could not open > ~/local/sage/local/bin/qepcad/share/qepcad/qepcad.help". Unfortunately, t

Re: [sage-support] Bug in qepcad?

2022-07-11 Thread 'Peter Mueller' via sage-support
Thanks for the suggestion, I wasn't aware of this feature. However, here it results in "Error HELPFRD: Could not open ~/local/sage/local/bin/qepcad/share/qepcad/qepcad.help". Unfortunately, the binary of qepcad is the file ~/local/sage/local/bin/qepcad, so I cannot symlink the existing help pag

Re: [sage-support] Bug in qepcad?

2022-07-11 Thread Dima Pasechnik
On Mon, 11 Jul 2022, 16:33 'Peter Mueller' via sage-support, < sage-support@googlegroups.com> wrote: > When running > > var('p1', 'p2', 'p3', 'q1', 'q2', 'q3') > qf = qepcad_formula > # q1 = p1 > l = [p1+q1 == 1, 0 < p1, p1 < 1, > 0 <= p2, p2 <= 1, 0 <= q2, q2 <= 1, > p2 + p1*q1 + q2 ==

[sage-support] Bug in qepcad?

2022-07-11 Thread 'Peter Mueller' via sage-support
When running var('p1', 'p2', 'p3', 'q1', 'q2', 'q3') qf = qepcad_formula # q1 = p1 l = [p1+q1 == 1, 0 < p1, p1 < 1, 0 <= p2, p2 <= 1, 0 <= q2, q2 <= 1, p2 + p1*q1 + q2 == 1, 0 <= p3, p3 <= 1, 0 <= q3, q3 <= 1, p3 + p2*q1 + p1*q2 + q3 == 1] F = qepcad_formula.and_(l) qepcad(F, s

Re: [sage-support] Bug

2022-03-05 Thread Dima Pasechnik
On Fri, Mar 4, 2022 at 6:00 PM Varun Kumar wrote: > > When I'm trying to do practical, we get some bug in sagemath occur that > shown below: > > sage: p=points((n,1/n) for n in range(1,1)) points() is meant to be used for graphics. Are you going to plot 10^8 points? It's much more tha

[sage-support] Bug

2022-03-04 Thread Varun Kumar
When I'm trying to do practical, we get some bug in sagemath occur that shown below: sage: p=points((n,1/n) for n in range(1,1)) sig_error() without sig_on() Unhandled SIGABRT: An abort() occurred. This proba

[sage-support] Bug in integrals

2021-12-15 Thread Juan Luis Varona
See this example: f(x)=(x+sin(3*x))*exp(-3*x*I) g(x)=f(x).expand() integral(f(x)-g(x),(x,0,2*pi)) The answer is I*pi, but it should be 0. Many other examples (related to Fourier coefficients) give similar errors. For instance: f(x)=(x+cos(x))*exp(-x*I) g(x)=f(x).expand() integral(f(x)-g(x),(x,

Re: [sage-support] bug while installing sage from source on macOS Monterey 12.01

2021-12-09 Thread Dima Pasechnik
If you use Homebrew, please don't forget about sourcing our .homebrew-build-env before builds, that's an error most people make, unfortunately. We have to do something about it. On Thu, Dec 9, 2021 at 10:11 AM Dima Pasechnik wrote: > > I presume you use Homebrew - can you install Homebrew'

Re: [sage-support] bug while installing sage from source on macOS Monterey 12.01

2021-12-09 Thread Dima Pasechnik
I presume you use Homebrew - can you install Homebrew's openblas rather than build it? https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/openblas.rb says that M1 is supported. By the way, at the end of ./configure run you'd see messages saying what you can install on your system/distro,

Re: [sage-support] bug while installing sage from source on macOS Monterey 12.01

2021-12-08 Thread Neelima Borade
Thank you Regards Neelima > On Dec 8, 2021, at 4:41 PM, Dima Pasechnik wrote: > > On Thu, Dec 9, 2021 at 12:22 AM Neelima Borade wrote: >> >> okay thank you I'm trying to install it from the source code, so which >> version on here is the development version? > Please see http://mirrors.mit.e

Re: [sage-support] bug while installing sage from source on macOS Monterey 12.01

2021-12-08 Thread Dima Pasechnik
On Thu, Dec 9, 2021 at 12:22 AM Neelima Borade wrote: > > okay thank you I'm trying to install it from the source code, so which > version on here is the development version? Please see http://mirrors.mit.edu/sage/devel/index.html > http://mirrors.mit.edu/sage/src/index.html Alternatively, inst

Re: [sage-support] bug while installing sage from source on macOS Monterey 12.01

2021-12-08 Thread Neelima Borade
okay thank you I'm trying to install it from the source code, so which version on here is the development version? http://mirrors.mit.edu/sage/src/index.html Best regards, Neelima On Wed, Dec 8, 2021 at 4:08 PM Dima Pasechnik wrote: > Sage 9.4 does not work on M1 Macs, you need to use the devel

Re: [sage-support] bug while installing sage from source on macOS Monterey 12.01

2021-12-08 Thread Dima Pasechnik
Sage 9.4 does not work on M1 Macs, you need to use the development version (and I am not 100% sure about the exact status of the support of M1, see https://trac.sagemath.org/ticket/30592) One of the culprits is indeed gpm, one needs gmp 6.2.1 (which is in the current beta) On Thu, Dec 9, 2021 at

[sage-support] bug in rootsystem class?

2021-07-09 Thread Amir-Kian Kashani-Poor
Hi, I'm running SageMath version 9.3, Release Date: 2021-05-09 on Mac OS, but the bug I encountered also occurred on a Windows machine. The code R = RootSystem(['D',4,1]) L = R.weight_lattice(extended = True) R.root_space().positive_real_roots() L.positive_real_roots()[12] leads to a long er

[sage-support] Bug in symbolic integration?

2021-06-15 Thread 'Hendrik Suess' via sage-support
The following two functions f(u)=-u/2+min_symbolic(0,u) + min_symbolic(u,2*u) and g(u)=-u/2+min_symbolic(u, 3*u) are mathematically equivalent, but the following symbolic integrals give different results. F(x)=integral(f(u)*u*exp(x*u),u,-1,1) FF(y)=F(y) G(x)=integral(g(u)*u*exp(x*u),u,-1,

[sage-support] bug ih hom?

2020-12-22 Thread Enrique Artal
I am running sage in Fedora 33, x86_64 sage 9.3beta4 (though the bug appears also in ubuntu sage 9.1). This is a toy example: K=GF(2) V=K^2 B=V.basis() B1=[vector(K,[i,j]) for i,j in [(1,0),(1,1)]] V1=V.subspace_with_basis(B1) I considere a vector space V of dimension 2 over the field of two el

[sage-support] Bug in scalar products of characters coming from restrictions

2020-08-14 Thread 'Peter Mueller' via sage-support
In the code below g1 and g2 are the same group, where g2 is produced as a subgroup of g1, and c is the principal character of g1. Still, when it comes to scalar products, somehow g1 is not considered as a subgroup of itself: sage: g1 = SymmetricGroup(2) : g2 = g1.conjugacy_classes_subgroups

Re: [sage-support] bug in CirculantGraph(10,[2,4])?

2020-06-29 Thread Dima Pasechnik
On Mon, 29 Jun 2020, 18:59 Dima Pasechnik, wrote: > On Mon, Jun 29, 2020 at 6:25 PM David Joyner wrote: > > > > Hi: > > > > In SageMath version 9.1.beta3, I get > > > > sage: Gamma1 = graphs.CirculantGraph(10,[2,4]) > > > > sage: Gamma1.is_connected() > > > > False > > > > > > My understanding i

Re: [sage-support] bug in CirculantGraph(10,[2,4])?

2020-06-29 Thread Dima Pasechnik
On Mon, Jun 29, 2020 at 6:25 PM David Joyner wrote: > > Hi: > > In SageMath version 9.1.beta3, I get > > sage: Gamma1 = graphs.CirculantGraph(10,[2,4]) > > sage: Gamma1.is_connected() > > False > > > My understanding is that all circulant graphs are connected. no, why? e.g. graphs.CirculantGraph(

[sage-support] bug in CirculantGraph(10,[2,4])?

2020-06-29 Thread David Joyner
Hi: In SageMath version 9.1.beta3, I get sage: Gamma1 = graphs.CirculantGraph(*10*,[*2*,*4*]) sage: Gamma1.is_connected() False My understanding is that all circulant graphs are connected. Is this a bug? - David -- You received this message because you are subscribed to the Google Groups

[sage-support] Bug (weird behaviour) of graph6_string/sparse6_string

2019-11-05 Thread Robert Samal
I noticed the following strange behavior of graph6_string()/sparse6_string() functions of graphs: sage: K2=graphs.CompleteGraph(2) sage: P=K2.cartesian_product(K2) sage: print(P.sparse6_string()) sage: print(Graph(P.graph6_string()).sparse6_string()) :CoKN :Cci To explain: I understand, that

[sage-support] Bug in rational_parameterization?

2019-07-05 Thread 'Peter Mueller' via sage-support
A slight modification of the example which documents the use of the method `rational_parameterization' yields a rather long Traceback: A. = AffineSpace(QQ, 2) C = Curve([10*x^2 + 2*y^2 - 3], A) C.rational_parameterization()

[sage-support] bug in simple limit

2019-02-14 Thread lists . gms
Hello. I have found the following bug in limit. ┌┐ │ SageMath version 8.6, Release Date: 2019-01-15 │ │ Using Python 2.7.15. Type "help()" for help. │ └───

[sage-support] BUG report

2018-08-16 Thread Laurent Bakri
Hi all, as indicated in the crash message, I email you the crash report. Cheers, *** IPython post-mortem report {'commit_hash': u'b467d487e', 'commit_source': 'installation', 'default_encoding': 'UTF-8', 'ipython_path':

[sage-support] Bug report: Kernel dies after 1 hour while dividing polynomials

2018-02-09 Thread Patrick Reichert
Paul, thank you very much for the reference to your book. This is a great help for me since I have still a lot of polynomial divisions to perform. -- Patrick Reichert -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this gro

[sage-support] Bug report: Kernel dies after 1 hour while dividing polynomials

2018-02-09 Thread Nicolas M. Thiery
Posting on behalf of Paul Zimmermann: > The workaround is not to create the quotient ring. > It is better to work in polynomial rings and to use the "lift" command > directly in Sage. note that this is discussed in detail in Chapter 9 of the book "Mathematical Computation with SageMath" availab

[sage-support] Bug in graphs.WheelGraph(3).show().

2018-01-10 Thread
sage: graphs.WheelGraph(3).is_isomorphic(graphs.CompleteGraph(3)) True But graphs.WheelGraph(3).show() show(Graph(graphs.WheelGraph(3).edges())) is OK. So I do not kno

Re: [sage-support] Bug in polynomial ring over quotient ring of multivariate polynomial ring?

2017-11-30 Thread Vincent Delecroix
Not really a bug but it is indeed annoying. I provided a fix for this very specific problem https://trac.sagemath.org/ticket/24308 And opened an issue for the more general problem of the fact that quotient rings do not know their characteristic https://trac.sagemath.org/ticket/24309 Vin

[sage-support] Bug in polynomial ring over quotient ring of multivariate polynomial ring?

2017-11-30 Thread 'Peter Mueller' via sage-support
Is it a bug, or is there a reasonable explanation of the following? kk. = GF(2)[] k. = kk.quo(a^2+a+1) K. = k[] for n in [10..32]: print n, (T*y)^n 0 y*T^10 11 (y + 1)*T^11 12 T^12 13 y*T^13 14 (y + 1)*T^14 15 T^15 16 y*T^16 17 (y + 1)*T^17 18 T^18 19 y*T^19 20 (y + 1)*T^20 21

[sage-support] Bug in BooleanFunction: truth_table(format="hex") is wrong

2017-11-23 Thread Paul Leopardi
Hi all, Sometimes, especially with functions of 8 variables, the BooleanFunction.truth_table() method with format='hex" gives wrong values that are the wrong length. I don't yet have a login to Trac. Should I obtain one and report the bug there? All the best, Paul *Bug in BooleanFunction.trut

[sage-support] Bug report.

2017-05-02 Thread Venkataraman S
-- S. Venkataraman -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@

[sage-support] Bug(?) in the division of polynomials with the TermOrder('neglex')

2016-11-17 Thread Sho Takemori
Dear all, I created a polynomial ring with the "neglex" term order and computed the division of polynomials as follows. sage: R. = PolynomialRing(QQ, 1, order=TermOrder('neglex')) sage: (1/2 + a) / (1 + 2 * a) 1/2 + a I expected the result was 1/2. The Sage version is 7.4 and Sage is running on

[sage-support] bug in hyperelliptic curve point counting

2016-10-09 Thread John Cremona
I have not before now used Sage to count points on hyperelliptic curves over finite fields, only elliptic curves. Am I doing something wrong or is this a bug? It certainly looks like a bug. sage: F=GF(23) sage: x=polygen(F) sage: C=HyperellipticCurve(x^8+1) sage: C.cardinality() ... ValueError:

[sage-support] Bug report : function Matrix.set_block() may not work correctly with extension fields

2016-05-23 Thread Guillaume Holler
Hello, I don't know if this is the right place to submit bugs. I have consistently reproduced the following bug: using set_block when matrix space is on a given NumberField or an extension field (at least when there are multiple generators) works as expected the first time (in a sage sessio

[sage-support] Bug in g.character_table()

2016-04-27 Thread 'Peter Mueller' via sage-support
sage: AlternatingGroup(12).character_table() File "", line 2 -zeta35**Integer(27)-zeta35**Integer(29)-zeta35**Integer(33) ^ IndentationError: unexpected indent Looking into the function character_table, there seems to be a problem in converting the Gap cyclotomic integer to Sage cycloto

[sage-support] Bug in integrate

2016-04-26 Thread Laurent Decreusefond
Hi everybody, here is the result of my session on Sage 7.2 beta0 (but I guess the problem is not specific to that version) > sage: var('t') > t > sage: integrate(exp(-2*t)/(1-exp(-2*t)),t) > 1/2*log(e^(-2*t) - 1) What does mean log(-1+e^(-2*t)) since the argument is negative ? -- You receive

[sage-support] bug in numerical evaluation of symbolic expression

2016-04-25 Thread William Stein
For a problem set I'm making today, I made up a random symbolic function, then evaluated it and got confusing/inconsistent behavior. See below: ~$ sage-develop ┌┐ │ SageMath version 7.2.beta5, Release Date: 2016-04-21

[sage-support] Bug in sqrt for QQbar elements

2015-12-29 Thread John Cremona
While working on #18836 I run into this, which is still a problem with 7.0beta1. In summary, I define an element d of QQbar which happens to equal -5 but is constructed by finding a root in QQbar of a polynomial with coefficients in a number field. Then d.sqrt() raises an error, unless I first c

Re: [sage-support] bug in == operator?

2015-07-13 Thread Anton Sherwood
For fun I found the continued fraction expression of the ratio of these two big integers: 1, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2,

Re: [sage-support] bug in == operator?

2015-07-13 Thread Nathann Cohen
>> 2) Why should * sqrt(1/2) belong to SR? Why isn't it >> turned into an algebraic number immediately? If it did, the problem, > > Nils answered 2 already and I agree with Nils. I do not think that he did. The __repr__ function of algebraic numbers is bad indeed, but if we can have this: sa

Re: [sage-support] bug in == operator?

2015-07-13 Thread William Stein
On Monday, July 13, 2015, Nathann Cohen wrote: > > Despite what other people are saying in this thread, I definitely 100% > > consider the above a bug. > > Despite what you say about what other said, I also believe that it is > a bug and that others in this thread agree with you. > > But what abo

Re: [sage-support] bug in == operator?

2015-07-13 Thread Nathann Cohen
> Despite what other people are saying in this thread, I definitely 100% > consider the above a bug. Despite what you say about what other said, I also believe that it is a bug and that others in this thread agree with you. But what about *two* bugs? 1) SR says that two unequal things are equal,

Re: [sage-support] bug in == operator?

2015-07-13 Thread William Stein
On Sun, Jul 12, 2015 at 11:54 PM, David Goldberg wrote: > This is in SageMath Version 6.6, Release Date: 2015-04-14 running on a > MacBook. The following lines print 'equal', even though m and m1 do not > appear equal to me! > > m=540579833922455191419978421211010409605356811833049025*sqrt(1/2) >

Re: [sage-support] bug in == operator?

2015-07-13 Thread Jan Groenewald
Hi They do look equal: sage: m.n() 3.82247666339266e53 sage: m1.n() 3.82247666339266e53 Regards, Jan On 13 July 2015 at 08:54, David Goldberg wrote: > This is in SageMath Version 6.6, Release Date: 2015-04-14 running on a > MacBook. The following lines print 'equal', even though m and m1 do

[sage-support] bug in == operator?

2015-07-13 Thread David Goldberg
This is in SageMath Version 6.6, Release Date: 2015-04-14 running on a MacBook. The following lines print 'equal', even though m and m1 do not appear equal to me! m=540579833922455191419978421211010409605356811833049025*sqrt(1/2) m1=382247666339265723780973363167714496025733124557617743 if m ==

Re: [sage-support] bug: adding a number to matrix

2015-07-12 Thread John Cremona
On 12 July 2015 at 11:57, avi kaur wrote: > Hello > > I figured out that when we add a number to a matrix, It adds this > number to all the elements at diagonal of matrix. for example: > > sage: a > [ 1 2 2 6] > [ 4 6 2 5] > [56 7 4 8] > [ 8 3 9 6] > sage: a + 2 > [ 3 2 2 6] > [ 4

[sage-support] bug: adding a number to matrix

2015-07-12 Thread avi kaur
Hello I figured out that when we add a number to a matrix, It adds this number to all the elements at diagonal of matrix. for example: sage: a [ 1 2 2 6] [ 4 6 2 5] [56 7 4 8] [ 8 3 9 6] sage: a + 2 [ 3 2 2 6] [ 4 8 2 5] [56 7 6 8] [ 8 3 9 8] As you can see in above examp

[sage-support] (Bug?) conjugate ignored by solve()

2015-05-23 Thread gschintgen
Hi, I think I may have found a bug in Sage's solve() function: z=var('z'); solve(conjugate(z)==1+i, z) [z == (I + 1)] It sems that the conjugate is simply ignored. Obviously this leads to incorrect result for (almost) all equations involving the conjugate. Yet, solve()'s docstring simply stat

Re: [sage-support] bug in Graph is_subgraph method

2015-05-02 Thread Vincent Delecroix
If you consider the documentation of the function you will see def is_subgraph(self, other, induced=True): """ Tests whether ``self`` is a subgraph of ``other``. .. WARNING:: Please note that this method does not check whether ``self`` contains a subgraph *isomorphic

[sage-support] bug in Graph is_subgraph method

2015-05-02 Thread Craig E Larson
Graph("E`oo") is the disjoint union of 2 triangles. Graph("ExSW") is two triangles with 2 more edges connecting them. So the first graph is a subgraph (a non-induced subgraph) of the second graph. But Sage reports that it is not. Both graphs have order 6. sage: h=Graph("E`oo") sage: g=Graph("Ex

Re: [sage-support] bug report with Rubik's cube functions

2015-03-19 Thread David Joyner
On Thu, Mar 19, 2015 at 10:43 AM, Pierre wrote: > I agree. Surely in the code one has started with a right action (say) and > has then decided to sometimes convert it to a left action using inverses. > > However, some consistency would be good :-) After all, various pieces of > code seem to disagr

Re: [sage-support] bug report with Rubik's cube functions

2015-03-19 Thread Pierre
I agree. Surely in the code one has started with a right action (say) and has then decided to sometimes convert it to a left action using inverses. However, some consistency would be good :-) After all, various pieces of code seem to disagree on what U is... On Thursday, March 19, 2015 at 3:32:

Re: [sage-support] bug report with Rubik's cube functions

2015-03-19 Thread David Joyner
On Thu, Mar 19, 2015 at 8:07 AM, Pierre wrote: > Hi, > > I have just realized this, and thought it would be helpful to know for > anyone playing with Sage's Rubik's cube abilitites. Here it is: > > While the following 3 commands: > > sage: CubeGroup().move("U") > > and > > sage: CubeGroup().plot3d

[sage-support] bug report with Rubik's cube functions

2015-03-19 Thread Pierre
Hi, I have just realized this, and thought it would be helpful to know for anyone playing with Sage's Rubik's cube abilitites. Here it is: While the following 3 commands: sage: CubeGroup().move("U") and sage: CubeGroup().plot3d_cube("U") and sage: RubiksCube().move("U").show3d() all take t

Re: [sage-support] Bug (?) while making a number field

2015-03-18 Thread Volker Braun
I made http://trac.sagemath.org/ticket/17996 for the missing A.n?? source. On Wednesday, March 18, 2015 at 10:16:29 PM UTC+1, John Cremona wrote: > > OK, so it is not the same as the other Pari recursion bug which was > fixed. I saw the ticket. I have never used the .n() method on > anything,

Re: [sage-support] Bug (?) while making a number field

2015-03-18 Thread John Cremona
OK, so it is not the same as the other Pari recursion bug which was fixed. I saw the ticket. I have never used the .n() method on anything, and when I want to embed a number field K into RR or CC I use K.embeddings(). Otherwise I might have noticed this before. I note that A.?? does *not* show

Re: [sage-support] Bug (?) while making a number field

2015-03-18 Thread kcrisman
> > Still happens with beta5. Do you want to open a ticket? > > Confirmed and see http://trac.sagemath.org/ticket/17985 > ┌┐ > │ Sage Version 6.6.beta5, Release Date: 2015-03-13 │ > │ Type "notebook()" for th

Re: [sage-support] Bug (?) while making a number field

2015-03-18 Thread Volker Braun
On Wednesday, March 18, 2015 at 8:02:55 AM UTC+1, John Cremona wrote: > > That has been fixed in 6.6.beta1, you did not say which version you were > using. > Still happens with beta5. Do you want to open a ticket? ┌┐ │ Sage Ver

Re: [sage-support] Bug (?) while making a number field

2015-03-18 Thread John Cremona
That has been fixed in 6.6.beta1, you did not say which version you were using. John On 18 March 2015 at 04:05, William Stein wrote: > On Tue, Mar 17, 2015 at 7:55 PM, kcrisman wrote: >> I fully accept the following is probably user error due to having not picked >> an embedding of the field. >

Re: [sage-support] Bug (?) while making a number field

2015-03-17 Thread William Stein
On Tue, Mar 17, 2015 at 7:55 PM, kcrisman wrote: > I fully accept the following is probably user error due to having not picked > an embedding of the field. > > sage: GaussianIntegers = NumberField(x^2+1, 'I').ring_of_integers() > sage: A = GaussianIntegers([2,1]) > sage: print A > I + 2 > sage: p

[sage-support] Bug (?) while making a number field

2015-03-17 Thread kcrisman
I fully accept the following is probably user error due to having not picked an embedding of the field. sage: GaussianIntegers = NumberField(x^2+1, 'I').ring_of_integers() sage: A = GaussianIntegers([2,1]) sage: print A I + 2 sage: print A.n() RuntimeError: maximum recursion depth exceeded while

[sage-support] bug report

2015-02-21 Thread William Stein
>From a user: I verified that Sage does what he claims [1]. I guess this is a bug in Maxima really. I'm constantly getting basic calculus bug reports because of SageMathCloud.We don't have a "sage-bugs" list, and even I'm not sure where to send these bug reports... "Hello, I tried this inp

Re: [sage-support] Bug in polynomial GCD (FLINT)

2015-02-17 Thread John Cremona
On 17 February 2015 at 09:06, John Cremona wrote: > Thanks, Anton -- I have forwarded to sage-devel and flint-devel and > we'll try to get this fixed before the release of 6.5. Too late, it was released overnight. > > John Cremona > > On 16 February 2015 at 23:54, Anton Mellit wrote: >> Here is

Re: [sage-support] Bug in polynomial GCD (FLINT)

2015-02-17 Thread John Cremona
Thanks, Anton -- I have forwarded to sage-devel and flint-devel and we'll try to get this fixed before the release of 6.5. John Cremona On 16 February 2015 at 23:54, Anton Mellit wrote: > Here is the code: > R.=QQ[] > X=3*q^12 - 8*q^11 - 24*q^10 - 48*q^9 - 84*q^8 - 92*q^7 - 92*q^6 - 70*q^5 - > 5

  1   2   3   >