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
Implementing subschemes functionality for projective "is_morphism" #17326
Comments
Author: jdefaria |
Branch: u/jdefaria/ticket/17326 |
Commit: |
New commits:
|
comment:4
You don't need this check since if it is a projective morphism it must be some kind of projective scheme.
|
Reviewer: Ben Hutz |
Changed author from jdefaria to Joao Alberto de Faria |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:9
Sorry to be picky, but I'd like a subscheme example that fails to be a morphism on projective space, but which is a morphism for a subscheme, ie., the indeterminancy locus does not intersect the subscheme. The example you give is already a morphism on projective space. Otherwise, this looks fine. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:12
ok, this looks good now. |
Changed branch from u/jdefaria/ticket/17326 to |
Changed commit from |
Changing the projective "is_morphism" to work over subschemes
Component: algebraic geometry
Author: Joao Alberto de Faria
Branch:
f9ce9da
Reviewer: Ben Hutz
Issue created by migration from https://trac.sagemath.org/ticket/17326
The text was updated successfully, but these errors were encountered: