Strict transforms #5683
Draft
Strict transforms #5683
Conversation
This file contains hidden or 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
HechtiDerLachs
force-pushed
the
strict_transforms_split
branch
from
55f6971 to
d8d5723
Compare
This reverts commit 59c6e2d.
HechtiDerLachs
force-pushed
the
strict_transforms_split
branch
from
d8d5723 to
fced11e
Compare
Collaborator
Author
|
Just rebased on #5702 . Still WIP. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is work in progress on computing intersection numbers in higher Nash blowups. It is based on #5681 and will be rebased once that is merged. For the moment, I would like to make this PR to get a better overview on where we stand, which tests fail and which ones are to be added, and how things need to eventually be split.