Rhythm Badge Analysis

[Robert White]

I have been looking at the GitHub site trying to identify which Python analysis files I need. Is there an order to them, do I just clone the openbadge_analysis file and run that? I am new to Python but working my way through. Any tips? Does the openbadge_analysis package still exist? I was trying to find the documentation file but it doesn't seem to exist.

Also I am wondering it the openbadge_analysis Python code is still applicable, as it appears that the proximity data that Scott has obtained (attached) is somewhat different than the proximity data in the analysis example file.

Pardon me if there are some obvious things I am missing..If all should work and my amateur Python abilities are the problem, just say the word and I will find a more skilled user..

Thanks so much!

Robert

[Oren Lederman]

Hi Robert,

The analysis package, and especially the proximity pipeline is up-to-date. I'm not sure which documentation file you are look for (it doesn't give me a link), but in general, there is very little documentation for this package (sorry). The best way to start is by looking at the examples that I mentioned (see blow). 

You should start by cloning the examples repository, and install the required packages from the requirement file. I can't teach the entire process of setting this up, but I recommend using a regular Python 2.7 installation (not Anaconda), and create a virtual python environment (for example, https://realpython.com/python-virtual-environments-a-primer/ ) to ensure you are using the correct versions of packages required for the package. If you decide to use Anconda, try to make sure you get the correct versions of the required packages. If you look closely at the requirements file, you'll see that it includes the openbadge-analysis package - it will pull the latest version form Github.

As for the file - yes, the example file slightly differs from your file, but your file should work with these examples . The main difference is in how we set the ids that badges broadcast, and how the analysis code translate them into member keys, but the code should be able to handle both.

Start by getting the example code to work, then we can figure out the rest.

Also, I'm copying some information from the other tread to make it easier for people to follow : For processing the data, you should checkout the analysis package (https://github.com/HumanDynamics/openbadge-analysis) and the examples (https://github.com/HumanDynamics/openbadge-analysis-examples). The examples are a bit mess (sorry), but I recommend focusing on these two:

1. https://github.com/HumanDynamics/openbadge-analysis-examples/blob/master/notebooks/meeting_simple_plots.ipynb - simple example for audio analysis. Note that the python code for audio analysis has a hard-coded timezone handling (it assumes GMT-4)
   
2. https://github.com/HumanDynamics/openbadge-analysis-examples/blob/master/notebooks/hub_proximity_example.ipynb - proximity data example. The proximity code is more up to date (and less messy), and has better support for timezones. The example shows how to generate the main data structures you might need - member-to-beacons (the beacons that member badges see) and member-to-member (the badges that each badge see at each point in time).

[Robert White]

Thank Oren, I was trying to use Python 3.6 through Anaconda) , I will try Strait Python 2.7, and see if I can get the examples working using that!

Kind regards

Robert