Something like this was suggested by @jankoboehm during the Jahrestagung.
Of course we can mention the "low level" interfaces by Singular.jl/GAP.jl/Polymake.jl here but that's not the main point (for those, hopefully their respective manuals already cover this, and we can just link there).
But the real point is to compare the "native" Oscar interfaces. But I think it should not be about simply giving a table comparing functions between systems; the real point is how things interact. Also, for things like "how do I create a polynomial ring and compute a Gröbner basis, I think our manual is already sufficient (or at least should/could be).
Better: present some medium sized examples and doing them in both systems, and comparing the various choice made.
I think to create those, we need to pair one Oscar expert A with one person B who is expert in one of the other systems and wants to learn Oscar; then pick a non-trivial example to handle, ask B to write it in their system, and then A and B together write it in Oscar (as a by product we may discover "missing" functionality and can add it as we go along)
Something like this was suggested by @jankoboehm during the Jahrestagung.
Of course we can mention the "low level" interfaces by Singular.jl/GAP.jl/Polymake.jl here but that's not the main point (for those, hopefully their respective manuals already cover this, and we can just link there).
But the real point is to compare the "native" Oscar interfaces. But I think it should not be about simply giving a table comparing functions between systems; the real point is how things interact. Also, for things like "how do I create a polynomial ring and compute a Gröbner basis, I think our manual is already sufficient (or at least should/could be).
Better: present some medium sized examples and doing them in both systems, and comparing the various choice made.
I think to create those, we need to pair one Oscar expert A with one person B who is expert in one of the other systems and wants to learn Oscar; then pick a non-trivial example to handle, ask B to write it in their system, and then A and B together write it in Oscar (as a by product we may discover "missing" functionality and can add it as we go along)