Opened 11 years ago
Closed 11 years ago
#5882 closed enhancement (fixed)
[with patch, positive review] implement general package for finitely generated not-necessarily free R-modules
Reported by: | was | Owned by: | was |
---|---|---|---|
Priority: | major | Milestone: | sage-4.1 |
Component: | linear algebra | Keywords: | |
Cc: | jhpalmieri, davidloeffler, bantieau | Merged in: | sage-4.1.rc0 |
Authors: | William Stein, David Loeffler | Reviewers: | Robert Miller, John Palmieri |
Report Upstream: | Work issues: | ||
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description (last modified by )
I *really* need this for my research.
Note, I only really need the case R=ZZ, and what I'll implement is likely to be this for any R that has a Smith normal form algorithm, e.g., class number 1.
I am finding and fixing some major bugs in basic linear algebra that have to be fixed in order to implement this. Thus this patch depends on: #5886, #5887, #5972, #5974
Attachments (8)
Change History (57)
comment:1 Changed 11 years ago by
- Description modified (diff)
comment:2 Changed 11 years ago by
- Description modified (diff)
comment:3 Changed 11 years ago by
comment:4 Changed 11 years ago by
- Cc jhpalmieri added
comment:5 Changed 11 years ago by
- Type changed from defect to enhancement
comment:6 Changed 11 years ago by
This is likely ready for review, but I want to do some additional testing before labeling it as such.
comment:7 Changed 11 years ago by
- Summary changed from implement general package for finitely generated not-necessarily free R-modules to [with patch; needs review] implement general package for finitely generated not-necessarily free R-modules
comment:8 Changed 11 years ago by
- Summary changed from [with patch; needs review] implement general package for finitely generated not-necessarily free R-modules to [with patch; not ready for review] implement general package for finitely generated not-necessarily free R-modules
I've changed this back to "not ready for review", since I think it's more likely to be higher quality code if I implement something nontrivial on top of it first, and fix any issues I find. So I'm doing #5969 first. Once that's done and I fixed all issues that crop up, then #5882 will be ready for review.
comment:9 Changed 11 years ago by
The one remaining problem: Some of the bug fixes in linear algebra included in this patch (or possibly, but unlikely, the dependency patches), cause a serious performance regression:
IN SAGE-3.4.1:
sage: time EllipticCurve('858k2').sha().an_padic(Integer(7)) CPU times: user 8.65 s, sys: 0.37 s, total: 9.02 s
After these patches the same takes much much longer (many minutes). Using set_verbose(2)
one sees that the codepaths are different.
It's not surprising that fixing bugs would uncover other buggy code and major performance issues, since buggy code is often very fast :-).
comment:10 Changed 11 years ago by
- Description modified (diff)
comment:11 Changed 11 years ago by
With these patches and dependencies installed, make ptestlong:
All tests passed! Timings have been updated. Total time for all tests: 331.9 seconds wstein@sage:~/build/sage-3.4.2.rc0$
comment:12 Changed 11 years ago by
It turns out there is a bug in 5882 still. In the following example, computing the kernel of f is wrong, because f somehow gets defined by a map on free modules V-->V that doesn't preserve the W's that we're quotienting out by. Trac 5882 is basically the ultimate generalization of that round2 problem everybody was confused by in 583 last quarter -- it's hard to get right!
sage: V = span([[1/14,3/14],[0,1/2]],ZZ); W = ZZ^2 sage: Q = V/W sage: f = Q.hom([Q([1,11]), Q([1,3])]) sage: f Morphism from module over Integer Ring with invariants (2, 14) to module with invariants (2, 14) that sends the generators to [(1, 11), (1, 3)] sage: f.kernel() Finitely generated module V/W over Integer Ring with invariants (14) sage: f.image() Finitely generated module V/W over Integer Ring with invariants (14) sage: f._phi Free module morphism defined by the matrix [ 11 -10] [ 3 -2] Domain: Free module of degree 2 and rank 2 over Integer Ring User basis ... Codomain: Free module of degree 2 and rank 2 over Integer Ring Echelon ... sage: R = Q.optimized()[0]; R Finitely generated module V/W over Integer Ring with invariants (2, 14) sage: f._phi(R.W()).is_submodule(W) False
comment:13 Changed 11 years ago by
Any chance you could combine the 7 (!) patches into one? That will make it a lot easier to read & judge, and to apply, of course!
comment:14 follow-up: ↓ 23 Changed 11 years ago by
Any chance you could combine the 7 (!) patches into one? That will make it a lot easier to read & judge, and to apply, of course!
Yes, I will, when it is ready for review.
Also, I'll rename the V, W methods to cover and relations, with C() and R() as aliases.
comment:15 Changed 11 years ago by
- Cc davidloeffler added
comment:16 Changed 11 years ago by
- Cc bantieau added
comment:17 Changed 11 years ago by
I like what I see in this patch. Especially the ability to lift an element of a quotient. Using this, one can create the long exact sequence associated to an exact sequence of chain complexes.
Changed 11 years ago by
this one patch is based against 4.0.2.rc3. it replaces the 8 patches from before.
comment:18 Changed 11 years ago by
- Summary changed from [with patch; not ready for review] implement general package for finitely generated not-necessarily free R-modules to [with patch; needs review] implement general package for finitely generated not-necessarily free R-modules
OK, this should get reviewed. I think it's probably quite *slow* right now -- I make no claims to speed at all. But as far as I know it is right.
comment:19 Changed 11 years ago by
- Reviewers set to Robert Miller
Since underscore methods don't show up under ReST documentation, I think all the documentation which falls under __init__
methods should be either moved or copied to the class level documentation.
comment:20 Changed 11 years ago by
Some typos maybe: Should "optimization representation" be "optimized representation?"
comment:21 Changed 11 years ago by
Applied to Sage-4.0.2, all doctests pass with -long
.
comment:22 Changed 11 years ago by
Maybe this is silly, but when I do:
sage: F = FreeModule(ZZ, 10) sage: K = F.span([F.0 + 4*F.1,5*F.2,3*F.3]) sage: X = F/K sage: X.<tab>
I don't see Hom, V and W, because they are the *only* capitalized methods listed at all, and so they come before all the underscore stuff, and I automatically don't look at the beginning of the list because I'm never looking for underscore methods. As far as I know, all methods of classes are lowercase. Also, V
and W
seem like maybe bad choices of names. As soon as you do sage: X.V?
, you immediately see what it is, but if you're scanning over what you get from tab completion, you might completely ignore it...
comment:23 in reply to: ↑ 14 Changed 11 years ago by
Replying to was:
Also, I'll rename the V, W methods to cover and relations, with C() and R() as aliases.
It looks like this didn't happen...
comment:24 Changed 11 years ago by
OK, and how about lowercase c and r instead of uppercase?
comment:25 Changed 11 years ago by
- Summary changed from [with patch; needs review] implement general package for finitely generated not-necessarily free R-modules to [with patch; needs work] implement general package for finitely generated not-necessarily free R-modules
Random comments while various people (like rlm (I hope) and me) work on more thorough reviews:
- the new files should be added to the reference manual, and there is some misformatted reST, which the attached patch fixes. It also moves docs from the
__init__
methods to the classes, as rlm suggests.
- I don't understand the point (or maybe the documentation) for M.optimized():
This has the advantage that any homomorphism from self extends to a homomorphism from V
If I have a map f: V/W --> Z, then I certainly get a map g: V --> Z: just compose the quotient map V --> V/W with f.
- the argument "check" should be documented: I can see what it does by reading the source code, but it should be described in
FGP_module
andFGP_Module_class.__init__
(or actually inFGP_Module_class
), and wherever else it's used.
comment:26 Changed 11 years ago by
the new files should be added to the reference manual, and there is some misformatted reST, which the attached patch fixes. It also moves docs from the init methods to the classes, as rlm suggests.
Thanks for ading ref_5882.patch to fix this!
I don't understand the point (or maybe the documentation) for M.optimized(): "This has the advantage that any homomorphism from self extends to a homomorphism from V"
Yes, I should change that, since of course any homomorphism extends. The point is that with M.optimized() it *trivially extends* because the gens for M.optimized().V() are *exactly the same* as the gens for M. Also, the dimension of M.optimized().V() is the same as the rank of M.
the argument "check" should be documented:
I can't disagree with that -- all options should be documented with examples.
Also, I'll rename the V, W methods to cover and relations, with C() and R() as aliases.
It looks like this didn't happen...
I was going to change them, but realized it will break compatibility with quotients of vector spaces, which have used V and W for a year now. I prefer instead just adding two new methods "cover()" and "relations()" that just return V() and W(), both to fgp modules and to quotients of vector spaces. Then everything is backward compatible and old code doesn't break.
comment:27 Changed 11 years ago by
OK, and how about lowercase c and r instead of uppercase?
I don't like that more, because they are modules. In mathematics, modules are usually upper case and *elements* of modules are lower case.
Changed 11 years ago by
comment:28 Changed 11 years ago by
- Summary changed from [with patch; needs work] implement general package for finitely generated not-necessarily free R-modules to [with patch; needs review] implement general package for finitely generated not-necessarily free R-modules
comment:29 Changed 11 years ago by
- Reviewers changed from Robert Miller to Robert Miller, John Palmieri
- Summary changed from [with patch; needs review] implement general package for finitely generated not-necessarily free R-modules to [with patch; needs work] implement general package for finitely generated not-necessarily free R-modules
A partial review; I've looked at the files *not* in the fg_pid directory, and I'm happy with them except for the minor comments below about free_module_morphism.py. I'm now working through the files in the fg_pid directory, and I'm about halfway through fgp_module.py.
*
In free_module_morphism.py:
in inverse_image
, is there any speed gain if you check whether the rank of the homomorphism is zero at the beginning? that is, change
if self.domain().rank() == 0: return self.domain()
to
if self.domain().rank() == 0 or self.rank() == 0: return self.domain()
or even to
if self.rank() == 0: return self.domain()
A very minor issue: In inverse_image
, in the lines
if R.is_field(): # By solving, find lifts of each of the basis elements of V. # Each row of Y gives a linear combination of the basis for the domain # that maps to one of the basis elements V. C = A.solve_left(B)
change "Each row of Y" to "Each row of C"?
*
fgp_module.py:
the function FGP_Module: documentation should say what it returns: V/W as a f.g. R-module. For the inputs, V and W need to be free R-modules.
_coerce_map_from_: I think that V/W should have a coercion from V, so testing isinstance(S, FGP_Module_class) won't work. More generally, you should have coercions from anything of the form V/W' to V/W, as long as W' is contained in W: that is, you should have coercions not just from submodules, but also from modules with canonical surjections onto V/W. (There may be many maps from V to V/W, but there is one *canonical* map, so I think there should be a coercion map.)
in free_module.py, there is a __cmp__
method but not an __eq__
method, and here it's the other way around. Is this an issue? Do we have a policy about which one to use?
Here's a problem with is_submodule:
sage: V = FreeModule(ZZ, 1) sage: W = V.submodule([0*V.0]) sage: W2 = V.submodule([2*V.0]) sage: V/W # isomorphic to Z Finitely generated module V/W over Integer Ring with invariants (0) sage: V/W2 # isomorphic to Z/2Z Finitely generated module V/W over Integer Ring with invariants (2) sage: (V/W).is_submodule(V/W2) True
This is because the implementation is wrong: if you want V/W to be a submodule of V'/W', then you want V to be a submodule of V', and the inclusion map should induce a surjection of W onto W' (hence an isomorphism between W and W' -- given an injection V --> V' which induces a map W --> W', the induced map must be an injection also). Should you change the end from
return self.V().is_submodule(A.V()) and self.W().is_submodule(A.W())
to
return self.V().is_submodule(A.V()) and self.W() == A.W()
The docstring should be changed to reflect this, as should the doctests; in the existing doctests, I don't think that A is actually a submodule of Q. In the simpler (but somewhat analogous) situation of Z/2Z and Z/4Z, then although abstractly Z/2Z is a submodule of Z/4Z, the identity map Z --> Z does not induce the inclusion. The identity map Z --> Z induces an inclusion 4Z --> 2Z, which then induces a *surjection* Z/4Z --> Z/2Z.
Also, the first sentence of the docstring is wrong: it says "Return True if A is a submodule of self", and it should be "Return True if self is a submodule of A".
base_ring: delete the comment (# this will be done in __init__
)?
_smith_form_
: document the form of the output, or at least give a reference to smith_form from matrix2.pyx.
invariants needs a docstring, not just doctests. (The term "invariants" is used frequently in fgp_module.py, but is never defined.) Document the argument "include_ones"?
gens: in the docstring, change "lements" to "elements". Change it to "elements g0,...,gn of self"? (Add "of self"?)
is it worth changing "isinstance(x, FGP_Module_class)" to "is_FGP_Module(x)" many places in this file? (Otherwise, is "is_FGP_Module" used anywhere? We could delete it...)
I'm still working on this file, and I haven't looked at fgp_morphism or fgp_element in any detail yet (except to note that the in the docstring for FGP_Morphism, the comment "where the morphism doesn't extend to V1" needs to be rephrased). I'm going on a family trip tomorrow, though, so I may not have time to work on this for a few days.
comment:30 follow-up: ↓ 31 Changed 11 years ago by
My next installment: this finishes up with the file fgp_module.py.
coordinate_vector:
self.optimized() # computes T as side effect -- see above
Should say "see below", I think.
optimize: in the comments
# Compute matrix X of linear transformation from self._V to V. # This matrix X gives each basis element of self._V in terms # of our new optimized V, modulo the W's.
Maybe "X" should be replaced by "T". If not, then "T" should be described, since it's cached, and so is presumably important.
hom: if len(im_gens) == 0
, then we can't use M.hom(...)
to define the zero map to another module. Should we be able to? That is, should we be able to specify the codomain explicitly instead of the method using N = im_gens.universe()
?
random_element: wouldn't it be better to pick a random element from self.optimized()[0]._V?
right before random_fgp_module: ZZ has already been imported
random_fgp_module: say that R
is optional, default ZZ
*
A general question: What's the obstruction to implementing this for modules over k[x], for k a field, or for general PIDs? This should be documented somewhere so interested people know what to work on.
*
I hope to get to the last two files soon.
comment:31 in reply to: ↑ 30 ; follow-up: ↓ 32 Changed 11 years ago by
Replying to jhpalmieri:
*
A general question: What's the obstruction to implementing this for modules over k[x], for k a field, or for general PIDs? This should be documented somewhere so interested people know what to work on.
*
To my understanding, it is the lack of an implementation of Hermite normal form for general PIDs.
comment:32 in reply to: ↑ 31 Changed 11 years ago by
comment:33 Changed 11 years ago by
I just downloaded the patches, installed, built, and tried it out. One of the first things that I tried was ngens()
-- I wanted to know if a module defined as a quotient of something of rank 2 counted as having 2 generators or 1. I got this:
sage: A = QQ**2 sage: B = A.span([[1,2], [5, 1/17]]) sage: C = A.span([[2,4],[5,1/17]],ZZ) sage: Q = B/C; Q Finitely generated module V/W over Integer Ring with invariants (2) sage: Q.ngens() --------------------------------------------------------------------------- RuntimeError Traceback (most recent call last) /home/david/.sage/temp/groke/6867/_home_david__sage_init_sage_0.py in <module>() /home/david/sage-4.0.2/local/lib/python2.5/site-packages/sage/structure/parent_gens.so in sage.structure.parent_gens.ParentWithGens.ngens (sage/structure/parent_gens.c:2383)() /home/david/sage-4.0.2/local/lib/python2.5/site-packages/sage/structure/parent_gens.so in sage.structure.parent_gens.check_old_coerce (sage/structure/parent_gens.c:1140)() RuntimeError: Finitely generated module V/W over Integer Ring with invariants (2) still using old coercion framework
comment:34 Changed 11 years ago by
(sorry, there is a ZZ missing in the second line of the example, I cut + pasted wrongly)
comment:35 Changed 11 years ago by
Another bug:
sage: A = ZZ**1 sage: Q3 = A / A.span([[3]]) sage: Q6 = A / A.span([[6]]) sage: Q6.is_submodule(Q3) True
I am currently doing a proof-of-concept abelian groups implementation using your code, and this has involved making a few minor changes anyway, so I'll do a fix for is_submodule as part of that (and add an is_quotient method).
comment:36 Changed 11 years ago by
OK, I've now read the docstrings and it looks like that was the intended behaviour; but I really don't like the idea of Z/6 being a submodule of Z/3. I suggest we have a new method called something like "maps_into" which does what "is_submodule" previously did, and reserve "is_submodule" for cases where the obvious map both exists and is injective.
comment:37 Changed 11 years ago by
Okay, I'm done with my review. Earlier, I discussed everything except the files "fgp_element.py" and "fgp_morphism.py". The file "fgp_element.py" looks good to me. The file "fgp_morphism.py" is mostly good, but I have a few comments:
FGP_Morphism: as mentioned avove, need to fix the part of the docstring which says "where the morphism doesn't extend to V1"
FGP_Morphism, __init__
: can we delete the line
from sage.matrix.all import diagonal_matrix
Also in __init__
: Do you expect the error messages like "domain of phi must be V for MO" to ever appear? They are pretty cryptic -- if you haven't read the code, you won't know what "V for MO" means.
In __call__
: when x is an FGP_Module, should you check that x is a submodule of self.domain() and return an appropriate error if not?
I note that in "image", you call FGP_Module with check=False
, but you don't have this in "kernel". Should you use check=False
there, too?
Should "preimage" be a synonym for "lift"? Or should there be a method "preimage" which acts like "lift" on elements, but also works on submodules?
In _coerce_map_from_
: should there be a coercion from Hom(X,Y) to Hom(X,Z) if there is a coercion from Y to Z? Should there be a coercion from Hom(X,Y) to Hom(W,Y) if there is a coercion from W to X?
Overall, this is very impressive, and it will be great to have this as part of Sage.
comment:38 Changed 11 years ago by
I have been working on this as part of a Sage Days 16 project to reimplement abelian groups. The above patch:
- adds new methods
_element_class
and_subquotient_class
which can be overridden by derived classes
- adds a new method
has_canonical_map_to
which does whatis_submodule
previously did, and changesis_submodule
so it is true if and only if the canonical map exists *and is injective*.
- adjusts some things relating to
gens
, so derived classes can have generators which are not necessarily in Smith form, and made the necessary corresponding changes tohom
. There are now separate methodssmithform_gens
andgens
, and the "internal" uses of generators all callsmithform_gens
, so it is safe for derived classes to overridegens
.
I *haven't* changed the printing code, as I threatened to do last week -- on reflection I decided that elements comparing as equal and printing as unequal was just too confusing.
David
comment:39 Changed 11 years ago by
adds new methods _element_class and _subquotient_class which can be overridden by derived classes
In the docstring for _element_class
, should "creating subquotients" say "creating elements"?
changes is_submodule
I like your change, but I would like is_submodule
to have more documentation, saying (for example) that it returns True if self.V() is a submodule of A.V(), with self.W() equal to A.W().
I don't have much of an opinion about this either way, but do you want to rename smithform_gens
to _smithform_gens
so it's less visible?
For annihilator
: the first line of the docstring ends a bit abruptly. Should this method return an actual ideal, not just an element of the ring?
comment:40 Changed 11 years ago by
Thanks for looking at this. I agree with your observations about the docstrings.
With smithform_gens
, the motivation is that I really want both gens and smithform_gens to be accessible to the user in cases where they're not automatically the same -- this is one of the most annoying features of the Gap-based abelian groups implementation we have now. If you create C2 x C3 x C5 x C7, then elementary_divisors
tells you that it is cyclic of order 210, but there's no way to find an element of order 210. But perhaps it is better to have these as private methods in FGP_Module_class
, and then have public methods in AdditiveAbelianGroup
that call them.
For annihilator
, essentially it is just there so I can use it to do exponent
for abelian groups, so I do want it to return an element.
comment:41 Changed 11 years ago by
Great, that all makes sense. For annihilator, then, you could the docstring from "Return the ideal" to "Return the generator of the ideal".
Changed 11 years ago by
comment:42 Changed 11 years ago by
I've uploaded a new patch taking into account John's suggestions.
comment:43 Changed 11 years ago by
- Summary changed from [with patch; needs work] implement general package for finitely generated not-necessarily free R-modules to [with patch; needs final review] implement general package for finitely generated not-necessarily free R-modules
RESPONSE TO ALL REFEREE COMMENTS IN WHICH EVERYTHING IS ADDRESSED. A patch will be posted in a moment too.
in inverse_image, is there any speed gain if you check whether the rank of the homomorphism is zero at the beginning? that is, change
DONE
A very minor issue: In inverse_image, in the lines
if R.is_field():
# By solving, find lifts of each of the basis elements of V. # Each row of Y gives a linear combination of the basis for the domain # that maps to one of the basis elements V. C = A.solve_left(B)
change "Each row of Y" to "Each row of C"?
DONE
*
fgp_module.py:
the function FGP_Module: documentation should say what it returns: V/W as a f.g. R-module. For the inputs, V and W need to be free R-modules.
DONE
_coerce_map_from_: I think that V/W should have a coercion from V, so testing isinstance(S, FGP_Module_class) won't work. More generally, you should have coercions from anything of the form V/W' to V/W, as long as W' is contained in W: that is, you should have coercions not just from submodules, but also from modules with canonical surjections onto V/W. (There may be many maps from V to V/W, but there is one *canonical* map, so I think there should be a coercion map.)
DONE
in free_module.py, there is a cmp method but not an eq method, and here it's the other way around. Is this an issue? Do we have a policy about which one to use?
I think eq is better since A < B suggest to a lot of people that "A is contained in B", which isn't the case at all. But I don't want to potentially break the API of the general free_module code in this patch.
Here's a problem with is_submodule:
sage: V = FreeModule?(ZZ, 1) sage: W = V.submodule([0*V.0]) sage: W2 = V.submodule([2*V.0]) sage: V/W # isomorphic to Z Finitely generated module V/W over Integer Ring with invariants (0) sage: V/W2 # isomorphic to Z/2Z Finitely generated module V/W over Integer Ring with invariants (2) sage: (V/W).is_submodule(V/W2) True
This is because the implementation is wrong: if you want V/W to be a submodule of V'/W', then you want V to be a submodule of V', and the inclusion map should induce a surjection of W onto W' (hence an isomorphism between W and W' -- given an injection V --> V' which induces a map W --> W', the induced map must be an injection also). Should you change the end from
return self.V().is_submodule(A.V()) and self.W().is_submodule(A.W())
to
return self.V().is_submodule(A.V()) and self.W() == A.W()
DONE -- good change. David Loeffler also found this issue and "fixed" the code, but his fix was wrong too (it basically ignored the V's).
By the way, after making the above fix then running doctests, the automated randomized testing code *did* find a bug in the image command. I fixed that by changing
V = self._phi.image()
to
V = self._phi.image() + self.codomain().W()
in the image method in fgp_morphism.py
The docstring should be changed to reflect this, as should the doctests; in the existing doctests, I don't think that A is actually a submodule of Q. In the simpler (but somewhat analogous) situation of Z/2Z and Z/4Z, then although abstractly Z/2Z is a submodule of Z/4Z, the identity map Z --> Z does not induce the inclusion. The identity map Z --> Z induces an inclusion 4Z --> 2Z, which then induces a *surjection* Z/4Z --> Z/2Z.
Also, the first sentence of the docstring is wrong: it says "Return True if A is a submodule of self", and it should be "Return True if self is a submodule of A".
DONE
base_ring: delete the comment (# this will be done in init)?
DONE
_smith_form_: document the form of the output, or at least give a reference to smith_form from matrix2.pyx.
DONE.
Also, I changed all the smithform's to smith_form's, which David L. introduced.
invariants needs a docstring, not just doctests. (The term "invariants" is used frequently in fgp_module.py, but is never defined.) Document the argument "include_ones"?
done.
gens: in the docstring, change "lements" to "elements". Change it to "elements g0,...,gn of self"? (Add "of self"?)
DONE
is it worth changing "isinstance(x, FGP_Module_class)" to "is_FGP_Module(x)" many places in this file? (Otherwise, is "is_FGP_Module" used anywhere? We could delete it...)
Yes, DONE.
I'm still working on this file, and I haven't looked at fgp_morphism or fgp_element in any detail yet (except to note that the in the docstring for FGP_Morphism, the comment "where the morphism doesn't extend to V1" needs to be rephrased). I'm going on a family trip tomorrow, though, so I may not have time to work on this for a few days.
done.
My next installment: this finishes up with the file fgp_module.py.
coordinate_vector:
self.optimized() # computes T as side effect -- see above
Should say "see below", I think.
DONE
optimize: in the comments
# Compute matrix X of linear transformation from self._V to V. # This matrix X gives each basis element of self._V in terms # of our new optimized V, modulo the W's.
Maybe "X" should be replaced by "T". If not, then "T" should be described, since it's cached, and so is presumably important.
DONE. I called it X at one point, e.g., in my doodles, but changed to T.
hom: if len(im_gens) == 0, then we can't use M.hom(...) to define the zero map to another module. Should we be able to? That is, should we be able to specify the codomain explicitly instead of the method using N = im_gens.universe()?
DONE -- You're right, yes, we should be able to. I implemented hom wrong, since hom should have an optional codomain parameter. Fixed.
random_element: wouldn't it be better to pick a random element from self.optimized()[0]._V?
I'm really not sure. Conceptually if one constructs A = V/W, then it is easiest to think of random_element as "Create a random element of self=V/W, by creating a random element of V and reducing it modulo W." The optimized() thing doesn't seem so canonical in terms of the given input. So I'm definitely not so sure. Why do you think that would be better? Efficiency?
right before random_fgp_module: ZZ has already been imported
DONE.
random_fgp_module: say that R is optional, default ZZ
DONE
*
A general question: What's the obstruction to implementing this for modules over k[x], for k a field, or for general PIDs? This should be documented somewhere so interested people know what to work on.
DONE - in the very top of fgp_module.py
*
I hope to get to the last two files soon.
Okay, I'm done with my review. Earlier, I discussed everything except the files "fgp_element.py" and "fgp_morphism.py". The file "fgp_element.py" looks good to me. The file "fgp_morphism.py" is mostly good, but I have a few comments:
FGP_Morphism: as mentioned avove, need to fix the part of the docstring which says "where the morphism doesn't extend to V1"
DONE
FGP_Morphism, init: can we delete the line
from sage.matrix.all import diagonal_matrix
DONE
Also in init: Do you expect the error messages like "domain of phi must be V for MO" to ever appear? They are pretty cryptic -- if you haven't read the code, you won't know what "V for MO" means.
DONE.
In call: when x is an FGP_Module, should you check that x is a submodule of self.domain() and return an appropriate error if not?
DONE, and I added some doctests.
I note that in "image", you call FGP_Module with check=False, but you don't have this in "kernel". Should you use check=False there, too?
DONE -- I've changed all the "internal checks" (not things passed in by the user) to use the DEBUG flag in fgp_module.py. Then one can uniformly turn them all on/off. I think it is best to leave all the checks on for now, but turn them off after the code has been out in the wild for a while, and work has gone into optimizing it (so far 0 work has gone into optimization).
Should "preimage" be a synonym for "lift"? Or should there be a method "preimage" which acts like "lift" on elements, but also works on submodules?
Hmm. Actually, we should have at least inverse_image as a method on morphisms of fgp modules, since that isn't there at all! It was important to add this method to fg modules, and should be easy on fgp modules. This provides the same functionality as preimage. I think preimage would be good to add, but then it should be added for fg free modules too, so it's best to wait for another ticket and do it right.
In _coerce_map_from_: should there be a coercion from Hom(X,Y) to Hom(X,Z) if there is a coercion from Y to Z? Should there be a coercion from Hom(X,Y) to Hom(W,Y) if there is a coercion from W to X?
Yes, yes, but I don't know if this will work, since at least currently that function returns bool rather than the actual map. Also, the same should be added to free modules. I think this would be better to do on another ticket.
Overall, this is very impressive, and it will be great to have this as part of Sage.
FOR NEW TICKETS:
- Add a method "preimage" that acts like "lift" on elements, but also works on submodules.
- There should be a coercion from Hom(X,Y) to Hom(X,Z) if there is a coercion from Y to Z. There should there be a coercion from Hom(X,Y) to Hom(W,Y) if there is a coercion from W to X.
From David Loeffler:
I have been working on this as part of a Sage Days 16 project to reimplement abelian groups. The above patch:
- adds new methods _element_class and _subquotient_class which can be overridden by derived classes
Looks good to me.
- adds a new method has_canonical_map_to which does what is_submodule previously did, and changes is_submodule so it is true if and only if the canonical map exists *and is injective*.
good
- adjusts some things relating to gens, so derived classes can have generators which are not necessarily in Smith form, and made the necessary corresponding changes to hom. There are now separate methods smithform_gens and gens, and the "internal" uses of generators all call smithform_gens, so it is safe for derived classes to override gens.
good, except I changed it to smith_form_gens (!)
I *haven't* changed the printing code, as I threatened to do last week -- on reflection I decided that elements comparing as equal and printing as unequal was just too confusing.
Yep.
From John:
adds new methods _element_class and _subquotient_class which can be overridden by derived classes
In the docstring for _element_class, should "creating subquotients" say "creating elements"?
DONE
changes is_submodule
I like your change, but I would like is_submodule to have more documentation, saying (for example) that it returns True if self.V() is a submodule of A.V(), with self.W() equal to A.W().
DONE
I don't have much of an opinion about this either way, but do you want to rename smithform_gens to _smithform_gens so it's less visible?
After hearing how say Henri Cohen thinks about abelian groups, I think it is probably a good idea having smith_form_gens be user-visible. It's an important function, and pretty canonical, and will be used from outside the class (that was the motivation for introducing it).
For annihilator: the first line of the docstring ends a bit abruptly. Should this method return an actual ideal, not just an element of the ring?
DONE, and added another doctest that illustrates the case when the annihilator is 0. Yes, it should return an ideal, and I fixed it so it will.
David said:
For annihilator, essentially it is just there so I can use it to do
exponent for abelian groups, so I do want it to return an element.
Well in the docstring you wrote *ideal*. And it straightforward to get the generator of an ideal, so I made it an ideal.
We're going to generalize all this soon enough to general commutative base rings (singular supports this sort of thing well, actually), and when we do so as much as possible we'll want to have a consistent API. So we should make annihilator return an ideal.
Changed 11 years ago by
comment:44 Changed 11 years ago by
- Summary changed from [with patch; needs final review] implement general package for finitely generated not-necessarily free R-modules to [with patch, positive review] implement general package for finitely generated not-necessarily free R-modules
Okay, this is great. Positive review.
The ticket is a bit of a mess, though: davidloeffler's and was's most recent patches conflict. I've taken the liberty of creating a single patch, containing all of the others, and merging the few differences between these two conflicting patches. (I'm taking William's side on annihilator
-- it should return an ideal.) My patch also includes a few trivial fixes: two typos, and a rewording of the annihilator docstring so that the second line takes into account that it returns an ideal, not an element. You can see my changes in "trac_5882_delta.patch"; this is for reference only.
I think that the "Author" and "Reviewer" fields are filled in accurately.
Apply only "trac_5882-all-in-one.patch".
comment:45 Changed 11 years ago by
- Summary changed from [with patch, positive review] implement general package for finitely generated not-necessarily free R-modules to [with patch, needs work] implement general package for finitely generated not-necessarily free R-modules
There is one doctest failure:
sage -t sage/modules/fg_pid/fgp_module.py ********************************************************************** File "/space/rlm/sage-4.1.alpha3/devel/sage-main/sage/modules/fg_pid/fgp_module.py", line 1453: sage: hash(A) Expected nothing Got: -7071641102956720018 **********************************************************************
comment:46 Changed 11 years ago by
- Summary changed from [with patch, needs work] implement general package for finitely generated not-necessarily free R-modules to [with patch, needs review] implement general package for finitely generated not-necessarily free R-modules
Sorry, that's what I get for only doctesting on a 32-bit machine. Here's a patch.
Changed 11 years ago by
comment:47 Changed 11 years ago by
- Summary changed from [with patch, needs review] implement general package for finitely generated not-necessarily free R-modules to [with patch, positive review] implement general package for finitely generated not-necessarily free R-modules
comment:48 Changed 11 years ago by
Re William's comments:
random_element: wouldn't it be better to pick a random element from self.optimized()[0]._V?
I'm really not sure. Conceptually if one constructs A = V/W, then it is easiest to think of random_element as "Create a random element of self=V/W, by creating a random element of V and reducing it modulo W." The optimized() thing doesn't seem so canonical in terms of the given input. So I'm definitely not so sure. Why do you think that would be better? Efficiency?
Because when I wrote that, I was having a mathematical brain freeze. It's fine the way it is.
The documentation builds fine, by the way.
comment:49 Changed 11 years ago by
- Merged in set to sage-4.1.rc0
- Resolution set to fixed
- Status changed from new to closed
NOTE: trac_5882-part2.patch (which I'll post soon) fixes numerous *major* bugs in matrix_morphism.py, e.g., in restrict_domain and restrict_codomain. I noticed these issues while reading the code and thinking about what it did...