I've been playing around with learning blender, with the idea of
animating some 4-D projection/rotations of polytopes into 3D. But all
I really want is a nice compressed animation/movie format, and it
seems like there should be a lighter-weight way to do that. If I come
up with anything
2008/9/1 mabshoff [EMAIL PROTECTED]:
Hi,
this is a followup to the above thread. Mike Hansen wrote a doctest
for gp.py and we hit the following problem:
sage -t devel/sage/sage/interfaces/gp.py
**
File
On Monday 01 September 2008, mabshoff wrote:
On Aug 31, 4:33 pm, Martin Albrecht [EMAIL PROTECTED]
wrote:
On Sunday 31 August 2008, John Cremona wrote:
SNIP
Hi there, that means that I screwed up 32-bit compatibility. I'll look
into it tomorrow.
This is now #4027.
Note that on OSX
On Sep 1, 11:05 am, root [EMAIL PROTECTED] wrote:
It would seem that ray tracing should be a fully parallel task.
Yes, it is, but multicore isn't the issue I think. Images can be split
up into smaller rectangles (i.e. rendering a single image by 4 cores
in parallel by splitting it into a 2x2
One possible source of confusion here is that pari's (and gp's)
precision parameters refer to numbers of decimal digits, while Sage's
(as in RealField(prec)) refer to bits. The first is about 0.301 times
the second, i.e. log_10(2). Moreover, pari only increases its
precision in steps of between
Thanks Vincent for the information. One reason I am choosing not to
use povray is the license, which I believe is not compatible with
inclusion in Sage.
Btw, the tachyon raytracer does seem to have good multicore support dy
default. Unfortunately it cannot animate. I wish we had someone who
I also find it frustrating that both prec and precision are used
as standard parameter names for either scale of precision all over the
place. It would be nice to standardise this. And in addition, I
propose a convention that we only use prec or precision to denote
bit precisions, and use
