On Thu, Feb 21, 2008 at 8:39 AM, Simon King <[EMAIL PROTECTED]> wrote:
>
> Dear Team,
>
>
> On Feb 20, 12:33 pm, Simon King <[EMAIL PROTECTED]> wrote:
> > Well, perhaps better to start the process again and (in 26 hours) save
> > the temporary file...
>
> I was not patient enough. Instead, i successfully tried a work around.
>
> I observed that
> singular.eval(s)
> creates a buffer file only if the string s is longer than about 850
> characters (why, anyway?).
Because if you try to write long strings to pexpect it gets INSANELY SLOW
and after about 2000-3000 characters it hangs. So instead, Sage writes
a file to disk then sends (via expect) the command "read this file" to
Singular. It does this sort of thing with all the interfaces. This is the key
thing that makes it possible to send very large inputs quickly to
the interfaces.
> In my case s has a very simple structure: It describes one minuend and
> a couple of hundred subtrahends. Moreover, minuend and subtrahends do
> not contain minus signs. So i can break it up into small pieces with
> s.split('-'), and then compute the result in a loop. In that way, i
> avoid the creation of a temporary file.
>
> And this helps, the interface stays awake.
>
> However, if you want to find out why the interface broke and if the
> singular logfile provided earlier does not suffice, i can return to a
> previous version of my program and reproduce it. But then please tell
> me what logs you need and how i can make them.
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
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://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
