-
Notifications
You must be signed in to change notification settings - Fork 130
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
Move dim
from schemes to rings
#4280
Merged
simonbrandhorst
merged 8 commits into
oscar-system:master
from
paemurru:ep/move_dim_to_rings
Nov 13, 2024
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
a584ce2
Move `dim` from schemes to rings
paemurru 747a65e
Add missing `return`
paemurru f5390f6
Separate dim for MPolyComplementOfKPointIdeal
paemurru c03b430
Apply suggestions from code review
paemurru 5082bf7
Remove redundant functions
paemurru 4b199f4
Fix bug when base ring is the integers
paemurru 5f4c467
dim for zzModRing and ZZModRing
paemurru c9c18f3
Update src/Rings/mpolyquo-localizations.jl
simonbrandhorst File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Please handle them separately. For MPolyComplementOfKPointIdeal P is certified to be zero-dimensional so that we do not need to compute dim(P).
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.
It seems that this is not true.
So I will leave it as it is for now.
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.
My guess is that
complement_of_point_ideal
silently assumes that we are working over a field? Perhaps the type and constructor should be restricted accordingly what do you think @afkafkafk13 ?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 is indeed a problem with complement_of_point_ideal:
This ideal is NOT maximal as we do not get a field as the quotient of the ring by it. This needs to be handled in
complement_of_point_ideal
. My suggestion: check dimension (not number of entries!!) of the ideal before doing anything else incomplement_of_point_ideal
, throw an error if it is not maximal (i.e. dim(ideal) is not zero -- this should already be working in Oscar) and point the user tocomplement_of_prime_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.
It is a bit fuzzy what a "point" is here. Will we get anything computationally effective for the "point" given by the maximal ideal
(2,x,y)
inZ[x,y]
? I impression was thatComplementOfKPointIdeal
just assumes a base field.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 it does assume but does not check for this (although it should).
I would leave fixing
complement_of_point_ideal
to a separate issue.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.
ok. fine with me. But we urgently need to fix complement_of_point_ideal. Maybe we can just check
@simonbrandhorst no, we won't get anything computationally effective currently. You are right. We should just tell the user to use
complement_of_prime_ideal
instead, whenever we are not over a field.Edit: This is a strategic decision and breaks some tests. I opened PR We need to discuss this. Over a ring this is not a point ideal and hence should not be used via this localization, anyway. Moreover, the localization at <x_1,\dots,x_n> in ZZ[x_1,\dots,x_n] is not what is produced here, as we are localizing w.r.t. a monomial ordering and continue working over ZZ and do not pass to QQ, even though ZZ \cap <x_1,\dots,x_n> = 0.