npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

edge-impulse-cli

v1.29.3

Published

Command-line interface tools for Edge Impulse

Downloads

1,875

Readme

Edge Impulse CLI tools

Command-line interface tools for Edge Impulse. We make things smarter by enabling developers to create the next generation of intelligent device solutions with embedded Machine Learning.

This package consists of four tools (click to see their respective documentation):

Installation

  1. Install Node.js v12 or higher on your host computer.

  2. Install the CLI tools via:

    $ npm install -g edge-impulse-cli

Afterwards you should have the tools available in your PATH.

Building from source

If you're making changes to the CLI you can build from source.

  1. Clone this repository:

    $ git clone https://github.com/edgeimpulse/edge-impulse-cli
  2. Install the dependencies:

    $ npm install
  3. Build and link the application:

    $ npm run build
    $ npm link

CLI Options

You can pass in options to the CLI. These options may vary between the various tools invoked. Here are the key ones:

  • --clean - clear credentials, and re-authenticate. Use this to switch projects or devices.
  • --api-key <apikey> - set an API key, useful for automatic authentication with a new project.
  • --greengrass - (Not used in serial daemon) utilize the AWS IoT Greengrass authentication context and AWS Secrets Manager to authenticate with a new project. Note below.
  • --help - see all options.

Greengrass command line option note

This option has no effect on the serial daemon process. If the option is provided to the serial daemon, it will be simply ignored.

Debugging the serial daemon

If you're adding support for a new development board, and you want to debug how the serial daemon implements serial protocol or what raw data the data forwarder sees, you can enable logging.

  • For the data forwarder, uncomment: 1.
  • For the serial daemon, uncomment these lines 1, 2.

Then build from source.

Troubleshooting

Tools version "2.0" is unrecognized (Windows)

If you receive the following error: The tools version "2.0" is unrecognized. Available tools versions are "4.0", launch a new command window as administrator and run:

$ npm install --global --production windows-build-tools
$ npm config set msvs_version 2015 --global

EACCES: permission denied, access '/usr/local/lib/node_modules' (macOS)

This is indication that the node_modules is not owned by you, but rather by root. This is probably not what you want. To fix this, run:

$ sudo chown -R $USER /usr/local/lib/node_modules