Skip to content
This repository has been archived by the owner on May 26, 2021. It is now read-only.

Oscar Roadmap #4

Closed
8 of 42 tasks
wbhart opened this issue Jun 17, 2019 · 4 comments
Closed
8 of 42 tasks

Oscar Roadmap #4

wbhart opened this issue Jun 17, 2019 · 4 comments

Comments

@wbhart
Copy link
Contributor

wbhart commented Jun 17, 2019

This is a roadmap of all issues people consider important or of high priority across the whole of the Oscar system.
Names are attached to the issues currently being worked on. They are in no particular order.

  • Infrastructure
  • AbstractAlgebra.jl, Nemo
    • Modules over Euclidean domains - @wbhart
    • iseuclidean, isdomain, etc. predicates in AbstractAlgebra
    • clean up left/right kernel/solve interface in AbstractAlgebra
    • Groups interface - @kalmarek @fieker @fingolfin
    • Interface conformance testing @kalmarek
    • Localisations of Z and K[x] in AbstractAlgebra/Nemo
  • Singular, Singular.jl
  • GAP, GAP.jl
  • Polymake, Polymayke.jl
  • Oscar.jl
    • User documentation for Oscar.jl
    • Conversion functions between different matrix and polynomial types in Oscar.jl
    • Make all dependencies of Oscar.jl build with a single version of Julia - @sebasguts @wbhart
    • Import of chosen default functionality into Oscar.jl from other systems
      • This does not mean "using Hecke; using Nemo; using Singular", etc. It means importing only the required functionality, as the former is not expected to be possible.
  • Unsorted
    • Finitely generated abelian groups - @fieker
    • Harmonise interface for Fin Gen Ab Gps and Fin Pres Mods over Euc Dom - @fieker @wbhart
    • Embeddings of finite fields
    • Euc. domain interface, esp. for polys and matrices in AbstractAlgebra - @wbhart @fieker
    • Rational functions over cyclotomic fields (requested by Frank and Thomas) - @wbhart @fieker @tthsqe12
    • Precompile some code for basic rings (e.g. Z, Z/pZ, Q, etc.) to avoid Jit overhead
    • Implement Julia map functionality for our types
    • Implement more of Julia's view/submatrix functionality where they make sense for our types
    • Decorated rings/modules (gradings, etc.)
@fingolfin
Copy link
Member

@fieker @CarloSircana we (me and @sebasguts ) have been wondering what "High level interface for GAP.jl" is meant to be -- is that just a duplicate of the "Groups interface" entry, or something else? If so, could you please explain? Clearly we can't implement anything we don't know about :-)

@fieker
Copy link

fieker commented Jun 19, 2019 via email

@wbhart
Copy link
Contributor Author

wbhart commented Jun 19, 2019

What @kalmarek and I had in mind for the Group Interface was a written document describing an interface to Groups in AbstractAlgebra and/or Oscar.

The high level interface for GAP.jl is an actual implementation of a layer on top of GAP.jl which makes the functionality in GAP available in a version that uses Julia naming conventions and paradigms, similar to what we have done with Singular.jl vs its libsingular module.

I am sure it will encompass parts of the Galois Groups interface @fieker has planned and certainly parts of the interface you guys have been working on. But note that the interface for Groups has to also encompass @kalmarek 's permutation groups (if possible) and @fieker 's finitely generated abelian groups, which are entirely in Julia. So the project is more than an interface layer to GAP.jl.

If everyone working on groups (I am not) think there is a better arrangement of what you guys are actually doing, please do rearrange this to reflect what you are actually doing.

@wbhart
Copy link
Contributor Author

wbhart commented Sep 25, 2019

Moved to Oscar.jl.

@wbhart wbhart closed this as completed Sep 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants