On Friday, November 8, 2013 1:24:33 PM UTC-8, Nils Bruin wrote:
>
> I think what you are experiencing can be characterized as a "bug".
> Hopefully someone can fix it or find a work-around.
>
In fact, I've just tried the same scenario on bsd.math.washington.edu,
which runs Darwin (so I guess OSX).
On Fri, 08 Nov 2013 at 01:41PM -0800, kcrisman wrote:
> Dan, I'm on a train with horrible internet - can you open a ticket, post to
> the Maxima list, etc.? Thanks!
This is now http://trac.sagemath.org/ticket/15386.
Dan
--
--- Dan Drake
- www.math.wisc.edu/~ddrake/
---
signature.
Another interesting data point - in Maxima itself:
(%i6) display2d:false;
(%o6) false
(%i7) limit(-(3*n^2 + 1)*(-1)^n/sqrt(n^5 + 8*n^3 + 8),n,inf);
(%o7) -38*und*log(-1)^2/25
But in Sage
sage: log(-1)
I*pi
which presumably leads to this.
Dan, I'm on a train with horrible internet - can you o
On Fri, 08 Nov 2013 at 01:03PM -0800, kcrisman wrote:
> Note the "und" - undefined. Maxima is probably noticing the (-1)^n piece...
I'm not sure it's the (-1)^n. I tried using cos(pi*n) instead and still
get "und":
sage: n = var('n')
sage: assume(n>0)
sage: series = -(3*n^2 + 1)*cos(pi*n)/sqrt(n
OK, I've tried to replicate your scenario and for me it works (on linux),
so it might be something about OSX. I think what you are experiencing can
be characterized as a "bug". Hopefully someone can fix it or find a
work-around. For reference, this is what I get:
$ pwd
/home/nbruin/U
$ ls -dl e
Looks like you are correct. When i took the absolute value of "series", it
gave me the correct answer. (Although absolute value doesn't work 100% of
the time.)
I'm currently doing (limit((series^2).simplify_full(), n=infinity))
It serves its purpose for now since I only want to know if the limit
On Friday, November 8, 2013 2:21:26 PM UTC-5, PavelY wrote:
>
> I am trying to compute a limit with sage, and I get incorrect answers.
>
> Here is an example which should produce the result of 0 but does not.
>
> reset()
> n = var('n')
>
> assume(n>0)
> series = -(3*n^2 + 1)*(-1)^n/sqrt(n^5 + 8
On Friday, November 8, 2013 9:53:06 AM UTC-7, Nils Bruin wrote:
> Hm, would you mind posting the results of:
>
> $pwd
>
> and then the permissions of all components, e.g.: if it's /home/user/sage
>
> $ ls -dl /home
> $ ls -dl /home/user
> $ ls -dl /home/user/sage
> $ ls -dl /home/user/sage/example
Dear all,
May I quickly share that I am currently referring to a course on Financial
time series & Markov Models by our none other than Prof. William Stein at:
http://wstein.org/wiki/2008(2f)simuw.html
and just wanted to share that I am facing issues in uploading worksheets to
SAGE encountering f
I am trying to compute a limit with sage, and I get incorrect answers.
Here is an example which should produce the result of 0 but does not.
reset()
n = var('n')
assume(n>0)
series = -(3*n^2 + 1)*(-1)^n/sqrt(n^5 + 8*n^3 + 8)
working_series = -(7*n^2 + 8)*(-1)^n/sqrt(n^5 + 4*n^2 + 2)
print "Li
On 8 November 2013 16:11, Georgi Guninski wrote:
> I am not an expert, but is it normal to get negative canonical
> height of a point on elliptic curve over number field?
No, this is certainly an error. There is at least one outstanding
patch relating to heights over number fields (#13951) but a
(I've did a little search on this but couldn't found the solution.)
How to use SR.wild(0) when "abs" is present in an expression ?
Thanks.
Pedro
EXAMPLE 1 (with abs)
t=var('t')
w0 = SR.wild(0)
e1 = abs(cos(t))^2; print e1
print e1.subs( abs(w0)^2 == w0 )
abs(cos(t))^2
abs(cos(t))#abs shou
On Friday, November 8, 2013 6:56:54 AM UTC-8, scma...@gmail.com wrote:
>
> That makes sense, but it didn't work for me:
>
> $ umask 002
> $ umask
> 0002
> $ sage -t example_script.py
> Traceback (most recent call last):
> ...
> RuntimeError: refusing to run doctests from the current directory
> '
I am not an expert, but is it normal to get negative canonical
height of a point on elliptic curve over number field?
sage: Z1.=ZZ[];Nf.=NumberField(Z**16-2);E=EllipticCurve(Nf,[-87, 504,
-40320, 0, 0]);P=E(0,0)
sage: P.height() #not very fast
-0.150688795814905
sage: P.height(precision=2000)
-0.
That makes sense, but it didn't work for me:
$ umask 002
$ umask
0002
$ sage -t example_script.py
Traceback (most recent call last):
...
RuntimeError: refusing to run doctests from the current directory
'/DIR1/DIR2' since untrusted users could put files in this directory,
making it unsafe to ru
On 2013-11-08 12:37, Dima Pasechnik wrote:
It might be that they want a platform-agnostic fix.
That's not the issue at all.
--
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
On 2013-11-08, Jeroen Demeyer wrote:
> On 2013-11-08 09:29, Nils Bruin wrote:
>> Do we have this documented anywhere?
> No. The place to document this would of course by Python. I personally
> find it very unfortunate that upstream CPython seems to ignore this
> issue. Perhaps my fix isn't perfe
On 2013-11-08 09:29, Nils Bruin wrote:
Do we have this documented anywhere?
No. The place to document this would of course by Python. I personally
find it very unfortunate that upstream CPython seems to ignore this
issue. Perhaps my fix isn't perfect (as shown by this thread), but not
doing an
On Thursday, November 7, 2013 11:20:53 PM UTC-8, Jeroen Demeyer wrote:
>
> On 2013-11-07 19:37, Nils Bruin wrote:
> > I can confirm that I also am not able to get "sage --python" to run
> > without printing a warning in any situation I tried where the current
> > directory is group writeable.
>
19 matches
Mail list logo