Thanks all.
On Jul 23, 10:06 pm, William Stein <wst...@gmail.com> wrote:
> Do you know about Python's "try/except" construction? Does the above
> raise a RuntimeError? Maybe you can do something sort of like:
No, it doesn't crash in the same way that it would if, say, I tried to
evaluate "1/0", which I think is what you're talking about. It simply
displays the "Axiom Crashed..." message exactly as if I'd done a print
() statement, and seems to keep running (green bar on the left),
though nothing actually happens. After I Interrupt, Axiom is working,
but all variables are cleared.
I know only the basics of Python at the moment, and learn parts of it
on an as-needed basis. That's how I learn programming languages best.
On Jul 24, 12:20 am, Bill Page <bill.p...@newsynthesis.org> wrote:
> I am very interested in your use of Axiom in Sage. I was beginning to
> think I was the only one doing this sort of thing. :-(
To be honest, this is the first time I've used Axiom. It was the only
CAS I could find that can do the calculations I needed. It seems like
an extremely powerful and useful system, though the 17,000+ page
reference manual is a bit intimidating. Plus as a stubborn windows
user, it annoys me that there's not a tidy way to run it in Windows
except through Sage. ;)
> I have been running a slightly modified version of your code (modified
> for compatibility with an older version of Sage 3.2 and Mike Hansen's
> patches for Axiom) on a fairly fast processor for more than 3 hours.
> Output from a 'print a,b,c' debugging statement currently shows:
...
> -8 2 2
Is that the last output you got before you posted? Mine gets a
litttle farther than that in 90 minutes, though I'm sure hundreds of
extra print statements are slowing yours down as well. I only have a
cheap Dell desktop.
> I realize that you are more interested in a work-a-round than in
> finding the cause of the problem but as both a Sage user and an Axiom
> developer I am motivated to look into this problem a little further.
Well that would be nice, too.
> By running "on Windows Vista", I presume that you mean you are running
> Sage (and FriCAS) on a virtual machine under Windows. Can you be more
> precise about exactly what versions you are running? What Sage source
> code or binary file did you download and build or install? How did you
> install Fricas 1.0.3? Was it built using clisp or ecl? How much memory
> is allocated for the virtual machine?
Yes, I just downloaded the sage-vmware-4.0.1.zip file from
sagemath.org, installed VMWare Player (2.5.2 build-156735), and opened
sage_vmx.vmx. I would've either installed fricas simply through an
install_package('fricas-1.0.3.p0') command in the Firefox session, or
with a sage -i -fricas-1.0.3.p0 from the command line.
As for the last two questions, I don't even know how to check, but I
didn't mess with anything, so things should still be set at the
defaults..
On Jul 24, 3:36 am, Martin Rubey <martin.ru...@math.uni-hannover.de>
wrote:
> If you are running longer jobs with fricas, you should consider
> switching to a faster lisp implementation. For FriCAS, clisp is
> aboutthe slowest.
Well, the speed it runs at now is servicable for me at this point.
I'm a bit Linux-illiterate, so I think it would probably take me more
time to figure out how to upgrade than I'd save.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
