On Nov 7, 5:29 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Michael,
>
> On Nov 7, 4:22 pm, mabshoff <[EMAIL PROTECTED]> wrote:
Hi Simon,
>
> <snip>
>
> > > This is indeed non-trivial! Even when i compute maxideal(19), which
> > > takes a couple of seconds, singular.cputime(t) only returns 0.001. I
> > > doubt that this is the correct time.
>
> > If you can reproduce this with a "stock" Singular somebody ought to
> > report this back to Hannes.
>
> This reminds me something.
>
> Recently i was building Singular from the sources. It kind of worked,
> but the timer was spoiled. Only rtimer did what it was supposed to.
> Hannes couldn't tell me what i did wrong. The timer of the downloaded
> Singular binary works, but the timer of "my own" Singular doesn't.
> Strange.
>
> I suspect that the timer problem of my Sage/Singular has the same
> source. By the way, i just checked that the timer of Sage/Singular on
> another machine (built by a colleague of mine) doesn't work either.
>
> Two questions:
> 1) Any idea why the Singular timer doesn't work when i build it? I
> mean, what piece of software involved in building Singular is
> responsible for the timer?
I would assume that they use getrusage, but I haven't checked.
> 2) Would it work to replace the Sage-Singular by a softlink to the
> downloaded Singular binary (with timer)?
>
It should work and has been done so by several people in the past,
i.e. on Solaris. I guess you can either modify the Singular script to
point to your own Singular or copy over the binary to Singular-3.0.3.
> Yours
> Simon
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/
-~----------~----~----~----~------~----~------~--~---
