> I'd have to check carefully. There's likely to be some performance loss > even when all obvious bottlenecks are accounted for, because for our > special classes BinaryMatrix, TernaryMatrix, QuaternaryMatrix we use inline > get() and set() methods that bypass the Sage finite field elements. We want > this code to push the limits of matroid computation, so we'd hate to incur > even a 10% speed loss. >
Oh, we also use bitpacking for GF(3) and GF(4), which in Sage is done only for binary matrices currently, if I'm not mistaken. -- 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.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
