PyQCore is a client in Python to access our high speed reservoir computing engine, WebQore.
We are in an early-release beta. Expect some adventures and rough edges.
Update
2019.06.13 Release 0.2.1: Add sofmax_top option to classification_predict to show the softmax values with predicted classes.
2019.03.08 Release 0.2.0: Add regression_train, regression_test, regression_predict.
More about PyQCore
At a granular level, PyQcore is a library that consists of the following components:
| Component | Description |
|---|---|
| pyqcore.client.SimpleQCoreClient | a client class that makes model on WebQore Engine |
| pyqcore.examples.jpvow.load_jpvow | a function that loads sample data from UCI repository and return as sklearn format |
This library is enable to use the WebQore Engine in your codes. Also you need get license code from QuantumCore website to use this library(QuantumCore Inc. ).
About QuantumCore Engine
WebQore Engine is developed by QuantumCore Inc. This new model is 4Kx faster and lighter than previous LSTM or RNN model without GPU. Also you do not have to adjust parameters anymore.
The Engine you use with this library is currently running on t2.micro on AWS (check out the speck here).
The company also plans to impliment this algorithm on small edge computer.
Installation
This library requires Python > 3.5.
Installing PyQcore is not difficult. Just run the command below:
pip install pyqcore
Or clone this repository and run:
python setup.py install
Getting Started
Refer our sample scrpts or tutorial notebook.
Make sure that you need get license code from QuantumCore Inc.
Communication
- GitHub issues: bug reports, feature requests, install issues, RFCs, thoughts, etc.
- Mailing List: please send any issue at info-dev@qcore.co.jp
License
Copyright (c) 2019 QuantumCore Inc.
Metadata
Release files for pyqcore 0.2.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 |
|---|---|---|---|---|
| pyqcore-0.2.1.tar.gz | 1.2 MB | Without provenance | Details for pyqcore-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyqcore-0.2.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for pyqcore-0.2.1-py2.py3-none-any.whl |
Total release size: 2.4 MB
Release files / pyqcore-0.2.1.tar.gz
| Download URL | pyqcore-0.2.1.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
18a53110cdae8fa39b962470fa29f5fdc0a78907e600cb7fb3e1a0edf96c1242
|
|
BLAKE2b-256 checksum How to use checksums |
39a267eef02966cbf41e420df15dbc6ab6ab1d5845f0724d718250d05a065ec2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.26.0 CPython/2.7.16
|
Release files / pyqcore-0.2.1-py2.py3-none-any.whl
| Download URL | pyqcore-0.2.1-py2.py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
90f93d910eeca0453034fe007d4dba2763c32fca6df5d565b4d4b78a5cea5e92
|
|
BLAKE2b-256 checksum How to use checksums |
def7125caacbe5bee5ed114c71655c084bafdf1896a87de8337f7795fb44fab7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/40.8.0 requests-toolbelt/0.9.1 tqdm/4.26.0 CPython/2.7.16
|
Security for pyqcore 0.2.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.