Added new example notebook to demonstrate 'risk bucketing' #3512
Conversation
Added a new example notebook to demonstrate 'risk bucketing' under the /use-cases folder. This is a technique used in credit risk and is relevant to FSI customers
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
| "cell_type": "markdown", | ||
| "metadata": {}, | ||
| "source": [ | ||
| "## The Elbow Method\n", |
There was a problem hiding this comment.
Since you've added this notebook to the RST index file, in order to have this notebook rendered correctly on the website, use H2-level headings with 2 pound symbols instead of 1 for all sub-headings (## The Elbow Method, ## Silhouette Scores, ## Gap Analysis, ## K-Means Clustering). A notebook needs a single H1-header which you will want to be # Risk Bucketing, the title of the notebook.
There was a problem hiding this comment.
Hi jkroll-aws,
As far as I'm aware I have done that (single pound for the single H1-header, double pound for all sub-headings). Have you spotted somewhere I have missed this?
There was a problem hiding this comment.
Ah I see, that was my mistake in a manual search. Please disregard, the headings look correct.
| @@ -0,0 +1,932 @@ | |||
| { | |||
There was a problem hiding this comment.
There was a problem hiding this comment.
Updated GAP to Gap in all cases for consistency
| @@ -0,0 +1,932 @@ | |||
| { | |||
There was a problem hiding this comment.
Please clear all notebook outputs. Feel free to include an extra markdown table or PNG file if you want to show any resulting tables or graphs.
Reply via ReviewNB
There was a problem hiding this comment.
That was done for last commit
| @@ -0,0 +1,932 @@ | |||
| { | |||
There was a problem hiding this comment.
How are you determining that the optimal number is 2 when the three different methods suggest 4, 2, and 5? How should customers compare the results of these different techniques?
Reply via ReviewNB
There was a problem hiding this comment.
I've added markup explaining to explain this.
| @@ -0,0 +1,932 @@ | |||
| { | |||
There was a problem hiding this comment.
Add a Conclusion section summarizing what the customer accomplished with this notebook, and suggesting any further applications or extensions.
Reply via ReviewNB
There was a problem hiding this comment.
Added a final conclusion section of markup
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Fixed spelling issues, added markup and removed dependency on local file
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
I have modified the notebook to incorporate suggestions identified by Julia |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Corrected spelling mistakes
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Fixed formatting issue with pip install
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Fixed version incompatibility issue between s3fs and pandas
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Added a new example notebook to demonstrate 'risk bucketing' under the /use-cases folder. This is a technique used in credit risk and is relevant to FSI customers
Issue #, if available:
Description of changes:
Testing done:
Merge Checklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.tox -e black-format,black-nb-formatBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.