Thanks for the suggestions. In my application (and perhaps in many others)
I do not care what order the diagonal entries are in (pari's convention is
that the largest is top left, while most others put the smallest there).
So I am working directly with the pari matrices and bypassing this function
The attached file defines a list of lists of integers and forms a 100 x 2
matrix M from it, successfully, but print(M) shows a lot of garbage.
John
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving
Actually, I think that it's the .sage() call which is already taking a
long time:
sage: M = MatrixSpace(ZZ,1000,5).random_element()
sage: %time res = M.__pari__().matsnf(1)
CPU times: user 68 ms, sys: 0 ns, total: 68 ms
Wall time: 68.7 ms
sage: %time v = res.sage()
CPU times: user 4.03 s, sys: 2
Part of the problem (but certainly not all of it) is
https://trac.sagemath.org/ticket/26463
Sage was executing "from sage.rings.integer import Integer" 100 times.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group
Thanks for taking the time for timings!
Since there is an already implemented conversion
PARI integer -> gmp integer (INT_to_mpz function in
sage.libs.pari.convert_gmp) we should use it for
converting dense integer matrices at C level.
Le 11/10/2018 à 11:38, Jeroen Demeyer a écrit :
Actually, I
I see no garbage in jupyter notebook with sage 8.4.beta1 on mac.
--
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 t
On Thu, 11 Oct 2018 at 14:21, Kwankyu Lee wrote:
> I see no garbage in jupyter notebook with sage 8.4.beta1 on mac.
>
If I do %runfile t.py what I see is
sage: %runfile t.py
[ 1
0]
[ 0
1]
[
I see that too. What is garbage about that? I haven't checked all entries,
but many entries look like what is part of the input.
It is a bit suspicious that a lot of the entries are so close to 128 bits,
and not more than that, but that's part of the input you're providing.
Are you unhappy about
On Thu, 11 Oct 2018 at 18:03, Nils Bruin wrote:
> I see that too. What is garbage about that? I haven't checked all entries,
> but many entries look like what is part of the input.
>
Nils you are. garbage in , garbage out. I think I had a bug in the code
producing the list-of-lists, as those nu
