Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User defined development factor in BootChainLadder #50

Open
ludovictheate opened this issue Jun 19, 2018 · 4 comments
Open

User defined development factor in BootChainLadder #50

ludovictheate opened this issue Jun 19, 2018 · 4 comments

Comments

@ludovictheate
Copy link

Hi,

I think it would be very useful to add an option in the BootChainLadder function in order to allow the user to force development factors other than those stemming from a pure application of the chainladder method. Indeed the calibration of development factors encompasses a certain level of expert judgement which can give rise to user defined development factors. The bootstrap should then be based on those DF and not on the canonical ones.

Is this something possible ? Thanks.

@mages
Copy link
Owner

mages commented Jun 19, 2018

This might be possible, but I am not sure this would make sense from a statistical point of view. It sounds too much like a fudge.

@ludovictheate
Copy link
Author

Hi Markus.

Apologies but I don't see why this would be a fudge. It is market best-practice (and also a main feature in many of the well known reserving software) to perform adjustments on the development factors (removing outliers, reducing the calibration history,...). Performing a bootstrap using the canonical factors when the "best-estimate" is computed using adjusted factors doesn't make a lot of sense.

@mages
Copy link
Owner

mages commented Jun 19, 2018

Hi Ludovic,
I am aware of the practice of selecting 'suitable' factors. However, it appears to me more based expert judgment, i.e. which data to include or exclude, rather than statistical, and therefore forcing a model to work with a given data set, instead of selecting a suitable model for the data at hand. Anyhow, that's more a philosophical point and what I would call 'fudging'.
Yet, I am happy to support you, if you would like to look into the implementation of your idea.

@trinostics
Copy link
Collaborator

trinostics commented Jun 19, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants