When I used *step = 0.095*, I have 64 frames, close enough to the wikipedia
image's
of 66.
But resultant animation is "choppy," where wikipedia's is fairly smooth.
I tinkered with a spline to smooth out a different curve, but it ran
fantastically slow, -- something
about too many points? -- so g
Sameer wrote:
> Hi,
> When I try to compile Sage 2.10.2 under ppc64 Linux using gcc,
> I see that some files are
> compiled in 32 bits and some others in 64 bits. Have you noticed this?
Hi Sameer,
there is several ways to solve the problem:
a) Use a gcc that forces 64 bit output per def
On Tue, Mar 4, 2008 at 8:03 PM, dean moore <[EMAIL PROTECTED]> wrote:
> I'm trying to spline the unit circle. The graph looks like a polynomial,
> not a fit to
> the unit circle.
>
Well, you're going to have some problems using spline since it does a
univariate polynomial spline interpolation. W
I'm trying to spline the unit circle. The graph looks like a polynomial,
not a fit to
the unit circle.
One of my references I screwed up; I meant < http://www.math.zju.edu.cn/yxn/>,
"Curve fitting and fairing using conic splines".
Dean
---
On Tue, Mar 4, 2008 at 8:28 PM, Mike Hansen <[EMAIL PR
Maybe I'm missing something, but what is your question?
--Mike
On Tue, Mar 4, 2008 at 12:00 PM, dean moore <[EMAIL PROTECTED]> wrote:
> Playing with splines for other reasons, I found what I beat down to the
> following snippet (see attached)
>
> v = [] # Will hold point
On Thu, Feb 28, 2008 at 9:36 AM, Kate <[EMAIL PROTECTED]> wrote:
>
> What gives with the following session below?
> More specifically, what happens to the file docstring
> when the file has a .sage extension?
There is a bug in the .sage --> .py conversion process that
your example below illust
Playing with splines for other reasons, I found what I beat down to the
following snippet (see attached)
*v = [] # Will hold points
step = 0.5 # "Fineness" of my approximation
for x in srange(0, 2*pi, step): # Fill parameter *v* with points
v.append
On Tue, Mar 4, 2008 at 1:25 PM, Reckoner <[EMAIL PROTECTED]> wrote:
>
>
> Does SAGE already contain the following package:
>
> http://sourceforge.net/projects/lpsolve
>
> for mixed Integer Linear Programming (MILP) solver lp_solve solves
> pure linear, (mixed) integer/binary, semi-continuous a
Hi,
When I try to compile Sage 2.10.2 under ppc64 Linux using gcc,
I see that some files are
compiled in 32 bits and some others in 64 bits. Have you noticed this?
When I type:
% make
I get the following error:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/PET/src/build/
sage-2.10
Jason: wow, that was quick. I'll try out the plot_vector_field patch
as soon as I figure out how to test patches etc
I ended up using Hector's example and some things from the matplotlib
documentation for my assignment. A notable improvement is using
axis('tight'), which solves the window mis-ali
SAGE includes CVXOPT, which might include it in future releases.
We're in
the process of making simple interfaces to the ILP solvers in GLPK and
MOSEK,
and we have considered lpsolve also. The default solvers in CVXOPT
does
not handle integer constraints.
On Mar 4, 8:25 pm, Reckoner <[EMAIL PROT
Does SAGE already contain the following package:
http://sourceforge.net/projects/lpsolve
for mixed Integer Linear Programming (MILP) solver lp_solve solves
pure linear, (mixed) integer/binary, semi-continuous and special
ordered sets (SOS) models.
If not, will it? Are there already alternative
Here is a snippet of code from cython.py in the main tree
(SAGE_ROOT/devel/sage/sage/misc/cython.py)
def cython(filename, verbose=False, compile_message=False,
use_cache=False, create_local_c_file=False, annotate=True,
sage_namespace=True):
if not filename.endswith('pyx'):
OK, thanks. I am happy to report I downloaded the source successfully
using "wget" and compiled it in about 5 hours (AMD Athlon XP1800 - 1.5
GHz)
Chris
On Mar 3, 3:10 pm, "Carlo Hamalainen" <[EMAIL PROTECTED]>
wrote:
> On Mon, Mar 3, 2008 at 8:01 PM, Chris S. <[EMAIL PROTECTED]> wrote:
>
> As Wi
Thanks for the matplotlib recipe! I just had the same problem with
plot_vector_field not accepting coordinate functions of two arguments.
I went ahead and created an issue:
http://trac.sagemath.org/sage_trac/ticket/2381
- Eric
On Feb 17, 10:19 am, "Hector Villafuerte" <[EMAIL PROTECTED]> wrote:
15 matches
Mail list logo
