Thanks for the report, I have fixed this for our master branch. I am slightly surprised that this did not trigger the sanitizer build in our CI, but I will check if we can add _GLIBCXX_ASSERTIONS to one of the builds. Benjamin - if (description.back() != '\n') + if (description.empty() || descriptio...
I think your polynomial is not parsed as expected, it might be using the Singular-inspired short form where \(3x5\) would be turned into \(3*x^5\), and \(x11\) will end up as \(x^{11}\). So to make sure this is parsed as variables please add an underscore: polytope > $str = "(x11*x21 + x11*x22 ...
This error g++: fatal error: Killed signal terminated program cc1plus is quite often an indication that your computer ran out of memory and the operating system killed the process. Have you tried running the build process with less jobs, i.e. `ninja -C build/Opt -j1`. I would recommend at most one p...
You can set the default to jreality with prefer "jreality"; This will be stored in the polymake configuration ( ~/.polymake/settings ) and persist across sessions, until you use reset_preference to restore the default behaviour, see https://polymake.org/doku.php/user_guide/howto/shell_cust...
sorry about that error, due to the limited address space, both for compilation and for actual computations, 32bit platforms are not covered by our CI.
Please try the patch I posted here on github, this will be included in the next release.
sorry about that downtime. It should be working again and I will improve the monitoring that didn't catch it being down, all processes were running but one somehow stopped responding to new requests.
I will also check if I can update it to polymake 4.6 soon.
Hi, This freezing can happen when the gcc processes exhaust all available system memory. Please try building polymake instead of the make command with: ninja -C build/Opt -j1 This will reduce the number of parallel processes to build polymake to one. You can increase the number a little depending on...
