> Notes:
>
> ## cremona.spkg ##
>
> Added copy command in spkg-install for
>
> qrank/mwrank
> qrank/tmrank
> qrank/ratpoint
> qcurves/findinf
> qcurves/tate
> qcurves/conductor
> qcurves/torsion
> qcurves/twist
> qcurves/allisog
> qcurves/indep
> procs/tconic
Is this supposed to be a list
PS I reopened trac 1403 to add a second patch since the original one
fixes mwrank only while the new one fixes the same termination
behaviour for the other executables in qcurves/*
John
On 06/12/2007, John Cremona <[EMAIL PROTECTED]> wrote:
> > Notes:
> >
> > ## cremona.spkg ##
> >
> > A
Wow, this pacakge is HUGE. I didn't realize it was this large. I hope
by cutting out extraneous stuff (docs, examples) we can make this much
smaller.
Marshall: if you (or anyone) want to build this on a mac
use this spkg-install
http://sage.math.washington.edu/home/jkantor/spkgs/spkg-install.w
Joshua Kantor wrote:
> Wow, this pacakge is HUGE. I didn't realize it was this large. I hope
> by cutting out extraneous stuff (docs, examples) we can make this much
> smaller.
>
Hi,
I copied the wxPython directory with the demos demos to a local file just
to test the install.
There is a demofi
Actually, don't use the spkg-install I posted. It seems to work but
near the end of the compile there are some weird missing symbols
problems on OSX.
I need to play around a bit more, I'll post again when I have it
actually working on OSX.
Josh
On Dec 6, 2:53 am, Joshua Kantor <[EMAIL PROTECTE
Hi,
I decided to try out Macaulay2 for some of the things that I've been
struggling with through singular. Unfortunately, the spkg install fails for
me with details in the P.S. The crucial bit seems to be
***
/bin/sh: etags: command not found
***
A little bit of google rewards me with the kn
Joel B. Mohler wrote:
> Hi,
>
> I decided to try out Macaulay2 for some of the things that I've been
> struggling with through singular. Unfortunately, the spkg install fails for
> me with details in the P.S. The crucial bit seems to be
> ***
> /bin/sh: etags: command not found
> ***
> A littl
On Dec 6, 10:09 am, "John Cremona" <[EMAIL PROTECTED]> wrote:
> PS I reopened trac 1403 to add a second patch since the original one
> fixes mwrank only while the new one fixes the same termination
> behaviour for the other executables in qcurves/*
Excellent. I just applied your patch. I am als
Someone noted in ticket 1346 that the fpLLL doctests use random data,
and said that we should do tests with fixed data which return a known
result.
I don't agree with this. There is no reason why LLL should return the
same result from implementation to implementation. fpLLL may well
change the la
Hi,
The patch trac1366.patch posted here:
http://trac.sagemath.org/sage_trac/ticket/1366
by Bobby Moretti (with help from me and Carl Witty)
uses caching to make it so typing "sage -b" or "sage -br"
is faster. It needs more testing.
For me on OSX.
BEFORE (but after doing "sage -b" many ti
On Dec 5, 2007 8:01 PM, William Stein <[EMAIL PROTECTED]> wrote:
> On Dec 5, 2007 4:17 PM, Robert Miller <[EMAIL PROTECTED]> wrote:
> >
> > Does anyone have any thoughts on the following? Luke Wolcott showed me
> > this example- the traceback looks suspect, but I don't know about the
> > internals
On Dec 6, 2007 4:27 AM, Joel B. Mohler <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I decided to try out Macaulay2 for some of the things that I've been
> struggling with through singular. Unfortunately, the spkg install fails for
> me with details in the P.S. The crucial bit seems to be
Just another
Hi there,
some quick idea such that Sage dominates our lives even more:
1. We should have "Doc Days" (*) in addition to "Bug Days". For these sessions
we would focus on (a) finding new bugs by (b) writing doctests. Also our Wiki
might need some care and the manuals always need updates.
2. Als
I think this would be great. Do recursive dependencies get caught now? They
didn't 6 months ago. For example, if I have a .pxd included (cimported,
whatever) in another .pxd which is included in a .pyx: i.e.
a.pxd -> b.pxd -> c.pxd -> c.pyx
then modifications of a.pxd should trigger c.pyx to
On Dec 6, 2007 7:49 AM, Joel B. Mohler <[EMAIL PROTECTED]> wrote:
>
> I think this would be great. Do recursive dependencies get caught now? They
> didn't 6 months ago. For example, if I have a .pxd included (cimported,
> whatever) in another .pxd which is included in a .pyx: i.e.
> a.pxd -> b
On Dec 5, 2007 8:01 PM, William Stein <[EMAIL PROTECTED]> wrote:
> On Dec 5, 2007 4:17 PM, Robert Miller <[EMAIL PROTECTED]> wrote:
> >
> > Does anyone have any thoughts on the following? Luke Wolcott showed me
> > this example- the traceback looks suspect, but I don't know about the
> > internals
Doc Days/Evenings/Whatever are a great idea.
One specific suggestion: the documentation for plotting should be
streamlined, more advanced examples given, and the plot and show
commands need better docstrings.
Cheers,
Marshall Hampton
On Dec 6, 9:40 am, Martin Albrecht <[EMAIL PROTECTED]>
wrote:
> 2. Also, a "Busfactor/Code-Review Day" might be a good idea. There are areas
> in the Sage codebase where basically only one developer feels comfortable
> poking around. This is usually not because of scary math only one person
> cares about but because nobody else every sat down and read the co
intimations of mortalityI wonder why I have been spending time
documenting the code in cremona.spkg recently, perhaps it is something
to do with crossing the road in front of Bristol buses frequently
these days.
Perhaps every file of code should have some lines (just after the
GPL?) bequeath
> If you don't mind, I have two sage/graphics questions. First, how do you
> animate tachyon objects? If I have a list L of t.cylinder()'s and I do
> sage: a = animate(L)
The problem here is that T.cylinder() returns a "Tachyon" object
instead of a "Graphics" object.
sage: type(L[0])
Wh
Yeah, I would be much more inclined to spend hours writing doctests
if I knew there were like ten other people doing so at the same time.
david
On Dec 6, 2007, at 10:40 AM, Martin Albrecht wrote:
>
> Hi there,
>
> some quick idea such that Sage dominates our lives even more:
>
> 1. We should
On Thu, Dec 06, 2007 at 04:47:25AM -0800, mabshoff wrote:
> Chances are it won't work anyway. You should go over to the google
> group Macaulay2 and read the top topic. Get somebody over there to fix
> the issue of library detection and I will create a M2 spkg from latest
> svn. Working on the old
Hello folks,
I finally upgraded FLINT to 1.0. I have compile tested it on Solaris
9, OSX 10.5 and Linux x86-64 and doctests pass. You can download it
from
http://sage.math.washington.edu/home/mabshoff/flint-1.0.spkg
Please touch devel/sage-main/sage/libs/flint/fmpz_poly.pyx and do a
"sage -b",
Joel B. Mohler wrote:
> On Thu, Dec 06, 2007 at 04:47:25AM -0800, mabshoff wrote:
>> Chances are it won't work anyway. You should go over to the google
>> group Macaulay2 and read the top topic. Get somebody over there to fix
>> the issue of library detection and I will create a M2 spkg from lates
Hello,
The clisp update didn't work out due to a known issue with
gcc 4.2.3 with Debian testing on x86. So I reverted back
to clisp-2.41.p11.spkg. There was some fallout from the
updated cremona.spkg, but now it should work out of the
box. FLINT was updated to 1.0. Until the final release
I plan
Okay, two things:
1) I would love to get some feedback from Linux/Itanium with this
since we have an open ticket for that.
2) The test suite failed on Solaris 9/Sparc in 32 bit mode. I ran it
three times and it was always the same failure:
Testing _fmpz_poly_max_bits1()... FAIL!
At least one
I just read the UWeek article about SAGE and am wondering about
how complete the matlab-style functionality is. I'd really like to
ask
some people to try their matlab code on it if possible. The shared
workbooks would also be a big plus.
I am a Sr Computer Specialist for a research group here at
On 12/6/07, mabshoff wrote:
>
> The clisp update didn't work out due to a known issue with
> gcc 4.2.3 with Debian testing on x86. So I reverted back
> to clisp-2.41.p11.spkg.
:-(
Michael, do you mean that this is a problem known to the clisp
developers? If so do you know if they have developed
On Dec 6, 11:36 pm, "Bill Page" <[EMAIL PROTECTED]> wrote:
> On 12/6/07, mabshoff wrote:
>
> > The clisp update didn't work out due to a known issue with
> > gcc 4.2.3 with Debian testing on x86. So I reverted back
> > to clisp-2.41.p11.spkg.
>
> :-(
>
> Michael, do you mean that this is a probl
You hopefully mean uint64_t, not u_int64_t. There should be no
occurrences of u_int64_t left in FLINT. If that's not the case, please
let me know.
Also, if uint32_t is not available in 32 bit mode, your compiler is
either not c99 compliant or the machine does not have both a native 32
bit type an
On Dec 6, 2007 3:32 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I just read the UWeek article about SAGE and am wondering about
> how complete the matlab-style functionality is. I'd really like to
> ask
> some people to try their matlab code on it if possible. The shared
> workbooks woul
Hi,
an interesting project to know about, related to SAGE notebook, is Crunchy:
http://code.google.com/p/crunchy/
http://crunchy.sourceforge.net/
especially watch the screencast in there:
http://showmedo.com/videos/video?name=143&fromSeriesID=143
I tried that half a year ago and it was qu
Hi,
in case you don't know about the Google Highly Open Participation
Contest (GHOP), read this:
http://code.google.com/opensource/ghop/2007-8/
There are plenty of tasks in SAGE that could be handled by high school
students (any thoughts on that Timothy?).
The SAGE notebook has a lot of things
On Dec 6, 2007 3:26 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> an interesting project to know about, related to SAGE notebook, is
> Crunchy:
>
> http://code.google.com/p/crunchy/
> http://crunchy.sourceforge.net/
>
> especially watch the screencast in there:
>
> http://showmedo.com/v
On Dec 6, 2007 3:52 PM, alex clemesha <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 6, 2007 3:26 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > an interesting project to know about, related to SAGE notebook, is
> Crunchy:
> >
> > http://code.google.com/p/crunchy/
> > http://crunchy.s
On Dec 6, 2007 3:18 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> in case you don't know about the Google Highly Open Participation
> Contest (GHOP), read this:
>
> http://code.google.com/opensource/ghop/2007-8/
>
> There are plenty of tasks in SAGE that could be handled by high school
> I just tried downloading it, starting it by just immediately doing
> sage -python crunchy.py
> in the unzip directory, and it is an interactive Python tutorial.
> However, if you type something that results in an infinite loop
> into there i/o boxes you'll just freeze the whole server. You
It looks to me like a short is 16 bits and a long is 32 bits on
SPARC32. But even finding documentation online which gives this
information is difficult.
Bill.
On 6 Dec, 23:02, Bill Hart <[EMAIL PROTECTED]> wrote:
> You hopefully mean uint64_t, not u_int64_t. There should be no
> occurrences of
> I'm not sure how Sage could participate, since it's not one of the
> list of software projects Google chose (Google chose what they
> viewed as the best of the Google Summer of Code projects).
>
> The only possible way I could think of for Sage to be involved would
> be to go here:
>
>
> ht
On Dec 6, 12:43 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> Please touch devel/sage-main/sage/libs/flint/fmpz_poly.pyx and do a
> "sage -b", otherwise the flint doctests will fail. The spkg runs the
> FLINT test suite per default, so please report success as well as
> failures here, toge
I can't help with SPM, but I can give some advice on
some of the MATLAB toolbox equivalents.
On Dec 6, 2007, at 5:32 PM, [EMAIL PROTECTED] wrote:
>
> FYI, the matlab toolboxes we have installed are:
>
> Image_Toolbox
>
I recommend looking at PIL. I don't think it is part of
Sage, but it is pyt
>
> SAGE brought fair amount of people to Python, right? So I think it's
> perfectly suitable for PSF.
I forgot to mention that Crunchy is also involved in that, so SAGE
notebook can be too.
I mentioned SAGE notebook to Crunchy in May already.
http://groups.google.com/group/crunchy-discuss/bro
On 12/6/07, mabshoff wrote:
> ...
> You might want to let Sam & Bruno know that we are counting on
> them :)
>
Right. Thanks!
> What we can do is offer clisp-2.43.spkg as experimental, so
> that people who want to install FriCAS or OpenAxiom can
> install it and cross their fingers that it works
On Dec 7, 4:07 am, Carl Witty <[EMAIL PROTECTED]> wrote:
> On Dec 6, 12:43 pm, mabshoff <[EMAIL PROTECTED]
>
> dortmund.de> wrote:
> > Please touch devel/sage-main/sage/libs/flint/fmpz_poly.pyx and do a
> > "sage -b", otherwise the flint doctests will fail. The spkg runs the
> > FLINT test suite
On Dec 7, 12:02 am, Bill Hart <[EMAIL PROTECTED]> wrote:
> You hopefully mean uint64_t, not u_int64_t. There should be no
> occurrences of u_int64_t left in FLINT. If that's not the case, please
> let me know.
[EMAIL PROTECTED] flint-1.0$ grep -r u_int64_t *
src/long_extras.c:static u_int64
I would be interested in helping with a PDE toolbox. I didn't want to
work on it alone as I'm pretty sure I'd make some stupid design
choices. It would be nice to start some work on PDE functionality in
SAGE.
On Dec 6, 6:40 pm, Tim Lahey <[EMAIL PROTECTED]> wrote:
> I can't help with SPM, but I c
On Dec 6, 2007 10:50 PM, Joshua Kantor <[EMAIL PROTECTED]> wrote:
>
> I would be interested in helping with a PDE toolbox. I didn't want to
> work on it alone as I'm pretty sure I'd make some stupid design
> choices. It would be nice to start some work on PDE functionality in
> SAGE.
[...]
> > >
On Dec 7, 3:24 am, "Bill Page" <[EMAIL PROTECTED]> wrote:
> On 12/6/07, mabshoff wrote:
> > ...
Bill,
> > You might want to let Sam & Bruno know that we are counting on
> > them :)
>
> Right. Thanks!
>
> > What we can do is offer clisp-2.43.spkg as experimental, so
> > that people who want to
48 matches
Mail list logo
