Home

Awesome

THIS REPOSITORY HAS BEEN DEPRECATED AND IS NO LONGER IN ACTIVE DEVELOPMENT.

OpenBCI JavaScript Utilities Library

<p align="center"> <img alt="banner" src="/images/node_icon2.png/" width="300"> </p> <p align="center" href=""> Provide a stable javascript library for OpenBCI </p>

Build Status codecov Dependency Status npm js-semistandard-style

Welcome!

First and foremost, Welcome! :tada: Willkommen! :confetti_ball: Bienvenue! :balloon::balloon::balloon:

Thank you for visiting the OpenBCI JavaScript Utilities Library repository.

This document (the README file) is a hub to give you some information about the project. Jump straight to one of the sections below, or just scroll down to find out more.

What are we doing?

The problem

So, if even developers are interested in working with [OpenBCI][link_shop_openbci] devices with javascript, they have a huge burden to overcome before they can parse the data.

The solution

The OpenBCI JavaScript Utilities Library will:

Using a single unified JavaScript library solves the challenges of parsing raw brainwave data. Our main goal is to provide a stable javascript library for OpenBCI

Who are we?

The main code writer of the OpenBCI JavaScript Utilities Library is AJ Keller. This code all started in the OpenBCI NodeJS SDK for Cyton. Many people contributed, if not directly, but by advice or instructions drawn on a coffee table to calculate impedance. A lot of people who use this library never have any idea about it! Every user of the OpenBCI GUI is heavily dependent on this code base for all data acquisition from the Cyton, Ganglion and WiFi shield!

What do we need?

You! In whatever way you can help.

We need expertise in programming, user experience, software sustainability, documentation and technical writing and project management.

We'd love your feedback along the way.

Our primary goal is to provide a stable javascript library for OpenBCI, and we're excited to support the professional development of any and all of our contributors. If you're looking to learn to code, try out working collaboratively, or translate you skills to the digital domain, we're here to help.

Get involved

If you think you can help in any of the areas listed above (and we bet you can) or in any of the many areas that we haven't yet thought of (and here we're sure you can) then please check out our contributors' guidelines and our roadmap.

Please note that it's very important to us that we maintain a positive and supportive environment for everyone who wants to participate. When you join us we ask that you follow our code of conduct in all interactions both on and offline.

Contact us

If you want to report a problem or suggest an enhancement we'd love for you to open an issue at this github repository because then we can get right on it. But you can also contact AJ by email (pushtheworldllc AT gmail DOT com) or on twitter.

Find out more

You might be interested in:

And of course, you'll want to know our:

Thank you

Thank you so much (Danke schön! Merci beaucoup!) for visiting the project and we do hope that you'll join us on this amazing journey to make programming with OpenBCI fun and easy.

Documentation

Table of Contents:


  1. Installation
  2. Usage
  3. Developing
  4. Testing
  5. Contribute
  6. License

<a name="install"></a> Installation:

npm install @openbci/utilities

<a name="usage"></a> Usage:

In NodeJS

const { constants, debug, utilities } = require("openbci-utilities");

console.log("OpenBCIUtilities", OpenBCIUtilities);

In Web Browser

index.html

<!DOCTYPE html>
<html>
  <head>
    <meta charset="UTF-8" />
    <meta
      name="viewport"
      content="width=device-width, initial-scale=1.0"
    />
    <meta http-equiv="X-UA-Compatible" content="ie=edge" />
    <title>OpenBCI Utilities</title>
  </head>
  <body>
    <pre>See data in the console</pre>
    <script src="../../dist/openbci-utilities.var.js"></script>
    <script src="./index.js"></script>
  </body>
</html>

index.js

console.log(OpenBCIUtilities);

<a name="developing"></a> Developing:

<a name="developing-running"></a> Running:

npm install

<a name="developing-testing"></a> Testing:

npm test

<a name="contribute"></a> Contribute:

  1. Fork it!
  2. Branch off of development: git checkout development
  3. Create your feature branch: git checkout -b my-new-feature
  4. Make changes
  5. If adding a feature, please add test coverage.
  6. Ensure tests all pass. (npm test)
  7. Commit your changes: git commit -m 'Add some feature'
  8. Push to the branch: git push origin my-new-feature
  9. Submit a pull request. Make sure it is based off of the development branch when submitting! :D

<a name="license"></a> License:

MIT