IRT Parameter Estimation routines
This package implements parameter estimation for logistic Item Characteristic Curves (ICC) from Item Response Theory (IRT).
Maximum likelihood estimation (MLE) fitting routines for the following logistic models are implemented:
- 1PL - 1 parameter logistic (Rausch) model
- b (difficulty)
- 2PL - 2 parameter logistic model
- a (discrimination) and b (difficulty)
- 3PL - 3 parameter logistic (Birnbaum) model
- a (discrimination), b (difficulty) and c (pseudo-guessing)
In addition, fitting using the zeta/lamdba/c formulation is also implemented. The difference here boils down to the logistic exponent. The conversion is:
a (θj - b) = ζ + λ θj
a * (theta_j - b) = zeta + lambda * theta_j
This seemingly insignificant change has drastic effects on the convergence properties (especially in the 2PL case, but also the 3PL case).
Many of the methods in this package are derived from work by Frank B. Baker and Seock-Ho Kim:
Item Response Theory: Parameter Estimation Techniques
http://www.crcpress.com/product/isbn/9780824758257
The exception is the 3 parameter zeta/lambda/c implementation which to our knowledge has not been derived or documented before. For this reason, we include the mathematical derivations here:
The original BASIC code that work was derived from can be downloaded here:
http://www.crcpress.com/downloads/DK2939/IRTPET.zip
The original python port of these hand-coded iterative schemes can be found in the file baker_mle.py (imported as "baker"). These are mainly useful for comparative purposes (for instance, the 2PL version matches 1-1 with the original routine's published values).
The main routines in this package (zlc_mle.py and abc_mle.py) use scipy.optimize.root instead for greater efficiency and accuracy. zlc uses a hybrid (zeta, lambda, c) formulation which makes the 2PL and 3PL systems converge much more much stably. This version is the one imported at the top level. This version also includes an "abc emulation" mode where zlc is still used internally, but automatic conversion is used so that the function takes a/b/c as arguments.
abc (in abc_mle.py) uses the (a,b,c) formulation, which may also be useful (try both for 3PL!). If you want to really dig into this code, it is very informative to use a side-by-side difference tool (like Vimdiff, KDiff3, WinMerge, FileMerge, or Meld) to compare abc_mle.py with zlc.mle.py.
All common utilities are found in util.py.
Tutorial
Updated 2021
To see a sample usage, check out the QuickTutorial notebook
Metadata
Release files for irt-parameter-estimation 0.4.1
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 |
|---|---|---|---|---|
| irt_parameter_estimation-0.4.1.tar.gz | 16.0 kB | Without provenance | Details for irt_parameter_estimation-0.4.1.tar.gz |
Release files / irt_parameter_estimation-0.4.1.tar.gz
| Download URL | irt_parameter_estimation-0.4.1.tar.gz |
|---|---|
| Size | 16.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
27ddd498425164c59ee14ca8792fc4f7e6427ca95cf1520e3819e2d2991ed9e8
|
|
BLAKE2b-256 checksum How to use checksums |
19bec35c3f323c2f5fa26d4551cb1f421c9157a89fcad0f9486557c015d0d8d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.5.0.1 requests/2.28.1 setuptools/51.3.3 requests-toolbelt/0.9.1 tqdm/4.41.1 CPython/3.8.10
|
Security for irt-parameter-estimation 0.4.1
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.