|
4 | 4 | - Python virtual environment (refer to the Emotibit Plugins [repo](https://github.com/EmotiBit/EmotiBit_Plugins/blob/main/README_py.md#Creating-python-env-with-pybind11) for specific instructions on how to setup) |
5 | 5 | - CMake |
6 | 6 | - [EmotiBit ArduinoFilters](https://github.com/EmotiBit/EmotiBit_ArduinoFilters) |
| 7 | + - The EmotiBit ArduinoFilter directory should be on the same level as this repository. |
7 | 8 | - **Option 1:** Library Manager |
8 | 9 | 1. Open Arduino IDE, |
9 | 10 | 1. open the Library Manager |
10 | 11 | 1. Download EmotiBit_ArduinoFilters `v1.0.1` (if not already installed) |
11 | | - - **Option 2:** `git clone` |
| 12 | + - **Option 2:** `git clone` (*example showing cloning in Arduino Libraries directory, but user can clone in any other location, as long as ArduinoFilters is also cloned at the same directory level*) |
12 | 13 | 1. `cd` into Arduino libraries folder |
13 | 14 | - **Windows:** `C:\Users\{username}\Documents\Arduino\libraries` |
14 | 15 | - **Mac:** `/Users/{username}/Documents/Arduino/libraries` |
15 | 16 | - **Linux:** `/home/{username}/Arduino/libraries` |
16 | 17 | 1. Run `git clone https://github.com/EmotiBit/EmotiBit_ArduinoFilters` |
17 | | - 1. Run `git checkout 2a1d6cfa0b36ba8cf9e9a19b97d8fa261519a2d9` |
18 | 18 |
|
19 | 19 | ## Build |
20 | 20 | - Open a terminal window |
21 | 21 | - `cd` into the `pybind` directory |
22 | | -- Activate the Python virtual environment (instructions found in Emotibit Plugins [repo](https://github.com/EmotiBit/EmotiBit_Plugins/blob/main/README_py.md#setting-up-python-virtual-environment)) |
| 22 | +- Before being able to run cmake, you will need to update the path to `pybind11` if required. `pybind11` is installed in the python virtual environment, as the link in the previous section explains. |
| 23 | + - We tested this with cirtual environment created using python 3.12, and therefore the path to pybind in the current CMakeLists.txt file is `py-env/lib/python3.12/site-packages/pybind11/share/cmake/pybind11/`. |
23 | 24 | - Run `cmake -B build` to generate the build files (the build files will be under a directory named `build`) |
24 | 25 | - Run `cmake --build build --config Release` to generate the `.pyd` file |
25 | 26 | - On Windows using MSVC, the `.pyd` file will be under `pybind/build/Release` |
26 | 27 | - Otherwise, the `.pyd` file will be under `pybind/build` |
| 28 | +- Activate the Python virtual environment (instructions found in Emotibit Plugins [repo](https://github.com/EmotiBit/EmotiBit_Plugins/blob/main/README_py.md#setting-up-python-virtual-environment)) |
| 29 | + |
| 30 | +### Running run.py |
27 | 31 | - Open `run.py` and uncomment lines 6-7 (if on linux/macOS), or uncomment lines 10-11 (if on Windows) |
| 32 | +- `run.py` runs on emotibit data. We have checked in test data in thie repositoty. By default, the script looks for a `data` directory on the same level. Therefore, to test the script, you can extract the `tests/sit-stand-sit_v0.0.0/ip900ap/sit-stand-sit_v0.0.0_ip900ap.zip` file and place the EMotiBit.csv file in the `data` folder. You can then use the EmotiBit data parser to parse the files, since the script looks for files ending in `_PR` and `_PI`. |
28 | 33 |
|
29 | 34 | ## Testing |
30 | 35 | - Unzip the `.zip` file in `tests/simulated-unobstructed-airway_v0.0.0/ip900ap` |
|
0 commit comments