2008/9/23 mhampton <[EMAIL PROTECTED]>:
>
> Thanks Arnaud. I have reviewed it on trac.
>
> Because of the issues I mentioned in the review, I didn't test your
> code on larger high-dimensional examples. But you did say it was slow
> in high-dimensions. If that is still the case after fixing the
On Sep 23, 2008, at 20:17 , mabshoff wrote:
>
>
>
> On Sep 23, 8:14 pm, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
>> IIRC "." is sh syntax, but also works with bash. "source" does not
>> work on csh and its descendants, i.e. tcsh to mention the most
>> common.
>
> Oops, do I look like an idio
On Sep 23, 2008, at 20:14 , mabshoff wrote:
> On Sep 23, 7:30 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
>> On Sep 23, 2008, at 11:15 , CristianCantoro wrote:
>
>
>
>>> Thanks Michael, that worked!
>>> just to know... what does "source local/bin/sage-env" do?
>>> I will start the translat
On Sep 23, 8:14 pm, mabshoff <[EMAIL PROTECTED]> wrote:
> IIRC "." is sh syntax, but also works with bash. "source" does not
> work on csh and its descendants, i.e. tcsh to mention the most common.
Oops, do I look like an idiot now. "source" obviously works with csh &
friends, but the sage-e
On Sep 23, 7:30 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> On Sep 23, 2008, at 11:15 , CristianCantoro wrote:
> > Thanks Michael, that worked!
> > just to know... what does "source local/bin/sage-env" do?
> > I will start the translation as soon as I can.
>
> 'source' is a shell buil
On Sep 23, 2008, at 11:15 , CristianCantoro wrote:
>
> Hi!
>
> On Sep 23, 3:03 am, mabshoff <[EMAIL PROTECTED]> wrote:
>> There is a README.txt in devel/doc which might be hepful. You should
>> also "source local/bin/sage-env" from $SAGE_ROOT before running make
>> in the doc directory. Another
On Sep 23, 2:14 pm, bourbabis <[EMAIL PROTECTED]> wrote:
Hi,
> 1) My computer is a desktop with an Athlon k7 800Mhz + 384 Mo RAM.
Ouch.
> The hardware sensor checking the temperature is up an running but
> never
> set off an alarm.
Ok, but that does not mean that the CPU is not overheating.
On Sep 23, 11:15 am, CristianCantoro <[EMAIL PROTECTED]> wrote:
> Hi!
> Thanks Michael, that worked!
Good.
> just to know... what does "source local/bin/sage-env" do?
It sets up the Sage environment properly, i.e. the location of Sage
and so on which is needed for a couple scripts that ass
Hi Georg,
Thanks for volunteering to look at this. Craig's also doing this, but a
second pair of eyes is always
welcome. Don't hesitate to ask questions if something in the patches looks
fishy.
I have updated Jason Grout's notes on mercurial queues at
http://wiki.sagemath.org/MercurialQueues
> sage: K. = CyclotomicField(23)
> sage: K.class_number()
>
> ...
>
> PariError: not enough precomputed primes, need primelimit ~ (35)
>
Hah, that's pretty hilarious. :) Actually, what it's telling you is
that it needs primes up to a primelimit, and then it doesn't actually
put in the primelimit
On Sep 23, 4:05 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> On 24 Sep., 00:34, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> > On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
> > wrote:
>
> > > On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
> >
>
> > > I'll
On Sep 23, 4:05 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> On 24 Sep., 00:34, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
> > wrote:
>
> > > On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
> >
>
> > > I'll open
Hi,
On 24 Sep., 00:34, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
> wrote:
>
> > On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
>
>
>
> > I'll open more tickets for other failures, as soon I can say for sure
> > "it' only timing"
On Sep 23, 3:49 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> --
> | SAGE Version 3.1.2, Release Date: 2008-09-19 |
> | Type notebook() for the GUI, and license() for information. |
> ---
On Sep 23, 3:46 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> Hi Dan,
Hi Georg,
> I can see this issue pretty often on my old PPC box.
> However I'll sacrifice my time first for the pari precision patch to
> get as soon as possible into 3.1.3, before going to look into more
> detail into
> it's not the smallest of patches, but at a first and at a second sight
> it is not only very well done, e.g. with accurate doctests for the
> nice new functions, but also presented "on a silver plate".
> I still have to learn how to use Mercurial, how to apply a patch on a
> branch, and such; an
--
| SAGE Version 3.1.2, Release Date: 2008-09-19 |
| Type notebook() for the GUI, and license() for information.|
--
sage: K. = Cy
Hi Dan,
On 23 Sep., 14:37, Dan Drake <[EMAIL PROTECTED]> wrote:
> On Wed, 17 Sep 2008 at 08:55PM -0700, mabshoff wrote:
> > > but when I run 'make test', some test will simply stop. This happens
> > > every time, and often with different tests. The CPU usage is zero,
> > > and nothing happens. Th
Hi,
On 20 Sep., 01:58, "Alex Ghitza" <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> John Cremona and I have been working for the past two weeks on fixing the
> way real precision gets passed from Sage to the Pari library and back.
> Things were extremely broken, due mostly to a misunderstanding of ho
On Sep 23, 3:27 pm, "Georg S. Weber" <[EMAIL PROTECTED]>
wrote:
> On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
> I'll open more tickets for other failures, as soon I can say for sure
> "it' only timing" and have a new "good" timing constant.
Please do not open any more ticket
On 23 Sep., 10:07, "John Cremona" <[EMAIL PROTECTED]> wrote:
> 2008/9/23 William Stein <[EMAIL PROTECTED]>:
>
> I still don't know if this is going to help the MACOS problem with my
> sll_finite_field odctest though!
>
> John
>
Hi all,
first some on-topic data:
on my PPC PowerBook with Mac OS
On Tue, Sep 23, 2008 at 3:11 PM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Sep 23, 3:07 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
>
>
>> > You can give the interface an optional log parameter. But I don't have
>> > a patch at the moment, give me a while if you still have problems.
>>
On Sep 23, 3:07 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> > You can give the interface an optional log parameter. But I don't have
> > a patch at the moment, give me a while if you still have problems.
>
> This is slightly OT, but Michael would you like it to so that
> one could more e
On Tue, Sep 23, 2008 at 11:12 AM, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Sep 23, 5:37 am, Dan Drake <[EMAIL PROTECTED]> wrote:
>> On Wed, 17 Sep 2008 at 08:55PM -0700, mabshoff wrote:
>
> Hi Dan,
>
>> > > but when I run 'make test', some test will simply stop. This happens
>> > > every tim
On Sep 9, 2008, at 9:20 AM, Robert Bradshaw wrote:
> On Sep 9, 2008, at 2:30 AM, Martin Albrecht wrote:
>
>>
>> On Tuesday 09 September 2008, William Stein wrote:
On a related note, recently I wrote a simple loop that went
something
like this:
while abs(err) < 1e-6:
1) My computer is a desktop with an Athlon k7 800Mhz + 384 Mo RAM.
The hardware sensor checking the temperature is up an running but
never
set off an alarm.
2) I've given it a try again, but compilation has leaded to the same
failure.
I saw this in the log file :
"ATLAS failed to build because yo
> You can always type "version()" in a cell to get the version number, but
> I agree, it would be a nice touch to have it
Yes, of course! But it's unlikely a first-time bug reporter will know
to do that.
> yesterday, i had exactly the same idea ;)
Harald, glad I wasn't the only one!
> (but pl
kcrisman wrote:
> As far as I can tell, when one uses the notebook directly, there is no
> announcement of the version number of Sage; for that matter, it's not
> even on the front page of the help. This is not a really big deal,
> but might occasionally be nice, say maybe right under the "Sage
>
yesterday, i had exactly the same idea ;)
+1
--~--~-~--~~~---~--~~
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 http://groups.google.com/group/
As far as I can tell, when one uses the notebook directly, there is no
announcement of the version number of Sage; for that matter, it's not
even on the front page of the help. This is not a really big deal,
but might occasionally be nice, say maybe right under the "Sage
notebook" header on the h
Hi!
On Sep 23, 3:03 am, mabshoff <[EMAIL PROTECTED]> wrote:
> There is a README.txt in devel/doc which might be hepful. You should
> also "source local/bin/sage-env" from $SAGE_ROOT before running make
> in the doc directory. Another thing worth trying is to delete all of
> the various temporary
On Sep 23, 5:37 am, Dan Drake <[EMAIL PROTECTED]> wrote:
> On Wed, 17 Sep 2008 at 08:55PM -0700, mabshoff wrote:
Hi Dan,
> > > but when I run 'make test', some test will simply stop. This happens
> > > every time, and often with different tests. The CPU usage is zero,
> > > and nothing happens
Will you provide videos of your lectures online? The outline looks very
interesting.
Cheers,
Martin
--
name: Martin Albrecht
_pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99
_www: http://www.informatik.uni-bremen.de/~malb
_jab: [EMAIL PROTECTED]
--~--~-~--~~--
Hi,
I wanted to advertise a class that I am going to teach this fall
semester, and which can be of interest for sage developers and users.
As its title suggests, it will be about theoretical and practical topics
on computational exact linear algebra. You can check out the web page
with the sylla
I think this looks great, very nicely done.
I am wondering if it would be possible to modify/include the "virtual"
files like htmlhead.shtml, since they are not in the zipped version,
and I had trouble finding them online.
Cheers,
M. Hampton
On Sep 18, 3:30 pm, Elliott <[EMAIL PROTECTED]> wrote
On Wed, 17 Sep 2008 at 08:55PM -0700, mabshoff wrote:
> > but when I run 'make test', some test will simply stop. This happens
> > every time, and often with different tests. The CPU usage is zero,
> > and nothing happens. The test just sits there.
>
> You can log the Sage<->Maxima communication a
Thanks Arnaud. I have reviewed it on trac.
Because of the issues I mentioned in the review, I didn't test your
code on larger high-dimensional examples. But you did say it was slow
in high-dimensions. If that is still the case after fixing the
current problems it might make sense to use a rand
2008/9/23 William Stein <[EMAIL PROTECTED]>:
>
> On Mon, Sep 22, 2008 at 6:11 PM, Craig Citro <[EMAIL PROTECTED]> wrote:
>>
>> Hi John,
>>
>>> That is not in itself slow:
>>> sage: time pp=pari.primes_up_to_n(10^8)
>>> CPU times: user 0.69 s, sys: 0.30 s, total: 1.00 s
>>> Wall time: 1.00 s
>>>
>>
38 matches
Mail list logo
