Start wrapping chainladder to use as MCP tools#23
Closed
little-croissant wants to merge 4 commits into
Closed
Conversation
Collaborator
Author
|
@hugolatendresse is this the best way? do I literally need to go thru chainladder and wrap everything we need? also check the repo structure, idk if this is the best way to organize |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added triangle conversion for loss run + exposure, started on methods (BF, expected loss, chainladder) for Ultimate/IBNR. Tested that Cline can access these tools via MCP server
Currently having an issue because chainladder has strict data type requirements to convert pandas DF to their Triangle class:
{
"triangle_id": null,
"profile": null,
"warnings": [
"Triangle build failed: unconverted data remains when parsing with format "%Y": "-01-01", at position 0. You might want to try:\n - passing
formatif your strings have a consistent format;\n - passingformat='ISO8601'if your strings are all ISO8601 but not necessarily in exactly the same format;\n - passingformat='mixed', and the format will be inferred for each element individually. You might want to usedayfirstalongside this."]
}