[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

lattE needs to compute a triangulation of the polytope; by default it uses 4ti2, but can instead use cddlib. Hence this option. See https://www.math.ucdavis.edu/~latte/software/packages/latte_current/manual_v1.7.2.pdf -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: Sage Days next July in Zaragoza (Spain)

Hello Miguel, I saw this discussion on Twitter and joined just to reply. From the Asociación Python España we would love to help, so please let me know if we can help you get in touch with the sponsors, spread the word... If you want, when the details are ready you can publish an article here

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Excellent! Adding the option prevents the crash. So on CoCalc (and locally) I can do: print(P.integral_points_count(preprocess=False, triangulation='cddlib')) And it prints out 19958. Without this extra option this example crashes on CoCalc but runs fine locally. What is this this option doin

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

I can't reproduce this locally, but you could see if passing --triangulation=cddlib to LattE helps. On Sunday, November 5, 2017 at 1:46:30 AM UTC-8, Mark Bell wrote: > > Here is the full CoCalc output when I run "sage error.py" in a terminal, > either via the web interface or via sshing into

[sage-devel] Re: Python3 comparing, an idea about deprecation

I'm not quite sure what you're asking. min and max are not fundamentally changed between Python3 except that the cmp keyword will no longer be valid. So if you do min(L) or min(L, key=foo), both will work in Python3, up to how you are doing comparisons within L. For that, it is localized to the

[sage-devel] Re: Import into sage nb causes internal error

Same problem here, I put the log in case it helps 2017-11-05T20:37:57+0100 [stdout#info] error uploading worksheet Could not build url for endpoint 'home' with values ['username']. Did you mean 'worksheet_listing.home' instead? Could not build url for endpoint 'home' with values ['username']. D

[sage-devel] Python3 comparing, an idea about deprecation

Is it possible to run min(L) in Python2 and at the same time check if it could be run in Python3 for given L? Reason: allow_multiple_edges() on generic_graph.py and keep_label='min' (or 'max'), can we have a nice deprecation? -- Jori Mäntysalo

[sage-devel] Re: cannot push to trac

I have exactly the same problem on Trac#24121 , and can't push "manually, since there is no upstream branch here yet. Y'v uploaded a patch, bu that's not as easy to manage... Any ideas ? -- Emmanuel Charpentier Le samedi 7 octobre 2017 15:23:41 UTC+2, M

Re: [sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Thanks for the suggestion. That might be the case but if I run "/usr/bin/time -v sage error.py" then I get Command exited with non-zero status 1 Command being timed: "sage error.py" User time (seconds): 2.22 System time (seconds): 0.67 Percent of CPU this job got: 86% Elapsed (wall clock) time (

[sage-devel] Re: Polyhedron.integral_points_count() gives inconsistent answers on slices

Here is the full CoCalc output when I run "sage error.py" in a terminal, either via the web interface or via sshing into the machine: Traceback (most recent call last): File "error.py", line 42, in print(P.integral_points_count(preprocess=False)) File "/ext/sage/sage-8.0/local/lib/pytho