Provide a stable javascript library for OpenBCI
First and foremost, Welcome! ๐ Willkommen! ๐ Bienvenue! ๐๐๐
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? (And why?)
- Who are we?
- What do we need?
- How can you get involved?
- Get in touch
- Find out more
- Understand the jargon
- The first javascript libraries for OpenBCI was the NodeJS Cyton SDK, then the NodeJS Ganglion SDK, then the NodeJS for WiFi, each with their own interfaces, serial, bluetooth, and wifi respectively.
- The ganglion's raw data is incredibly complex and must be decompressed and carefully parsed, in less words, it takes time to learn to parse this stream
- People want to use the Ganglion in the web browser
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 OpenBCI JavaScript Utilities Library will:
- Provide a nice cozy home to all the horror of parsing raw binary byte streams
- Use automated testing extensively and don't let untested code be released!
- Work in the browser and NodeJS!
- Be able to parse ganglion and cyton data.
- Store a constants file so every module agrees on names of keys and such
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
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!
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.
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.
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.
You might be interested in:
- What is OpenBCI?
And of course, you'll want to know our:
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.
npm install openbci-utilities
const { constants, debug, utilities } = require('openbci-utilities');
console.log('OpenBCIUtilities', OpenBCIUtilities);
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);
npm install
npm test
- Fork it!
- Branch off of
development
:git checkout development
- Create your feature branch:
git checkout -b my-new-feature
- Make changes
- If adding a feature, please add test coverage.
- Ensure tests all pass. (
npm test
) - Commit your changes:
git commit -m 'Add some feature'
- Push to the branch:
git push origin my-new-feature
- Submit a pull request. Make sure it is based off of the
development
branch when submitting! :D
MIT