luisqtr / exciteometer

The Excite-O-Meter is a user-friendly Unity plugin for XR creators to integrate physiological user information in the development and evaluation of XR content. Specifically, it allows to record, analyze, and visualize validated metrics of heart activity from the chest strap sensor Polar H10 and movement trajectories from VR headsets.

Hi there 👋

I'm a Doctoral Researcher at Stockholm University, and Virtual Reality Developer at PortalSense.

• 🔭 I'm currently working on Data Science and Virtual Reality
• 👯 I'm looking to collaborate on research projects
• 💬 Ask me about Time Series Analysis in Python or VR development in Unity
• 📫 How to reach me: luisqtr.com | LinkedIn | Twitter

exciteometer's Issues

Awesome project. Would love to use it, wondering if it works on latest 2021 LTS.

I tried the project on different versions of unity 2021 LTS and it doesn't seem to work.
Have you tested it on 2021 LTS?

Cheers

Ui Extensions particle shader cause build to fail

Not sure if this also happens in 2019, but in Unity 2020.3.12 the Ui Extensions particle shaders cause the build to fail:
http://baroquedub.co.uk/private/forum-images/shaders-build_failed.jpg

Deleting the ones prefixed as 'UI Particle' fixes the problem (they don't appear to be used in the Excite-O-Meter UI elements)
http://baroquedub.co.uk/private/forum-images/shaders-ui-extensions.jpg

This using the UnityUIExtensions-2019-6.unitypackage (I realise this isn't your asset but leaving this here for anyone having the same issue)

Issue with Windows 10 installation

Tried to follow the installation tutorial for Windows 10. I ran into the known issue of invalid certificate.
Can you generate an new build with the updated certificate?
Is the repo live?

Could you share the code of you Android project?

Could you share the code of you Android project? I am very interested in it and want to learn it.

ExciteOMeter_1.0.7.0_Test Win10 expired certificate

I'm trying to install the latest release of ExciteOMeter_1.0.7.0_Test for Win10 ( ExciteOMeter_1.0.7_UWP.zip) but after clicking the file Add-AppDevPackage.ps1 and click on Run with Powershell, I got the following error:

. : File C:\Users\admin\Documents\WindowsPowerShell\profile.ps1 cannot be loaded because running scripts is disabled
on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3

• . 'C:\Users\admin\Documents\WindowsPowerShell\profile.ps1'

• + CategoryInfo          : SecurityError: (:) [], PSSecurityException
  + FullyQualifiedErrorId : UnauthorizedAccess
  

Found bundle: C:\Users\admin\Desktop\ExciteOMeter_1.0.7.0_Test\ExciteOMeter_1.0.7.0_x86.appxbundle
Found certificate: C:\Users\admin\Desktop\ExciteOMeter_1.0.7.0_Test\ExciteOMeter_1.0.7.0_x86.cer
Error: The developer certificate "C:\Users\admin\Desktop\ExciteOMeter_1.0.7.0_Test\ExciteOMeter_1.0.7.0_x86.cer" has expired. One possible cause is the system clock isn't set to the correct date and time. If the system settings are correct, contact the app owner to re-create a package or bundle with a valid certificate.
Press Enter to continue...:

As in issue #3 I think that the problem is that the certificate has expired.

Thank you for your help

Best regards

Ivo

ScreenRecorder setup

Hi Luis,

I am testing the project in unity 2022 and most of it is working but not the screen recording. Do you know what this error could be.

Some questions regarding the heart rate sensor.

Hi,

I really like the idea and would like to test run the plug-in.
But we do not own a Polar H10 sensor at the moment.

Is it possible to use a different sensor. E.g BiosignalPlux or Polar Verity Sense sensors?

Many thanks!

ExciteOMeter_0.2.9.0_Win10 expired certificate

Trying to install the Windows10 device (ExciteOMeter_0.2.9.0_Win10.zip from the release v1.0.1 branch), after right-clicking Add-AppDevPackage.ps1 and running PowerShell, I first get the 'Execution Policy Change' message and type Y to proceed, but then I get the following error:

Found bundle: J:\ExciteOMeter_0.2.9.0_Win10\ExciteOMeter_0.2.9.0_Test\ExciteOMeter_0.2.9.0_x86.appxbundle Found certificate: J:\ExciteOMeter_0.2.9.0_Win10\ExciteOMeter_0.2.9.0_Test\ExciteOMeter_0.2.9.0_x86.cer Error: The developer certificate "J:\ExciteOMeter_0.2.9.0_Win10\ExciteOMeter_0.2.9.0_Test\ExciteOMeter_0.2.9.0_x86.cer" has expired. One possible cause is the system clock isn't set to the correct date and time. If the system settings are correct, contact the app owner to re-create a package or bundle with a valid certificate.

I've tried on two separate computers so i assume this is not caused by an incorrect system clock, but rather that the certificate has expired.

Quaternion stores local value (1,0,0,0) instead of global rotation.

https://github.com/luiseduve/exciteometer/blob/0711c6b19057b4ce1d957b12499f145180710576/EoM/Module1_DataProcessing/Scripts/DataLogReceivers/MovementReceiver.cs#L42

Logged movement data is in local rotation or attached to the wrong GO in the scene that causes position (0,0,0) and rotation (1,0,0,0) for all the session.

can't get real data (the polar h10 has functionally worked and sent data to the Android App)

I have a functionally working polar h10. Also the polar h10 successfully sends data to the Android App.
And the Android Device is in the same wifi than the PC which is running the unity project.
But the problem is: when I deactive the the prefab EoM_SignalEmulator of the SCENE Example_withURP_NewInputSystem.unity, the INCOMING BODY SIGNALS dont show, just as the following pic shows.
Besides, I have checked the lsl panel, and it shows "No streams found!"

Again, thank you for helping me. I'm really grateful for your time!

Building for WebGL ?

Thanks for your help Luis,

I'm now trying to build the project for webgl and getting these errors. Have you tried it for Webgl? I'm testing the project without LSL. Just with the synthetic data.

RuntimeError: null function or function signature mismatch,RuntimeError: null function or function signature mismatch
at wasm://wasm/05df438e:wasm-function[63118]:0x10ec56f
at wasm://wasm/05df438e:wasm-function[39276]:0xb81ace
at invoke_vii (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:370955)
at wasm://wasm/05df438e:wasm-function[63296]:0x10f560c
at wasm://wasm/05df438e:wasm-function[52350]:0xf68e4f
at wasm://wasm/05df438e:wasm-function[9166]:0x2f34bd
at wasm://wasm/05df438e:wasm-function[39273]:0xb81a5e
at invoke_iiii (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:369932)
at wasm://wasm/05df438e:wasm-function[1597]:0xa018c
at wasm://wasm/05df438e:wasm-function[35769]:0xb0a5c8
at wasm://wasm/05df438e:wasm-function[22208]:0x8bf58e
at wasm://wasm/05df438e:wasm-function[9313]:0x2f687e
at wasm://wasm/05df438e:wasm-function[13207]:0x4b3d4b
at wasm://wasm/05df438e:wasm-function[19086]:0x65858f
at wasm://wasm/05df438e:wasm-function[43531]:0xc98d3c
at wasm://wasm/05df438e:wasm-function[19083]:0x657ba9
at wasm://wasm/05df438e:wasm-function[19082]:0x657903
at wasm://wasm/05df438e:wasm-function[8425]:0x27c159
at wasm://wasm/05df438e:wasm-function[39286]:0xb9d4c1
at Module._main (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:301181)
at callMain (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:385681)
at doRun (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:386241)
at run (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:386413)
at runCaller (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:385340)
at Object.removeRunDependency (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:16322)
at http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:1948
at doCallback (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:93440)
at done (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:93594)
at transaction.oncomplete (http://localhost/test_ble/Build/BLE%20exciteometer%20web.framework.js:3:86699)
printErr @ BLE exciteometer web.loader.js:1
callMain @ BLE exciteometer web.framework.js:3
doRun @ BLE exciteometer web.framework.js:3
run @ BLE exciteometer web.framework.js:3
runCaller @ BLE exciteometer web.framework.js:3
removeRunDependency @ BLE exciteometer web.framework.js:3
(anonymous) @ BLE exciteometer web.framework.js:3
doCallback @ BLE exciteometer web.framework.js:3
done @ BLE exciteometer web.framework.js:3
transaction.oncomplete @ BLE exciteometer web.framework.js:3
BLE exciteometer web.framework.js:3 Uncaught RuntimeError: null function or function signature mismatch
at 05df438e:0x10ec56f
at 05df438e:0xb81ace
at invoke_vii (BLE exciteometer web.framework.js:3:370955)
at 05df438e:0x10f560c
at 05df438e:0xf68e4f
at 05df438e:0x2f34bd
at 05df438e:0xb81a5e
at invoke_iiii (BLE exciteometer web.framework.js:3:369932)
at 05df438e:0xa018c
at 05df438e:0xb0a5c8
at 05df438e:0x8bf58e
at 05df438e:0x2f687e
at 05df438e:0x4b3d4b
at 05df438e:0x65858f
at 05df438e:0xc98d3c
at 05df438e:0x657ba9
at 05df438e:0x657903
at 05df438e:0x27c159
at 05df438e:0xb9d4c1
at Module._main (BLE exciteometer web.framework.js:3:301181)
at callMain (BLE exciteometer web.framework.js:3:385681)
at doRun (BLE exciteometer web.framework.js:3:386241)
at run (BLE exciteometer web.framework.js:3:386413)
at runCaller (BLE exciteometer web.framework.js:3:385340)
at Object.removeRunDependency (BLE exciteometer web.framework.js:3:16322)
at BLE exciteometer web.framework.js:3:1948
at doCallback (BLE exciteometer web.framework.js:3:93440)
at done (BLE exciteometer web.framework.js:3:93594)
at transaction.oncomplete (BLE exciteometer web.framework.js:3:86699)

Analysis scene not displaying screen shots. Unity 2022

I ran the Example_withURP_NewInputSystem, and took random screenshots, checked that the screenshots were in the logfiles.

Then I went to the Analysis scene, but did not see any screenshots and also got this error.

Excitometer crashes when pairing Polar H10

Hi there,
I tried connecting my Polar H10 device via bluetooth. It recognizes the device succesfully in step 1. In step 2 I connect to a server and tell it to record heart rate changes. It advances to step 3 and starts logging data, at which point the program suddenly stops and vanishes. What can I do to make my heartrate data discoverable by the LabRecorder via the LSL protocol?
Best,
George

Support for Web bluetooth ?

Would it be possible to support Web bluetooth sensors.
There are projects that use RxJS and Web Bluetooth. Perhaps RxJS can act like a LSL stream.
If this is possible then it would be very amazing to collect data via the web.

https://urish.medium.com/reactive-brain-waves-af07864bb7d4
https://eegedu.com/