Skip to content

Releases: LiamMcAllisterGroup/cytools

v1.0.12

13 Dec 20:23
Compare
Choose a tag to compare
  • cleanup/style changes
  • allow an optional max_iter parameter to tip_of_stretched_cone
  • quicker secondary cones for star triangulations

Full Changelog: v1.0.11...v1.0.12

v1.0.11

18 Oct 17:21
Compare
Choose a tag to compare

Full Changelog: v1.0.10...v1.0.11

v1.0.10

17 Oct 13:30
Compare
Choose a tag to compare
  1. bugfix in 9645240

Full Changelog: v1.0.9...v1.0.10

v1.0.9

13 Oct 13:17
Compare
Choose a tag to compare
  1. fix dependency issues in 4c1070b
  2. minor bugfixes in e502995
  3. better allowance of sparse hyperplanes in 71d543e

Full Changelog: v1.0.8...v1.0.9

v1.0.8

03 Oct 01:26
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.7...v1.0.8

v1.0.7

22 Aug 14:13
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.6...v1.0.7

v1.0.6

16 Aug 18:05
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.0.5...v1.0.6

v1.0.5

18 May 17:15
Compare
Choose a tag to compare

What's Changed

  • Cleaned Cone class by @natemacfadden
  • Cleaned find_lattice_points when min_points is used by @natemacfadden
  • TOPCOM patch for trivial triangulations
  • Locked down pip package versions

Full Changelog: v1.0.4...v1.0.5

CYTools v1.0.4

03 May 16:58
Compare
Choose a tag to compare

Changelog:

  • Cone.find_lattice_points no longer crashes if both min_points is used and if the problem is infeasible at some degree
  • Updated GCD reduction of rays/hyperplanes in Cone.init to use integer arithmetic if the array is integer. Also, vectorized calculations
  • Included warning for very large coordinates in ray/hyperplane array (such large values definitely break Cone.is_sold, likely other methods, too)

Breaking changes:

None

CYTools v1.0.3

19 Apr 19:01
Compare
Choose a tag to compare

Changelog:

  • Fixed an installation issue due to the new version of pip being incompatible with python-flint.
  • Changed the all_triangulation function since the new version of TOPCOM does some things differently and was causing this function to get stuck even for very simple polytopes.
  • Changed the default backend behavior for the find_interior_point function.

Breaking changes:

None