Projection Pursuit
This repository is home to a couple scikit-learn-compatible estimators based on Jerome Friedman's generalizations[1] of his and Werner Stuetzle's Projection Pursuit Regression algorithm[2][3]. A regressor capable of multivariate estimation and dimensionality reduction and a univariate classifier based on regression to a one-hot multivariate representation are included.
This repository is also meant to serve as a fairly pared-down example of how to use Github Actions, Coveralls, Sphinx, PyTest, how to deploy to PyPI and Github Pages, and how to create a Scikit-Learn Estimator that passes the sklearn checks and follows the PEP 8 style standard.
Installation and Usage
The package by itself comes with a single module containing the estimators. Before
installing the module you will need numpy, scipy, scikit-learn, and matplotlib.
To install the module execute:
pip install projection-pursuit
or
$ python setup.py install
If the installation is successful, you should be able to execute the following in Python:
>>> from skpp import ProjectionPursuitRegressor
>>> estimator = ProjectionPursuitRegressor()
>>> estimator.fit(np.arange(10).reshape(10, 1), np.arange(10))
Sphinx is run via continuous integration to generate the API.
For a few usage examples, see the examples and benchmarks directories. For an intuition of what the learner is doing, try running viz_training_process.py. For comparisons to other learners and an intuition of why you might want to try PPR, try the benchmarks. For a deep dive in to the math and an explanation of exactly how and why this works, see math.pdf.
References
- Friedman, Jerome. (1985). "Classification and Multiple Regression Through Projection Pursuit." http://www.slac.stanford.edu/pubs/slacpubs/3750/slac-pub-3824.pdf
- Hastie, Tibshirani, & Friedman. (2016). The Elements of Statistical Learning 2nd Ed., section 11.2.
- (2017) Projection pursuit regression https://en.wikipedia.org/wiki/Projection_pursuit_regression
Metadata
Release files for projection-pursuit 1.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 |
|---|---|---|---|---|
| projection_pursuit-1.1.tar.gz | 12.1 kB | Without provenance | Details for projection_pursuit-1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| projection_pursuit-1.1-py3-none-any.whl | Python 3 | none | any | Details for projection_pursuit-1.1-py3-none-any.whl |
Total release size: 24.9 kB
Release files / projection_pursuit-1.1.tar.gz
| Download URL | projection_pursuit-1.1.tar.gz |
|---|---|
| Size | 12.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c88a2f2a1b649a300882313c091d630fff5acd1044e70ee988d03926c33e439
|
|
BLAKE2b-256 checksum How to use checksums |
8d95ea8d27193c42968528b014a60eff6bb931c93ac8e4ee57e4d6d5d7ed7d09
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Release files / projection_pursuit-1.1-py3-none-any.whl
| Download URL | projection_pursuit-1.1-py3-none-any.whl |
|---|---|
| Size | 12.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6bb094f1db35b76654bd7a1105edd3e20ed1c2bf5abe47d707d77dc346a0f72
|
|
BLAKE2b-256 checksum How to use checksums |
176b482e9160cb684d022a78b37247a9592a563a939fdbc1fc21a1d0272b26dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.5
|
Security for projection-pursuit 1.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.