On 4/23/13 10:54 PM, Gordon wrote:
On Tuesday, 23 April 2013 00:00:33 UTC+8, Volker Braun wrote:
The first question is, are you actually running out of ram? The
garbage collector seems to have triggered full collections at the
4gb mark, and memory fragmentation might have left you
On Tuesday, 23 April 2013 00:00:33 UTC+8, Volker Braun wrote:
>
> The first question is, are you actually running out of ram? The garbage
> collector seems to have triggered full collections at the 4gb mark, and
> memory fragmentation might have left you with 900mb of address space that
> is m
Kenneth Lin writes:
> Hey Sage,
>
> So I'm trying to make a really long function that I wanted to put on
> multiple lines to look nice. However, Sage's backslash preprocessing,
> combined with the preprocessing of making functions, doesn't allow me
> to do this:
>
> sage: botrk(h0_prime, a0, s0,
Yep, it might have switched to another internal library because of the
matrix size, and that library might have appeared incompatible with debian
(may be to new glibc version or like that) or just broken.
It could be interesting to try to reinstall from sources with system ATLAS.
I tried by ldd t
On 2013-04-23, Lorenzo Ricciardi wrote:
> Basically, I've been performing various matrix operations, with
> symbolic elements.
> The final result is very complex, but I can see patterns within it,
> so i wanted to rename those patterns with new variable names. That
> way, I can express the final
With "backend='ppl', base_ring=QQ" it works!
Thanks again ;)
Am Dienstag, 23. April 2013 14:10:26 UTC+2 schrieb Volker Braun:
>
> This is now http://trac.sagemath.org/14479 (needs review)
>
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
T
>
>
> The 3D plot handling has never been very good; it's harder to work with
> PNG files from TeX than vector formats such as EPS or PDF. And with so
> many options for the graphics commands, it's hard to come up with
> defaults that will make users happy while still allowing some people to
>
On Tue, 23 Apr 2013 at 02:15PM +0400, LRN wrote:
> If you typeset it (i'm using XeLaTeX and SageTeX), you'll see that png
> files are upscaled (badly, i might add). Turns out - they lack DPI
> information. If you typeset it (completely, with XeLaTex+Sage+XeLaTeX
> dance) once, then open up the png
> This is now http://trac.sagemath.org/14479 (needs review)
I love your style ! :-D
It says "Welcome in the world of Sage, where no known bug makes it past the
day" :-D
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscri
Hi all,
this is my first post on thins group :)
I've been searching for a solution to this problem but I didn't find any (yet).
Basically, I've been performing various matrix operations, with symbolic
elements.
The final result is very complex, but I can see patterns within it, so i wanted
to r
This is now http://trac.sagemath.org/14479 (needs review)
--
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
I can confirm this. The problem is that cdd errors out with "*Error:
Numerical inconsistency is found. Use the GMP exact arithmetic.". Gee,
thanks ;)
On Tuesday, April 23, 2013 9:09:08 AM UTC+1, Felix Wellen wrote:
>
> while trying to render the intersection of a 4-cube and a 3-cube (I guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've attached a sample tex file.
If you typeset it (i'm using XeLaTeX and SageTeX), you'll see that png
files are upscaled (badly, i might add). Turns out - they lack DPI
information. If you typeset it (completely, with XeLaTex+Sage+XeLaTeX
dance) onc
On 04/21/2013 09:50 AM, Kenneth Lin wrote:
Hi Sage,
I'm not sure if it's that I'm not doing this right, but I have this
function that has a ceiling in it. I defined it like so:
|
botrk(h0_prime,a0,s0,c0)=h0_prime /ceil(log(20*(a0 +25)/(h0_prime
+20*(a0 +25)),0.95))*(s0 +0.4)*(1+c0)
|
But it wo
Hey Sage,
So I'm trying to make a really long function that I wanted to put on
multiple lines to look nice. However, Sage's backslash preprocessing,
combined with the preprocessing of making functions, doesn't allow me to do
this:
sage: botrk(h0_prime, a0, s0, c0) = h0_prime / ceil(log(20 * (a
Hi Sage,
I'm not sure if it's that I'm not doing this right, but I have this
function that has a ceiling in it. I defined it like so:
botrk(h0_prime, a0, s0, c0) = h0_prime / ceil(log(20 * (a0 + 25) / (h0_prime
+ 20 * (a0 + 25)), 0.95)) * (s0 + 0.4) * (1 + c0)
But it won't do approximations of
Hi,
while trying to render the intersection of a 4-cube and a 3-cube (I guess
that really doesn't matter), I stopped on trouble with the following:
sage: point_list = [[0.132, -1.028, 0.028],[0.5, 0.5, -1.5],[-0.5, 1.5,
-0.5],[0.5, 0.5, 0.5],[1.5, -0.5, -0.5],[-0.332, -0.332, -0.668],[-1.332,
17 matches
Mail list logo
