-
Notifications
You must be signed in to change notification settings - Fork 123
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
Decomposition info #2504
Decomposition info #2504
Conversation
P3 = projective_space(QQ, 3) | ||
X = covered_scheme(P3) | ||
S = homogeneous_coordinate_ring(P3) | ||
(x,y, z, w) = gens(S) | ||
I = ideal(S, [x^3+y^3+z^3+w^3, x+y+z+w, 37*x^2-x*z+4*w^2-5*w*z]) | ||
II = ideal_sheaf(P3, I) | ||
@test oscar.colength(II) == 6 | ||
J = ideal(S, [x, y, z^4]) | ||
JJ = ideal_sheaf(P3, J) | ||
@test oscar.colength(JJ) == 4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are the relevant tests for this PR.
# The elements in h indicate where components must | ||
# be located so that they can not be spotted in other charts. | ||
# We iteratively single out these components by adding a sufficiently high | ||
# power of the equation to the ideal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...and this here how this can be brought to work.
The next step would be to automatically keep track of this information for blowups. Then integration of cycles should go through in little time once we allow weil divisor components to be non-prime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also need this information to down to subschemes.
If you agree with this concept, I could move forward with it. |
May I sum up the idea, how I understood it from the first glance (i5 minutes after receiving the first mail on this PR): |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2504 +/- ##
==========================================
- Coverage 72.95% 72.95% -0.01%
==========================================
Files 406 406
Lines 53962 53995 +33
==========================================
+ Hits 39366 39390 +24
- Misses 14596 14605 +9
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that overall this is a great Idea! But it needs a bit more documentation.
One general remark: Make sure to correctly carry along this information through a blow up and hence through any sequence of blow-ups. |
From my side this is good to go. |
of elements ``fᵢ₁,…,fᵢᵣ ∈ 𝒪(Uᵢ)``. These elements are chosen so that for every | ||
affine patch `Uᵢ` of ``X`` in the covering `C` the closed subvarieties ``Zᵢ ⊂ Uᵢ`` | ||
defined by the ``fᵢⱼ`` give rise to a decomposition of ``X`` as a **disjoint** union | ||
``X = \bigcup_{i} Z_i`` of locally closed subvarieties. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still don't understand this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
decomposition_info(X)[U_i]
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
O.k. please add this to the docstring with the next pr.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But still how do you get
Shouldn't
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This must hold by construction of the decomposition_info
. You do not get a decomposition with inclusion maps, etc. You get a list of ring elements for every patch and you may continue working with them while assuming that the decomposition described above is a disjoint union.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still don't get it. Because I do not get your definition of a decomposition_info.
Please give clean mathematical definition.
I set to auto merge. Please improve the docstring with the next pr. |
@HechtiDerLachs promised to add the check later. So I merge this now. |
We introduce a new pattern to keep track of a decomposition of a covered scheme as a disjoint union. The extended version of this should allow for the computation of intersection numbers without computing any glueings.
Let me know, what you think @simonbrandhorst @afkafkafk13 .