[sage-support] Re: BUG report

2018-08-16 Thread Dima Pasechnik
On Friday, August 17, 2018 at 1:48:30 AM UTC+3, Laurent Bakri wrote: > > Hi all, > as indicated in the crash message, I email you the crash report. > we need to know how you installed Sage, and something about your OS (what Linux distribution and what version it is). > > Cheers, > *

[sage-support] Re: Bug report-Sage

2018-02-13 Thread slelievre
PS: Found using the following trac query: https://trac.sagemath.org/query?order=id&desc=1&summary=~abs(sin -- 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-

[sage-support] Re: Bug report-Sage

2018-02-13 Thread slelievre
Sun 2018-02-11 21:55:14 UTC, Andrey Novoseltsev: > > I got this bug report and it seems that I have seen something similar > in the past but can't find it. Is it already known/tracked? > > show(integral(abs(sin(pi*x)), x, 0, 1)) > plot(abs(sin(pi*x)), 0, 1) > > The value of the integral is incorrec

[sage-support] Re: Bug report-Sage

2018-02-12 Thread Ralf Stephan
It's the pattern sqrt(f(x)) with f containing trigonometric functions. Use giac for such integrals. sage: integral(abs(sin(pi*x)), x, 0, 1, algorithm='giac') 2/pi There is no meta ticket for this, you can find integration tickets at https://trac.sagemath.org/wiki/symbolics#Integrationtickets I

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

2018-02-07 Thread Patrick Reichert
I will close this "error report thread" here, since I got a perfect answer at https://ask.sagemath.org/question/40935/bug-report-kernel-dies-after-1-hour-while-dividing-polynomials/ The workaround is not to create the quotient ring. It is better to work in polynomial rings and to use the "lift"

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

2018-02-07 Thread Patrick Reichert
Nils, thank you very much for your answer. (1) You are right when you say that the division of polynomials can't always be done in ideals. In my special case I deal with meromorphic functions on the general elliptic curve with 17-torsion point P=(0,0) and basepoint O and know the divisors of all

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

2018-02-06 Thread Nils Bruin
On Monday, February 5, 2018 at 9:11:44 AM UTC, Patrick Reichert wrote: > > I want to submit an *error report* for SAGE 7.0 and 8.0: > > The division of two polynomials in an ideal causes an *kernel death* > after one hour of computation. > Singular performs the calculation in about *one second*. >

[sage-support] Re: Bug report.

2017-05-02 Thread slelievre
The relevant line is ImportError: libgfortran.so.3: cannot open shared object file: No such file or directory You need to install libgfortran. For this, run this command in a terminal: sudo apt-get install libgfortran -- You received this message because you are subscribed to the Goog

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

2016-05-23 Thread Nils Bruin
On Monday, May 23, 2016 at 9:22:35 AM UTC-7, Guillaume Holler wrote: > > I don't know if this is the right place to submit bugs. > It's a reasonable place to start. > I have consistently reproduced the following bug: > I have tried and was unable to reproduce your results on 7.2. Can you give

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

2015-03-19 Thread Pierre
I have just realized that CubeGroup().faces("U") also goes counterclockwise ! what a mess ! On Thursday, March 19, 2015 at 1:07:12 PM UTC+1, 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. H

Re: [sage-support] Re: bug report

2015-02-21 Thread William Stein
On Feb 21, 2015 1:48 PM, "kcrisman" wrote: >> >> >> 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... >> > > Sage-support seems reasonable to me. Unless we have a way to m

[sage-support] Re: bug report

2015-02-21 Thread kcrisman
> > > 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... > > Sage-support seems reasonable to me. Unless we have a way to make it easier to use Trac (no reg process), but

[sage-support] Re: bug report

2015-02-21 Thread William Stein
On Sat, Feb 21, 2015 at 11:42 AM, William Stein wrote: > From a user: > > I verified that Sage does what he claims [1]. I guess this is a bug > in Maxima really. Follow-up: One can also get a different incorrect answer using algorithm='sympy' sage: limit(csc(x),x=0, algorithm='sympy') +Infi

[sage-support] Re: Bug report - solve([sin(cos(x))/cos(x)==0],x) gives wrong result

2014-06-30 Thread kcrisman
On Friday, June 27, 2014 5:26:36 PM UTC-4, Christoph Jentzsch wrote: > > Hi there, > > solve([sin(cos(x))/cos(x)==0],x) gives: > > [x == 1/2*pi] > which is wrong. There is no solution. > > Thanks for reporting this. > > See plot(sin(cos(x))/cos(x),(-pi,pi)) > > > Well, in any case solve is