Implements the Excess Certainty Adjusted Probability adjustment procedure as described in the paper “Irrational Exuberance: Correcting Bias in Probability Estimates” by Gareth James, Peter Radchenko, and Bradley Rava (Journal of the American Statistical Association, 2020; <doi:10.1080/01621459.2020.1787175>). The package includes a function that preforms the ECAP adjustment and a function that estimates the parameters needed for implementing ECAP. A tutorial is included / is available at my github url <https://github.com/bradleyrava/ecap-python>. Please review the full paper for detailed information about the ecap prodecure <http://faculty.marshall.usc.edu/gareth-james/Research/Probs.pdf>.
Metadata
Release files for ecap 0.2.3
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 |
|---|---|---|---|---|
| ecap-0.2.3.tar.gz | 13.4 kB | Without provenance | Details for ecap-0.2.3.tar.gz |
Release files / ecap-0.2.3.tar.gz
| Download URL | ecap-0.2.3.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
615436aaa6ead3735a5073a4e97115c64f07647d1e56ee7e49b70c90647237f2
|
|
BLAKE2b-256 checksum How to use checksums |
6462780d84e9bdaa8c43af1e5b4a23a85098d42059a80e8d12148b4c90aeaf22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.15.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.48.2 CPython/2.7.16
|
Security for ecap 0.2.3
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.