Code Monkey home page Code Monkey logo

Comments (6)

trinostics avatar trinostics commented on July 29, 2024

Please describe your "issue" and provide a reproducible example.

from chainladder.

grishaloshadinov avatar grishaloshadinov commented on July 29, 2024

to explain the issue I've got to attach excel file, word document and pdf file, how can I possibly do that over here? That's why I asked to send me an email and I actually provided my email address

from chainladder.

LostTriangles avatar LostTriangles commented on July 29, 2024

Hi, was this issue ever resolved?

I believe I'm running into the same issue when I pull up MackChainLadder commands for Total.ParameterRisk but not Total.ProcessRisk. Running R 3.3.1 and ChainLadderPackage 0.2.2

I'll use the basic RAA data as an example.

R> MackChainLadder(RAA) should yield Mack.S.E of

1981: 0
1982: 143
1983: 592
1984: 713
1985: 1,452
1986: 1,995
1987: 2,204
1988: 5,354
1989: 6,332
1990: 24,566

The total Mack.S.E should be Sqrt(Total Parameter Risk^2 + Total Process Risk^2), which I believe also equivalent to the square root of each year's Mack SE squared.

For that value, I'm getting 26,154.79.
In R, I'm seeing in the Totals section at the bottom 26,880.74 instead.

Digging deeper into the issue, I decided to look into the relationship between ProcessRisk/Parameter Risk and TotalProcessRisk/TotalParameterRisk.

The Total ProcessRisk/ParameterRisk for any given development period should simply be the square root of the sum of squares for each origin year at that development period from our Process/Parameter Risk triangles, right?

In other words:

R> MackChainLadder(RAA)$Total.ProcessRisk should show 12824.272 for dev period 3.
R> MackChainLadder(RAA)$Mack.ProcessRisk should show 2445.506 and 12588.942 along the period 3 triangle column.

Sqrt(2445.506^2+12588.942^2) = 12824.272... The same logic applies at the other development periods as well.

However, these calculations don't seem to hold true when querying for ParameterRisk, although I would expect them to be in order to get the 26,154.79 I referenced above.

R> MackChainLadder(RAA)$Total.ParameterRisk shows 4099.369 at dev period 3.
R> MackChainLadder(RAA)$Mack.ParameterRisk shows 732.8359 and 3877.6111 along the dev period 3 column.

Square Root(732.8359^2 + 3877.6111^2) = 3946.253 <> 4099.369

Is this a bug in the package?

Thanks in advance.

from chainladder.

chiefmurph avatar chiefmurph commented on July 29, 2024

I apologize for the late reply.

"The Total ProcessRisk/ParameterRisk for any given development period should simply be the square root of the sum of squares for each origin year at that development period from our Process/Parameter Risk triangles, right?"

No, that is incorrect. Yes, the process risk is assumed to be independent by origin year. But the parameter risk cannot be independent by origin year because the origin years use the same estimated link ratio, and therefore are correlated. So the square root of the sum of the squares does not work for parameter risk of the Total.

To understand the formula for the Total, think of the Total value in a development period as the projection of the previous total (which is an estimate) plus the projection of the value (a scalar) of the "next" origin year that gets into that particular Total. The parameter risk formula of that sum uses the same recursive derivation as the parameter risk formula of any individual origin year, with a bit more complication due to the mix of an estimate and a scalar in the sum. Please refer to my paper "Unbiased Loss Development Factors" for a more thorough explanation.

Again, apologies for the delay, and thank you for your interest in ChainLadder!

Best regards,
Dan Murphy

from chainladder.

LostTriangles avatar LostTriangles commented on July 29, 2024

Hi Dan,

No worries at all, I thank you very much for your response! My second guess would have been that there was some type of Covariance coming into play which was not being shown in the summaries.

The Mack excel handout on the CAS site actually did show a Covariance Matrix for Mack's example in his paper so I must have overlooked that - but everything makes sense now.

Thanks again for your explanation, and I am definitely appreciative of the ChainLadder!

from chainladder.

trinostics avatar trinostics commented on July 29, 2024

Not a ChainLadder issue

from chainladder.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.