So sage built, but it may or may not work. And you're building it on
another machine, but it may or not build. What was the point of
this post?
Thanks for clarifying. So apparently you feel David should have
waited to post something (hopefully!) like: "Sage built on Solaris
SPARC and doct
On 03/17/2010 11:52 PM, Nick Alexander wrote:
On 17-Mar-10, at 10:21 PM, Jason Grout wrote:
On 03/17/2010 06:41 PM, Dr. David Kirkby wrote:
What do you consider a Solaris-only issue? When a problem occurs with a
particular release only on Solaris? If that is not put on sage-devel,
you might
On Wed, Mar 17, 2010 at 10:47 PM, Nick Alexander wrote:
> At the time I worked with this code, which was several months ago, there was
> no public interface for crawling the structures. Testing for whether one
> was looking at a sage value (meaning something with a parent) versus a
> function app
On 17-Mar-10, at 10:41 PM, Dima Pasechnik wrote:
William,
While I think that posts here on a particular part of functionality
(e.g. Solaris port) *continuing to work after an
update* should not happen here, only posts on particular parts of
functionality *ceasing to work* should be welcome (D
On 17-Mar-10, at 10:21 PM, Jason Grout wrote:
On 03/17/2010 06:41 PM, Dr. David Kirkby wrote:
What do you consider a Solaris-only issue? When a problem occurs
with a
particular release only on Solaris? If that is not put on sage-devel,
you might as well say goodbye to keeping Sage building
Hello my name is Leonardo Parada, soon will be acoustic enginner. I am
interested in Hidden Markov models for acoustics pattern recognition!
2010/3/18 William Stein
> On Wed, Mar 17, 2010 at 10:25 PM, Jason Grout
> wrote:
> > On 03/17/2010 10:38 PM, William Stein wrote:
> >>
> >> Hi,
> >>
> >>
On 17-Mar-10, at 10:12 PM, Jason Grout wrote:
On 03/17/2010 11:40 AM, Nick Alexander wrote:
On 17-Mar-10, at 10:18 AM, Mike Hansen wrote:
On Wed, Mar 17, 2010 at 5:21 AM, Pablo Angulo
wrote:
Sorry to come back to this (two weeks) old topic, but what do you
think
about raising an exceptio
William,
While I think that posts here on a particular part of functionality
(e.g. Solaris port) *continuing to work after an
update* should not happen here, only posts on particular parts of
functionality *ceasing to work* should be welcome (Dave, please take
the note),
(while such posts would s
Minh and William,
Thank you very much and sorry that I didn't read about the
prerequisites before upgrading.
After installing gfortran (I did it system-wide, so setting
SAGE_FORTRAN and SAGE_FORTRAN_LIB was not necessary), everything was
going smooth.
The installation,building, and tuning took s
On Wed, Mar 17, 2010 at 10:25 PM, Jason Grout
wrote:
> On 03/17/2010 10:38 PM, William Stein wrote:
>>
>> Hi,
>>
>> I'm curious if anybody reading this uses the Hidden Markov Models
>> (HMM) code in Sage for anything. If so, send me an email, since I'm
>> working on 100% replacing it by some bran
On 03/17/2010 10:38 PM, William Stein wrote:
Hi,
I'm curious if anybody reading this uses the Hidden Markov Models
(HMM) code in Sage for anything. If so, send me an email, since I'm
working on 100% replacing it by some brand new better quality code.
In case you don't know, HMM's are a tool in
2010/3/18 kstueve :
> Does anyone have information on the maximum size of an array of
> doubles in C? I seem to be getting abnormal results using elements
> past the first 1e6. What is the standard way to deal with very large
> (millions to billions of elements) arrays of data in C?
> Kevin Stuev
On 03/17/2010 06:41 PM, Dr. David Kirkby wrote:
What do you consider a Solaris-only issue? When a problem occurs with a
particular release only on Solaris? If that is not put on sage-devel,
you might as well say goodbye to keeping Sage building on Solaris.
William,
Can you point out a post o
On 03/17/2010 11:40 AM, Nick Alexander wrote:
On 17-Mar-10, at 10:18 AM, Mike Hansen wrote:
On Wed, Mar 17, 2010 at 5:21 AM, Pablo Angulo
wrote:
Sorry to come back to this (two weeks) old topic, but what do you think
about raising an exception whenever a symbolic integral (or any symbolic
co
Hi Franco,
On Thu, Mar 18, 2010 at 3:41 PM, Franco Saliola wrote:
> I'd really appreciate it if people could describe the way they
> configure such a private server.
The following wiki page might help:
http://wiki.sagemath.org/DanDrake/JustEnoughSageServer
--
Regards
Minh Van Nguyen
--
T
Hello everyone,
I want to set up a private notebook server for a small group of
people, but the documentation for notebook? does not contain any
examples for configuring such a server. It also points to a wiki page
[1], which doesn't have the information, and to what seems to be a
non-existent cha
Hi,
I'm curious if anybody reading this uses the Hidden Markov Models
(HMM) code in Sage for anything. If so, send me an email, since I'm
working on 100% replacing it by some brand new better quality code.
In case you don't know, HMM's are a tool in statistics and machine
learning, which play a
Does anyone have information on the maximum size of an array of
doubles in C? I seem to be getting abnormal results using elements
past the first 1e6. What is the standard way to deal with very large
(millions to billions of elements) arrays of data in C?
Kevin Stueve
--
To post to this group,
Robert Bradshaw wrote:
On Mar 17, 2010, at 4:52 PM, Dr. David Kirkby wrote:
William Stein wrote:
On Wed, Mar 17, 2010 at 4:20 PM, Dr. David Kirkby
wrote:
I started a build of Sage 4.3.4.rc0 on 't2' and one of my own
SPARCs. The
build on 't2' is still going but it completed on on of my SPARCs
On Wed, Mar 17, 2010 at 7:26 PM, Alec Mihailovs
wrote:
> Upgrading to that release on my 64-bit Ubuntu 9.10 (from Sage 4.1.
> something) everything went fine except fortran. Here are the related
> error messages
>
> sage-spkg fortran-20100118 2>&1
> Warning: Attempted to overwrite SAGE_ROOT enviro
Hi Alec,
On Thu, Mar 18, 2010 at 1:26 PM, Alec Mihailovs
wrote:
> Upgrading to that release on my 64-bit Ubuntu 9.10 (from Sage 4.1.
> something) everything went fine except fortran. Here are the related
> error messages
Having a working gfortran compiler is a prerequisite for compiling
Sage, ev
On Wed, Mar 17, 2010 at 5:41 PM, Dr. David Kirkby
wrote:
> But I will have to tell you publicly, I will not be subscribing to
> sage-solaris, and will take no further part in Sage development.
It's a shame to see that you have quit over what seems to be a small
misunderstanding (?). In any case,
Upgrading to that release on my 64-bit Ubuntu 9.10 (from Sage 4.1.
something) everything went fine except fortran. Here are the related
error messages
sage-spkg fortran-20100118 2>&1
Warning: Attempted to overwrite SAGE_ROOT environment variable
fortran-20100118
...
Extracting package /home/alec/s
On Mar 17, 8:02 pm, William Stein wrote:
> I didn't realize that the VirtualBox distro hadn't been upgraded in so long.
> I'll try hard to upgrade it to 4.3.4 and post a new version before I
> leave for Canada on Sunday morning. (Upgrading it is not easy, as
> you found...)
Thank you very much
On Wed, Mar 17, 2010 at 3:27 PM, Alec Mihailovs
wrote:
> It's not related to this particular release - just in general.
>
> I tried to upgrade Sage in VirtualBox on Windows (from version 4.3
> that I installed 2 days ago, which is the latest version distributed
> for Windows), and everything seeme
On Mar 17, 6:46 pm, "Nicolas M. Thiery"
wrote:
> Dear Dima, dear Sage devs,
>
> Dan Bump recently raised the issue that the `lattice` method for Weyl
> groups is badly named. I agree, but the issue is more general. Hence,
> here is a call for good names.
>
> Let P be a parent endowed with
On Mar 17, 2010, at 4:52 PM, Dr. David Kirkby wrote:
William Stein wrote:
On Wed, Mar 17, 2010 at 4:20 PM, Dr. David Kirkby
wrote:
I started a build of Sage 4.3.4.rc0 on 't2' and one of my own
SPARCs. The
build on 't2' is still going but it completed on on of my SPARCs
at home. I
just sta
William Stein wrote:
On Wed, Mar 17, 2010 at 4:52 PM, Dr. David Kirkby
wrote:
Personally I think that was a *very* bad idea. 95% of people won't read the
list, so 95% of people will not read particular problems that were created
by others that have an impact on Solaris.
Out of respect to t
Nick Alexander wrote:
On 17-Mar-10, at 4:27 PM, Dr. David Kirkby wrote:
Minh posted the subject "Sage 4.3.4.rc0 released" a perfectly logical
subject.
Loads of people have replied so the subject becomes "Re: Sage
4.3.4.rc0 released". They report success/failure on various systems.
So far t
On Wed, Mar 17, 2010 at 4:52 PM, Dr. David Kirkby
wrote:
> William Stein wrote:
>>
>> On Wed, Mar 17, 2010 at 4:20 PM, Dr. David Kirkby
>> wrote:
>>>
>>> I started a build of Sage 4.3.4.rc0 on 't2' and one of my own SPARCs. The
>>> build on 't2' is still going but it completed on on of my SPARCs
William Stein wrote:
On Wed, Mar 17, 2010 at 4:20 PM, Dr. David Kirkby
wrote:
I started a build of Sage 4.3.4.rc0 on 't2' and one of my own SPARCs. The
build on 't2' is still going but it completed on on of my SPARCs at home. I
just started to run the long doctests.
Yeah! All this successful
This is only part of the confusion, but it seems worthy to note:
in sage.misc.misc:
{{{
def cancel_alarm():
signal.signal(signal.SIGALRM, signal.SIG_IGN)
}}}
This leaves the clock counting, but sets it up so that the alarm gets
ignored when it does go off. This is bad when someone else write
Dear Dima, dear Sage devs,
Dan Bump recently raised the issue that the `lattice` method for Weyl
groups is badly named. I agree, but the issue is more general. Hence,
here is a call for good names.
Let P be a parent endowed with a natural action (or representation) on
a space `E`. For exa
On Wed, Mar 17, 2010 at 4:32 PM, Nick Alexander wrote:
>> So what do people think is best - reply directly to Minh's post, or start
>> a new subject as I did?
Like Nick said, keeping the threading is best.
--Mike
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubsc
On 17-Mar-10, at 4:27 PM, Dr. David Kirkby wrote:
Minh posted the subject "Sage 4.3.4.rc0 released" a perfectly
logical subject.
Loads of people have replied so the subject becomes "Re: Sage
4.3.4.rc0 released". They report success/failure on various systems.
So far there is only half a
Minh posted the subject "Sage 4.3.4.rc0 released" a perfectly logical subject.
Loads of people have replied so the subject becomes "Re: Sage 4.3.4.rc0
released". They report success/failure on various systems. So far there is only
half a dozen, but in time there will probably be 20 or more of t
On Wed, Mar 17, 2010 at 4:20 PM, Dr. David Kirkby
wrote:
> I started a build of Sage 4.3.4.rc0 on 't2' and one of my own SPARCs. The
> build on 't2' is still going but it completed on on of my SPARCs at home. I
> just started to run the long doctests.
Yeah! All this successful work on Sage+Solar
I started a build of Sage 4.3.4.rc0 on 't2' and one of my own SPARCs. The build
on 't2' is still going but it completed on on of my SPARCs at home. I just
started to run the long doctests.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, se
In fact, it really appears as though the place the code is getting
stuck at *is* properly wrapped with _sig_on and _sig_off. What could
be happening?
On Wed, Mar 17, 2010 at 3:50 PM, Robert Miller wrote:
> I'm having a frustrating time with this...
>
> I'm using signal.alarm to time out computati
I'm having a frustrating time with this...
I'm using signal.alarm to time out computations that take too long. In
most cases they work, but sometimes they don't. The CPU stops
spinning, but I don't get my prompt back, the program just hangs
forever. I know this is due to a lack of sig_on/sig_off c
It's not related to this particular release - just in general.
I tried to upgrade Sage in VirtualBox on Windows (from version 4.3
that I installed 2 days ago, which is the latest version distributed
for Windows), and everything seemed fine for a while, but then I got
the error message that I run o
Dear Sage-Devel,
This is a short email to Sage developers to let them know that if they
run into serious problems with how tickets they're involved with are
being refereed, they should definitely feel OK with writing to me
offlist about these issues.The problem will then get discussed
offlist
Built and all tests passed on 64-bit Ubuntu 9.10, and OS X 10.6.2.
-Marshall
On Mar 17, 3:23 am, Minh Nguyen wrote:
> Hi folks,
>
> This release candidate cleans up warnings resulting from building the
> Sage documentation. If there are no show stoppers, then this release
> is considered the fin
On 17 March 2010 09:23, Minh Nguyen wrote:
> Hi folks,
>
> This release candidate cleans up warnings resulting from building the
> Sage documentation. If there are no show stoppers, then this release
> is considered the final release candidate.
>
> Source tarball:
>
> http://sage.math.washington.e
Minh Nguyen wrote:
Hi folks,
This release candidate cleans up warnings resulting from building the
Sage documentation. If there are no show stoppers, then this release
is considered the final release candidate.
Sorry, but once again the build failed:
gcc -fPIC -g -I/home/jaap/downloads/sage-
On 17-Mar-10, at 10:18 AM, Mike Hansen wrote:
On Wed, Mar 17, 2010 at 5:21 AM, Pablo Angulo
wrote:
Sorry to come back to this (two weeks) old topic, but what do you
think
about raising an exception whenever a symbolic integral (or any
symbolic
computation) fails? Otherwise, is there a si
On Wed, Mar 17, 2010 at 5:21 AM, Pablo Angulo wrote:
> Sorry to come back to this (two weeks) old topic, but what do you think
> about raising an exception whenever a symbolic integral (or any symbolic
> computation) fails? Otherwise, is there a simple way to distinguish a
> succesful integration
Hello,
As often in algebraic combinatoric, I compute very very huge
FreeModule/VectorSpace... Let's me give some examples :
- I have a Matrix algebra (Hecke like) defined by a set of 5 matrices
of size factorial(5)*factorial(5) and I want to get a basis this
algebra as a VectorSpace over Q. For t
Sorry to come back to this (two weeks) old topic, but what do you think
about raising an exception whenever a symbolic integral (or any symbolic
computation) fails? Otherwise, is there a simple way to distinguish a
succesful integration from failed ones that are just indicated (e.g.,
integrate(e^(x
Hi folks,
This release candidate cleans up warnings resulting from building the
Sage documentation. If there are no show stoppers, then this release
is considered the final release candidate.
Source tarball:
http://sage.math.washington.edu/home/release/sage-4.3.4.rc0/sage-4.3.4.rc0.tar
sage.mat
For an example of how polynomials over number fields are converted
into pari polynomials, see
sage/rings/polynomial/polynomial_element.pyx, in the factor function.
This is the code already used to factor polynomials over number fields
by converting to pari. It is more complicated than one would li
51 matches
Mail list logo
