New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compute (degree bounded) minimal model of cdga's #27045
Comments
Commit: |
comment:3
Retarging tickets optimistically to the next milestone. If you are responsible for this ticket (either its reporter or owner) and don't believe you are likely to complete this ticket before the next release (8.7) please retarget this ticket's milestone to sage-pending or sage-wishlist. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:6
I don't know how close this is to review, but this version of Old one:
New one:
|
comment:7
I am still working on it (I plan to add too the computation of the cohomology algebra, and maybe a test for formality, although I have to consider if that should go on the same ticket or not). I didn't notice such a big difference in the timimgs, but maybe that is because I only tested up to relitvely low degrees. Anyways, I don't think it would make sense to keep the old implementation since it doesn't grant to give the right answer (in the sense of not giving a minimal set of generators). I will try to think of another aproach that still grants to give a minimal set of generators, but doesn't get so slow. BTW, if you would like to review this, I could try to get it to the "needs review" point today or tomorrow, and leave the rest of the work for other tickets. |
comment:8
If the new version gives different answers from the old one, you should add some doctests to demonstrate this, and in particular the advantages of the new one. Don't hurry this on my account; it is not always predictable when I will have time to review a ticket. |
comment:9
Another option (and my preference) would be to have an I can try to review this when it is ready. |
comment:10
My point is that the previous method gave an answer that is "wrong", in the sense of giving a generating system that has redundant elements. If one wants just a generating system, one can use all the cohomology classes up to the given degree. So it only makes sense to provide a specific method to compute a reduced system if it is indeed minimal. Hence the change. I will add a doctest with an example where the given answer is different from the previous method. |
comment:11
In particular, with the old method:
whereas with the new:
Note that |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. Last 10 new commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:30
Wouldn't the testing framework complain if the expected output differs from the actual one by some line breaks? |
comment:31
Can you please take a nother look? I think it is pretty much ready. |
comment:32
Docbuild errors noted on the patchbot as per comment:29: - ``i`` -- integer (default: `3`); degree to which the result is
- required to induce an isomorphism in cohomology, and the domain is
- required to be minimal.
+ required to induce an isomorphism in cohomology, and the domain is
+ required to be minimal and similar. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:34
I think I addressed the complains in the patchbot. New commits:
|
comment:35
So the patchbots are reporting failures:
The 3 main ones seem like they are trivial failures and just need to be updated. Two of the other failures I cannot reproduce, but could always just be marked by |
comment:36
Hmmm, that's strange: I get an error message when testing myself:
But when I run that code inside an interactive session, it works as expected. I wonder if some of the errors come from the fact that i am developping on a python 3 environment. Seems plausible, since most are due to orderings of the answers in dictionaries. |
comment:37
Hmm...I didn't think about testing it on Python3. Frédéric (and likely John as well) will be happy that this works on both versions. I cannot say why it doesn't work by using the doctest runner but is fine in an interactive session. Maybe something is being cached or getting put in the "wrong" order in some set/dict. I can probably look into this more tomorrow. |
comment:38
Ok, if that is a big touble, we could remove the |
comment:39
With Python3, I am getting the other 3 failures reported by the patchbot. So we can ignore those (I am guessing that is a Python3-based patchbot). I still have no idea about the failure on your doctest run. Which version of Sage are you using to develop this? I think we should either update the output to match (for the failing tests in |
comment:40
Maybe I had something outdated on my sage install. After doing a full rebuild, I get no errors at all. About the ordering issues in python 3, that is a common problen for all doctests that involve dictionaries... ¿what is the general policy about that? |
comment:41
It depends on what the issue is. In this case, it seems the added tests do not differ from Python2 and Python3 (at least on my machine), and from looking at the code, it is fed off to the |
comment:42
So, just to clarify: you also get errors in a python2 build? After fully compiling a sage-python2 environment, I get no errors at all. |
comment:43
Yes, that is correct. I get the same 3 errors about output order in |
comment:44
That is strange, I get the same result as the doctests. Have you rebased to the last development version? Or mayb there is something machine dependent there? |
comment:45
I am using |
comment:46
Well, we can sidestep this problem by what I suggested in commnet:39 (as the nc-relations are not important for the doctest). |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:48
If that is the only discrepancy, then I agree that is the best we can do right now. Maybe when we do the final switch to python 3 these glitches will stabilize, and get more predictable doctests. New commits:
|
Reviewer: Travis Scrimshaw |
comment:49
I wish I did have a better understanding why it is not stable even across our machines, but this will do for now. Lo mira bien a mi. |
Changed branch from u/mmarco/compute__degree_bounded__minimal_model_of_cdga_s to |
Changed author from Miguel Marco to Miguel Marco, Victor Manero |
Changed commit from |
This ticket compute the i-minimal model of a cdg-algebra.
It also implements the cohomology algebra up to a given degree.
CC: @jhpalmieri @tscrim
Component: algebra
Author: Miguel Marco, Victor Manero
Branch:
612cfb3
Reviewer: Travis Scrimshaw
Issue created by migration from https://trac.sagemath.org/ticket/27045
The text was updated successfully, but these errors were encountered: