On Fri, 29 May 2015, Nathann Cohen wrote:
I did P6=Posets(6).list() and then for 4 time
I ran the code you give, and instead of 33s I get 94ms :-P
sage: P6=Posets(6).list()
sage: %timeit for P in P6:g=P.hasse_diagram()
10 loops, best of 3: 94.2 ms per loop
OK, so it's dot2tex (I guess
>
> I did P6=Posets(6).list() and then for 4 time
>
I ran the code you give, and instead of 33s I get 94ms :-P
sage: P6=Posets(6).list()
sage: %timeit for P in P6:g=P.hasse_diagram()
10 loops, best of 3: 94.2 ms per loop
sage: %timeit for P in P6:g=P.hasse_diagram()
10 loops, best of 3: 97.2 ms
I did P6=Posets(6).list() and then for 4 time
%timeit
for P in P6:
g=P.hasse_diagram()
and got
CPU time: 28.67 s, Wall time: 33.25 s
CPU time: 35.25 s, Wall time: 38.82 s
CPU time: 42.67 s, Wall time: 46.22 s
CPU time: 52.55 s, Wall time: 56.22 s
Anybody have an idea about what is happ
Thanks Jan! I was having the same issue with 6.7. The 6.6 deb you posted
installed fine.
Best,
Dow Drake
On Friday, May 29, 2015 at 8:42:26 AM UTC-7, Jan Groenewald wrote:
>
> The sage installation tree has moved is *probably* unrelated. It always
> says that on upgrade. I suspect two possibi
On May 28, 2015, at 04:33 , Jason Grout wrote:
> On 5/27/15 22:09, Jason Grout wrote:
>> On 5/27/15 18:38, Justin C. Walker wrote:
>>> Are you building multi-threaded?
>>>
>>
>> Interestingly, this may be the problem. When I do:
>>
>> export MAKE="make -j1"
>>
>> and then build, it seems lik
I noticed that earlier today, its fixed now.
On Friday, May 29, 2015 at 5:24:49 PM UTC+2, Ivan Andrus wrote:
>
> I’m afraid I can’t help you with it’s (lack of) presence on the mirror
> servers. I’ve CC’d sage-devel for that. In the mean time, you should be
> able to install it from the bitb
If you want to know exactly how it is currently working, it is this one line
https://github.com/sagemath/sage_trac_plugin/blob/dddc41b60a7620ebe0e224973497d83c719d9cd9/sage_trac/git_merger.py#L92
(the rest of that function deals with trivial merges, and writing
unreferenced objects back to trac's
On 29/05/15 17:46, Marc Mezzarobba wrote:
Fredrik Johansson's "Arb" library hasn't been an optional package for a
full year yet, but Volker already suggested fast-tracking it to standard
a while ago[1], and the (few) replies to his message were positive.
Doing it now would make the development of
Go for it!
John
On 29 May 2015 at 16:46, Marc Mezzarobba wrote:
> Hi,
>
> Fredrik Johansson's "Arb" library hasn't been an optional package for a
> full year yet, but Volker already suggested fast-tracking it to standard
> a while ago[1], and the (few) replies to his message were positive.
> Doi
Hi,
Fredrik Johansson's "Arb" library hasn't been an optional package for a
full year yet, but Volker already suggested fast-tracking it to standard
a while ago[1], and the (few) replies to his message were positive.
Doing it now would make the development of the sage bindings a bit
easier. Do
The sage installation tree has moved is *probably* unrelated. It always
says that on upgrade. I suspect two possibilities
1) it is from Thierry's binary not a buildslave binary
2) I changed the dpkg-source format from quilt to native to solve (1)'s
impact on dpkg, and at the same time removed .git
On Friday, May 29, 2015 at 2:50:02 PM UTC+1, Jan Groenewald wrote:
>
> Hi
>
> I'm working on this but compressing, building debs, and uploading takes
> quite long. Any feedback on any new version working or not working is
> useful.
>
> If I don't have it working by end of weekend I'll probably re
I’m afraid I can’t help you with it’s (lack of) presence on the mirror servers.
I’ve CC’d sage-devel for that. In the mean time, you should be able to
install it from the bitbucket spkg.
sage -i https://bitbucket.org/gvol/sage-mode/downloads/sage_mode-0.14.spkg
-Ivan
> On May 28, 2015, at 4
Hi
I'm working on this but compressing, building debs, and uploading takes
quite long. Any feedback on any new version working or not working is
useful.
If I don't have it working by end of weekend I'll probably revert to 6.6
with a version number like 6.7ppa14revertsage6.6 in the PPA and make a
> I have been doing some documentation polishing to functions of posets and
> lattices. (For example http://trac.sagemath.org/ticket/18489 )
>
> Should they be ticket on "documentation" or in "combinatorics"?
>
>
Probably wherever you think it's more likely that people who will review it
will
I have been doing some documentation polishing to functions of posets and
lattices. (For example http://trac.sagemath.org/ticket/18489 )
Should they be ticket on "documentation" or in "combinatorics"?
--
Jori Mäntysalo
Hi,
Same problem on Linux Mint 17 with the new version in the ppa
(sagemath-upstream-binary_6.7ppa6_amd64.deb). As in the other cases, Sage
was working perfectly fine yesterday. Thank you all,
(Reading database ... 383085 files and directories currently installed.)
Preparing to unpack .../sagem
Hi,
same issue here on Kubuntu 14.04.2
best,
cri
Am Donnerstag, 28. Mai 2015 11:52:28 UTC+2 schrieb Denny Fuchs:
>
> hi,
>
> I wanted to upgrade the system (Linux Mint 17), but SageMath
> "sagemath-upstream-binary" fails:
>
>
> =
> # aptitude upgrade
> The following partially in
Hi,
I have exactly the same issue on Kubuntu 14.04.2
best
cri
Am Donnerstag, 28. Mai 2015 11:52:28 UTC+2 schrieb Denny Fuchs:
>
> hi,
>
> I wanted to upgrade the system (Linux Mint 17), but SageMath
> "sagemath-upstream-binary" fails:
>
>
> =
> # aptitude upgrade
> The following
On Thu, 28 May 2015, Travis Scrimshaw wrote:
But it will be reversed then. A.is_subgraph(B) means that B is bigger
one, but here A.is_sublattice(B) would mean that A is bigger one and B
is the subset.
Ah, yes; good point. How about is_superlattice() then?
As superlattice does not to seem u
20 matches
Mail list logo