-
-
Notifications
You must be signed in to change notification settings - Fork 453
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
Improve and fix documentation of Combinatorial or Discrete Geometry #22496
Comments
Branch: u/jipilab/improve_doc_poly |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Commit: |
comment:5
Salut ! missing empty line here
and in several other places.... |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:10
I would not give cones and fan "Toric Varieties" title, there are classes for these which are based on fans and cones. Also |
comment:11
I agree. I was sorting through the files and for the first version I put the 7 files whose documentation started with This module was designed as a part of framework for toric varieties together in a section called Toric Varieties. Perhaps naming the section. Lattices, Cones, Fans, and related objects ? What do you think? Do you have any suggestions?
Okay. Are there other modules that would logically go with them as well? |
comment:12
"Toric Geometry" may be appropriate, just no "varieties" themselves, I think. Everything under "Lattice polyhedra" may be clamped with it - while there are presumably other reasons to consider them, almost everything here was done with toric geometry and mirror symmetry applications in mind. |
comment:13
Replying to @novoselt:
Sounds good.
I could put it in the polyhedral computations section after the lattice polytopes, that would be good? One argument to keep "Toric geometry" in its own section is somehow to reflect a little bit the structure in the geometry component (although I admit it does not necessarily have to follow it...) since polyhedron is a module on its own and the toric geometry framework is located directly in geometry and not in polyhedron... I'm fine with both. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Dependencies: #22469 |
comment:16
A very related question (for another ticket, but it is good to have your opinion while you are at it) would be to move the isolated python files within The files to classify are:
|
Changed dependencies from #22469 to none |
comment:17
Would make sense to have
|
comment:18
Replying to @novoselt:
OK great, having such a |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Dependencies: #13517 |
comment:20
Okay. I would say that it is ready to be reviewed again. |
Changed dependencies from #13517 to none |
Branch pushed to git repo; I updated commit sha1. New commits:
|
Reviewer: Vincent Klein |
comment:24
doctest passed on :
build of the doc passed and page discrete_geometry/index.html looks conform. |
Changed branch from u/jipilab/improve_doc_poly to |
The reference manual for the currently called combinatorial geometry needs some logical reorganization.
http://doc.sagemath.org/html/en/reference/geometry/index.html
This ticket fixes the following:
CC: @mo271 @mkoeppe @videlec @sagetrac-tmonteil @fchapoton
Component: geometry
Keywords: polyhedron, days84
Author: Jean-Philippe Labbé
Branch/Commit:
f931571
Reviewer: Vincent Klein
Issue created by migration from https://trac.sagemath.org/ticket/22496
The text was updated successfully, but these errors were encountered: