RxSci operators for Scikit River.
Get Started
Evaluate and train a Hoeffding Tree Classifier from a stream of events:
import rx
import rxsci_river as rsr
from river import synth
from river.tree import HoeffdingTreeClassifier
gen = synth.Agrawal(classification_function=0, seed=42)
rx.from_(gen.take(1000)).pipe(
rsr.evaluate.prequential(
model=HoeffdingTreeClassifier(
grace_period=100,
split_confidence=1e-5,
nominal_attributes=['elevel', 'car', 'zipcode'],
),
pretrain_size=100),
).subscribe(
on_next=print,
)See the Maki Nage documentation for more information.
Installation
RxSci River is available on PyPi and can be installed with pip:
python3 -m pip install rxsci-river1 maintainer
Metadata
1 maintainer
Release files for rxsci-river 0.1.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 | |
|---|---|---|---|---|
| rxsci-river-0.1.0.tar.gz | 4.8 kB | Without provenance | Details |
Release files / rxsci-river-0.1.0.tar.gz
| Download URL | rxsci-river-0.1.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7c2eba37e6c11065d5c86f9f274bd65cf12afe96c526f731364b470d4d6d6a5f
|
|
BLAKE2b-256 checksum How to use checksums |
b583c1fe59afc49833de952cd5069b7e949eb7577a26cf1a8aceda95f6960fad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.10
|
Security for rxsci-river 0.1.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.
