| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| mptopcom [2020/06/05 12:25] – lkastner | mptopcom [2020/08/28 10:48] – New release mptopcom 1.2 lkastner |
|---|
| Here are download links to tarballs containing the sources of **mptopcom**: | Here are download links to tarballs containing the sources of **mptopcom**: |
| |
| * [[https://polymake.org/lib/exe/fetch.php/download/mptopcom-1.1.tar.bz2|mptopcom-1.1.tar.bz2]] from 2019-05-29 for polymake versions before 4.0. | * [[https://polymake.org/lib/exe/fetch.php/download/mptopcom-1.2.tar.bz2|mptopcom-1.2.tar.bz2]] |
| * [[https://polymake.org/lib/exe/fetch.php/download/mptopcom-1.1_polymake4.0.tar.bz2|mptopcom-1.1_polymake4.0.tar.bz2]] from 2020-02-07 for polymake versions after 4.0. | |
| |
| Note that recent changes in polymake were breaking, so only the second version works with polymake 4.0 and newer. | Note that recent changes in polymake were breaking, so only the second version works with polymake 4.0 and newer. |
| ==== Old versions ==== | ==== Old versions ==== |
| |
| | * [[https://polymake.org/lib/exe/fetch.php/download/mptopcom-1.1.tar.bz2|mptopcom-1.1.tar.bz2]] from 2019-05-29 for polymake versions before 4.0. |
| | * [[https://polymake.org/lib/exe/fetch.php/download/mptopcom-1.1_polymake4.0.tar.bz2|mptopcom-1.1_polymake4.0.tar.bz2]] from 2020-02-07 for polymake versions after 4.0. |
| * [[https://polymake.org/lib/exe/fetch.php/download/mptopcom-1.0r2.tar.bz2|mptopcom-1.0r2.tar.bz2]] from 2018-05-14 with a bugfix for newer polymake. | * [[https://polymake.org/lib/exe/fetch.php/download/mptopcom-1.0r2.tar.bz2|mptopcom-1.0r2.tar.bz2]] from 2018-05-14 with a bugfix for newer polymake. |
| |
| --prefix=/path/to/install/dir | --prefix=/path/to/install/dir |
| </code> | </code> |
| The configure command will extract most of the information needed from polymake's ''%%polymake-config%%'' command. | The configure command will extract most of the information needed from polymake’s ''%%polymake-config%%'' command. |
| |
| The binaries are in the ''%%build/Opt/bin%%'' folder after building and in the ''%%prefix/bin%%'' folder after installation. Besides the usual **TOPCOM** binaries there are four new binaries: | The binaries are in the ''%%build/Opt/bin%%'' folder after building and in the ''%%prefix/bin%%'' folder after installation. Besides the usual **TOPCOM** binaries there are four new binaries: |
| </code> | </code> |
| ===== Usage ===== | ===== Usage ===== |
| Input files are formatted as in TOPCOM. The points are given homogeneously, i.e. embedded at height one. After the points you can give the generators of a group acting on your point set. Here is the example of the input file for the two-dimensional 0-1-square: | |
| | Input files are formatted as in TOPCOM, please have a look at the files in the ''%%examples%%'' folder for samples. The points are given homogeneously, i.e. embedded at height one. After the points you can give the generators of a group acting on your point set. Here is the example of the input file for the two-dimensional 0-1-square: |
| |
| <code> | <code> |
| ] | ] |
| </code> | </code> |
| If this file is called ''square.dat'', you can then call mptopcom in the following way: | You can then call mptopcom in the following way: |
| <code> | <code> |
| mpirun -np 5 mptopcom < square.dat | mpirun -np 5 mptopcom < examples/cube_4.dat |
| </code> | </code> |
| For other examples, please have a look at the files in the ''%%examples%%''. | |
| |
| If you did not run ''%%make install%%'' you can call the binary in the ''%%build/Opt/bin%%'' folder: | If you did not run ''%%make install%%'' you can call the binary in the ''%%build/Opt/bin%%'' folder: |
| |
| ==== Budgeting options ==== | ==== Budgeting options ==== |
| |
| - ''%%-maxnodes%%'' only affects the "bumps" at maxnodes and scale*maxnodes. | - ''%%-maxnodes%%'' only affects the “bumps” at maxnodes and scale*maxnodes. |
| - ''%%-scale%%'' sets the scaling factor when we have many jobs available (workers can work longer if we aren't trying to split jobs) | - ''%%-scale%%'' sets the scaling factor when we have many jobs available (workers can work longer if we aren’t trying to split jobs) |
| - ''%%-maxd%%'' sets the max depth to go to when we don't have enough jobs available (2 is the default, which is aggressive. 0 disables) | - ''%%-maxd%%'' sets the max depth to go to when we don’t have enough jobs available (2 is the default, which is aggressive. 0 disables) |
| - ''%%-lmax%%'' sets the point where -scale is used (if |L| > lmax * numproc) | - ''%%-lmax%%'' sets the point where -scale is used (if |L| > lmax * numproc) |
| - ''%%-lmin%%'' sets the point where -maxd is used (if |L| < lmin * numproc) | - ''%%-lmin%%'' sets the point where -maxd is used (if |L| < lmin * numproc) |
| ''%%mptopcom1%%'' can output polymake code that one can paste into polymake to obtain the reverse search tree in the edge graph of the secondary polytope. This will not work for large examples, so handle with care. There are three possibilities: | ''%%mptopcom1%%'' can output polymake code that one can paste into polymake to obtain the reverse search tree in the edge graph of the secondary polytope. This will not work for large examples, so handle with care. There are three possibilities: |
| |
| <HTML><ol style="list-style-type: decimal;"></HTML> | - Give ''%%mptopcom1%%'' an example without symmetry group: |
| <HTML><li></HTML><HTML><p></HTML>Give ''%%mptopcom1%%'' an example without symmetry group:<HTML></p></HTML> | |
| <code> | <code> |
| ./build/Opt/bin/mptopcom1 --make-tree < mp_examples/nosym/moae.dat | ./build/Opt/bin/mptopcom1 --make-tree < mp_examples/nosym/moae.dat |
| </code> | </code> |
| This will just draw all nodes in the same color and the edges between them that the reverse search used.<HTML></li></HTML> | This will just draw all nodes in the same color and the edges between them that the reverse search used. 2. Give ''%%mptopcom1%%'' an example with symmetry group: |
| <HTML><li></HTML><HTML><p></HTML>Give ''%%mptopcom1%%'' an example with symmetry group:<HTML></p></HTML> | |
| <code> | <code> |
| ./build/Opt/bin/mptopcom1 --make-tree < examples/moae.dat | ./build/Opt/bin/mptopcom1 --make-tree < examples/moae.dat |
| </code> | </code> |
| Now just the canonical representatives are drawn and the edges between them come from the reverse search, but they do not have to correspond to edges of the secondary polytope, since there can be a flip between classes of triangulations, while there is no flip between the canonical representatives.<HTML></li></HTML> | Now just the canonical representatives are drawn and the edges between them come from the reverse search, but they do not have to correspond to edges of the secondary polytope, since there can be a flip between classes of triangulations, while there is no flip between the canonical representatives. 3. Give ''%%mptopcom1%%'' an example with symmetry group and the parameter –make-marked-tree: |
| <HTML><li></HTML><HTML><p></HTML>Give ''%%mptopcom1%%'' an example with symmetry group and the parameter --make-marked-tree:<HTML></p></HTML> | |
| <code> | <code> |
| ./build/Opt/bin/mptopcom1 --make-marked-tree < examples/moae.dat | ./build/Opt/bin/mptopcom1 --make-marked-tree < examples/moae.dat |
| </code> | </code> |
| <HTML><p></HTML>This call will make ''%%mptopcom1%%'' ignore the symmetry group. So the node number and the edges are the same as in 1. However, the tree generating procedure will use the symmetry group to color nodes according to their class membership.<HTML></p></HTML><HTML></li></HTML><HTML></ol></HTML> | This call will make ''%%mptopcom1%%'' ignore the symmetry group. So the node number and the edges are the same as in 1. However, the tree generating procedure will use the symmetry group to color nodes according to their class membership. |
| |
| ===== Authors ===== | ===== Authors ===== |