VotingChainladder enhancements
See original GitHub issueWould like to get additional model properties functioning with the VotingChainladder
estimator prior to release.
import chainladder as cl
raa = cl.load_sample('RAA')
bcl1 = cl.Pipeline(steps=[('dev', cl.Development(average='volume')), ('model', cl.Chainladder())])
bcl2 = cl.Pipeline(steps=[('dev', cl.Development(average='simple')), ('model', cl.Chainladder())])
estimators = [('bcl1', bcl1), ('bcl2', bcl2)]
vot = cl.VotingChainladder(estimators=estimators)
vot.fit(raa)
assert abs((bcl1.fit(raa).named_steps['model'].full_expectation_ + bcl2.fit(raa).named_steps['model'].full_expectation_)/2 - vot.full_expectation_).max().max()< 1e-4
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Releases & Changelog — Reserving in Python
#117 - VotingChainladder enhancements to allow for more flexibility in defining weights (courtesy of @cbalona). Bug Fixes.
Read more >chainladder: Versions | Openbase
#131 - Added a BarnettZenwirth development estimator; #117 - VotingChainladder enhancements to allow for more flexibility in defining weights (courtesy of ...
Read more >Additive Enhancements (Commander / EDH MTG Deck)
Additive Enhancements · Enchantment (26) · Sorcery (6) · Creature (21) · Instant (6) · Artifact (3) · Planeswalker (1) · Commander (1)...
Read more >Game of Thrones Conquest: Building Enhancements - YouTube
Everything you want to know about building enhancements and which ones may help you most as a new player. GOTC tips!
Read more >chainladder - Property and Casualty Loss Reserving in Python
VotingChainladder enhancements. Would like to get additional model properties functioning with the VotingChainladder estimator prior to ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This may help reduce the complexity of the dictionary approach:
This is due to adding a new axis so that the weights can multiply with the ultimates. When refitting, it is adding a 6th axis. Should be a quick easy fix. It may also be avoided through better handling of the weights as per my previous comment.