On Mon, 8 Jun 2015, Viviane Pons wrote:
if your code only depends on general mathematical properties of posets
and not on the specific implementation of the poset object, then it
should be in the category.
Then I guess is_bounded should be in the category. But this has been
discussed
Hi everyone,
I'm doing this:
sage: FreeA.a,b,c,d,e,f = FreeAlgebra(QQ,implementation=letterplace)
sage: P = a*b*a*c*c*b + a*b*a*d*d*b + a*c*a*d*d*c + b*c*b*d*d*c
sage: X = P.lm()
sage: X
a*b*a*c*c*b
And now I would like a way to cut my element X into two factors of a
given size. Something like
I'd appreciate if you would keep that page where it is.
I don't doubt it. But perhaps you should stop considering Sage's
website as a convenient way to store your pages. It strikes me at the
moment that I am the one trying to rearrange sage-combinat's and
mupad-combinat's bibliography, while
Sorry for being slow. I just tried to make FindStatMap inherit from
Morphism, and create its parent on the fly (because the parent doesn't do
all that much anyway) with
Morphism.__init__(self, homset(self.domain(), self.codomain())
However, sage complains that homset wants a parent (and
Sage-Combinat is part of Sage. Sage-Combinat's website is a page on
the Sage wiki. The Sage-Combinat's NSF grant benefited Sage at large.
I don't see the point of suddenly having to duplicate the
infrastructure.
Yeah. But Mupad-combinat is none of that, yet you expect us to host it.
Also, I
On Mon, Jun 08, 2015 at 09:51:36AM +0200, Nathann Cohen wrote:
I did not propose to remove sage-combinat's publications list (which
will be merged on a common page), I was only talking about
mupad-combinat.
Indeed. But Anne raised a point which I had overseen: the URL
initially I tried to install via git as described here
http://trac.sagemath.org/wiki/Cygwin64Port but, because I have a very poor
internet connection behind some company firewalls I dit not suceed with git
clone git://trac.sagemath.org/sage.git. So I downloaded sage-6.7.tar.gz
Hi Martin,
Le lundi 8 juin 2015 10:04:08 UTC+2, Martin R a écrit :
Sorry for being slow. I just tried to make FindStatMap inherit from
Morphism, and create its parent on the fly (because the parent doesn't do
all that much anyway) with
Morphism.__init__(self, homset(self.domain(),
On Mon, Jun 08, 2015 at 09:48:17AM +0200, Nathann Cohen wrote:
I don't doubt it. But perhaps you should stop considering Sage's
website as a convenient way to store your pages. It strikes me at the
moment that I am the one trying to rearrange sage-combinat's and
mupad-combinat's bibliography,
Documentation on posets.py seems to say that show() accepts some
parameters in itself and others to be forwarded to plot(). But is there
really anything on the first class?
Or to put it other way: can documentation of show() be simplified to
something like Display the Hasse diagram of the
When reading graph_plot.py doc [1], I thought figsize was accepted by show
but not by plot:
sage: from sage.graphs.graph_plot import DEFAULT_PLOT_OPTIONS,
DEFAULT_SHOW_OPTIONS
sage: [o for o in DEFAULT_SHOW_OPTIONS if o not in DEFAULT_PLOT_OPTIONS]
['figsize']
but when I do the following, I
There is some discussion at http://trac.sagemath.org/ticket/18534 . Maybe
this could be a topic in this sage-devel list also.
For now there is no list of what can I do with these posets -functions.
That's because we have, for example, is_connected() on
.../combinat/posets/posets.py and
Isn't it possible to just remove the link to the mupad page from the menu
without removing the page? Then the page would only be accessible from the
combinat page, which makes sense.
And the link is the following: https://github.com/sagemath/website/pull/46
Honestly, I cannot see the cost of
IMHO running Cygwin without admin rights is next to impossible :(
On Monday, 8 June 2015 11:15:33 UTC+1, Stefan Auracher wrote:
initially I tried to install via git as described here
http://trac.sagemath.org/wiki/Cygwin64Port but, because I have a very
poor internet connection behind some
Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit :
In the past I had the same experience. I did it but in the last years, but
it was really difficult. But recently I tried an install of cygwin with the
setup-x86_64.exe --no-admin switch and it worked very well wihout any
In the past I had the same experience. I did it but in the last years, but
it was really difficult. But recently I tried an install of cygwin with the
setup-x86_64.exe --no-admin switch and it worked very well wihout any
problems. The recent problems with installation of sage are really my
Le lundi 8 juin 2015 14:22:20 UTC+2, Jean-Pierre Flori a écrit :
Le lundi 8 juin 2015 13:54:01 UTC+2, Stefan Auracher a écrit :
In the past I had the same experience. I did it but in the last years,
but it was really difficult. But recently I tried an install of cygwin with
the
Documentation on sagemath.org works. In my own machine, where Sage is
compiled from source taken from git, it works when loading local www-page:
Return True if x is greater than but not equal to y in the poset, and
False otherwise.
And then after loading is completed, changes to
Return True
On Mon, 8 Jun 2015, Sébastien Labbé wrote:
When reading graph_plot.py doc [1], I thought figsize was accepted by show
but not by plot: - - So, the question is still open.
Just the same issue that I found...
There might be something like axes_*() or so, but they will do nothing (or
do
Hi Nathann,
Isn't it possible to just remove the link to the mupad page from the menu
without removing the page? Then the page would only be accessible from the
combinat page, which makes sense. Honestly, I cannot see the cost of
hosting a html page on a related former project...
Best
Viviane
Yo,
I disagree with that. There's some advantage: if your code only depends on
general mathematical properties of posets and not on the specific
implementation of the poset object, then it should be in the category.
Absolutely no code in poset.py depends on the actual implementation.
This is
Hello guys,
I don't know anything about Poset's show/plot functions. For Graph.plot(),
however, it is true that it is never said explicitly that additional
parameters will be forwarded to matplotlib. It is done in Graph.show? but
not in Graph.plot?.
I'll patch that soon.
Nathann
--
You
2015-06-08 9:51 GMT-05:00 Nathann Cohen nathann.co...@gmail.com:
To me it is not a problem of doc but a problem of code. The issue is that
we have 99% of the poset functions in the poset/ folder, and a couple of
them in the category/ folder. If we move everything to posets, there's no
2015-06-08 10:14 GMT-05:00 Nathann Cohen nathann.co...@gmail.com:
Yo,
I disagree with that. There's some advantage: if your code only depends
on
general mathematical properties of posets and not on the specific
implementation of the poset object, then it should be in the category.
To me it is not a problem of doc but a problem of code. The issue is that
we have 99% of the poset functions in the poset/ folder, and a couple of
them in the category/ folder. If we move everything to posets, there's no
problem. I don't see any advantage in having poset code in a file that is
How to do this ?
I found in ~/sage-6.7/src/module_list.py
Extension('sage.rings.polynomial.pbori',
sources = ['sage/rings/polynomial/pbori.pyx'],
libraries=['polybori-' + polybori_major_version,
'polybori_groebner-' + polybori_major_version,
Le lundi 8 juin 2015 18:02:46 UTC+2, Stefan Auracher a écrit :
How to do this ?
I found in ~/sage-6.7/src/module_list.py
Extension('sage.rings.polynomial.pbori',
sources = ['sage/rings/polynomial/pbori.pyx'],
libraries=['polybori-' + polybori_major_version,
27 matches
Mail list logo
