‣ InfoPolymaking | ( info class ) |
If set to at least 2, the output of polymake is shown. At level 1, warnings are shown. This is the default. And at level 0, the polymake package remains silent.
‣ POLYMAKE_LAST_FAIL_REASON | ( global variable ) |
Contains a string that explains the last occurrence of fail as a return value of Polymake (2.5-1).
The variables for interaction with the system are contained in the file environment.gi. Each of these variables has a function to set it, see 1.2. If POLYMAKE_COMMAND or POLYMAKE_DATA_DIR are set at startup, they are not overwritten. So if you don't want (or don't have the rights) to modify environment.gi, you can set the variables in your .gaprc file.
‣ POLYMAKE_COMMAND | ( global variable ) |
This variable should contain the name of the polymake program in the form as returned by Filename So a probable value is Filename(Directory("/usr/local/bin"),"polymake").
‣ POLYMAKE_DATA_DIR | ( global variable ) |
In this directory the files for polymake will be created. By default, this generates a temporary directory using DirectoryTemporary
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chapInd_mj.html 0000644 0001751 0001751 00000015401 15114057717 017007 0 ustar runner runnerAppendInequalitiesToPolymakeObject 2.4-4 AppendPointlistToPolymakeObject 2.4-2 AppendToPolymakeObject 2.4-1 AppendVertexlistToPolymakeObject 2.4-3 CheckAppVerTypList 2.1-3 ClearPolymakeObject 2.4-6 ConvertMatrixToPolymakeString 2.4-5 ConvertPolymakeBoolToGAP 4.2-6 ConvertPolymakeGraphToGAP 4.2-9 ConvertPolymakeIntVectorToGAPPlusOne 4.2-5 ConvertPolymakeListOfSetsToGAP 4.2-8 ConvertPolymakeListOfSetsToGAPPlusOne 4.2-8 ConvertPolymakeMatrixOrListOfSetsToGAP 4.2-3 ConvertPolymakeMatrixOrListOfSetsToGAPPlusOne 4.2-3 ConvertPolymakeMatrixToGAP 4.2-4 ConvertPolymakeMatrixToGAPKillOnes 4.2-4 ConvertPolymakeNumber 4.2-1 ConvertPolymakeOutputToGapNotation 4.1-2 ConvertPolymakeScalarToGAP 4.2-2 ConvertPolymakeSetToGAP 4.2-7 ConvertPolymakeVectorToGAP 4.2-5 ConvertPolymakeVectorToGAPKillOne 4.2-5 CreateEmptyFile 2.1-1 CreatePolymakeObject 2.1-2 CreatePolymakeObjectFromFile 2.1-4 DirectoryOfPolymakeObject 2.2-1 FilenameOfPolymakeObject 2.2-2 FullFilenameOfPolymakeObject 2.2-3 InfoPolymaking 3.1-1 KnownPropertiesOfPolymakeObject 2.2-5 NamesKnownPropertiesOfPolymakeObject 2.2-4 ObjectConverters 4.1-4 Polymake 2.5-1 POLYMAKE_COMMAND 3.2-1 POLYMAKE_DATA_DIR 3.2-2 POLYMAKE_LAST_FAIL_REASON 3.1-2 PropertyOfPolymakeObject 2.2-6 SetPolymakeCommand 1.2-2 SetPolymakeDataDirectory 1.2-1 SplitPolymakeOutputStringIntoBlocks 4.1-3 UnbindKnownPropertyOfPolymakeObject 2.4-8 WriteKnownPropertyToPolymakeObject 2.4-7
generated by GAPDoc2HTML
polymaking-0.8.8/doc/output.xml 0000644 0001751 0001751 00000007442 15114057717 016155 0 ustar runner runner[GJ] Gawrilow, E. and Joswig, M., polymake, \url{https://polymake.org/}.
generated by GAPDoc2HTML
polymaking-0.8.8/doc/polymaking.xml 0000644 0001751 0001751 00000000700 15114057717 016755 0 ustar runner runnerThe interaction with the polymake program is done via files. A PolymakeObject is mainly a pointer to a file and a list of known properties of the object. These properties need not be stored in the file. Whenever polymake is called, the returned value is read from standard output and stored in the PolymakeObject corresponding to the file for which polymake is called. The files for polymake are written in the old (non-xml) format. The first run of polymake converts them into the new (xml) format. This means that changes to the file by means of the methods outlined below after the first run of polymake will probably lead to corrupted files.
‣ CreateEmptyFile( filename ) | ( method ) |
Returns: nothing
Creates an empty file with name filename. Note that filename has to include the full path and the directory for the file must exist.
‣ CreatePolymakeObject( [prefix][,] [dir][,] [appvertyp] ) | ( method ) |
Returns: PolymakeObject
If called without arguments, this method generates an empty file in the directory defined by POLYMAKE_DATA_DIR (3.2-2). If a directory dir is given (this directory must exist), an empty file is generated in this directory. If prefix is not given, the file is called polyN where N is the current runtime. If a file of this name already exists, a number is appended separated by a dot (example: "poly1340" and "poly1340.1"). If prefix is given, the filename starts with this prefix. Optionally, the file can be generated with a header specifying application, version and type of the object. This is done by passing the triple of strings appvertyp to CreatePolymakeObject. A valid triple is ["polytope","2.3","RationalPolytope"]. Validity is checked by CheckAppVerTypList (2.1-3).
‣ CheckAppVerTypList( appvertyp ) | ( method ) |
Returns: bool
Checks if the triple arppvertyp of strings specifies an application and type of polymake version 2.3. More specifically, the first entry has to be an application from ["polytope","surface","topaz"] and the third entry has to be a type corresponding to the application given in the first entry. The second entry is not checked.
‣ CreatePolymakeObjectFromFile( [dir, ]filename ) | ( method ) |
Returns: PolymakeObject
This method generates a PolymakeObject corresponding to the file filename in the directory dir. If dir is not given, the POLYMAKE_DATA_DIR is used.If no file with name filename exists in dir (or POLYMAKE_DATA_DIR, respectively), an empty file is created. Note that the contents of the file do not matter for the generation of the object. In particular, the object does not know any of the properties that might be encoded in the file. The only way to transfer information from files to PolymakeObjects is via Polymake (2.5-1).
A PolymakeObject contains information about the directory of its file, the name of its file and about properties calculated by calling Polymake (2.5-1). The properties returned by the polymake program are stored under the name polymake assigns to them (that is, the name of the data block in the corresponding file). The following methods can be used to access the information stored in a PolymakeObject. But be careful! All functions return the actual object. No copies are made. So if you change one of the returned objects, you change the PolymakeObject itself.
‣ DirectoryOfPolymakeObject( poly ) | ( method ) |
Returns: Directory
Returns the directory of the file associated with poly.
‣ FilenameOfPolymakeObject( poly ) | ( method ) |
Returns: String
Returns the name of the file associated with poly. This does only mean the name of the file, not the full path. For the full path and file name see FullFilenameOfPolymakeObject (2.2-3)
‣ FullFilenameOfPolymakeObject( poly ) | ( method ) |
Returns: String
Returns the file associated with the PolymakeObject poly with its complete path.
‣ NamesKnownPropertiesOfPolymakeObject( poly ) | ( method ) |
Returns: List of Strings
Returns a list of the names of all known properties. This does only include the properties returned by Polymake (2.5-1), "dir" and "filename" are not included. If no properties are known, fail is returned.
‣ KnownPropertiesOfPolymakeObject( poly ) | ( method ) |
Returns: Record
Returns the record of all known properties. If no properties are known, fail is returned.
‣ PropertyOfPolymakeObject( poly, name ) | ( method ) |
Returns the value of the property name if it is known. If the value is not known, fail is returned. name must be a String.
Suppose the file /tmp/threecube.poly contains the three dimensional cube in polymake form. Now generate a PolymakeObject from this file and call Polymake (2.5-1) to make the vertices of the cube known to the object.
### suppose we have a polymake file /tmp/threecube.poly ### containing a cube in three dimensions gap> cube:=CreatePolymakeObjectFromFile(Directory("/tmp"),"threecube.poly"); <polymake object. No properties known> gap> FilenameOfPolymakeObject(cube); "threecube.poly" gap> FullFilenameOfPolymakeObject(cube); "/tmp/threecube.poly" #nothing is known about the cube: gap> NamesKnownPropertiesOfPolymakeObject(cube); fail gap> Polymake(cube,"VERTICES"); [ [ -1, -1, -1 ], [ 1, -1, -1 ], [ -1, 1, -1 ], [ 1, 1, -1 ], [ -1, -1, 1 ], [ 1, -1, 1 ], [ -1, 1, 1 ], [ 1, 1, 1 ] ] # Now <cube> knows its vertices: gap> Print(cube); <polymake object threecube.poly. Properties known: [ "VERTICES" ]> gap> PropertyOfPolymakeObject(cube,"VERTICES"); [ [ -1, -1, -1 ], [ 1, -1, -1 ], [ -1, 1, -1 ], [ 1, 1, -1 ], [ -1, -1, 1 ], [ 1, -1, 1 ], [ -1, 1, 1 ], [ 1, 1, 1 ] ] gap> KnownPropertiesOfPolymakeObject(cube); rec( VERTICES := [ [ -1, -1, -1 ], [ 1, -1, -1 ], [ -1, 1, -1 ], [ 1, 1, -1 ], [ -1, -1, 1 ], [ 1, -1, 1 ], [ -1, 1, 1 ], [ 1, 1, 1 ] ] )
To transfer data from GAP to polymake, the following methods can be used. But bear in mind that none of these functions test if the resulting polymake file is still consistent.
‣ AppendToPolymakeObject( poly, string ) | ( method ) |
Returns: nothing
This appends the string string to the file associated to the PolymakeObject poly. It is not tested if the string is syntactically correct as a part of a polymake file. It is also not tested if the string is compatible with the data already contained in the file.
INEQUALITIES, POINTS and VERTICES can be appended to a polymake object using the following functions:
‣ AppendPointlistToPolymakeObject( poly, pointlist ) | ( method ) |
Returns: nothing
Takes a list pointlist of vectors and converts it into a string which represents a polymake block labeled "POINTS". This string is then added to the file associated with poly. The "POINTS" block of the file associated with poly then contains points with leading ones, as polymake uses affine notation.
‣ AppendVertexlistToPolymakeObject( poly, pointlist ) | ( method ) |
Returns: nothing
Does the same as AppendPointlistToPolymakeObject, but with "VERTICES" instead of "POINTS".
‣ AppendInequalitiesToPolymakeObject( poly, ineqlist ) | ( method ) |
Returns: nothing
Just appends the inequalities given in ineqlist to the polymake object poly (with caption "INEQUALITIES"). Note that this does not check if an "INEQUALITIES" section does already exist in the file associated with poly.
‣ ConvertMatrixToPolymakeString( name, matrix ) | ( method ) |
Returns: String
This function takes a matrix matrix and converts it to a string. This string can then be appended to a polymake file via AppendToPolymakeObject (2.4-1) to form a block of data labeled name. This may be used to write blocks like INEQUALITIES or FACETS.
‣ ClearPolymakeObject( poly[, appvertyp] ) | ( method ) |
Returns: nothing
Deletes all known properties of the PolymakeObject poly and replaces its file with an empty one.
If the triple of strings appvertyp specifying application, version and type (see CheckAppVerTypList (2.1-3)) is given, the file is replaced with a file that contains only a header specifying application, version and type of the polymake object.
There are also methods to manipulate the known values without touching the file of the PolymakeObject:
‣ WriteKnownPropertyToPolymakeObject( poly, name, data ) | ( method ) |
Takes the object data and writes it to the known properties section of the PolymakeObject poly. The string name is used as the name of the property. If a property with that name already exists, it is overwritten. Again, there is no check if data is consistent, correct or meaningful.
‣ UnbindKnownPropertyOfPolymakeObject( poly, name ) | ( method ) |
If the PolymakeObject poly has a property with name name, that property is unbound. If there is no such property, fail is returned.
‣ Polymake( poly, option: PolymakeNolookup ) | ( method ) |
This method calls the polymake program (see POLYMAKE_COMMAND (3.2-1)) with the option option. You may use several keywords such as "FACETS VERTICES" as an option. The returned value is cut into blocks starting with keywords (which are taken from output and not looked up in option). Each block is then interpreted and translated into GAP readable form. This translation is done using the functions given in ObjectConverters (4.1-4). The first line of each block of polymake output is taken as a keyword and the according entry in ObjectConverters (4.1-4) is called to convert the block into GAP readable form. If no conversion function is known, an info string is printed and fail is returned. If only one keyword has been given as option, Polymake returns the result of the conversion operation. If more than one keyword has been given or the output consists of more than one block, Polymake returns fail. In any case, the calculated values for each block are stored as known properties of the PolymakeObject poly as long as they are not fail. If Polymake is called with an option that corresponds to a name of a known property of poly, the known property is returned. In this case, there is no call of the external program. (see below for suppression of this feature).
Note that the command Polymake returns fail if nothing is returned by the program polymake or more than one block of data is returned. For example, the returned value of Polymake(poly,"VISUAL") is always fail. Likewise, Polymake(poly,"POINTS VERTICES") will return fail (but may add new known properties to poly). For a description of the conversion functions, see chapter 4.
If the option PolymakeNolookup is set to anything else than false, the polymake program is called even if poly already has a known property with name option.
Note that whenever Polymake returns fail, a description of the problem is stored in POLYMAKE_LAST_FAIL_REASON (3.1-2). If you call Polymake with more than one keyword, POLYMAKE_LAST_FAIL_REASON (3.1-2) is changed before polymake is called. So any further reason to return fail will overwrite it.
Let's generate a three dimensional permutahedron.
gap> S:=SymmetricGroup(3);
Sym( [ 1 .. 3 ] )
gap> v:=[1,2,3];
[ 1, 2, 3 ]
gap> points3:=Orbit(S,v,Permuted);;
# project to reduce ambient dimension
gap> points:=points3{[1..6]}{[1,2]};;
gap> permutahedron:=CreatePolymakeObject();
<polymake object. No properties known>
gap> AppendPointlistToPolymakeObject(permutahedron,points);
gap> Polymake(permutahedron,"VOLUME");
3
gap> Polymake(permutahedron,"N_VERTICES");
6
#Now <permutahedron> knows its number of vertices, but not the vertices:
gap> PropertyOfPolymakeObject(permutahedron,"VERTICES");
fail
gap> NamesKnownPropertiesOfPolymakeObject(permutahedron);
[ "VOLUME", "N_VERTICES" ]
#Let's look at the object!
gap> Polymake(permutahedron,"VISUAL");
#I There was no or wrong polymake output
fail
gap> Polymake(permutahedron,"DIM");
2
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chap0.html 0000644 0001751 0001751 00000030142 15114057717 015745 0 ustar runner runnerVersion 0.8.8
3 December 2025
Marc Roeder
Email: roeder.marc@gmail.com
This package provides a very basic interface to the polymake program by Ewgenij Gawrilow, Michael Joswig et al. [GJ]. The polymake program itself is not included.
© 2007--2013 Marc Roeder.
This package is distributed under the terms of the GNU General Public License version 2 or later (at your convenience). See the file "LICENSE" or https://www.gnu.org/copyleft/gpl.html
This work has been supported by Marie Curie Grant No. MTKD-CT-2006-042685
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chap0_mj.html 0000644 0001751 0001751 00000030713 15114057717 016437 0 ustar runner runnerVersion 0.8.8
3 December 2025
Marc Roeder
Email: roeder.marc@gmail.com
This package provides a very basic interface to the polymake program by Ewgenij Gawrilow, Michael Joswig et al. [GJ]. The polymake program itself is not included.
© 2007--2013 Marc Roeder.
This package is distributed under the terms of the GNU General Public License version 2 or later (at your convenience). See the file "LICENSE" or https://www.gnu.org/copyleft/gpl.html
This work has been supported by Marie Curie Grant No. MTKD-CT-2006-042685
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chapBib.txt 0000644 0001751 0001751 00000000235 15114057717 016155 0 ustar runner runner [1XReferences[101X [[20XGJ[120X] [16XGawrilow, E. and Joswig, M.[116X, [17Xpolymake[117X, \url{https://polymake.org/}. [32X polymaking-0.8.8/doc/times.css 0000644 0001751 0001751 00000000261 15114057717 015716 0 ustar runner runner /* times.css Frank Lübeck */ /* Change default CSS to use Times font. */ body { font-family: Times,Times New Roman,serif; } polymaking-0.8.8/doc/rainbow.js 0000644 0001751 0001751 00000005336 15114057717 016072 0 ustar runner runner function randchar(str) { var i = Math.floor(Math.random() * str.length); while (i == str.length) i = Math.floor(Math.random() * str.length); return str[i]; } hexdigits = "0123456789abcdef"; function randlight() { return randchar("cdef")+randchar(hexdigits)+ randchar("cdef")+randchar(hexdigits)+ randchar("cdef")+randchar(hexdigits) } function randdark() { return randchar("012345789")+randchar(hexdigits)+ randchar("012345789")+randchar(hexdigits)+ randchar("102345789")+randchar(hexdigits) } document.write('\n'); polymaking-0.8.8/doc/nocolorprompt.css 0000644 0001751 0001751 00000000313 15114057717 017510 0 ustar runner runner /* colors for ColorPrompt like examples */ span.GAPprompt { color: #000000; font-weight: normal; } span.GAPbrkprompt { color: #000000; font-weight: normal; } span.GAPinput { color: #000000; } polymaking-0.8.8/doc/chap1_mj.html 0000644 0001751 0001751 00000020221 15114057717 016431 0 ustar runner runnerTo install the package, just unpack it in your packages directory (usually ~/gap/pkg for local installation). To use polymaking, you need a working installation of the program polymake https://polymake.org. The package has been tested on linux and Mac OS X (10.4, 10.5 and 10.6). But it should be as platform independent as GAP and polymake.
The interaction with polymake is restricted to writing files and carrying out simple operations. These looked like
polymake file KEYWORD1 KEYWORD2 KEYWORD3
on the command line for polymake versions before 4. The keywords are polymake methods without arguments. Since polymake no longer supports this interface the polymaking package provides the script lib/pm_script_arg.pl to emulate this.
polymake ––script lib/pm_script_arg.pl KEYWORD1 KEYWORD2 KEYWORD3
Using custom scripts is not supported.
Every call to polymake will re-start the program anew. This causes considerable overhead. The number of calls to polymake is reduced by caching the results in the so-called PolymakeObject in GAP. As of polymaking version 0.8.0, old versions of polymake (i.e. versions before 2.7.9) are not supported anymore.
polymaking will try to guess the location of polymake. If this fails, a warning is issued at load time (InfoWarning level 1). Note that the guessing procedure is suppressed when POLYMAKE_COMMAND (3.2-1) is set manually (see 1.2-3).
setenv PATH ${PATH}:<your polymakepath>
The general rule is: If polymaking finds polymake by itself, there is nothing to worry about.
As polymaking uses the program polymake, it needs to know where this program lives. The communication with polymake is done by writing files for polymake and reading its output (as returned to standard output "the prompt"). Note that the interface does not read any polymake file.
‣ SetPolymakeDataDirectory( dir ) | ( method ) |
Sets the directory in which all polymake files are created to dir. The standard place for these files is a temporary directory generated when the package is loaded. This manipulates POLYMAKE_DATA_DIR (3.2-2).
‣ SetPolymakeCommand( command ) | ( method ) |
Sets the name for the polymake program to command. This manipulates POLYMAKE_COMMAND (3.2-1).
To permanently set the values of POLYMAKE_COMMAND (3.2-1), and POLYMAKE_DATA_DIR (3.2-2), add the lines
POLYMAKE_DATA_DIR:=Directory("/home/mypolymakedatadir");
POLYMAKE_COMMAND:=Filename(Directory("/home/mypolymakebindir/"),"polymake");
to your .gaprc file (see Reference: The gap.ini and gaprc files). Note that these have to be before the LoadPackage("polymaking"); line. Or you can change the values of the above variables by editing lib/environment.gi
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chap0.txt 0000644 0001751 0001751 00000007202 15114057717 015621 0 ustar runner runner [1X polymaking [101X [1X Interfacing the geometry software polymake [101X Version 0.8.8 3 December 2025 Marc Roeder Marc Roeder Email: [7Xmailto:roeder.marc@gmail.com[107X ------------------------------------------------------- [1XAbstract[101X [33X[0;0YThis package provides a very basic interface to the polymake program by Ewgenij Gawrilow, Michael Joswig et al. [GJ]. The polymake program itself is not included.[133X ------------------------------------------------------- [1XCopyright[101X [33X[0;0Y© 2007--2013 Marc Roeder.[133X [33X[0;0YThis package is distributed under the terms of the GNU General Public License version 2 or later (at your convenience). See the file "LICENSE" or [7Xhttps://www.gnu.org/copyleft/gpl.html[107X[133X ------------------------------------------------------- [1XAcknowledgements[101X [33X[0;0YThis work has been supported by Marie Curie Grant No. MTKD-CT-2006-042685[133X ------------------------------------------------------- [1XContents (polymaking)[101X 1 [33X[0;0YInstallation and Preface[133X 1.1 [33X[0;0YA few words about the installation of polymake[133X 1.2 [33X[0;0YSetting variables for external programs[133X 1.2-1 SetPolymakeDataDirectory 1.2-2 SetPolymakeCommand 1.2-3 [33X[0;0YSetting variables permanently[133X 2 [33X[0;0YPolymake interaction[133X 2.1 [33X[0;0YCreating Polymake Objects[133X 2.1-1 CreateEmptyFile 2.1-2 CreatePolymakeObject 2.1-3 CheckAppVerTypList 2.1-4 CreatePolymakeObjectFromFile 2.2 [33X[0;0YAccessing Properties of Polymake Objects[133X 2.2-1 DirectoryOfPolymakeObject 2.2-2 FilenameOfPolymakeObject 2.2-3 FullFilenameOfPolymakeObject 2.2-4 NamesKnownPropertiesOfPolymakeObject 2.2-5 KnownPropertiesOfPolymakeObject 2.2-6 PropertyOfPolymakeObject 2.3 [33X[0;0YExample: Creating and Accessing Polymake Objects[133X 2.4 [33X[0;0YWriting to Polymake Objects[133X 2.4-1 AppendToPolymakeObject 2.4-2 AppendPointlistToPolymakeObject 2.4-3 AppendVertexlistToPolymakeObject 2.4-4 AppendInequalitiesToPolymakeObject 2.4-5 ConvertMatrixToPolymakeString 2.4-6 ClearPolymakeObject 2.4-7 WriteKnownPropertyToPolymakeObject 2.4-8 UnbindKnownPropertyOfPolymakeObject 2.5 [33X[0;0YCalling Polymake and converting its output[133X 2.5-1 Polymake 2.6 [33X[0;0YAn Example[133X 3 [33X[0;0YGlobal Variables[133X 3.1 [33X[0;0YGetting information about polymake output[133X 3.1-1 InfoPolymaking 3.1-2 POLYMAKE_LAST_FAIL_REASON 3.2 [33X[0;0YVariables for system interaction[133X 3.2-1 POLYMAKE_COMMAND 3.2-2 POLYMAKE_DATA_DIR 4 [33X[0;0YConverting Polymake Output[133X 4.1 [33X[0;0YThe General Method[133X 4.1-1 [33X[0;0YConverter- Philosopy[133X 4.1-2 ConvertPolymakeOutputToGapNotation 4.1-3 SplitPolymakeOutputStringIntoBlocks 4.1-4 ObjectConverters 4.2 [33X[0;0YConversion Functions[133X 4.2-1 ConvertPolymakeNumber 4.2-2 ConvertPolymakeScalarToGAP 4.2-3 ConvertPolymakeMatrixOrListOfSetsToGAP 4.2-4 ConvertPolymakeMatrixToGAP 4.2-5 ConvertPolymakeVectorToGAP 4.2-6 ConvertPolymakeBoolToGAP 4.2-7 ConvertPolymakeSetToGAP 4.2-8 ConvertPolymakeListOfSetsToGAP 4.2-9 ConvertPolymakeGraphToGAP [32X polymaking-0.8.8/doc/chap1.txt 0000644 0001751 0001751 00000007600 15114057717 015624 0 ustar runner runner [1X1 [33X[0;0YInstallation and Preface[133X[101X [33X[0;0YTo install the package, just unpack it in your packages directory (usually [10X~/gap/pkg[110X for local installation). To use [5Xpolymaking[105X, you need a working installation of the program polymake [7Xhttps://polymake.org[107X. The package has been tested on linux and Mac OS X (10.4, 10.5 and 10.6). But it should be as platform independent as [5XGAP[105X and polymake.[133X [33X[0;0YThe interaction with polymake is restricted to writing files and carrying out simple operations. These looked like[133X [33X[0;0Y[10Xpolymake file KEYWORD1 KEYWORD2 KEYWORD3[110X[133X [33X[0;0Yon the command line for polymake versions before 4. The keywords are polymake methods without arguments. Since polymake no longer supports this interface the polymaking package provides the script [10Xlib/pm_script_arg.pl[110X to emulate this.[133X [33X[0;0Y[10Xpolymake ––script lib/pm_script_arg.pl KEYWORD1 KEYWORD2 KEYWORD3[110X[133X [33X[0;0YUsing custom scripts is not supported.[133X [33X[0;0YEvery call to polymake will re-start the program anew. This causes considerable overhead. The number of calls to polymake is reduced by caching the results in the so-called [9XPolymakeObject[109X in GAP. As of polymaking version 0.8.0, old versions of polymake (i.e. versions before 2.7.9) are not supported anymore.[133X [1X1.1 [33X[0;0YA few words about the installation of polymake[133X[101X [33X[0;0Y[5Xpolymaking[105X will try to guess the location of polymake. If this fails, a warning is issued at load time ([9XInfoWarning[109X level 1). Note that the guessing procedure is suppressed when [2XPOLYMAKE_COMMAND[102X ([14X3.2-1[114X) is set manually (see [14X1.2-3[114X).[133X [33X[0;0Y[10Xsetenv PATH ${PATH}:`.6M`0 f .w@Y >F /7Y%Tګok%hâll;\ o~Wt<7`4]
GqUi|NCs}_Y$zCʎ1먏 T%-(üu 6˯iΓOOӄ0eu{OPWrGBѠBK!gIje]w`M*zĵ,A9q*lY3eߴ^8N\ns
RBŢ BZpܖP\" W%eIrt3[ ? 95zb9@LXm8|P]Si%Im؇ݪnP;D/e&.%M).
|8~dSwiu`Kd dto$̟vCC8/MvzTڒjhZgX MfZ
_z
ke{ ]Qƫk7 S\^F@f -T:͐]p
AppendInequalitiesToPolymakeObject 2.4-4 AppendPointlistToPolymakeObject 2.4-2 AppendToPolymakeObject 2.4-1 AppendVertexlistToPolymakeObject 2.4-3 CheckAppVerTypList 2.1-3 ClearPolymakeObject 2.4-6 ConvertMatrixToPolymakeString 2.4-5 ConvertPolymakeBoolToGAP 4.2-6 ConvertPolymakeGraphToGAP 4.2-9 ConvertPolymakeIntVectorToGAPPlusOne 4.2-5 ConvertPolymakeListOfSetsToGAP 4.2-8 ConvertPolymakeListOfSetsToGAPPlusOne 4.2-8 ConvertPolymakeMatrixOrListOfSetsToGAP 4.2-3 ConvertPolymakeMatrixOrListOfSetsToGAPPlusOne 4.2-3 ConvertPolymakeMatrixToGAP 4.2-4 ConvertPolymakeMatrixToGAPKillOnes 4.2-4 ConvertPolymakeNumber 4.2-1 ConvertPolymakeOutputToGapNotation 4.1-2 ConvertPolymakeScalarToGAP 4.2-2 ConvertPolymakeSetToGAP 4.2-7 ConvertPolymakeVectorToGAP 4.2-5 ConvertPolymakeVectorToGAPKillOne 4.2-5 CreateEmptyFile 2.1-1 CreatePolymakeObject 2.1-2 CreatePolymakeObjectFromFile 2.1-4 DirectoryOfPolymakeObject 2.2-1 FilenameOfPolymakeObject 2.2-2 FullFilenameOfPolymakeObject 2.2-3 InfoPolymaking 3.1-1 KnownPropertiesOfPolymakeObject 2.2-5 NamesKnownPropertiesOfPolymakeObject 2.2-4 ObjectConverters 4.1-4 Polymake 2.5-1 POLYMAKE_COMMAND 3.2-1 POLYMAKE_DATA_DIR 3.2-2 POLYMAKE_LAST_FAIL_REASON 3.1-2 PropertyOfPolymakeObject 2.2-6 SetPolymakeCommand 1.2-2 SetPolymakeDataDirectory 1.2-1 SplitPolymakeOutputStringIntoBlocks 4.1-3 UnbindKnownPropertyOfPolymakeObject 2.4-8 WriteKnownPropertyToPolymakeObject 2.4-7
generated by GAPDoc2HTML
polymaking-0.8.8/doc/manual.js 0000644 0001751 0001751 00000010113 15114057717 015673 0 ustar runner runner /* manual.js Frank Lübeck */ /* This file contains a few javascript functions which allow to switch between display styles for GAPDoc HTML manuals. If javascript is switched off in a browser or this file in not available in a manual directory, this is no problem. Users just cannot switch between several styles and don't see the corresponding button. A style with name mystyle can be added by providing two files (or only one of them). mystyle.js: Additional javascript code for the style, it is read in the HTML pages after this current file. The additional code may adjust the preprocessing function jscontent() with is called onload of a file. This is done by appending functions to jscontentfuncs (jscontentfuncs.push(newfunc);). Make sure, that your style is still usable without javascript. mystyle.css: CSS configuration, read after manual.css (so it can just reconfigure a few details, or overwrite everything). Then adjust chooser.html such that users can switch on and off mystyle. A user can change the preferred style permanently by using the [Style] link and choosing one. Or one can append '?GAPDocStyle=mystyle' to the URL when loading any file of the manual (so the style can be configured in the GAP user preferences). */ /* generic helper function */ function deleteCookie(nam) { document.cookie = nam+"=;Path=/;expires=Thu, 01 Jan 1970 00:00:00 GMT"; } /* read a value from a "nam1=val1;nam2=val2;..." string (e.g., the search part of an URL or a cookie */ function valueString(str,nam) { var cs = str.split(";"); for (var i=0; i < cs.length; i++) { var pos = cs[i].search(nam+"="); if (pos > -1) { pos = cs[i].indexOf("="); return cs[i].slice(pos+1); } } return 0; } /* when a non-default style is chosen via URL or a cookie, then the cookie is reset and the styles .js and .css files are read */ function overwriteStyle() { /* style in URL? */ var style = valueString(window.location.search, "GAPDocStyle"); /* otherwise check cookie */ if (style == 0) style = valueString(document.cookie, "GAPDocStyle"); if (style == 0) return; if (style == "default") deleteCookie("GAPDocStyle"); else { /* ok, we set the cookie for path "/" */ var path = "/"; /* or better like this ??? var here = window.location.pathname.split("/"); for (var i=0; i+3 < here.length; i++) path = path+"/"+here[i]; */ document.cookie = "GAPDocStyle="+style+";Path="+path; /* split into names of style files */ var stlist = style.split(","); /* read style's css and js files */ for (var i=0; i < stlist.length; i++) { document.writeln(''); document.writeln(''); } } } /* this adds a "[Style]" link next to the MathJax switcher */ function addStyleLink() { var line = document.getElementById("mathjaxlink"); var el = document.createElement("a"); var oncl = document.createAttribute("href"); var back = window.location.protocol+"//" if (window.location.protocol == "http:" || window.location.protocol == "https:") { back = back+window.location.host; if (window.location.port != "") { back = back+":"+window.location.port; } } back = back+window.location.pathname; oncl.nodeValue = "chooser.html?BACK="+back; el.setAttributeNode(oncl); var cont = document.createTextNode(" [Style]"); el.appendChild(cont); line.appendChild(el); } var jscontentfuncs = new Array(); jscontentfuncs.push(addStyleLink); /* the default jscontent() only adds the [Style] link to the page */ function jscontent () { for (var i=0; i < jscontentfuncs.length; i++) jscontentfuncs[i](); } polymaking-0.8.8/doc/internals.xml 0000644 0001751 0001751 00000022174 15114057717 016613 0 ustar runner runner1 a1 a2 a3... which does not go very well
with the usual &GAP; conventions of column vectors and multiplying matrices
from the right. So [a1,a2,a3,...] and the user is left with the problem of
augmentation and left or right multiplication.
Another area where the &GAP; object isn't a literal translation from the
polymake world is combinatorics. In Polymake, list elements are enumerated
starting from 0. &GAP; enumerates lists starting at 1. So the conversion
process adds 1 to the numbers corresponding to vertices in facet lists, for
example.
To install the package, just unpack it in your packages directory (usually ~/gap/pkg for local installation). To use polymaking, you need a working installation of the program polymake https://polymake.org. The package has been tested on linux and Mac OS X (10.4, 10.5 and 10.6). But it should be as platform independent as GAP and polymake.
The interaction with polymake is restricted to writing files and carrying out simple operations. These looked like
polymake file KEYWORD1 KEYWORD2 KEYWORD3
on the command line for polymake versions before 4. The keywords are polymake methods without arguments. Since polymake no longer supports this interface the polymaking package provides the script lib/pm_script_arg.pl to emulate this.
polymake ––script lib/pm_script_arg.pl KEYWORD1 KEYWORD2 KEYWORD3
Using custom scripts is not supported.
Every call to polymake will re-start the program anew. This causes considerable overhead. The number of calls to polymake is reduced by caching the results in the so-called PolymakeObject in GAP. As of polymaking version 0.8.0, old versions of polymake (i.e. versions before 2.7.9) are not supported anymore.
polymaking will try to guess the location of polymake. If this fails, a warning is issued at load time (InfoWarning level 1). Note that the guessing procedure is suppressed when POLYMAKE_COMMAND (3.2-1) is set manually (see 1.2-3).
setenv PATH ${PATH}:<your polymakepath>
The general rule is: If polymaking finds polymake by itself, there is nothing to worry about.
As polymaking uses the program polymake, it needs to know where this program lives. The communication with polymake is done by writing files for polymake and reading its output (as returned to standard output "the prompt"). Note that the interface does not read any polymake file.
‣ SetPolymakeDataDirectory( dir ) | ( method ) |
Sets the directory in which all polymake files are created to dir. The standard place for these files is a temporary directory generated when the package is loaded. This manipulates POLYMAKE_DATA_DIR (3.2-2).
‣ SetPolymakeCommand( command ) | ( method ) |
Sets the name for the polymake program to command. This manipulates POLYMAKE_COMMAND (3.2-1).
To permanently set the values of POLYMAKE_COMMAND (3.2-1), and POLYMAKE_DATA_DIR (3.2-2), add the lines
POLYMAKE_DATA_DIR:=Directory("/home/mypolymakedatadir");
POLYMAKE_COMMAND:=Filename(Directory("/home/mypolymakebindir/"),"polymake");
to your .gaprc file (see Reference: The gap.ini and gaprc files). Note that these have to be before the LoadPackage("polymaking"); line. Or you can change the values of the above variables by editing lib/environment.gi
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chapBib_mj.html 0000644 0001751 0001751 00000004642 15114057717 016776 0 ustar runner runner[GJ] Gawrilow, E. and Joswig, M., polymake, \url{https://polymake.org/}.
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chap3_mj.html 0000644 0001751 0001751 00000014366 15114057717 016450 0 ustar runner runner‣ InfoPolymaking | ( info class ) |
If set to at least \(2\), the output of polymake is shown. At level \(1\), warnings are shown. This is the default. And at level \(0\), the polymake package remains silent.
‣ POLYMAKE_LAST_FAIL_REASON | ( global variable ) |
Contains a string that explains the last occurrence of fail as a return value of Polymake (2.5-1).
The variables for interaction with the system are contained in the file environment.gi. Each of these variables has a function to set it, see 1.2. If POLYMAKE_COMMAND or POLYMAKE_DATA_DIR are set at startup, they are not overwritten. So if you don't want (or don't have the rights) to modify environment.gi, you can set the variables in your .gaprc file.
‣ POLYMAKE_COMMAND | ( global variable ) |
This variable should contain the name of the polymake program in the form as returned by Filename So a probable value is Filename(Directory("/usr/local/bin"),"polymake").
‣ POLYMAKE_DATA_DIR | ( global variable ) |
In this directory the files for polymake will be created. By default, this generates a temporary directory using DirectoryTemporary
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chap4.html 0000644 0001751 0001751 00000040517 15114057717 015760 0 ustar runner runnerWhen polymake is called, its output is read as a string and then processed as follows:
the lines containing upper case letters are found. These are treated as lines containing the keywords. Each of those lines marks the beginning of a block of data.
The string is then cut into a list of blocks (also strings). Each block starts with a line containing the keyword and continues with some lines of data.
for each of the blocks, the appropriate function of ObjectConverters is called. Here "appropriate" just means, that the keyword of the block coincides with the name of the function.
The output of the conversion function is then added to the known properties of the PolymakeObject for which Polymake was called.
The converter functions should take meaningful polymake data into meaningful GAP data. This sometimes means that the (mathematical) representation is changed. Here is an example: polymake writes vectors as augmented affine vectors of the form 1 a1 a2 a3... which does not go very well with the usual GAP conventions of column vectors and multiplying matrices from the right. So polymaking converts such a vector to [a1,a2,a3,...] and the user is left with the problem of augmentation and left or right multiplication.
Another area where the GAP object isn't a literal translation from the polymake world is combinatorics. In Polymake, list elements are enumerated starting from 0. GAP enumerates lists starting at 1. So the conversion process adds 1 to the numbers corresponding to vertices in facet lists, for example.
The conversion process is done by the following methods:
‣ ConvertPolymakeOutputToGapNotation( string ) | ( method ) |
Returns: Record having polymake keywords as entry names and the respective converted polymake output as entries.
Given a the output of the polymake program as a string string, this method first calls SplitPolymakeOutputStringIntoBlocks (4.1-3). For each of the returned blocks, the name (=first line) of the block is read and the record ObjectConverters (4.1-4) is looked up for an entry with that name. If such an entry exists, it (being a function!) is called and passed the block. The returned value is then given the name of the block and added to the record returned by ConvertPolymakeOutputToGapNotation.
‣ SplitPolymakeOutputStringIntoBlocks( string ) | ( method ) |
Returns: List of strings -- "blocks"--
The string string is cut at the lines starting with an upper case character and consisting only of upper case letters, numbers and underscore (_) characters. The parts are returned as a list of strings. The initial string string remains unchanged.
‣ ObjectConverters | ( global variable ) |
The entries of this record are labeled by polymake keywords. Each of the entries is a function which converts a string returned by polymake to GAP format. So far, only a few converters are implemented. To see which, try RecNames(ObjectConverters);
You can define new converters using the basic functions described in section 4.2.
The following functions are used for the functions in ObjectConverters (4.1-4).
‣ ConvertPolymakeNumber( string ) | ( method ) |
The string string is converted to a rational number. Unlike Rat, it tests, if the number represented by string is a floating point number an converts it correctly. If this is the case, a warning is issued.
‣ ConvertPolymakeScalarToGAP( list ) | ( method ) |
If list contains a single string, this string is converted into a number using ConvertPolymakeNumber (4.2-1).
‣ ConvertPolymakeMatrixOrListOfSetsToGAP( list ) | ( method ) |
‣ ConvertPolymakeMatrixOrListOfSetsToGAPPlusOne( list ) | ( method ) |
Tries to decide if the list list of strings represents a matrix or a list of sets by testing if they start with "{". It then calls either ConvertPolymakeMatrixToGAP (4.2-4) or ConvertPolymakeListOfSetsToGAP (4.2-8). The "PlusOne" version calls ConvertPolymakeListOfSetsToGAPPlusOne (4.2-8) if list represents a list of sets.
‣ ConvertPolymakeMatrixToGAP( list ) | ( method ) |
‣ ConvertPolymakeMatrixToGAPKillOnes( list ) | ( method ) |
The list list of strings is interpreted as a list of row vectors and converted into a matrix. The "KillOnes" version removes the leading ones.
‣ ConvertPolymakeVectorToGAP( list ) | ( method ) |
‣ ConvertPolymakeVectorToGAPKillOne( list ) | ( method ) |
‣ ConvertPolymakeIntVectorToGAPPlusOne( list ) | ( method ) |
As the corresponding "Matrix" version. Just for vectors. ConvertPolymakeIntVectorToGAPPlusOne requires the vector to contain integers. It also adds 1 to every entry.
‣ ConvertPolymakeBoolToGAP( list ) | ( method ) |
If list contains a single string, which is either 0,false,1, or true this function returns false or true, respectively.
‣ ConvertPolymakeSetToGAP( list ) | ( method ) |
Let list be a list containing a single string, which is a list of numbers separated by whitespaces and enclosed by { and } . The returned value is then a set of rational numbers (in the GAP sense).
‣ ConvertPolymakeListOfSetsToGAP( list ) | ( method ) |
‣ ConvertPolymakeListOfSetsToGAPPlusOne( list ) | ( method ) |
Let list be a list containing several strings representing sets. Then each of these strings is converted to a set of rational numbers and the returned value is the list of all those sets. The "PlusOne" version adds 1 to every entry.
‣ ConvertPolymakeGraphToGAP( list ) | ( method ) |
Let list be a list of strings representing sets (that is, a list of integers enclosed by { and }). Then a record is returned containing two sets named .vertices and .edges.
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chap3.txt 0000644 0001751 0001751 00000003623 15114057717 015627 0 ustar runner runner [1X3 [33X[0;0YGlobal Variables[133X[101X [1X3.1 [33X[0;0YGetting information about polymake output[133X[101X [1X3.1-1 InfoPolymaking[101X [33X[1;0Y[29X[2XInfoPolymaking[102X [32X info class[133X [33X[0;0YIf set to at least [22X2[122X, the output of polymake is shown. At level [22X1[122X, warnings are shown. This is the default. And at level [22X0[122X, the polymake package remains silent.[133X [1X3.1-2 POLYMAKE_LAST_FAIL_REASON[101X [33X[1;0Y[29X[2XPOLYMAKE_LAST_FAIL_REASON[102X [32X global variable[133X [33X[0;0YContains a string that explains the last occurrence of [9Xfail[109X as a return value of [2XPolymake[102X ([14X2.5-1[114X).[133X [1X3.2 [33X[0;0YVariables for system interaction[133X[101X [33X[0;0YThe variables for interaction with the system are contained in the file [11Xenvironment.gi[111X. Each of these variables has a function to set it, see [14X1.2[114X. If [9XPOLYMAKE_COMMAND[109X or [9XPOLYMAKE_DATA_DIR[109X are set at startup, they are not overwritten. So if you don't want (or don't have the rights) to modify [11Xenvironment.gi[111X, you can set the variables in your [11X.gaprc[111X file.[133X [1X3.2-1 POLYMAKE_COMMAND[101X [33X[1;0Y[29X[2XPOLYMAKE_COMMAND[102X [32X global variable[133X [33X[0;0YThis variable should contain the name of the polymake program in the form as returned by [10XFilename[110X So a probable value is [10XFilename(Directory("/usr/local/bin"),"polymake")[110X.[133X [1X3.2-2 POLYMAKE_DATA_DIR[101X [33X[1;0Y[29X[2XPOLYMAKE_DATA_DIR[102X [32X global variable[133X [33X[0;0YIn this directory the files for polymake will be created. By default, this generates a temporary directory using [9XDirectoryTemporary[109X[133X polymaking-0.8.8/doc/input.xml 0000644 0001751 0001751 00000027031 15114057717 015750 0 ustar runner runnerThe interaction with the polymake program is done via files. A PolymakeObject is mainly a pointer to a file and a list of known properties of the object. These properties need not be stored in the file. Whenever polymake is called, the returned value is read from standard output and stored in the PolymakeObject corresponding to the file for which polymake is called. The files for polymake are written in the old (non-xml) format. The first run of polymake converts them into the new (xml) format. This means that changes to the file by means of the methods outlined below after the first run of polymake will probably lead to corrupted files.
‣ CreateEmptyFile( filename ) | ( method ) |
Returns: nothing
Creates an empty file with name filename. Note that filename has to include the full path and the directory for the file must exist.
‣ CreatePolymakeObject( [prefix][,] [dir][,] [appvertyp] ) | ( method ) |
Returns: PolymakeObject
If called without arguments, this method generates an empty file in the directory defined by POLYMAKE_DATA_DIR (3.2-2). If a directory dir is given (this directory must exist), an empty file is generated in this directory. If prefix is not given, the file is called polyN where N is the current runtime. If a file of this name already exists, a number is appended separated by a dot (example: "poly1340" and "poly1340.1"). If prefix is given, the filename starts with this prefix. Optionally, the file can be generated with a header specifying application, version and type of the object. This is done by passing the triple of strings appvertyp to CreatePolymakeObject. A valid triple is ["polytope","2.3","RationalPolytope"]. Validity is checked by CheckAppVerTypList (2.1-3).
‣ CheckAppVerTypList( appvertyp ) | ( method ) |
Returns: bool
Checks if the triple arppvertyp of strings specifies an application and type of polymake version 2.3. More specifically, the first entry has to be an application from ["polytope","surface","topaz"] and the third entry has to be a type corresponding to the application given in the first entry. The second entry is not checked.
‣ CreatePolymakeObjectFromFile( [dir, ]filename ) | ( method ) |
Returns: PolymakeObject
This method generates a PolymakeObject corresponding to the file filename in the directory dir. If dir is not given, the POLYMAKE_DATA_DIR is used.If no file with name filename exists in dir (or POLYMAKE_DATA_DIR, respectively), an empty file is created. Note that the contents of the file do not matter for the generation of the object. In particular, the object does not know any of the properties that might be encoded in the file. The only way to transfer information from files to PolymakeObjects is via Polymake (2.5-1).
A PolymakeObject contains information about the directory of its file, the name of its file and about properties calculated by calling Polymake (2.5-1). The properties returned by the polymake program are stored under the name polymake assigns to them (that is, the name of the data block in the corresponding file). The following methods can be used to access the information stored in a PolymakeObject. But be careful! All functions return the actual object. No copies are made. So if you change one of the returned objects, you change the PolymakeObject itself.
‣ DirectoryOfPolymakeObject( poly ) | ( method ) |
Returns: Directory
Returns the directory of the file associated with poly.
‣ FilenameOfPolymakeObject( poly ) | ( method ) |
Returns: String
Returns the name of the file associated with poly. This does only mean the name of the file, not the full path. For the full path and file name see FullFilenameOfPolymakeObject (2.2-3)
‣ FullFilenameOfPolymakeObject( poly ) | ( method ) |
Returns: String
Returns the file associated with the PolymakeObject poly with its complete path.
‣ NamesKnownPropertiesOfPolymakeObject( poly ) | ( method ) |
Returns: List of Strings
Returns a list of the names of all known properties. This does only include the properties returned by Polymake (2.5-1), "dir" and "filename" are not included. If no properties are known, fail is returned.
‣ KnownPropertiesOfPolymakeObject( poly ) | ( method ) |
Returns: Record
Returns the record of all known properties. If no properties are known, fail is returned.
‣ PropertyOfPolymakeObject( poly, name ) | ( method ) |
Returns the value of the property name if it is known. If the value is not known, fail is returned. name must be a String.
Suppose the file /tmp/threecube.poly contains the three dimensional cube in polymake form. Now generate a PolymakeObject from this file and call Polymake (2.5-1) to make the vertices of the cube known to the object.
### suppose we have a polymake file /tmp/threecube.poly ### containing a cube in three dimensions gap> cube:=CreatePolymakeObjectFromFile(Directory("/tmp"),"threecube.poly"); <polymake object. No properties known> gap> FilenameOfPolymakeObject(cube); "threecube.poly" gap> FullFilenameOfPolymakeObject(cube); "/tmp/threecube.poly" #nothing is known about the cube: gap> NamesKnownPropertiesOfPolymakeObject(cube); fail gap> Polymake(cube,"VERTICES"); [ [ -1, -1, -1 ], [ 1, -1, -1 ], [ -1, 1, -1 ], [ 1, 1, -1 ], [ -1, -1, 1 ], [ 1, -1, 1 ], [ -1, 1, 1 ], [ 1, 1, 1 ] ] # Now <cube> knows its vertices: gap> Print(cube); <polymake object threecube.poly. Properties known: [ "VERTICES" ]> gap> PropertyOfPolymakeObject(cube,"VERTICES"); [ [ -1, -1, -1 ], [ 1, -1, -1 ], [ -1, 1, -1 ], [ 1, 1, -1 ], [ -1, -1, 1 ], [ 1, -1, 1 ], [ -1, 1, 1 ], [ 1, 1, 1 ] ] gap> KnownPropertiesOfPolymakeObject(cube); rec( VERTICES := [ [ -1, -1, -1 ], [ 1, -1, -1 ], [ -1, 1, -1 ], [ 1, 1, -1 ], [ -1, -1, 1 ], [ 1, -1, 1 ], [ -1, 1, 1 ], [ 1, 1, 1 ] ] )
To transfer data from GAP to polymake, the following methods can be used. But bear in mind that none of these functions test if the resulting polymake file is still consistent.
‣ AppendToPolymakeObject( poly, string ) | ( method ) |
Returns: nothing
This appends the string string to the file associated to the PolymakeObject poly. It is not tested if the string is syntactically correct as a part of a polymake file. It is also not tested if the string is compatible with the data already contained in the file.
INEQUALITIES, POINTS and VERTICES can be appended to a polymake object using the following functions:
‣ AppendPointlistToPolymakeObject( poly, pointlist ) | ( method ) |
Returns: nothing
Takes a list pointlist of vectors and converts it into a string which represents a polymake block labeled "POINTS". This string is then added to the file associated with poly. The "POINTS" block of the file associated with poly then contains points with leading ones, as polymake uses affine notation.
‣ AppendVertexlistToPolymakeObject( poly, pointlist ) | ( method ) |
Returns: nothing
Does the same as AppendPointlistToPolymakeObject, but with "VERTICES" instead of "POINTS".
‣ AppendInequalitiesToPolymakeObject( poly, ineqlist ) | ( method ) |
Returns: nothing
Just appends the inequalities given in ineqlist to the polymake object poly (with caption "INEQUALITIES"). Note that this does not check if an "INEQUALITIES" section does already exist in the file associated with poly.
‣ ConvertMatrixToPolymakeString( name, matrix ) | ( method ) |
Returns: String
This function takes a matrix matrix and converts it to a string. This string can then be appended to a polymake file via AppendToPolymakeObject (2.4-1) to form a block of data labeled name. This may be used to write blocks like INEQUALITIES or FACETS.
‣ ClearPolymakeObject( poly[, appvertyp] ) | ( method ) |
Returns: nothing
Deletes all known properties of the PolymakeObject poly and replaces its file with an empty one.
If the triple of strings appvertyp specifying application, version and type (see CheckAppVerTypList (2.1-3)) is given, the file is replaced with a file that contains only a header specifying application, version and type of the polymake object.
There are also methods to manipulate the known values without touching the file of the PolymakeObject:
‣ WriteKnownPropertyToPolymakeObject( poly, name, data ) | ( method ) |
Takes the object data and writes it to the known properties section of the PolymakeObject poly. The string name is used as the name of the property. If a property with that name already exists, it is overwritten. Again, there is no check if data is consistent, correct or meaningful.
‣ UnbindKnownPropertyOfPolymakeObject( poly, name ) | ( method ) |
If the PolymakeObject poly has a property with name name, that property is unbound. If there is no such property, fail is returned.
‣ Polymake( poly, option: PolymakeNolookup ) | ( method ) |
This method calls the polymake program (see POLYMAKE_COMMAND (3.2-1)) with the option option. You may use several keywords such as "FACETS VERTICES" as an option. The returned value is cut into blocks starting with keywords (which are taken from output and not looked up in option). Each block is then interpreted and translated into GAP readable form. This translation is done using the functions given in ObjectConverters (4.1-4). The first line of each block of polymake output is taken as a keyword and the according entry in ObjectConverters (4.1-4) is called to convert the block into GAP readable form. If no conversion function is known, an info string is printed and fail is returned. If only one keyword has been given as option, Polymake returns the result of the conversion operation. If more than one keyword has been given or the output consists of more than one block, Polymake returns fail. In any case, the calculated values for each block are stored as known properties of the PolymakeObject poly as long as they are not fail. If Polymake is called with an option that corresponds to a name of a known property of poly, the known property is returned. In this case, there is no call of the external program. (see below for suppression of this feature).
Note that the command Polymake returns fail if nothing is returned by the program polymake or more than one block of data is returned. For example, the returned value of Polymake(poly,"VISUAL") is always fail. Likewise, Polymake(poly,"POINTS VERTICES") will return fail (but may add new known properties to poly). For a description of the conversion functions, see chapter 4.
If the option PolymakeNolookup is set to anything else than false, the polymake program is called even if poly already has a known property with name option.
Note that whenever Polymake returns fail, a description of the problem is stored in POLYMAKE_LAST_FAIL_REASON (3.1-2). If you call Polymake with more than one keyword, POLYMAKE_LAST_FAIL_REASON (3.1-2) is changed before polymake is called. So any further reason to return fail will overwrite it.
Let's generate a three dimensional permutahedron.
gap> S:=SymmetricGroup(3);
Sym( [ 1 .. 3 ] )
gap> v:=[1,2,3];
[ 1, 2, 3 ]
gap> points3:=Orbit(S,v,Permuted);;
# project to reduce ambient dimension
gap> points:=points3{[1..6]}{[1,2]};;
gap> permutahedron:=CreatePolymakeObject();
<polymake object. No properties known>
gap> AppendPointlistToPolymakeObject(permutahedron,points);
gap> Polymake(permutahedron,"VOLUME");
3
gap> Polymake(permutahedron,"N_VERTICES");
6
#Now <permutahedron> knows its number of vertices, but not the vertices:
gap> PropertyOfPolymakeObject(permutahedron,"VERTICES");
fail
gap> NamesKnownPropertiesOfPolymakeObject(permutahedron);
[ "VOLUME", "N_VERTICES" ]
#Let's look at the object!
gap> Polymake(permutahedron,"VISUAL");
#I There was no or wrong polymake output
fail
gap> Polymake(permutahedron,"DIM");
2
generated by GAPDoc2HTML
polymaking-0.8.8/doc/_entities.xml 0000644 0001751 0001751 00000000065 15114057717 016572 0 ustar runner runner polymaking'> polymaking-0.8.8/doc/toggless.css 0000644 0001751 0001751 00000001672 15114057717 016433 0 ustar runner runner /* toggless.css Frank Lübeck */ /* Using javascript we change all div.ContSect to div.ContSectOpen or div.ContSectClosed. This way the config for div.ContSect in manual.css is no longer relevant. Here we add the CSS for the new elements. */ /* This layout is based on an idea by Burkhard Höfling. */ div.ContSectClosed { text-align: left; margin-left: 1em; } div.ContSectOpen { text-align: left; margin-left: 1em; } div.ContSectOpen div.ContSSBlock { display: block; text-align: left; margin-left: 1em; } div.ContSectOpen div.ContSSBlock a { display: block; width: 100%; margin-left: 1em; } span.tocline a:hover { display: inline; background: #eeeeee; } span.ContSS a:hover { display: inline; background: #eeeeee; } span.toctoggle { font-size: 80%; display: inline-block; width: 1.2em; } span.toctoggle:hover { background-color: #aaaaaa; } polymaking-0.8.8/doc/environment.xml 0000644 0001751 0001751 00000007264 15114057717 017163 0 ustar runner runner]]>
When polymake is called, its output is read as a string and then processed as follows:
the lines containing upper case letters are found. These are treated as lines containing the keywords. Each of those lines marks the beginning of a block of data.
The string is then cut into a list of blocks (also strings). Each block starts with a line containing the keyword and continues with some lines of data.
for each of the blocks, the appropriate function of ObjectConverters is called. Here "appropriate" just means, that the keyword of the block coincides with the name of the function.
The output of the conversion function is then added to the known properties of the PolymakeObject for which Polymake was called.
The converter functions should take meaningful polymake data into meaningful GAP data. This sometimes means that the (mathematical) representation is changed. Here is an example: polymake writes vectors as augmented affine vectors of the form 1 a1 a2 a3... which does not go very well with the usual GAP conventions of column vectors and multiplying matrices from the right. So polymaking converts such a vector to [a1,a2,a3,...] and the user is left with the problem of augmentation and left or right multiplication.
Another area where the GAP object isn't a literal translation from the polymake world is combinatorics. In Polymake, list elements are enumerated starting from 0. GAP enumerates lists starting at 1. So the conversion process adds 1 to the numbers corresponding to vertices in facet lists, for example.
The conversion process is done by the following methods:
‣ ConvertPolymakeOutputToGapNotation( string ) | ( method ) |
Returns: Record having polymake keywords as entry names and the respective converted polymake output as entries.
Given a the output of the polymake program as a string string, this method first calls SplitPolymakeOutputStringIntoBlocks (4.1-3). For each of the returned blocks, the name (=first line) of the block is read and the record ObjectConverters (4.1-4) is looked up for an entry with that name. If such an entry exists, it (being a function!) is called and passed the block. The returned value is then given the name of the block and added to the record returned by ConvertPolymakeOutputToGapNotation.
‣ SplitPolymakeOutputStringIntoBlocks( string ) | ( method ) |
Returns: List of strings -- "blocks"--
The string string is cut at the lines starting with an upper case character and consisting only of upper case letters, numbers and underscore (_) characters. The parts are returned as a list of strings. The initial string string remains unchanged.
‣ ObjectConverters | ( global variable ) |
The entries of this record are labeled by polymake keywords. Each of the entries is a function which converts a string returned by polymake to GAP format. So far, only a few converters are implemented. To see which, try RecNames(ObjectConverters);
You can define new converters using the basic functions described in section 4.2.
The following functions are used for the functions in ObjectConverters (4.1-4).
‣ ConvertPolymakeNumber( string ) | ( method ) |
The string string is converted to a rational number. Unlike Rat, it tests, if the number represented by string is a floating point number an converts it correctly. If this is the case, a warning is issued.
‣ ConvertPolymakeScalarToGAP( list ) | ( method ) |
If list contains a single string, this string is converted into a number using ConvertPolymakeNumber (4.2-1).
‣ ConvertPolymakeMatrixOrListOfSetsToGAP( list ) | ( method ) |
‣ ConvertPolymakeMatrixOrListOfSetsToGAPPlusOne( list ) | ( method ) |
Tries to decide if the list list of strings represents a matrix or a list of sets by testing if they start with "{". It then calls either ConvertPolymakeMatrixToGAP (4.2-4) or ConvertPolymakeListOfSetsToGAP (4.2-8). The "PlusOne" version calls ConvertPolymakeListOfSetsToGAPPlusOne (4.2-8) if list represents a list of sets.
‣ ConvertPolymakeMatrixToGAP( list ) | ( method ) |
‣ ConvertPolymakeMatrixToGAPKillOnes( list ) | ( method ) |
The list list of strings is interpreted as a list of row vectors and converted into a matrix. The "KillOnes" version removes the leading ones.
‣ ConvertPolymakeVectorToGAP( list ) | ( method ) |
‣ ConvertPolymakeVectorToGAPKillOne( list ) | ( method ) |
‣ ConvertPolymakeIntVectorToGAPPlusOne( list ) | ( method ) |
As the corresponding "Matrix" version. Just for vectors. ConvertPolymakeIntVectorToGAPPlusOne requires the vector to contain integers. It also adds 1 to every entry.
‣ ConvertPolymakeBoolToGAP( list ) | ( method ) |
If list contains a single string, which is either 0,false,1, or true this function returns false or true, respectively.
‣ ConvertPolymakeSetToGAP( list ) | ( method ) |
Let list be a list containing a single string, which is a list of numbers separated by whitespaces and enclosed by { and } . The returned value is then a set of rational numbers (in the GAP sense).
‣ ConvertPolymakeListOfSetsToGAP( list ) | ( method ) |
‣ ConvertPolymakeListOfSetsToGAPPlusOne( list ) | ( method ) |
Let list be a list containing several strings representing sets. Then each of these strings is converted to a set of rational numbers and the returned value is the list of all those sets. The "PlusOne" version adds 1 to every entry.
‣ ConvertPolymakeGraphToGAP( list ) | ( method ) |
Let list be a list of strings representing sets (that is, a list of integers enclosed by { and }). Then a record is returned containing two sets named .vertices and .edges.
generated by GAPDoc2HTML
polymaking-0.8.8/doc/chapInd.txt 0000644 0001751 0001751 00000003777 15114057717 016211 0 ustar runner runner [1XIndex[101X [2XAppendInequalitiesToPolymakeObject[102X 2.4-4 [2XAppendPointlistToPolymakeObject[102X 2.4-2 [2XAppendToPolymakeObject[102X 2.4-1 [2XAppendVertexlistToPolymakeObject[102X 2.4-3 [2XCheckAppVerTypList[102X 2.1-3 [2XClearPolymakeObject[102X 2.4-6 [2XConvertMatrixToPolymakeString[102X 2.4-5 [2XConvertPolymakeBoolToGAP[102X 4.2-6 [2XConvertPolymakeGraphToGAP[102X 4.2-9 [2XConvertPolymakeIntVectorToGAPPlusOne[102X 4.2-5 [2XConvertPolymakeListOfSetsToGAP[102X 4.2-8 [2XConvertPolymakeListOfSetsToGAPPlusOne[102X 4.2-8 [2XConvertPolymakeMatrixOrListOfSetsToGAP[102X 4.2-3 [2XConvertPolymakeMatrixOrListOfSetsToGAPPlusOne[102X 4.2-3 [2XConvertPolymakeMatrixToGAP[102X 4.2-4 [2XConvertPolymakeMatrixToGAPKillOnes[102X 4.2-4 [2XConvertPolymakeNumber[102X 4.2-1 [2XConvertPolymakeOutputToGapNotation[102X 4.1-2 [2XConvertPolymakeScalarToGAP[102X 4.2-2 [2XConvertPolymakeSetToGAP[102X 4.2-7 [2XConvertPolymakeVectorToGAP[102X 4.2-5 [2XConvertPolymakeVectorToGAPKillOne[102X 4.2-5 [2XCreateEmptyFile[102X 2.1-1 [2XCreatePolymakeObject[102X 2.1-2 [2XCreatePolymakeObjectFromFile[102X 2.1-4 [2XDirectoryOfPolymakeObject[102X 2.2-1 [2XFilenameOfPolymakeObject[102X 2.2-2 [2XFullFilenameOfPolymakeObject[102X 2.2-3 [2XInfoPolymaking[102X 3.1-1 [2XKnownPropertiesOfPolymakeObject[102X 2.2-5 [2XNamesKnownPropertiesOfPolymakeObject[102X 2.2-4 [2XObjectConverters[102X 4.1-4 [2XPolymake[102X 2.5-1 [2XPOLYMAKE_COMMAND[102X 3.2-1 [2XPOLYMAKE_DATA_DIR[102X 3.2-2 [2XPOLYMAKE_LAST_FAIL_REASON[102X 3.1-2 [2XPropertyOfPolymakeObject[102X 2.2-6 [2XSetPolymakeCommand[102X 1.2-2 [2XSetPolymakeDataDirectory[102X 1.2-1 [2XSplitPolymakeOutputStringIntoBlocks[102X 4.1-3 [2XUnbindKnownPropertyOfPolymakeObject[102X 2.4-8 [2XWriteKnownPropertyToPolymakeObject[102X 2.4-7 ------------------------------------------------------- polymaking-0.8.8/read.g 0000644 0001751 0001751 00000000534 15114057717 014404 0 ustar runner runner ReadPackage("polymaking","lib/environment.gi"); ReadPackage("polymaking","lib/Objects.gi"); ReadPackage("polymaking","lib/construct.gi"); ReadPackage("polymaking","lib/workaround_maps.gi"); ReadPackage("polymaking","lib/convert.gi"); ReadPackage("polymaking","lib/ObjectConverters.gi"); ReadPackage("polymaking","lib/application_version_type.gi"); polymaking-0.8.8/LICENSE 0000644 0001751 0001751 00000043103 15114057717 014325 0 ustar runner runner GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.