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

To fix issue with Betti Tables #3800

Merged
merged 9 commits into from
May 30, 2024
Merged

Conversation

Lax202
Copy link
Contributor

@Lax202 Lax202 commented May 27, 2024

This is an attempt to fix Issue #3798 @wdecker

  • I have removed the extra line at the end of the show function of the Betti table.
  • I am unsure about the negative degrees in the Betti table. I've made some kind of change but don't have an example yet to test it on. Help with an example with negative cohomological degrees would be great.

@Lax202 Lax202 marked this pull request as draft May 27, 2024 14:07
@wdecker
Copy link
Collaborator

wdecker commented May 27, 2024

@Lax202 Please, your changes with respect to catching non-gradedness are not helpful. You ONLY need to erase as well as copy and paste as I described in the issue:

Please remove test in the loop and, instead, start the function body with something like

@Assert is_standard_graded(base_ring(F)) "resolution must be defined over a standard graded ring"
@Assert is_graded(F) "resolution must be graded"

That is all.

@Lax202
Copy link
Contributor Author

Lax202 commented May 27, 2024

@wdecker sorry for misunderstanding. I have added the assert statements.

@wdecker
Copy link
Collaborator

wdecker commented May 27, 2024

Please delete this line:

module_degrees === nothing && error("One of the modules in the graded free resolution is not graded.")

@joschmitt joschmitt added the backport 1.0.x Should be backported to the release 1.0 branch label May 28, 2024
@benlorenz
Copy link
Member

joschmitt added the backport 1.0.x label yesterday

I would rather not backport this as this is not really a bugfix and it does change the output of the book examples (even if it is just whitespace). If I understand it correctly this is about doing extra checks to catch invalid input?

@joschmitt
Copy link
Member

joschmitt added the backport 1.0.x label yesterday

I would rather not backport this as this is not really a bugfix and it does change the output of the book examples (even if it is just whitespace). If I understand it correctly this is about doing extra checks to catch invalid input?

Ah, okay, sorry. I just read "fix issue".

@Lax202 Lax202 marked this pull request as ready for review May 29, 2024 12:19
Copy link

codecov bot commented May 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.30%. Comparing base (7d851c2) to head (0935040).
Report is 32 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3800      +/-   ##
==========================================
+ Coverage   81.25%   81.30%   +0.05%     
==========================================
  Files         580      579       -1     
  Lines       79289    79229      -60     
==========================================
- Hits        64426    64419       -7     
+ Misses      14863    14810      -53     
Files Coverage Δ
src/Modules/ModulesGraded.jl 73.35% <100.00%> (-0.03%) ⬇️

... and 27 files with indirect coverage changes

@benlorenz benlorenz removed the backport 1.0.x Should be backported to the release 1.0 branch label May 29, 2024
@wdecker
Copy link
Collaborator

wdecker commented May 29, 2024

does change the output of the book examples

Indeed? In the latex version of the book it looks okay.

@benlorenz
Copy link
Member

The CI job for the book tests is complaining about the removed lines, e.g.:

  julia> betti(free_resolution(defining_ideal(D)))
  0  1
  -----------
  2    : 3  2
  -----------
  total: 3  2
- 
  
  julia> Oscar.rat_normal_curve_anticanonical_map(D)

But it turns out in the book there is no extra new line. This was probably not flagged because the old Documenter based checking needed some extra filtering which removed the extra newline. So backporting this PR would change the output of 1.0.x but on the other hand adjust it to match the output in the book.

@benlorenz
Copy link
Member

So on second thought I think it does make sense to backport this since it will bring 1.0 and the book closer together even if it does change the output of 1.0 slightly.

Please adjust the remaining jlcons, I think exres2.jlcon and param.jlcon, and once it is merged I will check if it applies cleanly to the release branch.

@benlorenz benlorenz added the backport 1.0.x Should be backported to the release 1.0 branch label May 29, 2024
@benlorenz benlorenz merged commit 0810b2d into oscar-system:master May 30, 2024
29 checks passed
benlorenz pushed a commit that referenced this pull request May 30, 2024
* removed extra line in betti show

* changed range to include negative cohomologies -NOTSURE

* Revert "changed range to include negative cohomologies -NOTSURE"

This reverts commit e819131.

* added asserts to betti

* fixed with wdecker

* removed extra line in betti table tests

* extra line removed in documentation

* deleted extra line in book tests

* extra line in betti removed in book tests

(cherry picked from commit 0810b2d)
@benlorenz benlorenz mentioned this pull request May 30, 2024
19 tasks
@benlorenz benlorenz removed the backport 1.0.x Should be backported to the release 1.0 branch label May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Problems with function betti_table
4 participants