This is part 8 of a multipart series showing you how to get started with the MetaWear platform. View the contents of the series to easily skip forwards or backwards
For anyone looking to do analysis of the data they are collecting with their board, it is likely that you will want to access the data so you can analyze it using languages/tools like Python, R or Matlab. The easiest way to get started here is by writing your sensor readings to a comma separated values (CSV) file. Let’s see how to do it.
We will need to import a few libraries to assist:
Now, in our
onCheckChanged switch function, we instantiate more variables for our CSV writing:
The File we are creating in the above code will be located in your downloads directory. See more information about Android Environment variabes.
Within our route subscription, we add the main CSV writing code:
A few points to note from the above code:
- We append a comma to the end of our
csv_accel_entryvariable, to separate the readings (i.e. columns).
- Our CSV writing code must be wrapped in a
- We add a line break (
\n) to separate the entries
At this point, the bare bones of our CSV writing code are complete, but if you were to run the app you would receive an
EACCES (Permission denied) error. To remedy this, we must grant certain permissions within our AndroidManifest.xml file. Add the following line before your
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
Now run the app. After you toggle the switch on and off, you should be able to find a file called
METAWEAR.csv in your downloads folder. You may find it easier to download and use one of the many free Android OS file manager apps such as ‘file explorer’ for this purpose.
Your CSV file should look like this:
So far so good. Now we duplicate the code in the Gyroscope route (see the github version-0.7 branch if you have any trouble). Now when you open your csv file you will see alternating rows of accelerometer and gyroscope data.
To make sure your two sensor readings in sync, you must ensure that the Output Data Rate (ODR) for both sensors is configured to the same frequency. Knowing this, you can store the data you received in order, and use the sensor’s and the data’s list index to compute approximately when said data was received relative to the starting time.
It’s likely that we will want a header in our CSV file. We add this earlier in our code, writing the header before other data:
Finally, in its current form, every new entry will be appended to the existing CSV file. This may not be desirable, so we add a couple of lines of code which delete the previous CSV file before creating a new one everytime the switch is toggled. If this behaviour is not what you require, you can omit this, or put it into a separate method if you wish to add more complex logic:
You now have a CSV file which you can use for your data analysis. In the next section we will discuss ensuring the connection to your board is reliable.
Note You can view all these changes in the github repository on the branch version-0.7