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

Database on Enriques surfaces and docu #4560

Merged
merged 9 commits into from
Feb 8, 2025
Merged

Conversation

simonbrandhorst
Copy link
Collaborator

@simonbrandhorst simonbrandhorst commented Feb 7, 2025

  • database of Enriques surfaces and docu

@simonbrandhorst
Copy link
Collaborator Author

@antonydellavecchia

@lgoettgens
Copy link
Member

Could you please rebase this onto the latest master branch? Currently, github shows #4540 as part of the changes, which makes it incredibly difficult to see the "real changes".
And there are conflicts to be resolved.


The group ``\mathrm{Aut}(Y)`` is a dihedral group of order ``8`` and its image ``\mathrm{Aut}^*(Y)`` in ``O(S_Y)`` is a group of order ``4``. It is this group we compute.
```jldoctest EnriquesAut
julia> SY, SX, L26, w, u = load("data/TauTaubarGenericEnriquesSurfaces/TauTaubarGenericEnriquesSurfaceNo172.mrdi");
Copy link
Collaborator

Choose a reason for hiding this comment

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

If the surfaces are numbered then it probably makes sense to implement a load_enriques_surface function and then users can just pass an int as oppose to trying to find the path similar to the johnson_solid function or similar to the code Oscar/src/AlgebraicGeometry/Surfaces/SurfacesP4.jl .
Then adding a test in the data section to make sure we are still able to load the files when there is an upgrade is also import.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks for the suggestion. Done.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The test is part of a doctest.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Or should I add a test in the data section anyways?

Copy link
Collaborator

Choose a reason for hiding this comment

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

If the data between files has exactly the same types then this should be fine.
Otherwise it would good to make sure that we test all files with different type structure.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

All exactly the same types.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Great, then I think the doc test is sufficient

@simonbrandhorst
Copy link
Collaborator Author

Should be good to go for my part.

Copy link
Collaborator

@antonydellavecchia antonydellavecchia left a comment

Choose a reason for hiding this comment

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

looks good from the data side

@simonbrandhorst simonbrandhorst enabled auto-merge (squash) February 8, 2025 17:36
@simonbrandhorst simonbrandhorst merged commit 8fc7969 into master Feb 8, 2025
28 of 33 checks passed
@simonbrandhorst simonbrandhorst deleted the sb/enriques_wip branch February 8, 2025 18:29
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.

3 participants