> Ok, I'll have a look at frobby! Just to check, I installed Macaulay2 and
> did the same computation and it gave me the right answer...
>
CoCoA might also compute the correct answer, as I believe CoCoA switches
silently to bigint whenever it notices the need. I don't think Sage
supports CoC
Very good!
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.co
On Friday, May 22, 2015 at 6:13:28 PM UTC+2, kcrisman wrote:
>
>
> http://git.sagemath.org/sage.git/diff/?id=75ab6f97a1bcf94a6fe4eb30d84dade96830b802
>
> - related to http://trac.sagemath.org/ticket/1 and if you go up the
> commit tree a little you see something about a "temporary merge".
On Friday, 22 May 2015 10:16:12 UTC-6, mmarco wrote:
>
> I think i could get a VM inside a quad corte xeon in universidad de
> Zaragoza. Although they have a policy about only hosting services in the
> same domain name. I guess it wouldn't be a big problem to be cakes called
> sagecell.unizar.es
On Thursday, 21 May 2015 19:54:52 UTC-6, William wrote:
>
> On Thu, May 21, 2015 at 4:50 PM, Andrey Novoseltsev > wrote:
> > If anyone in North America can provide a server instead of GCE that also
> > would be fantastic. The current setup on GCE will cost about $1000/year
>
> Andrey, did you h
I think i could get a VM inside a quad corte xeon in universidad de Zaragoza.
Although they have a policy about only hosting services in the same domain
name. I guess it wouldn't be a big problem to be cakes called sagecell.unizar.es
--
You received this message because you are subscribed to th
> The object is not on the git server (or not referenced by a branch).
>
> $ git show 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
> fatal: bad object 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
>
> If you pushed something while the git repo was out of disk space then it
> was NOT uploaded
>
>>
>>
The
Congratulations to everyone involved!
Cheers,
basu.
On Wednesday, May 20, 2015 at 5:47:27 AM UTC+8, Nicolas M. Thiéry wrote:
>
>Dear Sage developers,
>
> We are delighted to announce that the Horizon 2020 research proposal
> OpenDreamKit was accepted by the European commission:
>
>
Dear John,
Ok, I'll have a look at frobby! Just to check, I installed Macaulay2 and
did the same computation and it gave me the right answer... So I could
interface my code, but this is not the optimal way. If it is a bug, it
should be looked at and repaired...
Best,
Jean-Philippe
Le jeudi 2
The object is not on the git server (or not referenced by a branch).
$ git show 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
fatal: bad object 2341c22ee7ce66cd1cf80949b1a7c9a4f6e5431f
If you pushed something while the git repo was out of disk space then it
was NOT uploaded
On Thursday, May 21, 20
On 22/05/15 13:03, David Joyner wrote:
On Fri, May 22, 2015 at 3:46 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
Hello,
On 22/05/15 04:33, Rob Beezer wrote:
The code below fails on 6.7 with a RuntimeError.
r = 2
C = codes.HammingCode(r, GF(2))
C.minimum_distance()
This is
On Fri, May 22, 2015 at 3:46 AM, Vincent Delecroix
<20100.delecr...@gmail.com> wrote:
> Hello,
>
>
>
> On 22/05/15 04:33, Rob Beezer wrote:
>>
>> The code below fails on 6.7 with a RuntimeError.
>>
>> r = 2
>> C = codes.HammingCode(r, GF(2))
>> C.minimum_distance()
>
>
> This is a bug in the algori
It seems the trac/git failure was not caused by the lack of space on /tmp
as it is still dysfunctional.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel
Hi Herbert
On 2015-05-20, Simon King wrote:
> Yes, the failures seem mostly harmless now. Nonetheless, I wish Hilbert
> driven computation would work (it is much faster than without Hilbert
> series).
I have updated p_group_cohomology-2.1.5.spkg. Now, there should only
remain two test failures t
Hello,
On 22/05/15 04:33, Rob Beezer wrote:
The code below fails on 6.7 with a RuntimeError.
r = 2
C = codes.HammingCode(r, GF(2))
C.minimum_distance()
This is a bug in the algorithm since it does not handle the case where
all your vectors have non zero entries. It might be because of me i
15 matches
Mail list logo
