Dear Michael,
just a short recap, whether I have understood things correctly:
the problem you currently face with external symbolic calculus is that the
representation of the objects is not identical in SAGE and in the external
progam (Maxima).
you are using something called
[this email will likely bounce somewhere, so if it doesn't show up in
some place please forward]
Martin Rubey wrote:
Dear Michael,
Hi Martin,
just a short recap, whether I have understood things correctly:
the problem you currently face with external symbolic calculus is that the
[Note: If you are interested in announcements only please subscribe to
sage-announce. It is limited to roughly one email every ten days.]
Hello folks,
Sage 3.0 has been released on April 21st, 2008. It is available at
http://sagemath.org/download.html
* About Sage
Hello folks,
since 3.0 is out the inevitable happens: 3.0.1 is next release. We
would like to do a mostly bug fix release, but that somehow depends on
how buggy 3.0 is. So far the issues with the notebook seems to be only
big issues reported so far.
I did talk to Robert in IRC earlier today and
On my Gentoo box I unpacked the subject tarball, changed to the sage
directory and did a make with the results:
gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2)
RHOMES= []
DEBUG= True
Setting RHOMES
On Wed, Apr 23, 2008 at 4:28 AM, Michael.Abshoff wrote:
Martin Rubey wrote:
I do not see how the problem of differing representations can be
resolved. Up to now I thought that Sage simply doesn't have an
internal representation, and just uses the one from the external
program -
The install.log file is at
http://daly.axiom-developer.org/install.log
This fails on fedora 5
[EMAIL PROTECTED] sage-3.0]# uname -a
Linux localhost.localdomain 2.6.18-1.2239.fc5 #1 Fri Nov 10 13:04:06 EST 2006
i686 i686 i386 GNU/Linux
You have new mail in /var/spool/mail/root
[EMAIL
On Wed, Apr 23, 2008 at 9:46 AM, [EMAIL PROTECTED] wrote:
The install.log file is at
http://daly.axiom-developer.org/install.log
This fails with internal compiler error:
'__pyx_pf_4sage_7modules_18real_double_vector_28RealDoubleVectorSpaceElement___init__':
What problems are you having? Beamer and SageTeX are largely orthogonal,
but there are some tricky bits with verbatim environments
When I add a sageblock in a frame, e.g.,
\begin{sageblock}
var('x')
f = log(sin(x)/x)
\end{sageblock}
I get the error message
Runaway argument?
! Paragraph
Are their binaries for OS X 10.4?
On Apr 23, 2008, at 4:58 AM, mabshoff wrote:
[Note: If you are interested in announcements only please subscribe to
sage-announce. It is limited to roughly one email every ten days.]
Hello folks,
Sage 3.0 has been released on April 21st, 2008. It is
On Wed, Apr 23, 2008 at 10:03 AM, Robert Bradshaw
[EMAIL PROTECTED] wrote:
Are their binaries for OS X 10.4?
NO. And there won't be until somebody volunteers to make them. See
my long email about this a few minutes ago in Sage-support.
Can you make them?
On Apr 23, 2008, at 4:58 AM,
On Apr 23, 2008, at 10:06 AM, William Stein wrote:
On Wed, Apr 23, 2008 at 10:03 AM, Robert Bradshaw
[EMAIL PROTECTED] wrote:
Are their binaries for OS X 10.4?
NO. And there won't be until somebody volunteers to make them. See
my long email about this a few minutes ago in Sage-support.
I have a MAC OX X 10.4.4 build in process.
Its on a PowerPC (G4)
I'll make it available when it completes.
Tim
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
No doubt the sage system is a bit too ad hoc. However, this is something
that will be fixed in the symbolics rewrite. While externally it will
maintain most backwards compatibility, internally it will be vastly
different (for example, elements (including variables) in the symbolic
ring (which is
Dear all,
I've posted on trac the current version of my posets code.
There is still much to be done, some algorithms need
to be improved and others need to be implemented. (There
are no NotImplementedErrors.)
http://trac.sagemath.org/sage_trac/ticket/2519
But before I continue working, I'd
On Wed, Apr 23, 2008 at 1:48 PM, Gary Furnish wrote:
...
Right now, most functionality of the sage.calculus module is dictated
strictly by how maxima is designed. As we move to our own internal
representation, this obviously will not be sufficient.
It is not immediately obvious to me that
2008/4/23 Waldek Hebisch wrote:
...
For FriCAS in longer run dropping Lisp is likely -- most Lisp code
is machine generated during FriCAS build. With enough effort we
could directly generate C code. Currently effort to drop Lisp would
be prohibitive, but the FriCAS code is constanly
On Apr 23, 1:08 pm, Robert Bradshaw [EMAIL PROTECTED]
wrote:
Are their binaries for OS X 10.4?
NO. And there won't be until somebody volunteers to make them.
Can you make them?
Yes, do I just build and do sage -bdist?
I attempted to compile sage 3.0 on my Mac G5 running OS X 10.4.10,
There's a serious inefficiency in the construction of finite fields
GF(2^n) in Sage at the moment.
For n=15 these are constructed of type
sage.rings.finite_field_givaro.FiniteField_givaro, about which I have
nothing to say now; for n=16 they have type
On Apr 23, 4:52 pm, strogdon [EMAIL PROTECTED] wrote:
Hi,
On my Gentoo box I unpacked the subject tarball, changed to the sage
directory and did a make with the results:
gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2)
On Apr 23, 1:08 pm, Bill Page [EMAIL PROTECTED] wrote:
Perhaps you have other ideas about how to achieve this kind of
interoperability? I could imagine for example linking Python directly
into the Aldor C run-time system or maybe linking the Python into the
lisp image that runs Axiom?
There
On Apr 23, 9:23 pm, mark mcclure [EMAIL PROTECTED] wrote:
On Apr 23, 1:08 pm, Robert Bradshaw [EMAIL PROTECTED]
wrote:
Are their binaries for OS X 10.4?
NO. And there won't be until somebody volunteers to make them.
Can you make them?
Yes, do I just build and do sage -bdist?
Hi Mark!
I'm not sure what the problem is, probably William Stein or Michael
Abshoff will be able to answer that, but maybe its simplest to just
upgrade your gcc with the latest stuff from apple. My gcc is build
5465; I'm not sure how they pick those version numbers.
I know you are (or were?)
We might want to think about the naming conventions for Lattice. As
with all words in mathematics, this one has multiple meanings. A
lattice can be a poset with a meet and a join, or it can be a free
abelian group with an inner product. Normally I wouldn't bring such a
thing up, but I'm working
Gary,
If you're interested in exploring Axiom's type system
the best source of material available is the Jenk's book.
It would be useful if Sage's type hierarchy was close to
the one Axiom uses, making it possible to share algorithms.
If you'll mail me a postal address (offline),
I'll send you
Hi All,
Perhaps someone can help me figure this out. I am trying to create an
elementary abelian subgroup of a symmetric group and then look at its
normalizer. Here's what doesn't work:
s6 = SymmetricGroup(6)
c1 = s6([(1,2)])
c2 = s6([(3,4)])
c3 = s6([(5,6)])
e8 =
Michael,
Yes I do have R installed on my system. No, RHOMES is not set;
however, R_HOMES is set to /usr/lib64/R. Apparently, the R
installation does this. And yes I do have the install.log. The
specific test fails as:
sage -t devel/sage/sage/stats/test.py
On Apr 23, 3:54 pm, mhampton [EMAIL PROTECTED] wrote:
I'm not sure what the problem is, probably William Stein or Michael
Abshoff will be able to answer that, but maybe its simplest to just
upgrade your gcc with the latest stuff from apple. My gcc is build
5465; I'm not sure how they pick
On Apr 23, 6:10 pm, mabshoff [EMAIL PROTECTED]
dortmund.de wrote:
for whatever reason there is no Singular in your build log. Right at
the top it says:
...
Could you check if spkg/standard contains any file called
singular-3-0-4-2-20080405.p1.spkg, i.e:
No, there's not. Strangely, there's
AFAIK, the normalizer of a group is not yet implemented.
If you type
sage: s6.normalizer?
you'll see the synax for that command. My guess is that normalizer_of_group
would be an easy function to implement (and I can do that if no one
else wants to).
On Wed, Apr 23, 2008 at 4:06 PM, Hy Ginsberg
sage -t devel/sage/sage/modular/abvar/morphism.py *** ***
Error: TIMED
OUT! *** ***
*** *** Error: TIMED OUT! *** ***
[1358.6 s]
[...]
Odd, it shouldn't time out on that machine. I am hoping William or
Craig can take a close look since they are much more familiar
On Apr 24, 2:22 am, mark mcclure [EMAIL PROTECTED] wrote:
On Apr 23, 6:24 pm, mark mcclure [EMAIL PROTECTED] wrote:
SNIP
Hi Mark,
make; followed by sage -ba seems to have done the trick. Everything
seems to be working great and ./sage -testall passed all tests.
I've got a working G5
Dan Drake wrote:
On Wed, 23 Apr 2008 at 01:25PM -0700, John H Palmieri wrote:
This is exactly why die-hard Python people say don't use backslashes to
continue statements:
http://docs.python.org/dev/howto/doanddont.html#using-backslash-to-continue-statements
Perhaps we should link to the
Have you copied the image?
Can I remove it?
Tim
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
On Wed, 23 Apr 2008 at 09:45PM -0400, Alex Ghitza wrote:
Dan Drake wrote:
On Wed, 23 Apr 2008 at 01:25PM -0700, John H Palmieri wrote:
This is exactly why die-hard Python people say don't use backslashes to
continue statements:
My Mac box is generally idle except when I'm doing the every-other-month
Axiom release. If you need images I can build them for OSX 10.4
Tim
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group,
Hello!
I've run some Sage labs using the notebook here at UVM and two things
have come up.
(1) At the end of class, I asked my students to print out their work
and turn it in. I stopped this almost immediately, since the
printouts are hugely wasteful: blank pages, things overrun the
margins,
On Wed, 23 Apr 2008 at 01:25PM -0700, John H Palmieri wrote:
This is exactly why die-hard Python people say don't use backslashes to
continue statements:
http://docs.python.org/dev/howto/doanddont.html#using-backslash-to-continue-statements
Perhaps we should link to the above guide in
On Wed, Apr 23, 2008 at 8:29 PM, John Voight [EMAIL PROTECTED] wrote:
Hello!
I've run some Sage labs using the notebook here at UVM and two things
have come up.
(1) At the end of class, I asked my students to print out their work
and turn it in. I stopped this almost immediately,
On Apr 23, 12:08 pm, Bill Page [EMAIL PROTECTED] wrote:
...
Both you and Gaby have discussed the possibility of defining an
abstract machine (aka. run-time system) to replace the role that Lisp
plays for Axiom. We also know that Aldor has already defined such a
machine called FOAM. FOAM can
On Wed, Apr 23, 2008 at 1:42 PM, Franco Saliola [EMAIL PROTECTED] wrote:
On Wed, Apr 23, 2008 at 4:05 PM, Robert Miller [EMAIL PROTECTED] wrote:
We might want to think about the naming conventions for Lattice. As
with all words in mathematics, this one has multiple meanings. A
On Apr 24, 1:54 am, Bjake Hammersholt Roune [EMAIL PROTECTED]
wrote:
Hi Bjake,
It just now occured to me that this might be due to counting wall-time
instead of CPU-time, since I put the machine to sleep during a lecture
while it was running the tests.
Ok, that explains it. On OSX time
42 matches
Mail list logo