>> sage: %crun -s cumlative BIBD_45_9_8(True)
>> /home/ncohen/.Sage//sage: line 134: 3174 Profiling timer expired
>> "$SAGE_ROOT/src/bin/sage" "$@"
>
> I got a similar error from time to time. I have no idea how it is
> triggered.
Ticket 19185 apparently fixes it. And I hope that it will also fix
Hi Nathann,
On 2015-09-10, Nathann Cohen wrote:
> It is still relatively easy to make this %crun crash, though:
>
> sage: %crun -s cumlative BIBD_45_9_8(True)
> /home/ncohen/.Sage//sage: line 134: 3174 Profiling timer expired
> "$SAGE_ROOT/src/bin/sage" "$@"
I got a similar error from time to t
Helloo again,
With this other code cleared, and I went back to this problem. You
were indeed right, I was missing the executable -_-
For some reason it was not here anymore, well. I installed it, and it
did its job. Most of the time seems to be spend on free module
elements, which is "expected",
Hi Nathann,
On 2015-09-10, Nathann Cohen wrote:
>> Seriously? At first, it crashed Sage with an error message asking me to
>> install some package---which my OS did not know. Volker eventually told
>> me that I have to install -devel...
>
> But I know that I have all the packages, for it worked i
> Seriously? At first, it crashed Sage with an error message asking me to
> install some package---which my OS did not know. Volker eventually told
> me that I have to install -devel...
But I know that I have all the packages, for it worked in the past.
> Anyway, if it crashes, I think you should
On 2015-09-10, Simon King wrote:
> At first, it crashed Sage with an error message asking me to
> install some package---which my OS did not know. Volker eventually told
> me that I have to install -devel...
Now I recall: The error mentioned gperftools, but I had to install
gperftools-devel.
--
Hi Nathann,
On 2015-09-10, Nathann Cohen wrote:
>> Perhaps %crun helps?
>
> Ahahaa. Well I gave it a try and it crashed Sage every time without
> any error message. Didn't feel like debugging this now ^^;
Seriously? At first, it crashed Sage with an error message asking me to
install some packag
> Perhaps %crun helps?
Ahahaa. Well I gave it a try and it crashed Sage every time without
any error message. Didn't feel like debugging this now ^^;
"perf top" does not say much either.
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
Hi Nathann,
On 2015-09-10, Nathann Cohen wrote:
> HMmm... The odd thing is that %prun does not say much about what the
> bottleneck is in those computations. It seems that GAP works in the
> background, but I do not see it there ...
Perhaps %crun helps?
Best regards,
Simon
--
You received thi
Hello !
> There is no significantly faster method than trying all possibilities.
> Finding the minimum-weight codewords of a linear code is a hard problem.
> Since your code is not too big, the naive method takes only a few seconds.
Thanks for your answer. As it takes something like 40s a
Hi Nathann,
There is no significantly faster method than trying all possibilities.
Finding the minimum-weight codewords of a linear code is a hard problem.
Since your code is not too big, the naive method takes only a few seconds.
There are clever algorithms (still exponential) for computing th
11 matches
Mail list logo
