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

FTheoryTools - Goals for 2024 and beyond #2699

Open
24 of 65 tasks
HereAround opened this issue Aug 17, 2023 · 0 comments
Open
24 of 65 tasks

FTheoryTools - Goals for 2024 and beyond #2699

HereAround opened this issue Aug 17, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request optimization Simpler/more performant code or more/better tests topic: FTheoryTools

Comments

@HereAround
Copy link
Member

HereAround commented Aug 17, 2023

To be discussed

  • Agenda for FTheoryTools paper.
  • Use https://docs.oscar-system.org/stable/Groups/action/ for the action of the discrete quotient on the center of the Lie group factors. E.g., the gauge group SU(6)/Z_3 would be stored as the Lie algebra sl(6), then a group action of the quotient factor Z_3 on the center Z_6 of SU(6).
    • Add these to the existing .json files in place of the current specification of the gauge quotients
  • Make computation of Tate sections lazy? Would speed-up the constructor of the big model A LOT!
  • Andrew:
    • Kodaira type of SU(3)s in toric hypersurface models coming back as nonsplit?? Fix and extend tests for the Kodaira type of the toric hypersurface models.
    • Documentation of HypersurfaceModels/Constructors.jl and alike needs updating. For instance D1 etc. are probably to be removed/explained better. Also, the above changes need to be worked in/should be reflected.
    • Add comments in code that fully explain defining_classes, explicit_model_sections, etc.
    • Fix tutorial (Martin: What does this mean? What is broken?)
    • Add Tate table functionality (Please elaborate. What does that mean?)
    • Improve/enhance family of spaces.
      • Martin: I discussed this at length with Matthias today (Feb. 14). Based on this, I see only one way forward. Family of bases serves as placeholder and placeholder only. That is, it must always be replaced with an explicit geometry (be it a toric variety, scheme, ...) if any non-trivial computations are to be conducted, such as blowups/resolutions of singularities. Based on recent conversations with @wdecker , I believe we should discuss if abstract varieties (cf. https://docs.oscar-system.org/dev/Experimental/IntersectionTheory/AbstractVarieties/) are to replace family of spaces. (Related old PR: [FTheoryTools] Remove stanley reisner ideal for family of spaces #3544.)
      • Related question: Can we have defining_classes, explicit_model_sections and alike for those abstract varieties? But maybe we indeed can...
  • Mikelis:
    • Update attribute that associates a Weierstrass model to a hypersurface/Tate model, so that it can construct the WS model associated to a given model from the database when another database file exists for it.
  • Martin:

QSM focus

  • Expect matter at curves between different U(2) factors, that is not charged under U(1). Add technology for these computations into FTheoryTools. (Andrew)
  • Present the blow_ups (in particular if conducted on affine charts) in a way that is readable for physicists. Also interpret complicated blowups. To be discussed with Anne. (Andrew)
  • Some level of support for chiral spectra. (Martin)

Final goals:

  • Study singular limit of QSMs (c.f. root bundles papers) and try to resolve the singular geometry.
  • Keep track of U(1) sections. (Yes, their resolution is at another level, but we should be able to keep track of them.)

New models for data base (for @emikelsons)

Data and serialization (for and with Antony)

  • We could consider serialzing G4-fluxes (a.k.a. cohomology classes on toric spaces). At least for the QSMs, there is each time a specifically chosen G4-fluxes (cf. https://arxiv.org/pdf/2102.10115, equ. 2.25).
  • Based on Serialization of Lie algebras #3980, could also serialize Lie algebras of the FTheoryModels. Again, a particular instance includes the QSM models.
  • Add an artifact/database or alike for the model discussed in [FTheoryTools] Add model 1511.03209 #3978. I have the corresponding .mrdi files and will be happy to share them. They are about 1.5TB in total size.)
  • Make use of the attribute saver of @antonydellavecchia (cf. Serialize Types with Attributes #4020) to automatically serialize more/all attributes. For instance, even after the above, for instance the known resolutions are not saved for FTheory models.
  • Database 2.0, i.e. use mrdi files.
  • Metadata via Mardi portal.

Milestones

  • Tate autoresolver: Use insights of "Tateform on steroids" to automatically resolve a Tate model as much as possible. (Andrew)
  • Migrate the code from experimental into source.
  • Nagell's algorithm?

Completed

Abandoned (at least for now)

  • Convert a Weierstrass into a Tate model? Can be done locally, but what is the global obstruction? Answer: Let us not (yet) get into this.~~

(cc @apturner)

@HereAround HereAround added enhancement New feature or request optimization Simpler/more performant code or more/better tests topic: FTheoryTools labels Aug 17, 2023
@HereAround HereAround changed the title FTheoryTools - Goals for 2023 and beyond FTheoryTools - Goals for 2024 and beyond Feb 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request optimization Simpler/more performant code or more/better tests topic: FTheoryTools
Projects
None yet
Development

No branches or pull requests

2 participants