Tropical polyhedra: Types and basic properties#4001
Tropical polyhedra: Types and basic properties#4001benlorenz merged 51 commits intooscar-system:masterfrom
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #4001 +/- ##
==========================================
- Coverage 84.88% 84.82% -0.07%
==========================================
Files 697 699 +2
Lines 94180 94337 +157
==========================================
+ Hits 79948 80019 +71
- Misses 14232 14318 +86
🚀 New features to boost your workflow:
|
|
At the moment, questions that need to be discussed:
|
|
What the status of this PR? |
|
This has been pushed to my backlog over the last few months, but I just finished a great deal of work. So thank you for reminding me of this. At the moment, I just had some prototype code. |
8b01da9 to
b52bd86
Compare
|
Let's first finalize #4061. Afterwards it will be easier to see how we want to design this. One aspect to take into account is that @YueRen chose a nonhomogeneous setting. However, the natural interface between tropical convexity and tropical algebraic geometry goes through tropical hyperplane arrangements described by homogeneous linear forms. |
|
In the meantime #4061 has been merged a few weeks ago. So if @ooinaruhugh is still interested and has some spare time, perhaps this can be brought forward? :-) |
|
The overall goal still stands. To make progress now, we tackle the following slightly simpler problem. first Input: point configuration in tropical projective space; Output: covector decomposition induced on tropical projective torus (which is an ordinary polyhedral complex). This can be inherited from polymake directly. |
b52bd86 to
b0c6c19
Compare
|
While testing the |
3bb1149 to
7510eef
Compare
Can you provide an explicit (polymake) example of this discrepancy? |
aa47c2d to
6037119
Compare
|
ping @ooinaruhugh |
|
The discussed discrepancies meant that we had to fix some parts in |
8b9a54a to
f0e3eff
Compare
371a8d7 to
c9ef278
Compare
Co-authored-by: Lars Göttgens <lars.goettgens@gmail.com>
Co-authored-by: Yue Ren <yue.ren.kl@gmail.com>
Co-authored-by: Yue Ren <yue.ren.kl@gmail.com>
Co-authored-by: Yue Ren <yue.ren.kl@gmail.com>
b2502ef to
d3f2edd
Compare
Co-authored-by: Yue Ren <yue.ren.kl@gmail.com>
fingolfin
left a comment
There was a problem hiding this comment.
Would be nice to get this merged. There is a bunch of minor code review comments that could be addressed with a few clicks of "apply suggestions". A couple others seem to be resolved and just need to be marked as such.
There is also the issue of the "polymake hotfix", no idea what the status there is?
It was released as part of polymake 4.15 and is available as polymake_jll-400.1500.000. This version is already in use by Oscar. |
There was a problem hiding this comment.
@ooinaruhugh Looks great, thanks for your contribution! Here just some very minor nitpicks.
Co-authored-by: Max Horn <max@quendi.de> Co-authored-by: Yue Ren <yue.ren.kl@gmail.com>
fingolfin
left a comment
There was a problem hiding this comment.
Looks good to me, thank you very much!
Co-authored-by: Benjamin Lorenz <benlorenz@users.noreply.github.com>
Polymake has support for tropical polyhedra, but what is there does not interface so nicely with OSCAR.
This PR serves to add a proper Julia type
TropicalPolyhedronand provide basic functionality, to fix some design decisions about the data type.This might also be useful in light of #3989 (review).
EDIT: I discussed this PR with @micjoswig and we came up with the following outline.
In terms of data types: try a map which send a set (describing the stratum) to a polyhedral complex. Beware that polyhedral complexes require the vertices to be numbered consecutively. Because each stratum only sees a subset of the given points, we need an array and a map for translating indices back and forth.