POLYMAKE(1)

💖 POLYMAKE 💖

okay bestie, so you know that manual page POLYMAKE(1)? The one filed under "User Commands"? Yeah. We're doing it, but make it cute. Sit down, grab a boba, let's go 🧋✨

---

✨ NAME ✨

polymake — the tool for algorithmic treatment of polytopes and polyhedra. That's the whole job description. Iconic, honestly. 👑

---

🦋 SYNOPSIS 🦋

polymake [-dv] [-A|-a application] [--reconfigure]
         [--config-path filename|user[=directory]]
         [--no-config] [--ignore-config]
         [--script|--iscript [application::]script_file arguments ...]
         [--touch data_file [ data_file ... ]]
         [-]

like. look at her. so much range. 🫶

---

🌸 DESCRIPTION 🌸

so polymake is open source software for research in polyhedral geometry. no cap, that's the vibe. She deals with:

• polytopes
• polyhedra
• fans
• simplicial complexes
• matroids
• graphs
• tropical hypersurfaces
• and various other objects, because she contains multitudes 💅

and when you call her with no arguments at all? She just... starts an interactive shell. main character behavior fr fr. Then hit help; for a very short introduction — literally just type that and she'll walk you through it. 🎀

---

🌈 ARGUMENTS 🌈

• --help — print the help text and dip. that's it. that's the whole thing. ✨
• --version — print the version number, the copyright notice, and exit. a little flex, as a treat. 👑
• [application::]script_file — execute the perl script that's in the file. and if you specify an application prefix? then that application gets loaded and the script file gets looked up in its script directory. iykyk. 📂
• --script [application::]script_file arguments ... — execute the perl script in the file, and pass the arguments along in @ARGV. slay. 🏃♀️
• --iscript [application::]script_file arguments ... — same energy as --script, but the file may contain interactive commands. and yeah, arguments still go in @ARGV. 🦋
• 'script text' — interpret that string as an inline polymake/perl script. one-liner queen. ✨
• - — read and execute the commands from standard input. important: standard output and error streams are not redirected. noted. 💀
• --touch data_file [ data_file ... ] — read the files and write them back out. super useful for converting from earlier polymake versions. glow-up service, lowkey. 🌟

---

💅 OPTIONS 💅

• -A application_name — start with this application, ignoring the $default_application and @start_applications settings. zero chill, straight to business.
• -a application_name — start with this application, ignoring $default_application — but in contrast to -A, it still loads everything in @start_applications. so like, same but softer 🥺
• -d — produce some debug output. and you can repeat it to crank the debug level up. stack 'em. 📚
• -v — tell what's going on, and yep, you can repeat it to raise the verbosity level.

⚠️ heads up bestie: this is an obsolete option. please use custom variables $Verbose::* to gain more detailed control. she's retired, but she's still here, living her life. 🙈

• --reconfigure — rerun the autoconfiguration sections in all rule files. full reset, deep breath, fresh start. 🔄
• --config-path settings_file — import settings from a global configuration file. and you can pass --config-path several times — later instances have higher priority. last one wins, periodt. 👑
• --config-path user[=config_directory] — specify the location of the user's private settings. by default that's ~/.polymake, which may be overridden via the POLYMAKE_USER_DIR environment variable.

🚨 real talk: all global --config-path imports must come before this option. order matters, don't play yourself.

• --no-config — don't read any configuration files, don't try to configure rules automatically, don't load rule files that require auto-configuration. it's giving leave me alone. Equivalent to --config-path=none. 🚫
• --ignore-config — don't read any configuration files, and skip auto-configuration routines in the rule files. Equivalent to --config-path=ignore. also giving leave-me-alone but like, slightly different. 🙈

---

🎀 COPYRIGHT 🎀

Copyright © 1997-2021 Ewgenij Gawrilow, Michael Joswig, and the polymake team Technische Universität Berlin, Germany https://polymake.org

This is free software licensed under GPL; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

💀 no warranty bestie. none. not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. read it and weep (respectfully). GPL though, so she's free, and she's ours. 🫶

---

and that's the whole page, my love 🌈💜

polymake 4.3 — dated January 2021 — written up as POLYMAKE(1). mwah. go compute some polytopes. 💋✨