Hi All,
Whenever I try installing the combinat queue on top of a new verion tehse
days I run into an error like this:
MacAndrew-528-(sage-5.10)-combinat: sage -combinat install
Creating sage-combinat branch:
/usr/local/src/sage/sage-5.10/sage -b main
Hey Andrew,
Are you compiling it from source code or using the prebuilt? Because I
believe building the doc is built during the compilation. As for the
prebuilts, since sage now copies over the doc (previously it just rebuilt
it) and it may not be included in; so look in your
Hi,
here's a quick question: I'm defining some method on a class and then
redefining it on a subclass for speed improvement. (Concretely, it is
a map on the symmetric functions which I redefine on the power-sum
basis because it's easier to compute there.) What should I do with the
docstring?
Hi Simon,
thanks -- but the doctests are the least of my worries (I was going to
do what you suggested). I am trying to figure out what to do with the
docstring text that explains what the function does. If I don't
copypaste it, then calling ?? on the function won't always return the
text. If I
Hi Darij,
On 2013-06-28, Darij Grinberg darijgrinb...@gmail.com wrote:
here's a quick question: I'm defining some method on a class and then
redefining it on a subclass for speed improvement. (Concretely, it is
a map on the symmetric functions which I redefine on the power-sum
basis because
Hey Darij,
My belief/viewpoint is that the one-line will likely be about the same
since it is suppose to be a concise summery, and the more detailed
description can be linked to one abstract/base function by using
:meth:`SuperClass.foo`. I'd also suspect I'm somewhat in the minority here
On Friday, June 21, 2013 10:43:13 PM UTC+2, Dima Pasechnik wrote:
I think a decorator like this makes the code unreadable, and if it can
be avoided then it should be avoided.
+1
My opinion is very close to the one of Dima in this thread. I believe we
should avoid to spread such decorator in
Hi all,
I've been out of the Sage loop for a while, but upon upgrading to 5.10, I
found that Maxima seems to choke on the following innocuous code which used
to run fine. I'm posting this here, because this issue came up while I was
working on #10132, and also because it affects usability.
Hi!
On 2013-06-27, Simon King simon.k...@uni-jena.de wrote:
Is there currently a problem with the patchbots on trac?
According to your answers, indeed some bots went down. But now, the
colourful blobs show up again.
At #13589, we are
currently struggling against a 5% regression of startup
Hi Dima,
On Thu, Jun 27, 2013 at 10:40:07PM +, Dima Pasechnik wrote:
it seems to be some kind of ongoing project
which might be very important for you, but outsiders have no clue
what it is, it seems. Indeed, check out
http://en.wikipedia.org/wiki/Combinatorial_map :-)
As I
+lots on behalf of the Sage-Combinat community. It's been so helpful
to have someone super competent, timely, and rigorous like you!
Cheers,
Nicolas
--
Nicolas M. Thiéry Isil nthi...@users.sf.net
http://Nicolas.Thiery.name/
--
You received this message because
Dear Sage developers,
In the last two years, I have been progressively redesigning the
category infrastructure to make it scale better (#10963). For a buzz
word, it introduces axioms, which automatizes part of the
construction of the category hierarchy when there are many variants of
a
it is however might sound convincing that you basically pollute the
codebase with
stuff that only you and your collaborators know about.
This is not quite right, see
https://groups.google.com/d/topic/sage-combinat-devel/a7wq0ksV2fY/discussion
the initial discussion on this topic on
Hi Nicolas,
On 2013-06-28, Nicolas M. Thiery nicolas.thi...@u-psud.fr wrote:
Issue: this induces a small overhead in the creation of categories; in
particular, upon startup, Sage creates more than 70 categories, and
according to the patch bot this gives a startup time regression of 5%,
that
Am Freitag, 28. Juni 2013 15:14:48 UTC+2 schrieb Simon King:
And I do believe that 0.5% (hence, 8 ms) is negligible and worth paying
in this particular case, because:
Sorry for the typo. I meant to write 0.25% (which would be 4 ms on my
machine). The plugin only has
78% confidence for
Dear Sage developers,
On Fri, Jun 28, 2013 at 12:44:10PM +0200, Nicolas M. Thiery wrote:
Issue: this induces a small overhead in the creation of categories; in
particular, upon startup, Sage creates more than 70 categories, and
according to the patch bot this gives a startup time
Symbolic expressions have a .is_trivial_zero() method which is more
suitable for use here. It doesn't try anything advanced so it has
predictable runtime.
I just wanted to say that I had no idea that this function existed when I
wrote that code, and it seems like a good idea to use it
Hi Nicolas,
On 2013-06-28, Nicolas M. Thiery nicolas.thi...@u-psud.fr wrote:
Oh wow, never mind: I just read that he found the way to transform the
startup time regression into an actual improvement!
Not significantly. One patchbot found
+With 32% confidence, startup time decreased by at least
Hell !
I don't agree on the
situation for Poset, identifying a (finite) poset with its Hasse
diagram is very natural, so to_directed_graph seems to be very
natural to me.
What could possibly be wrong with the existing Poset.hasse_diagram() method
?
Where do I find this
I could try to change something... However, What is the way to provide a
patch? Is it through github?
On Friday, 28 June 2013 09:36:47 UTC-4, Joris Vankerschaver wrote:
Symbolic expressions have a .is_trivial_zero() method which is more
suitable for use here. It doesn't try anything
*Putting on my Physicist hat*
You should be taking the actual standard deviation into account, too. Most
likely, patchbot number one gave less consistent timings, possibly due to
background jobs, mechanical harddisk, or memory pressure. This is why it
failed to detect any effect, not because
I had my desktop rebooted manually.
You can't call the plugin directly, but it is very straightforward code and
it would be easy to turn it into a standalone script that just compares any
two sage trees.
--
You received this message because you are subscribed to the Google Groups
I can confirm the regression, after a few seconds I get
TypeError: ECL says: Memory limit reached. Please jump to an outer pointer,
quit program and enlarge the
memory limits before executing the program again.
The process that consumes the memory is sage-ipython (in the ECL shared
library),
Hi Volker,
On 2013-06-28, Volker Braun vbraun.n...@gmail.com wrote:
--=_Part_728_19221634.1372430567336
Content-Type: text/plain; charset=ISO-8859-1
*Putting on my Physicist hat*
You should be taking the actual standard deviation into account, too. Most
likely, patchbot number one
Hi Volker,
On 2013-06-28, Volker Braun vbraun.n...@gmail.com wrote:
You can't call the plugin directly, but it is very straightforward code and
it would be easy to turn it into a standalone script that just compares any
two sage trees.
This would be nice to have! As I wrote on the other
On Friday, June 28, 2013 5:09:49 AM UTC-7, Joris Vankerschaver wrote:
Hi all,
Is there something I can do to avoid this?
I tried this in Maxima 5.25.1 and 5.28.02
You can avoid this problem by just using one of those versions of Maxima
directly.
I suspect, but do not know,
On Friday, June 28, 2013 10:56:48 AM UTC-4, Simon King wrote:
This would be nice to have! As I wrote on the other thread, I took 20
samples of sage -startuptime without and 20 with the patches, but I
am not totally confident how to interprete it.
Yes, especially since it turns out to be
See the other
thread https://groups.google.com/d/msg/sage-devel/s-LAqd0pXlg/XVX0xQLAS9IJ
On Friday, June 28, 2013 10:54:50 AM UTC-4, Simon King wrote:
Speaking about statistics: On my own machine, I made 20 runs of
sage -startuptime with (1) only the dependencies of the ticket
applied,
Hi Volker,
On 2013-06-28, Volker Braun vbraun.n...@gmail.com wrote:
Yes, especially since it turns out to be not to approximate a normal
distribution particularly well. The patchbot does a non-parametric test:
http://en.wikipedia.org/wiki/Mann%E2%80%93Whitney_U
Thanks!
--
You received
On Fri, Jun 28, 2013 at 5:25 AM, Simon King simon.k...@uni-jena.de wrote:
Hi!
On 2013-06-27, Simon King simon.k...@uni-jena.de wrote:
Is there currently a problem with the patchbots on trac?
According to your answers, indeed some bots went down. But now, the
colourful blobs show up again.
What could possibly be wrong with the existing Poset.hasse_diagram()
method ?
Nothing.
Well. It's a bit hard to grep the conversions that can be obtained from
the constructors, though :-P
All I wanted to show is that we didn't invent the to_??? methods which
you call unusual Sage
Hellooo !
but I do think that this .to_partition() and .to_graph() are not valuable
to Sage
My impression is that you only care because it is your graph code.
I think that I would have said the same if you had patched any other class,
but I look closely at what happens to graphs in Sage,
On 2013-06-28, Christian Stump christian.st...@gmail.com wrote:
--=_Part_74_1772145.1372424392980
Content-Type: text/plain; charset=ISO-8859-1
it is however might sound convincing that you basically pollute the
codebase with
stuff that only you and your collaborators know about.
This
33 matches
Mail list logo
