On 10/27/07, David Joyner <[EMAIL PROTECTED]> wrote:
> Is the following a feature or a bug?
>
> sage: set([1,2])
> set([1, 2])
> sage: set([[1],[2]])
> ---
> Traceback (most recent call last)
>
> /Users/wdj/sagef
Hello,
My new(er) Permutations combinatorial class should handle things correctly.
sage: MS = MatrixSpace(QQ, 2, 2)
sage: A = MS([1,2,3,4])
sage: Permutations(A.rows()).list()
[[(1, 2), (3, 4)], [(3, 4), (1, 2)]]
sage: MS = MatrixSpace(GF(2),2,2)
sage: A = MS([1,2,3,4])
sage: Permutations(A.rows
Hi:
Either a bug in combinat.py's permutations, or an indication that
it needs to be rewritten. (permutations is a GAP wrapper which
I might have written, so should probably fix ...)
- David Joyner
sage: MS = MatrixSpace(QQ,2,2)
sage: A = MS([1,2,3,4])
sage: permutations(A.rows())
[[(3, 4), (1,
Hi:
Is the following a feature or a bug?
sage: set([1,2])
set([1, 2])
sage: set([[1],[2]])
---
Traceback (most recent call last)
/Users/wdj/sagefiles/sage-2.8.2/ in ()
: list objects are unhashable
(Set also
Dear Jonathan,
> I suspect that part of the reason for this is that cpu time spent in the
> maxima process is not counted by 'time'. (Because it is going on in a
> different process.)
OK, this explains why there is some difference of CPU and Wall time.
However, it does not explain why the differ
On Sat, 2007-10-27 at 12:03 -0700, Simon King wrote:
> Problem was:
> i) When i computed some cup product out of copies of these cocycles,
> then the CPU time was 0.4s, but the Wall time 2.2s. I think this is an
> inacceptable overhead.
I suspect that part of the reason for this is that cpu tim
Dear sage-support team,
in a recent post, i reported a phenomenon that i met when i was using
log: When i repeat a computation then the Wall time rapidly increases
while the CPU time is about constant in each repetition.
My original code would be far too long, but i succeeded to produce
reasonab
Dear Mike,
> > I don't think that anything is really going wrong. There is overhead
> > when talking to Maxima through the pexpect interface. You should post
> > the code you are running to see if it can be optimized (with respect
> > to the maxima interface).
>
> In a nutshell, the code was ..
