We received a substantial (~500K$) grant for doing a project on the "border"
between polyhedral computation, multidimensional moment problem (moments
meant as moments of measures), and hard-core numerical computing.
We see a considerable part (if not all) of the software to be written done
in Sa
On 17 Sep., 21:11, Dima Pasechnik wrote:
> one can have two modes, a debug one, with old the behaviour, and the
> performance one, with the new behaviour.
+1
-leif
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-dev
Hi Volker,
On 17 Sep., 22:39, Volker Braun wrote:
> I'll do it.
Thank you very much!
Best regards,
Simon
--
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 thi
I'll do it.
--
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
URL: http://www.sagemath.org
Oops, sorry for the double post. I had the impression that the first
hit on the "send" button had no effect.
--
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 th
Hi!
Since quite a long time, #5 is in need of a review. I think that
it provides quite useful stuff and should thus soon be added to Sage.
Currently, cached_method is implemented in Python, and can be so
frustratingly slow that it is faster to not cache simple routines, or
to implement a cach
Hi!
Since quite a long time, #5 is in need of a review. I think that
it provides quite useful stuff and should thus soon be added to Sage.
Currently, cached_method is implemented in Python, and can be so
frustratingly slow that it is faster to not cache simple routines, or
to implement a cach
Hi Richard,
On 17 Sep., 20:09, rjf wrote:
> Data need not be stored in random access memory. A disk file might be
> quite adequate,
> since documentation presumably is not needed in a hurry, nor is it
> needed in huge
> quantities.
I think the application Stan had in mind was indeed to add
docu
one can have two modes, a debug one, with old the behaviour, and the
performance one, with the new behaviour.
--
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 t
On Sep 17, 10:17 am, Simon King wrote:
> Hi!
>
> On 17 Sep., 18:15, rjf wrote:
>
> > \begin{sarcasm}
> > I'm sure glad that python/sage is so easy to read.
> > \end{sarcasm}
>
> Yeah, I know that kind of sarcasm from my 15 year old son.
>
> > I was suggesting the use of STRINGS as indexes.
>
>
Hi!
On 17 Sep., 18:15, rjf wrote:
> \begin{sarcasm}
> I'm sure glad that python/sage is so easy to read.
> \end{sarcasm}
Yeah, I know that kind of sarcasm from my 15 year old son.
> I was suggesting the use of STRINGS as indexes.
Do I understand correctly: You suggest to use the name of a glob
\begin{sarcasm}
I'm sure glad that python/sage is so easy to read.
\end{sarcasm}
I don't see what is going on, so I am guessing that
you are doing something different.
I was suggesting the use of STRINGS as indexes.
Now it is possible that the same name, i.e. string
would have different meanings
Hi!
In the last few minutes, I hacked something that provides the
following:
sage: ZZ.set_custom_doc('I like this text better.')
sage: ZZ?
Type: IntegerRing_class
Base Class:
String Form:Integer Ring
Namespace: Interactive
File: /mnt/local/king/SAG
Hi Maarten!
On 17 Sep., 10:39, Maarten Derickx
wrote:
> Note that there are also weak referenced versions of dictionairy so the
> memory leak can be solved easily.
No, it can't. For the approach to work generally, for *any* object O,
it is not possible to use O *itself* as (weak) key of a dicti
Thanks! The info on the wiki page about stopping the background ecm
jobs is very useful as well.
David
On Sep 16, 10:43 pm, John H Palmieri wrote:
> On Friday, September 16, 2011 2:17:17 PM UTC-7, daveloeffler wrote:
>
> > Right, so now I have a skynet account, and I tried to grab a copy of
> >
You may also try to start a bash enviroment with sage variables set.
your_dir$ sage -sh
(sage subshell) your_dir$ make html
--
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 op
This change you describe sound like one that has been made for performance
reasons. But since it obviously breaks tracebacks I think it should be either
undone or made such that tracebacks work. There should at least be made a trac
ticket for this issue.
--
To post to this group, send an ema
Note that there are also weak referenced versions of dictionairy so the memory
leak can be solved easily.
--
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
18 matches
Mail list logo
