MIES
Miniature Insurance Economic Simulator
Introduction
The purpose of MIES is to simulate, with the appropriate balance between detail and abstraction, various economic equilibria that result between the interactions between insurance firms, policyholders, and regulators.
The goal is to create an explanatory model that links economic theory with actuarial science.
Development Blog
Additional examples can be found in a series of blog posts, here:
https://genedan.com/category/mies/
Documentation
Documentation can be found here:
https://genedan.com/MIES/docs/
Concepts Modeled
- Availability of insurance
- Predatory pricing
- Impact of insolvency on insureds
Project Goals
- Should be consistent with both macro and microeconomic theory
- Should be consistent with actuarial theory
Example Simulation
import pandas as pd
import datetime as dt
from entities.god import God
from entities.broker import Broker
from entities.insurer import Insurer
Set up the environment and relative entities - A broker, a population of insureds, and two insurers with 4B in capital:
ahura = God()
ahura.make_population(1000)
rayon = Broker()
company_1 = Insurer(4000000, 'company_1')
company_2 = Insurer(4000000, 'company_2')
Set up the pricing strategy for each company:
company_1_formula = 'incurred_loss ~ age_class + profession + health_status + education_level'
company_2_formula = 'incurred_loss ~ age_class'
The broker can now be used to place business, given each insurer's pricing strategy:
rayon.place_business(
pricing_date,
company_1,
company_2
)
event_date = pricing_date + dt.timedelta(days=1)
Generate losses, report claims, and then reprice and renew policies:
event_date = pricing_date + dt.timedelta(days=1)
ahura.smite(event_date)
rayon.report_claims(event_date)
company_1.price_book(company_1_formula)
company_2.price_book(company_2_formula)
pricing_date = pricing_date.replace(pricing_date.year + 1)
Metadata
Release files for mies 0.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mies-0.0.0.tar.gz | 12.0 kB | Without provenance | Details for mies-0.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mies-0.0.0-py3-none-any.whl | Python 3 | none | any | Details for mies-0.0.0-py3-none-any.whl |
Total release size: 38.5 kB
Release files / mies-0.0.0.tar.gz
| Download URL | mies-0.0.0.tar.gz |
|---|---|
| Size | 12.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
67f7676b0c971da1c5507ef7a2d159766bcfc5f046d8748ed3e0f6ef84b18ccf
|
|
BLAKE2b-256 checksum How to use checksums |
98c12b2bd6f87207b4b6ebe626dedd4c7c200415fe15dad5a4b606c64ac805b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.2
|
Release files / mies-0.0.0-py3-none-any.whl
| Download URL | mies-0.0.0-py3-none-any.whl |
|---|---|
| Size | 26.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f203612311128497ce10acab066ae575f9dfa3866124a6d06d6a4ce4b217e12
|
|
BLAKE2b-256 checksum How to use checksums |
850a6c237828cb614042aeb78658f862137cdc9b60a9c7cc25ac4ec491b26823
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.2
|
Security for mies 0.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.