Dear William,
Thank your for the reply. I hadn't used PARI for this before, but
when I tried this right now I am getting very similar results.
About the strange CPU info, I actually cannot quite see where the
discrepancy is coming from. As perhaps you guessed from the format,
in each case I ha
On Sat, Nov 14, 2009 at 9:00 PM, Sebastian Pancratz wrote:
>
> Dear William,
>
> I am adding a somewhat more detailed performance report below,
> comparing my own FLINT-based C code, MAGMA, SAGE 4.1.2.alpha2 and SAGE
> 4.1.2.alpha2 with the patch from trac ticket #4000.
>
> To give an impression
Dear William,
I am adding a somewhat more detailed performance report below,
comparing my own FLINT-based C code, MAGMA, SAGE 4.1.2.alpha2 and SAGE
4.1.2.alpha2 with the patch from trac ticket #4000.
To give an impression of the results, for very small examples MAGMA
marginally beats my C implem
On Nov 14, 2009, at 5:59 PM, Sebastian Pancratz wrote:
> Dear all,
>
> Some might remember that in September I put a lot of effort into
> rewriting Q[t] to use FLINT. While the patch (see trac #4000) was
> very usable in practice already, despite the help of many people there
> remained a few do
On Nov 14, 9:05 pm, William Stein wrote:
> Could you add something to this email about performance comparisons with
> Magma?
> It's one thing to say "Sage is slow compared to my custom optimized C
> code" (no surprise), and another to say "Sage is 1000 times slower
> than some easy-to-write int
On Sat, Nov 14, 2009 at 6:48 PM, Jason Moxham wrote:
>
> On Sunday 15 November 2009 02:24:47 William Stein wrote:
>> On Sat, Nov 14, 2009 at 6:17 PM, Jason Moxham
> wrote:
>> > Of course , that is the error
>> > LD_LIBRARY_PATH sets the path for executables so there is no need for it
>> > to be
On Sat, Nov 14, 2009 at 5:39 PM, Minh Nguyen wrote:
>
> Hi folks,
>
> Here is a series of blog posts on writing documentation for an open
> source project. The project in question is Django. The first part [1]
> in the series covers what sort of documentation an open source project
> needs. The s
On Sat, Nov 14, 2009 at 6:17 PM, Jason Moxham wrote:
>
> Of course , that is the error
> LD_LIBRARY_PATH sets the path for executables so there is no need for it to be
> set when building pari (just when running it) so the only thing that is USING
> libgmp is gcc which doesn't like it .
This me
On Sat, Nov 14, 2009 at 5:59 PM, Sebastian Pancratz wrote:
>
> Dear all,
>
> Some might remember that in September I put a lot of effort into
> rewriting Q[t] to use FLINT. While the patch (see trac #4000) was
> very usable in practice already, despite the help of many people there
> remained a
Dear all,
Some might remember that in September I put a lot of effort into
rewriting Q[t] to use FLINT. While the patch (see trac #4000) was
very usable in practice already, despite the help of many people there
remained a few doctest failures throughout SAGE.
In short, while using SAGE with my
On Nov 14, 2:46 pm, Alex Ghitza wrote:
> On Sat, Nov 14, 2009 at 02:20:43PM -0800, John H Palmieri wrote:
>
> > In what way are they a total mess? I'm curious.
>
> > > Of course, it was inevitable that we would run head first into this
> > > problem eventually, and it's amusing that we did th
On Nov 14, 2:38 pm, William Stein wrote:
>
> (1) Almost all of the docstrings in Sage look like this:
>
> INPUT:
>
> - `n` - an integer
>
> - `m` - another integer
>
> - `k` - a third integer, with a longer description
>
> with spaces. I'm not sure why, but I think Mike Hansen argued that
On Sat, Nov 14, 2009 at 3:09 PM, Dr. David Kirkby
wrote:
>
> William Stein wrote:
>> 2009/11/14 Dr. David Kirkby :
>
>>> I assume 'experimental' are less stable than 'optional'. IMHO, the user
>>> downloading the file should be made aware it is experimental, and so one
>>> way to
>>> do that wou
On Sat, Nov 14, 2009 at 3:02 PM, Alex Ghitza wrote:
> There is an enhancement ticket for making Sphinx read Bibtex files:
>
> http://bitbucket.org/birkenfeld/sphinx/issue/63/make-sphinx-read-bibtex-files-for
>
> There seems to have been some activity on it, but the latest was 10
> months ago.
I
William Stein wrote:
> 2009/11/14 Dr. David Kirkby :
>> I assume 'experimental' are less stable than 'optional'. IMHO, the user
>> downloading the file should be made aware it is experimental, and so one way
>> to
>> do that would be to have an option like
>>
>> sage --install-experimental some_
On Sat, Nov 14, 2009 at 02:38:06PM -0800, William Stein wrote:
>
> On Sat, Nov 14, 2009 at 2:20 PM, John H Palmieri
> wrote:
> >
> > On Nov 14, 1:55 pm, William Stein wrote:
> >> On Fri, Nov 13, 2009 at 11:18 PM, Robert Bradshaw
> >>
> >> wrote:
> >>
> >> > This is one of the many, many cases
On Sat, Nov 14, 2009 at 02:20:43PM -0800, John H Palmieri wrote:
>
>
> In what way are they a total mess? I'm curious.
>
> > Of course, it was inevitable that we would run head first into this
> > problem eventually, and it's amusing that we did this week.
> >
> > Anyway, I agree with Rober
Hi folks,
Here is a series of blog posts on writing documentation for an open
source project. The project in question is Django. The first part [1]
in the series covers what sort of documentation an open source project
needs. The second part [2] is about technical style. And the third
part [3] ta
On Sat, Nov 14, 2009 at 2:20 PM, John H Palmieri wrote:
>
> On Nov 14, 1:55 pm, William Stein wrote:
>> On Fri, Nov 13, 2009 at 11:18 PM, Robert Bradshaw
>>
>> wrote:
>>
>> > This is one of the many, many cases where I think it would be easier
>> > to fix the tool rather than change people's be
On Nov 14, 1:55 pm, William Stein wrote:
> On Fri, Nov 13, 2009 at 11:18 PM, Robert Bradshaw
>
> wrote:
>
> > This is one of the many, many cases where I think it would be easier
> > to fix the tool rather than change people's behavior. Why not have our
> > cake and eat it too? [ABC] can automat
On Sat, Nov 14, 2009 at 01:55:29PM -0800, William Stein wrote:
>
> I strongly agree with this. In fact, last week when I was hanging out
> with Jarrod Millman (of scipy/numpy), he baited me -- "so, are you
> guys using Sphinx a lot for Sage yet?" When I said "yes!", he
> responded, "so how did
On Sat, Nov 14, 2009 at 01:58:23PM -0800, Robert Bradshaw wrote:
> > One good habits which will probably solve a large part of the
> > duplicate it to
> > put the reference not in the doctring of the methods or function but
> > in that
> > of the module = file. It is very likely that several
On Nov 14, 2009, at 2:36 AM, Florent Hivert wrote:
>
> Hi,
>
>> 1. These references used to be local to the docstring they appear in.
>> As soon as we ReST-ify them, they become global in the reference
>> manual. Therefore if there is already a reference labeled [ABC],
>> Sphinx will rightf
On Fri, Nov 13, 2009 at 11:18 PM, Robert Bradshaw
wrote:
>
> On Nov 13, 2009, at 9:53 PM, Alex Ghitza wrote:
>
>> Hi,
>>
>> Martin Albrecht pointed out to me that there is a way to markup
>> citations and references in ReST (and that I should be using that in
>> my patches). I was so happy to se
Hi,
> 1. These references used to be local to the docstring they appear in.
> As soon as we ReST-ify them, they become global in the reference
> manual. Therefore if there is already a reference labeled [ABC],
> Sphinx will rightfully complain. That's easy to fix, just use a
> different l
2009/11/14 Dr. David Kirkby :
>
> William Stein wrote:
>> On Sat, Nov 14, 2009 at 11:40 AM, Dr. David Kirkby
>> wrote:
>>> William Stein wrote:
Hi,
I want to formulate a rough ideal strategy for how to deal with
"optional stuff" in Sage, and get feedback.
PROPOSAL: 1. Be
On Sat, Nov 14, 2009 at 1:13 PM, Nils Bruin wrote:
>
> On Nov 14, 10:03 am, Jason Grout wrote:
>> William Stein wrote:
>> > Burcin -- does this needs to be added? I can't figure out how to do
>> > it either? It used to be easy with the old symbolics, but not with
>> > the new ones.
>
> What yo
On Nov 14, 10:03 am, Jason Grout wrote:
> William Stein wrote:
> > Burcin -- does this needs to be added? I can't figure out how to do
> > it either? It used to be easy with the old symbolics, but not with
> > the new ones.
What you are looking for is is_SymbolicVariable(), I think.
I think c
William Stein wrote:
> On Sat, Nov 14, 2009 at 12:17 AM, Dr. David Kirkby
> wrote:
>> Dr. David Kirkby wrote:
>>> William Stein wrote:
sage: An error occurred while installing database_cremona_ellcurve-20071019
I'm really surprised that this fails, given that it is just extracting
William Stein wrote:
> On Sat, Nov 14, 2009 at 11:40 AM, Dr. David Kirkby
> wrote:
>> William Stein wrote:
>>> Hi,
>>>
>>> I want to formulate a rough ideal strategy for how to deal with
>>> "optional stuff" in Sage, and get feedback.
>>> PROPOSAL: 1. Before releasing a new version of Sage, we t
Pardon the newbie question,
Is there a quick way to get backtraces for doctest failures?
I have been running gdb python in a sage subshell, then copying the offending
lines into a text file and then running from within gdb. This seems to be
awkward and I was looking for a better way.
This
On Sat, Nov 14, 2009 at 11:40 AM, Dr. David Kirkby
wrote:
>
> William Stein wrote:
>> Hi,
>>
>> I want to formulate a rough ideal strategy for how to deal with
>> "optional stuff" in Sage, and get feedback.
>
>> PROPOSAL: 1. Before releasing a new version of Sage, we test
>> installing all of th
William Stein wrote:
> Hi,
>
> I want to formulate a rough ideal strategy for how to deal with
> "optional stuff" in Sage, and get feedback.
> PROPOSAL: 1. Before releasing a new version of Sage, we test
> installing all of the optional spkg's on the most recent 64-bit
> version of Ubuntu. If
Hi,
I want to formulate a rough ideal strategy for how to deal with
"optional stuff" in Sage, and get feedback.
1. OPTIONAL CODE:
Throughout the sage library there is code with doctests marked "#
optional - tag". You can doctest all the blocks of code in the sage
library for a given tags by d
Jason wrote :
> The calculation below caused some concern for a few minutes with one of
> my students the other day. We reasoned through it and saw that
> everything was mathematically correct, but it seemed odd that Sage/pynac
> would automatically pull a negative one out of (x-2t) and square
On 14 lis, 18:30, Francois Maltey wrote:
> a'-Extract and test sin in sin(x) is easy, but recognize the + in x+y is
> heavy.
>
And perhaps even worse for x+z+z+z_1
The paper of RJF can be perhaps useful (examples written in Maxima,
but general ideas) to deal with addition and multiplication:
On Sat, Nov 14, 2009 at 12:17 AM, Dr. David Kirkby
wrote:
>
> Dr. David Kirkby wrote:
>> William Stein wrote:
>
>>> sage: An error occurred while installing database_cremona_ellcurve-20071019
>>>
>>> I'm really surprised that this fails, given that it is just extracting
>>> and copying over a dir
On Sat, Nov 14, 2009 at 12:33 AM, Kwankyu Lee wrote:
>
> Hi,
>
> What is the standard way to get a reference to a magma object in Sage?
>
> Is it "m._ref()" or "m.name()"? What is their difference?
>
m.name() gives the name of the variable corresponding to m in the
magma session.
m._ref() is do
On Thu, Nov 12, 2009 at 11:43 PM, Kwankyu Lee wrote:
>
> Hi,
>
> Is this an expected behavior of the magma interface?
>
> --
> | Sage Version 4.2, Release Date: 2009-10-24 |
> | Type notebook() for the GUI
Many thanks for the 2 previous help !
About operator.add and expr.variables()...
The (real-?) last question is
a=4*x
b=4/3*x
c=4.0*x
d=4*I*x
I can get the constant by a.operands(), a.operands()[-1], but how can I
test (without error) if this term is an integer, a rational, a float or
a compl
On Sat, Nov 14, 2009 at 10:12 AM, Francois Maltey wrote:
>
> William wrote :
>> But isn't it just operator()???
>>
>> sage: var('x,y'); a = x+y
>> (x, y)
>> sage: a.operator()
>>
>>
> Sage also need tests over theses operators :
> In an expression we test
>
> op = expr.operator
>
> if op == sin
William wrote :
> But isn't it just operator()???
>
> sage: var('x,y'); a = x+y
> (x, y)
> sage: a.operator()
>
>
Sage also need tests over theses operators :
In an expression we test
op = expr.operator
if op == sin : ... # is right
elif op == + : ... # doesn't work (or add or _plus...)
The
William Stein wrote:
> Burcin -- does this needs to be added? I can't figure out how to do
> it either? It used to be easy with the old symbolics, but not with
> the new ones.
Here's a round-about (and probably failure-prone) way:
a=sqrt(2)
t=a.variables()
if len(t)==1:
print bool(t[0]=
The calculation below caused some concern for a few minutes with one of
my students the other day. We reasoned through it and saw that
everything was mathematically correct, but it seemed odd that Sage/pynac
would automatically pull a negative one out of (x-2t) and square that
negative one aw
On Sat, Nov 14, 2009 at 9:30 AM, Francois Maltey wrote:
>
> Hello,
>
> This purpose about expression has 3 differents aspects.
>
> A/ The first aspect we discover is the user interface. This interface
> must be coherent.
> This means that 1/ it's possible to describe it with "few word" 2/ The
> m
Hello,
This purpose about expression has 3 differents aspects.
A/ The first aspect we discover is the user interface. This interface
must be coherent.
This means that 1/ it's possible to describe it with "few word" 2/ The
most common calculus has no option 3/ This system will be able to be
re
> I see no point at all in building ATLAS on OS X, since OS X already
> ships a highly tuned "Apple-certified" multi-core aware build of ATLAS
> systemwide. The ATLAS's we build/ship with Sage are never multicore
> aware. It's simply much better as far as I can tell for Sage to use
> the system
On Sat, Nov 14, 2009 at 01:58:46AM +0100, Florent hivert wrote:
> > > As an online document, I think the cost for repetition is almost
> > > nothing, and is greatly outweighed by the benefit of having these
> > > inherited functions explicitly listed.
> >
> > We can also *list* them without listi
Hi,
What is the standard way to get a reference to a magma object in Sage?
Is it "m._ref()" or "m.name()"? What is their difference?
Kwankyu
--~--~-~--~~~---~--~~
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group,
Dr. David Kirkby wrote:
> William Stein wrote:
>> sage: An error occurred while installing database_cremona_ellcurve-20071019
>>
>> I'm really surprised that this fails, given that it is just extracting
>> and copying over a directory -- nothing gets built. Maybe it is a
>> GNU-ism to copy, or a
Dear category fans,
Latest status report for the category patches:
- They apply smoothly on 4.2.1 alpha0, with all test passing :-)
(This is on a macbook pro ubuntu 9.4 with everything up to
sage-4.3.patch in the Sage-Combinat queue)
Mike: could you please run the tests on a v
51 matches
Mail list logo
