> took about 10 second. Of course this would be faster if we can integrate code
> more directly; propably only milliseconds if glued together with
> static_sparse_graph.pyx.
If would be very cool to have such timings in Sage indeed, though even
there knowing that most of the computation time is
On Thu, 28 Aug 2014, Nicolas M. Thiery wrote:
Posets(5)
which internally does something like
[x for x in GenerateAllDirectedGrapsh(5) if x.is_poset()]
Semantically, this is correct. Luckily the implementation is more
clever than this: it only runs through digraphs that are actually
Hasse di
On Tue, 2 Sep 2014, Nathann Cohen wrote:
Because it is (mostly) irrelevant. Just as users should not be bothered
by things like "There is a SSD disk in this computer" or "Calculations
are actually executed on cloud" or "This mail was delivered with SMTP
protocol".
It's a point of faith, I b
> Because it is (mostly) irrelevant. Just as users should not be bothered by
> things like "There is a SSD disk in this computer" or "Calculations are
> actually executed on cloud" or "This mail was delivered with SMTP protocol".
It's a point of faith, I believe. I feel that we owe users a good
On Tue, 2 Sep 2014, Nathann Cohen wrote:
But at least user should not see details like "There was an error in
code three years ago. We show that it is corrected by...".
Why shouldn't we see it ?
Because it is (mostly) irrelevant. Just as users should not be bothered by
things like "There i
Y !
> I think that this is bad from user viewpoint.
>
> In the ideal world things would "just work". For a software like this it
is
> not possible --- there will always be notes of implemtation details and
> limits of algorithms somewhere. But at least user should not see details
> lik
On Tue, 2 Sep 2014, Nathann Cohen wrote:
I would say that it should be the union of the two. Some examples are
meant to the users, some are meant to test past bugs that we fixed, and
we do not want to lose that.
I think that this is bad from user viewpoint.
In the ideal world things would "j
Hello !
> And how is documentation supposed to be?
>
> As I said, has_top() has same examples. mobius_function(x, y) has one common
> example. mobius_function_matrix() has totally different examples.
> open_interval() has basically same example.
I would say that it should be the union of the tw
On Tue, 2 Sep 2014, Nathann Cohen wrote:
If there is a Poset function which is an exact copy of the HasseDiagram
function, is there any reason for not removing the HasseDiagram one ?
And how is documentation supposed to be?
As I said, has_top() has same examples. mobius_function(x, y) has one
>
> My understanding is Hasse diagram is the back-end digraph for the poset
>> and many of the methods don't want to be inherited/exposed. However I'm not
>> completely sure why that particular the design decision was made.
>>
>
If there is a Poset function which is an exact copy of the HasseDia
>
>
> For example view(Poset( ([1,2,3,4,5], [[1,2],[1,3],[3,4],[2,5],[4,5]]) ),
> tightpage=True) does nothing.
>
It takes a few seconds to feed it to my pdf viewer, but it works for me
(and I have installed the dot2tex optional spkg).
>
> OK, maybe I understood a little of that.
>
> But th
On Mon, 25 Aug 2014, Travis Scrimshaw wrote:
IIRC most of the doc is in the header of some module... just use view(P,
tightpage=True), it uses dot2tex if you install the optional spkg (with
sage -i dot2tex). IMO the output is much prettier.
For example view(Poset( ([1,2,3,4,5], [[1,2],[1,3],[
On Mon, Aug 25, 2014 at 11:14:09AM +0300, Jori Mantysalo wrote:
> Posets(5)
>
> which internally does something like
>
> [x for x in GenerateAllDirectedGrapsh(5) if x.is_poset()]
Semantically, this is correct. Luckily the implementation is more
clever than this: it only runs through digraphs tha
Hey Jori,
>
> OK. I have used to using html docs, but this of course varies.
>
Of course (although I should be a little more honest and state that my
viewpoint comes primarily from people who I've told to use the `?`).
>
> Neither way, at least .show() function for poset does not tell about
>
On Mon, 25 Aug 2014, Travis Scrimshaw wrote:
In my experience, most people read the documentation in Sage using `?`
rather than the reference manual. So it's not a matter of where the method
is defined (you can think of the category like an ABC in this case).
OK. I have used to using html docs
Hey Jori,
The short version why is_lattice is in the category is that *every*
finite poset can check if is a lattice (if it has implementations to check
if it's a join and meet semilattice). In fact, I would argue that there are
many methods of the current implementation of FinitePoset (with
16 matches
Mail list logo
