On Dec 22, 2007 1:16 PM, William Stein <[EMAIL PROTECTED]> wrote:
> Did you first run the VMware vmshrink utility, then turn the vmware
> machine off and exit vmware before creating the 7z file? Also,
> how big is your vmware-sage-deluxe when uncompressed?
vmshrink gives the result "disk compre
Hi:
Suppose you follow the instructions in the programming
manual to edit one of the latex doc files, such as prog,tex,
const.tex, tut.tex, etc.
http://www.sagemath.org/doc/html/prog/node31.html
Roughly, the steps are
sage: hg_doc.pull()
(edit the file, say devel/doc/prog.tex)
sage: hg_doc.comm
On Dec 27, 9:57 pm, "Mike Hansen" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The reason why the symbolic stuff in Sage is slow is that it uses a
> psuedo-tty interface to talk to Maxima. There is a lot of overhead
> with this due to waiting, synchronization, parsing the string output,
> etc. One
Hello,
The reason why the symbolic stuff in Sage is slow is that it uses a
psuedo-tty interface to talk to Maxima. There is a lot of overhead
with this due to waiting, synchronization, parsing the string output,
etc. One way to get the symbolic stuff to be faster is to make using
Sympy since i
I'm having problems doing symbolic computations in Sage. Calls to
rational_simplify() seem to take about .2 seconds each. Working
directly in Maxima is about 100 times faster. Mathematica is
something like 500 times faster.
In Sage, where does the time go? Is there something I can do right
no
On Dec 27, 4:39 pm, "Kate Minola" <[EMAIL PROTECTED]> wrote:
Hi Kate,
> When I build sage-2.9.1.1 from source on the architectures
> of interest to me, I get an error when building
>
> mpfi-1.3.4-cvs20071125.p2
>
> gcc -fPIC -o test_mpfi test_mpfi.o ../src/.libs/libmpfi.a
> /home/kate/sa
When I build sage-2.9.1.1 from source on the architectures
of interest to me, I get an error when building
mpfi-1.3.4-cvs20071125.p2
gcc -fPIC -o test_mpfi test_mpfi.o ../src/.libs/libmpfi.a
/home/kate/sage/sage-2.9.1.1-x86_64-Linux/local/lib/libmpfr.a -lgmp
../src/.libs/libmpfi.a(mpfi_io.
On Dec 27, 2007 12:45 AM, William Stein <[EMAIL PROTECTED]> wrote:
> On Dec 26, 2007 10:19 PM, David Joyner <[EMAIL PROTECTED]> wrote:
>
> > I'm thinking of adding matplotlib and jmol to the history and completely
> > rewriting the graphics section. Thoughts?
>
> Yes, please do. Definitely add
Added to trac 1544.
Will be fixed in next version of tutorial.
On Dec 8, 2007 5:12 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> -- Forwarded message --
> From: Haydn Huntley
> Date: Dec 8, 2007 2:00 PM
> Subject: I just finished reading through tut.pdf...
> To: [EMAIL PROTECT
I am working today and tomorrow on fixing all your typos and
possibly adding a few more examples to the tutorial.
Thanks very much for your reports.
++
On Dec 17, 2007 12:23 PM, bill purvis <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I'm looking at the Sage Tutorial, file node3
Hi,
I got the error in subject while trying the new ECM().one_curve() command
in sage-2.9. The problem might be due to the fact that I perform thousands of
calls to ECM().one_curve(), and maybe pexpect does not correctly frees pty
devices.
The problem can be reproduced with:
$ sage < in5
Hello Kiran,
On Mon, 17 Dec 2007 08:05:29 -0800 (PST)
mabshoff <[EMAIL PROTECTED]> wrote:
> On Dec 17, 2:37 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> > I tried sage -upgrade on my 64-bit RHEL5 box (Opteron 246), and the
> > upgrade dies pretty definitively at PolyBoRi. As far as I ca
> Sorry sage is so hard to use! What can we learn from the above?
> The main problem is acsc versus arccsc, which caused confusion.
> Should we change the names of the "arc" functions to arc* instead of a*?
>
> Maple: uses arcsin:
> sage: maple.eval('arcsin(1)')
> '1/2*Pi'
> sage: maple.eval('as
Thanks for the help so far. I've been able to make some minor changes
to the code
and checked the behaviour. I'm still a bit stuck on how it all ties
together. I have added
a new routine to the C++ code, but so far I've been unable to trace
how the existing
code is invoked from the Python code. I'
On Dec 18, 2007 7:36 AM, kcrisman <[EMAIL PROTECTED]> wrote:
>
> Thanks - this was very helpful. The SAGE programming guide could use
> the exact examples above pasted in, perhaps in a 2.1.1 or 4.3.1.1
> "Testing reminders for novice programmers" - it makes it clear that
> the importing has to ha
15 matches
Mail list logo
