Skip to content
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

Strict transform of an ideal in Cox ring #4154

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

paemurru
Copy link
Contributor

TODO: tests, docstrings, documentation

TODO: tests, docstrings, documentation
Copy link

codecov bot commented Sep 26, 2024

Codecov Report

Attention: Patch coverage is 0% with 50 lines in your changes missing coverage. Please review.

Project coverage is 84.64%. Comparing base (5371a13) to head (1971b4d).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
experimental/Schemes/src/ToricBlowups/methods.jl 0.00% 50 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4154      +/-   ##
==========================================
- Coverage   84.69%   84.64%   -0.05%     
==========================================
  Files         627      627              
  Lines       84300    84350      +50     
==========================================
+ Hits        71399    71401       +2     
- Misses      12901    12949      +48     
Files with missing lines Coverage Δ
experimental/Schemes/src/ToricBlowups/methods.jl 3.70% <0.00%> (-46.30%) ⬇️

... and 1 file with indirect coverage changes

Copy link
Collaborator

@afkafkafk13 afkafkafk13 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I leave you a few comments on the code.

sideremark: I am not convinced (theorywise) that you can just set one entry to -1 in the grading change, but I am not a Cox-ring specialist. So I leave the reviewing of the content to someone else.

Comment on lines +50 to +51
@assert grading_group(cox_ring(Y)) === class_group(Y)
G = class_group(Y)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First define G as the class_group(Y) and then use G in the assert, since you need G afterwards anyway and in the case of failure of the assert, you did not loose anything.

n = number_of_generators(G)
new_var = cox_ring(Y)[index_of_new_ray(f)]
M = generator_degrees(cox_ring(Y))
@assert M[index_of_new_ray(f)][n] < 0 "Assuming the blowup adds a new column vector to `Oscar.generator_degrees(cox_ring(codomain(f)))`, the entry of that vector corresponding to the new ray should be negative. If not, multiply by -1."
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your error messages in case of failing asserts seem pretty long to me. Please try to make them shorter and maybe add appropriate notes to the documentation instead.

Comment on lines +57 to +58
for i in 1:n_rays(Y)
i == index_of_new_ray(f) || @assert M[i][n] >= 0 "Assuming the blowup adds a new column vector to `Oscar.generator_degrees(cox_ring(codomain(f)))` for which the entry corresponding to the new ray is negative, the entries corresponding to all the other rays should be nonnegative. If not, add integer multiples of the other columns until it is."
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to say
@assert findfirst(M[i][n] < 0 && i != index_of_new_ray(f) , 1:n_rays(Y)) === nothing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants