I've added this into Trac. http://trac.sagemath.org/sage_trac/ticket/5135
Jason - thanks for the heads-up on 3058. William - someplace you *have* to turn rows into columns. ;-) In my book, I think it is all buried into "column space of A = row space of transpose(A)" or something similar. Would it be worthwhile to move most of the basis construction into right_kernel()? Right now, a call to right_kernel() does two transposes. With a change, left_kernel() would still do a transpose, but then call right_kernel(). kernel() could then be a call to left_kernel(). On Jan 28, 4:24 pm, Jason Grout <jason-s...@creativetrax.com> wrote: > Rob Beezer wrote: > > William, > > >> I think the right change for your application would be to change this > >> line in left_kernel: > > >> W = V.submodule(basis) > > >> to > > >> if echelonize: > >> W = V.submodule(basis) > >> else: > >> W = V.submodule_with_basis(basis) > > >> then put an echelonize=True option in the left_kernel function header. > > >> William > > Just FYI, I think there is still an issue sometimes when using > user-defined bases: > > http://trac.sagemath.org/sage_trac/ticket/3058 > > Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
