Skip to content

Releases: siboehm/lleaves

lleaves v1.2.3

04 Aug 15:20
7b38bac
Compare
Choose a tag to compare
Release version 1.2.3

lleaves 1.2.2

03 Aug 18:04
7b38bac
Compare
Choose a tag to compare

Safe softmax for multiclass in #83
Thanks @starkwj and Claude!

lleaves 1.2.1

05 Feb 04:05
82ec179
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 1.2.0...1.2.1

lleaves 1.1.0

11 Nov 15:36
Compare
Choose a tag to compare

What's Changed

Full Changelog: 1.0.0...1.1.0

lleaves 1.0.0

10 May 10:21
Compare
Choose a tag to compare

FIRST MAJOR VERSION RELEASE. There are actually no big changes in this version, but lleaves has been so stable over the past 2 years that not calling it v1 was just me chickening out 🐓

Minor changes:

  • C interface: the results array passed via pointer is now overwritten with the results instead of being accumulated into.

lleaves 0.2.7

10 Aug 07:08
Compare
Choose a tag to compare

What's Changed

  • Avoid undefined behaviour / poison by checking for NaNs before llvm::fptosi by @siboehm in #23. This broke categorical predictions when NaNs occurred, but only on ARM arch.

Full Changelog: 0.2.6...0.2.7

lleaves 0.2.6

10 Jul 16:59
Compare
Choose a tag to compare

Minor new feature: Allow specification of the root function's name in the compiled binary. This enables linking against multiple lleaves-compiled trees. Thanks @fuyw!

What's Changed

  • Chore: Bump pre-commit and Github actions + py3.10 on CI by @siboehm in #22
  • add function_name to compiler by @fuyw in #21

New Contributors

  • @fuyw made their first contribution in #21

Full Changelog: 0.2.5...0.2.6

lleaves 0.2.5

23 Mar 08:11
63a26d0
Compare
Choose a tag to compare
  • Fix a bug when predicting from pandas Dataframes for models with pandas_categorical:null. Thanks @chenglin!

lleaves 0.2.4

22 Nov 06:43
26e39d6
Compare
Choose a tag to compare

Bugfix release: Removes an accidentally introduced dependency on pandas.

lleaves 0.2.3

21 Nov 16:57
fa14013
Compare
Choose a tag to compare
  • Fixed an overflow issue occurring during predictions on very large datasets (>50Mio rows, >20 features)