[sage-support] Strange mpmath result in $\sum_{ n 0} \pi^n$
Perhaps someone should forward this upstream.
$\sum_{ n 0} \pi^n$ certainly diverges though
mpmath claims it equals -pi/(pi-1)
sage: import mpmath
sage: mpmath.mp.pretty=True;mpmath.mp.dps=40
sage: r1=mpmath.nsum(lambda n: mpmath.pi**n,[ 1, mpmath.inf])
sage: r1
-1.466942206924259859983394813233667573143
sage:
sage: r2=-mpmath.pi/(mpmath.pi - 1)
sage: r1-r2
0.0
sage: r3=mpmath.nsum(lambda n: mpmath.mpf('2')**n,[ 1, mpmath.inf]);r3
-2.0
Computing zeta(2) appears OK:
sage: z2=mpmath.nsum(lambda n: 1/n**2,[ 1, mpmath.inf]);z2
1.644934066848226436472415166646025189219
sage: z2 - mpmath.zeta(2)
0.0
--
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/groups/opt_out.
[sage-support] Re: Please elaborate on the difference between the two OS X binaries for Sage 6.0.
I'd also like to know what the expectations for the OSX binaries are. Why are there two separate ones to start with? Should I change something in how they are built? On Sunday, January 19, 2014 10:25:45 AM UTC, Geoff Oxberry wrote: According to the download website ( http://boxen.math.washington.edu/home/sagemath/sage-mirror/osx/intel/index.html), the main difference between the two binaries is that one is geared towards Unix-style CLI use on OS X, and the other is meant to be a clickable Mac-style binary. The README in both disk images reflects this distinction. However, having downloaded both disk images, I don't see a sage folder in the Unix-style CLI disk image. I only see the README, and Sage.app (technically a folder, but not named sage), so the first-level directory layout looks the same, and double-clicking on Sage.app from the Unix-style CLI disk image starts Sage without having to resort to any of the additional steps for launching Sage from the README. Obviously, the two disk images are different; they have different checksums, and different file sizes. Could someone explain the differences in a little more detail? -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
[sage-support] Re: Sage cell server has no result
Hi Jason,
I redo http://ufrmeca.univ-lyon1.fr/~buffat/sagecell.html
and i found out I have an error after ../sage -sh -c make -B
if git submodule status | grep -q ^[+-]; then git submodule update --init
/dev/null; fi
python -c import urllib;
urllib.urlretrieve('http://code.jquery.com/jquery-2.0.3.min.js',
'static/jquery.min.js')
r.js -o static/require/main.js
appDir=/home/sshuser/sage2/ipython/IPython/html/static/
make: r.js: Command not found
Do you know what causing this problem?
Yi Juin Tan
--
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/groups/opt_out.
[sage-support] Re: Sage cell server has no result
On 1/20/14, 12:36, y tan wrote:
Hi Jason,
I redo http://ufrmeca.univ-lyon1.fr/~buffat/sagecell.html
and i found out I have an error after ../sage -sh -c make -B
if git submodule status | grep -q ^[+-]; then git submodule update
--init /dev/null; fi
python -c import urllib;
urllib.urlretrieve('http://code.jquery.com/jquery-2.0.3.min.js',
'static/jquery.min.js')
r.js -o static/require/main.js
appDir=/home/sshuser/sage2/ipython/IPython/html/static/
make: r.js: Command not found
You'll need to install requirejs in the system. I do this on CentOS here:
https://github.com/sagemath/sagecell/blob/master/contrib/vm/install-sagecell-functions#L165
(I also installed nodejs before elsewhere.)
Thanks,
Jason
--
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@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/groups/opt_out.
[sage-support] Re: [sage-devel] Re: Please elaborate on the difference between the two OS X binaries for Sage 6.0.
There are supposed to be two versions–one with the app and the other without. The reason for the non-app version is so that those users who don’t want to use the app can more easily access the sage folder. In an ideal world there would be one version that contains the app, and also the sage directory at the top level. But this would double the size of the download unless the sage directory was a hard link to the one embedded in the app. Hard linking is technically possible but would be tricky to implement and brittle since there are no public apis for it. Using a soft link/alias won’t work nicely since copying it will copy the link instead of the directory linked to. So that’s the background. As for how to build them, it should be a matter of setting the environment variable SAGE_APP_BUNDLE=yes vs. setting it to anything else (or leaving it unset). -Ivan On Jan 20, 2014, at 7:12 AM, Volker Braun vbraun.n...@gmail.com wrote: I'd also like to know what the expectations for the OSX binaries are. Why are there two separate ones to start with? Should I change something in how they are built? On Sunday, January 19, 2014 10:25:45 AM UTC, Geoff Oxberry wrote: According to the download website (http://boxen.math.washington. edu/home/sagemath/sage-mirror/osx/intel/index.html), the main difference between the two binaries is that one is geared towards Unix-style CLI use on OS X, and the other is meant to be a clickable Mac-style binary. The README in both disk images reflects this distinction. However, having downloaded both disk images, I don't see a sage folder in the Unix-style CLI disk image. I only see the README, and Sage.app (technically a folder, but not named sage), so the first-level directory layout looks the same, and double-clicking on Sage.app from the Unix-style CLI disk image starts Sage without having to resort to any of the additional steps for launching Sage from the README. Obviously, the two disk images are different; they have different checksums, and different file sizes. Could someone explain the differences in a little more detail? -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
[sage-support] Re: [sage-devel] Re: Please elaborate on the difference between the two OS X binaries for Sage 6.0.
Ok, I think I fixed it on the buildbot. Is it possible to have a second directory next to the Contents subdir in the app bundle, for example: Sage.app/Contents Sage.app/sage-6.1 Imho that would still be less confusing than having two different dmg's. If anybody thinks about refactoring the sage-bdist script, please replace the environment variables SAGE_APP_BUNDLE and SAGE_APP_DMG with command line arguments ;-) On Monday, January 20, 2014 7:17:03 PM UTC, Ivan Andrus wrote: There are supposed to be two versions–one with the app and the other without. The reason for the non-app version is so that those users who don’t want to use the app can more easily access the sage folder. In an ideal world there would be one version that contains the app, and also the sage directory at the top level. But this would double the size of the download unless the sage directory was a hard link to the one embedded in the app. Hard linking is technically possible but would be tricky to implement and brittle since there are no public apis for it. Using a soft link/alias won’t work nicely since copying it will copy the link instead of the directory linked to. So that’s the background. As for how to build them, it should be a matter of setting the environment variable SAGE_APP_BUNDLE=yes vs. setting it to anything else (or leaving it unset). -Ivan On Jan 20, 2014, at 7:12 AM, Volker Braun vbrau...@gmail.comjavascript: wrote: I'd also like to know what the expectations for the OSX binaries are. Why are there two separate ones to start with? Should I change something in how they are built? On Sunday, January 19, 2014 10:25:45 AM UTC, Geoff Oxberry wrote: According to the download website (http://boxen.math.washington. edu/home/sagemath/sage-mirror/osx/intel/index.html), the main difference between the two binaries is that one is geared towards Unix-style CLI use on OS X, and the other is meant to be a clickable Mac-style binary. The README in both disk images reflects this distinction. However, having downloaded both disk images, I don't see a sage folder in the Unix-style CLI disk image. I only see the README, and Sage.app (technically a folder, but not named sage), so the first-level directory layout looks the same, and double-clicking on Sage.app from the Unix-style CLI disk image starts Sage without having to resort to any of the additional steps for launching Sage from the README. Obviously, the two disk images are different; they have different checksums, and different file sizes. Could someone explain the differences in a little more detail? -- 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@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/groups/opt_out.
