On Wed, Dec 02, 2009 at 09:08:11PM -0800, Nick Alexander wrote:
>
> I would say, clearly you should use sage-mode from within emacs. Why
> not edit emacs buffers with all the tools that you would expect, plus
> deep integration between your buffers and the sage interpreter?
>
Nick,
I know
Then @parallel will almost certainly satisfy:
@parallel(16)
def embarrassing(x):
return factor(x)
for args, fac in embarrassing(range(1,200)):
print args[0], fac
On Wed, Dec 2, 2009 at 9:23 PM, Ethan Van Andel wrote:
> I was basically thinking that my project, which uses a lot of
> n
I was basically thinking that my project, which uses a lot of
numerical array computing is what my prof would call "an
embarrassingly parallel problem"
Ethan
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubs
>> Well, clearly you should be using emacs instead of vi :)
>
> Aah, the answer to all of life's problems! :)
I would say, clearly you should use sage-mode from within emacs. Why
not edit emacs buffers with all the tools that you would expect, plus
deep integration between your buffers and t
On Dec 2, 2009, at 7:53 PM, Minh Nguyen wrote:
> Hi Ethan,
>
> On Thu, Dec 3, 2009 at 2:22 PM, Ethan Van Andel
> wrote:
>> Does sage support multi-core or multi-processor computation?
>>
>> If so, in what format (MPI, OpenMP etc)
There's mpi4py and pyMPI, and probably several packages one can
2009/12/3 William Stein :
> On Wed, Dec 2, 2009 at 9:48 PM, Dr David Kirkby wrote:
>> Harald has clearly shown there are dramatic savings in space for lzma
>> compression compared to both bzip2 and gzip.
>
> No, Harald said about compressing the Sage source using lzma: "Not so
> much". I.e., ther
Hi Ethan,
On Thu, Dec 3, 2009 at 2:22 PM, Ethan Van Andel wrote:
> Does sage support multi-core or multi-processor computation?
>
> If so, in what format (MPI, OpenMP etc)
I think one way to answer such a question is to survey what's
available in Sage and the Python ecosystem. Starting with Pyth
On Wed, Dec 2, 2009 at 9:48 PM, Dr David Kirkby wrote:
> Harald has clearly shown there are dramatic savings in space for lzma
> compression compared to both bzip2 and gzip.
No, Harald said about compressing the Sage source using lzma: "Not so
much". I.e., there is not dramatic savings in using
Does sage support multi-core or multi-processor computation?
If so, in what format (MPI, OpenMP etc)
If not, are there plans to include it?
Thanks,
Ethan Van Andel
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-dev
Harald has clearly shown there are dramatic savings in space for lzma
compression compared to both bzip2 and gzip. I beliveve lzma
decompresses faster than bzip2 too, though compressing it is very
slow.
At the moment Sage sources are distributed as a tar file, but mainly
consistes of bzip2 compres
On Dec 2, 2009, at 3:46 PM, strogdon wrote:
> On Dec 2, 2:28 pm, François Bissey wrote:
>> On Thu, 03 Dec 2009 08:03:44 strogdon wrote:> So, it would appear
>> that it is not the CFLAGS but whether CFLAGS has
>>> been set to something. The no-strict-aliasing is suspiciously
>>> missing.
>>> T
John H Palmieri wrote:
> On Dec 2, 3:24 pm, Jason Grout wrote:
>> Dan Drake wrote:
>>> On Wed, 02 Dec 2009 at 11:47AM -0800, John H Palmieri wrote:
By the way, I discovered accidentally that from the command line (not
the notebook) if you type:
sage: ed # or %ed or %edit
>>> Oh ma
On Dec 2, 2:28 pm, François Bissey wrote:
> On Thu, 03 Dec 2009 08:03:44 strogdon wrote:> So, it would appear that it is
> not the CFLAGS but whether CFLAGS has
> > been set to something. The no-strict-aliasing is suspiciously missing.
> > The documentation I have on gcc 4.3.4 indicates that op
On Dec 2, 3:24 pm, Jason Grout wrote:
> Dan Drake wrote:
> > On Wed, 02 Dec 2009 at 11:47AM -0800, John H Palmieri wrote:
> >> By the way, I discovered accidentally that from the command line (not
> >> the notebook) if you type:
>
> >> sage: ed # or %ed or %edit
>
> > Oh man, that is great. Ofte
Dan Drake wrote:
> On Wed, 02 Dec 2009 at 11:47AM -0800, John H Palmieri wrote:
>> By the way, I discovered accidentally that from the command line (not
>> the notebook) if you type:
>>
>> sage: ed # or %ed or %edit
>
> Oh man, that is great. Often I am trying to type in a multi-line
> statement
On Wed, 02 Dec 2009 at 11:47AM -0800, John H Palmieri wrote:
> By the way, I discovered accidentally that from the command line (not
> the notebook) if you type:
>
> sage: ed # or %ed or %edit
Oh man, that is great. Often I am trying to type in a multi-line
statement and I mess something up and
first, you might be interested by this:
L = zip(Vars,p.lm().exponents()[0].sparse_iter())
its faster but still not enough...
then you might look at http://trac.sagemath.org/sage_trac/ticket/7587,
apply it ( review it ;) )
and do
L = [(Vars[i],e) for i,e in enumerate(p.lm().exponents
(as_ETuples=
Hello, I got this from the "report a problem" link in the notebook. I
don't know if anything could be done about it though ...
-
I've got a problem evaluating some pretty simple math functions; a
small fourier series, and integrals thereof, then evaluating
numerically (because sag
Hi John,
On Thu, Dec 3, 2009 at 6:47 AM, John H Palmieri wrote:
> By the way, I discovered accidentally that from the command line (not
> the notebook) if you type:
>
> sage: ed # or %ed or %edit
That is so cool! And very useful, too! What a serendipitous discovery!
> and it will let you
On Thu, 03 Dec 2009 08:03:44 strogdon wrote:
> So, it would appear that it is not the CFLAGS but whether CFLAGS has
> been set to something. The no-strict-aliasing is suspiciously missing.
> The documentation I have on gcc 4.3.4 indicates that optimization
> levels O2 and O3 turn on strict-aliasing
On Dec 2, 11:47 am, John H Palmieri wrote:
> sage: ed # or %ed or %edit
>
> then it opens up your favorite editor (whatever is set by the $EDITOR
> shell variable). Then in the editor you can type
>
> sage: ed FF
>
> and it will let you modify your code. This is an ipython feature, it
> seems.
> In the Python environment, if someone detects an error in a Python
> function FF, then the function can be replaced in the run-time
> environment, e.g. at a command line by:
This is technically true but in practice not useful. Most Python code
is not a top-level function; it is a class member
On Dec 2, 10:46 am, Harald Schilly wrote:
> On Dec 2, 5:01 pm, rjf wrote:
>
> > In the Maxima environment, if someone detects an error in a lisp
> > function, FF then the function
> > can be replaced in the run-time environment, e.g. at a command line
> > (%i100) by:
> > :lisp (defun FF(x y z)
On Dec 1, 2:10 pm, François Bissey wrote:
> On Wed, 02 Dec 2009 04:17:50 strogdon wrote:
>
> > Hey Francois. I too thought that perhaps the spkg supplied flags would
> > override any changes with custom flags. However the custom flags seem
> > to be appended to the spkg provided ones. For exampl
On Dec 2, 5:01 pm, rjf wrote:
> In the Maxima environment, if someone detects an error in a lisp
> function, FF then the function
> can be replaced in the run-time environment, e.g. at a command line
> (%i100) by:
> :lisp (defun FF(x y z) )
>
In the Python environment, if someone detects an er
Hi!
On 2 Dez., 17:47, Simon King wrote:
[...]
> IIRC, I tried various other methods (without strings), but they were
> all slower. However, I don't remember any concrete examples.
> So, it would help me if you commented
> onhttp://trac.sagemath.org/sage_trac/ticket/7580
> what I should try inste
Bill Hart wrote:
> If you want to use the 4.3 series, then 4.3.0, 4.3.1, 4.3.2 are
> definitely extremely buggy (so much so I find them almost unusable).
> Another really buggy release was 4.1.2.
>
> I am also aware of bugs in the 4.4 series.
>
> Of course these are my own opinions and may not re
If you want to use the 4.3 series, then 4.3.0, 4.3.1, 4.3.2 are
definitely extremely buggy (so much so I find them almost unusable).
Another really buggy release was 4.1.2.
I am also aware of bugs in the 4.4 series.
Of course these are my own opinions and may not reflect any objective
reality.
B
Hi William!
On 2 Dez., 17:26, William Stein wrote:
...
> I'm not surprised. Looking through the code, its use of strings and
> regular expressions is fairly delicate -- I wouldn't use regular
> expressions at all to implement the same functionality (and more). But
> I'm not rewriting anything (t
On Wed, Dec 2, 2009 at 4:36 AM, Nathann Cohen wrote:
> Hello everybody
>
> Concerning the use of InfinitePolynomialRing in Sage, it was discussed
> in another thread and I since wrote a patch (#7561) to change it. As
> mentionned, I need nothing of what this class has been built for, and
> n
Hi Ethan,
On Thu, Dec 3, 2009 at 3:16 AM, Ethan Van Andel wrote:
> Minh,
>
> Have you been able to look at it at all?
My apologies. Not yet. I have been reviewing other tickets and the
reviewing is done. Your ticket is the next one I'll review.
--
Regards
Minh Van Nguyen
--
To post to this g
Minh,
Have you been able to look at it at all?
Ethan
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
U
On Dec 2, 2009, at 2:46 AM, Alex Ghitza wrote:
>
> The docstring for CyclotomicField says that "Due to their default
> embedding into `\CC`, cyclotomic number fields are all compatible."
> and goes on to show some operations between elements of different
> cyclotomic fields.
>
> And yet, I run int
While it may not be entirely helpful to point it out, I thought that
one of the advantages of using
python was some kind of rapid development. NTL is not in python so
maybe it doesn't "count"?
In the Maxima environment, if someone detects an error in a lisp
function, FF then the function
can be r
On Dec 2, 11:38 am, Harald Schilly wrote:
> Ok, I did some tests with the ...
... and with sage-4.2.1.tar source distribution:
I extracted the tar, went into spkg/standard, decompressed all of them
with tar xjf ...
Then that magic:
$ find -mindepth 1 -maxdepth 1 -type d | xargs -I{} tar --lzma
The docstring for CyclotomicField says that "Due to their default
embedding into `\CC`, cyclotomic number fields are all compatible."
and goes on to show some operations between elements of different
cyclotomic fields.
And yet, I run into this:
sage: a = CyclotomicField(100).random_element()
sag
Hello,
After upgrade from 3.4 to 4.2.1 I tried to access from the notebook,
logged as admin, I try to access the "notebook settings" page and get:
Internal Server Error
An error occurred rendering the requested page. More information is
available in the server log.
On the server I get:
2009-12-
Ok, I did some tests with the binary distribution (bdist) of 4.2.1 on
ubuntu 9.10 for my local machine. i.e. a regular binary.
I did "cat sage-4.2.1-*.tar | $CMD > file" where
.tar.gz is the regular sage-bdist one
.tar.best.gz CMD is "gzip --best"
.tar.best.bzip2 CMD is "bzip2 --best"
.tar.lz
Hello everybody
Concerning the use of InfinitePolynomialRing in Sage, it was discussed
in another thread and I since wrote a patch (#7561) to change it. As
mentionned, I need nothing of what this class has been built for, and
now that it is replaced with plain "var", it is a thousand times
f
On Tue, Dec 1, 2009 at 2:36 AM, Nicolas M. Thiery
wrote:
> Please let me know in case the automatic changes come out wrong, so
> that we can think whether there is something to be done to improve the
> script.
>
sage -fixdoctests worked beautifully. I've uploaded a patch to fix the
doctests to #1
Hi!
On Dec 2, 6:40 am, William Stein wrote:
> On Wed, Dec 2, 2009 at 1:01 AM, Mike Hansen wrote:
> > On Wed, Dec 2, 2009 at 12:57 PM, William Stein wrote:
> >> WTF? Regular expressions?!?!
There are regular expressions in InfinitePolynomialRing, but (at least
after applying my patch) I don't
William Stein wrote:
> Hi,
>
> I think I like David Kirkby's suggestion that we ship libstdc++. Even
> on Linux, not having it *does* cause trouble sometimes. At least, if
> we ship it then a sage binary built for LinuxDistro x.y will be more
> likely to work on LinuxDistro x'.y'. There hav
42 matches
Mail list logo
