tutorial:poly_db_querying

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Last revisionBoth sides next revision
tutorial:poly_db_querying [2017/08/07 15:26] – paffenholztutorial:poly_db_querying [2017/08/09 09:46] – paffenholz
Line 82: Line 82:
        print $p->N_LATTICE_POINTS;        print $p->N_LATTICE_POINTS;
                
-=== Obtain Information about available Databases and Collections === 
- 
-You can obtain information on the databases and collections in the database using the ''db_info'' command.  
-<code> 
-polytope> db_info(); 
-DATABASE: LatticePolytopes 
-This database contains various classes of lattice polytopes. 
- 
-Collection: SmoothReflexive 
-A complete collection of smooth reflexive lattice polytopes in dimensions up to 9, up to lattice equivalence. The lists were computed with the algorithm of  
-Mikkel Oebro (see [[http://arxiv.org/abs/0704.0049|arxiv: 0704.0049]]) and are taken from the [[http://polymake.org/polytopes/paffenholz/www/fano.html|website  
-of Andreas Paffenholz]]. 
- 
-In dimensions up to 7 the database contains the properties: 
-H_STAR_VECTOR, REFLEXIVE, DIM, LATTICE_CODEGREE, N_INTERIOR_LATTICE_POINTS, SMOOTH, N_LATTICE_POINTS, FACET_WIDTHS, VERTICES, FACETS, CENTROID, N_VERTICES,  
-contributor, LATTICE_DEGREE, LATTICE_VOLUME, EHRHART_POLYNOMIAL_COEFF, N_BOUNDARY_LATTICE_POINTS, ESSENTIALLY_GENERIC, VERY_AMPLE, F_VECTOR, GORENSTEIN,  
-FEASIBLE, LINEALITY_SPACE, AFFINE_HULL. 
- 
-In dimension 8 the lattice points are not stored, and in dimension 9 also NORMAL is not computed 
- 
-__________________ 
- 
-DATABASE: Manifolds 
-This database contains combinatorial manifolds 
- 
-Collection: DIM2_3 
-This is a collection of  combinatorial 2-  and  3-manifolds with up to 10 vertices given as triangulations and calculcated by Frank Lutz found at:  
-http://page.math.tu-berlin.de/~lutz/stellar/mixed.html 
- 
-[...] 
-</code> 
-The command takes the options ''db'' to list only collections in a particular database, ''collection'' to list only one collection (in this case ''db'' must also be given), and ''username'', if you have access to some collections not (yet) publicly available.  
- 
 === Obtain Information about Searchable Fields in a Collection === === Obtain Information about Searchable Fields in a Collection ===
  
Line 134: Line 101:
 GORENSTEIN  [int] GORENSTEIN  [int]
 H_STAR_VECTOR  [int] H_STAR_VECTOR  [int]
-LATTICE_CODEGREE  [int] +[...] 
-LATTICE_DEGREE  [int] + 
-LATTICE_POINTS_GENERATORS  [int] +Entries for smooth reflexive polytopes in dimension 8 
-LATTICE_VOLUME  [int] +---------------------------- 
-LINEALITY_SPACE  [dense, int] +AFFINE_HULL  [dense, int] 
-NORMAL  [int] +[...] 
-N_BOUNDARY_LATTICE_POINTS  [int] + 
-N_FACETS  [int] +Entries for smooth reflexive polytopes in dimension 9 
-N_INTERIOR_LATTICE_POINTS  [int] +---------------------------- 
-N_LATTICE_POINTS  [int] +AFFINE_HULL  [dense, int] 
-N_VERTICES  [int] +[...]
-POINTED  [int] +
-REFLEXIVE  [int] +
-SMOOTH  [int] +
-VERTICES  [dense, int] +
-VERY_AMPLE  [int]+
 </code> </code>
 +
 +There may be more than one list of searchable properties, e.g. if some properties cannot be stored or computed for some objects. Observe the header line of the list of properties to see which list applies to the objects you are looking for. The above lists apply to smooth reflexive polytopes in dimensions 1 to 7, in dimension 8 and in dimension 9. If a property appears in more than one list any search for this property will be executed on all objects that belong to one of the lists. 
                
 === Type Information === === Type Information ===
Line 159: Line 123:
    $t = db_get_type_information(db=>"LatticePolytopes", collection=>"SmoothReflexive", type_information_key=>'fano');    $t = db_get_type_information(db=>"LatticePolytopes", collection=>"SmoothReflexive", type_information_key=>'fano');
        
-For the format of such a typer information entry in the database see [[devel/polydb/format|here]].+For the format of such a type information entry in the database see [[devel/polydb/format|here]].