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
composition of scheme morphism defined by polynomials #15378
Comments
Author: vdelecroix |
Changed keywords from none to sage-days55 |
New commits:
|
Commit: |
comment:3
see the discussion at |
Changed branch from u/vdelecroix/15378-scheme_morphism_composition to u/bhutz/15378-scheme_morphism_composition |
comment:8
I added the ref to the inheritance issue in #14711. It would be nice if we could have composition working independent of the inheritance structure correction. Accordingly, I put the inheritance back how it was and the composition seems to work fine with this implementation. I added one example to test failure, but that is all. Comments? New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
You wrote
first of all the right syntax is (EDIT: it might not be you, but it appears in the total diff.) |
Changed author from vdelecroix to Vincent Delecroix, Ben Hutz |
comment:11
I put in needs review in order to make a sign to the patchbots... |
comment:12
Yes, I can fixed the syntax mistake. As for it being a closed ticket. In trying to investigate this issue, the comment in the code was not very helpful. The closed ticket #14711 has a much longer description of the issue and is part of what is needed. If I'm not mistaken the other part is a python bug not tracked on trac. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:14
And this can also be removed I guess
|
comment:15
The correct syntax is |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:17
I was wondering about that trac formatting. I didn't think the docs linked to trac like that, but I figured if you said so... ;) |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:19
Note that even without your branch it (sort of) works!
But I guess it is better to have the result of
|
comment:20
I guess that the lines
would better be replaced with
as there might be some morphism other than polynomial that you may want to compose with polynomial ones. I was not able to build example though. |
comment:21
This composition is specifically for SchemeMorphism_polynomial, so I'm fine with the NotImplementedError if there are not any polynomials. If it is a different kind of morphism, it shouldn't be calling this one. Yes, getting the defining polynomials of the composition really the point. We needed this to speed up the computations for things like #21118. |
comment:22
More precisely: |
comment:23
This gets the NotImplementedError
|
comment:24
I also built another example with Galois conjugation
|
comment:25
If I make your code
Then I get
However, I can't seem to actually apply the map
With your new example, I now get:
I haven't been able to evaluate yours at a pt yet... |
comment:26
For Galois conjugation the point is that the ring homomorphism There is something weird with the composition telling that it is the composition of two And an other error
I opened #21160 for the above since it is distinct from what we are trying to do here... |
comment:27
I do think allowing this general morphism composition is better, so I'll push that change shortly |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Vincent Delecroix |
Changed branch from u/bhutz/15378-scheme_morphism_composition to |
Currently the following fails
We just propose a generic implementation.
Component: algebraic geometry
Keywords: sage-days55
Author: Vincent Delecroix, Ben Hutz
Branch/Commit:
c6c853f
Reviewer: Vincent Delecroix
Issue created by migration from https://trac.sagemath.org/ticket/15378
The text was updated successfully, but these errors were encountered: