============================================
|PyPI version| |license|
About this library(watch test folder for more detailed)
-------------------------------------------------------
1. Set train and test dataset under data/input.
2. Created features from original dataset need to be under
data/output/features.
3. Models for stacking are defined in scripts under scripts folder.
4. Need to define created features in that scripts.
5. Just run ``sh run.sh`` (``python scripts/XXX.py``)
--------------
Getting started: 30 seconds to stacking
---------------------------------------
--------------
Installation
------------
To install stacking, ``cd`` to the stacking folder and run the install
command:
::
sudo python setup.py install
You can also install stacking from PyPI:
::
pip install stacking
--------------
Tree of files
-------------
- base\_fixed\_fold.py (class of stacking)
- data/
- input/
- train.csv (train dataset)
- test.csv (test dataset)
- output/
- features/
- features.csv (features user created)
- temp/
- temp.csv (files saved in stacking)
- scripts/
- script.csv (main script where concrete models defined)
--------------
Details of scripts
------------------
- base.py:
- Base models for stacking are defined here (using
sklearn.base.BaseEstimator).
- Some models are defined here. e.g., XGBoost, Keras, Vowpal Wabbit.
- These models are wrapped as scikit-learn like (using
sklearn.base.ClassifierMixin, sklearn.base.RegressorMixin).
- That is, model class has some methods, fit(), predict\_proba(), and
predict().
New user-defined models can be added here.
Scikit-learn models can be used.
Base model have some arguments.
- 's': Stacking. Saving a oof(out-of-fold)
prediction({model\_name}\_all\_fold.csv) and average of test
prediction based on train-fold models({model\_name}\_test.csv). These
files will be used for next level stacking.
- 't': Training with all data and predict
test({model\_name}\_TestInAllTrainingData.csv). In this training, no
validation data are used.
- 'st': Stacking and then training with all data and predict test ('s'
and 't').
- 'cv': Only cross validation without saving the prediction.
Define several models and its parameters used for stacking. Define task
details on the top of script. Train and test feature set are defined
here. Need to define CV-fold index.
Any level stacking can be defined.
--------------
TODO LIST
---------
Need to be more general library.
Please check isuues!!
.. |PyPI version| image:: https://badge.fury.io/py/stacking.svg
:target: https://badge.fury.io/py/stacking
.. |license| image:: https://img.shields.io/github/license/mashape/apistatus.svg?maxAge=2592000
:target: https://github.com/ikki407/stacking/LICENSE
Metadata
Release files for stacking 0.1.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 |
|---|---|---|---|---|
| stacking-0.1.3.tar.gz | 12.5 kB | Without provenance | Details for stacking-0.1.3.tar.gz |
Release files / stacking-0.1.3.tar.gz
| Download URL | stacking-0.1.3.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5616f58c4ffbee695b6d58829a7489e2fe2208bf94f8b67a87b90f3f1694b669
|
|
BLAKE2b-256 checksum How to use checksums |
dddb1c7854e524635f6599bce2fcabac00f60d7b2d88121b31c0e68c7c18dada
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for stacking 0.1.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.