Skip to main content

MANUAL:

“-t” (training) parameter:

Accepts a string with arguments for training the model.

Training tasks executes in parallel processes. Each training task

generates: “.sv” file for FPGA, “.wd” file and “.tar” archive with model data for prospective classification task.

Training rules:
  1. “training_file.csv” must contain classes in the first column.

  2. “training_file.csv” must not contain a column head.

  3. The character - separator of “training_file.csv” must be “,”.

  4. You can check available training algorithms with option “–info”.

“-c” (classification) parameter:

Accepts a string with arguments for classification the passed data set.

Classification tasks might be executed parallel on several FPGAs.

Several classification tasks, addressed to FPGA, execute consistently. Each classification task generates “.csv” file with predicted answers.

Classification rules:
  1. “classification_file.csv” must not contain a column head.

  2. The character - separator of “training_file.csv” must be “,”.

  3. The “word_dict.wd” might match to firmware of FPGA.

  4. You can check available training algorithms and USB serial ports

    with option “–info”.

“-s” (split) flag:
In case the “-t” parameter is passed, it breaks the file into a training

and test sample in the ratio of 70/30.

“-v” (verbose) flag:

Enables verbose output of all errors.

All additional notifications are highlighted in yellow.

“-i” (information) flag:

Displays a message about the available algorithms and serial ports.

“-a” (accuracy) flag:

Calculates classification accuracy.

The sample passed for classification must contain the classes

in the first column.

Examples:

  1. This example starts the training task:

    $ fpga4p -t “training.csv,nbc_t”

  1. This example starts the classification task:

    $ fpga4p -c “class.csv,nbc_c,training.wd,/dev/ttyUSB0”

  2. This example prints available modules for training and

    classification, as well as available serial USB ports:

    $ fpga4p -i

Metadata

Release files for fpga4p 2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fpga4p 2.1
File Size Uploaded Provenance Actions
fpga4p-2.1.tar.gz 18.5 kB Without provenance Details for fpga4p-2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fpga4p 2.1
File Interpreter ABI Platform Actions
fpga4p-2.1-py3-none-any.whl Python 3 none any Details for fpga4p-2.1-py3-none-any.whl

Total release size: 44.0 kB

Release files / fpga4p-2.1.tar.gz

Download URL fpga4p-2.1.tar.gz
Size 18.5 kB
Tags Source
SHA-256 checksum
How to use checksums
f0a90a16730af85d45e5d622ccf0540833b4798007d4425906138c180208c146
BLAKE2b-256 checksum
How to use checksums
2c8a878424dfdf4e4b9805bf6f08a128213288934d8f2e38574f20924e1aefec
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/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7

Release files / fpga4p-2.1-py3-none-any.whl

Download URL fpga4p-2.1-py3-none-any.whl
Size 25.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
1e1b9d440215adb484070b7eb024788a5934cd56ba805fbc230b4d309b7c5859
BLAKE2b-256 checksum
How to use checksums
029218c851367d5848c5b10a675873c34e01bbda29190f93af761c2962e9e4c9
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/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7

Security for fpga4p 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page