NaN and zeros in raw data
NaN and zeros in raw data
I’m currently analyzing EEG data collected using the Muse headset and examining the raw signals from TP10, TP9, AF7, and AF8. However, I’ve noticed some NaN and 0 values in my data, and I’m trying to understand their causes. My current assumption is that 0 values occur when the electrodes lose proper contact with the forehead. Is this correct? As for the NaN values, I’m unsure what might be causing them. What could be the reason for this?
Re: NaN and zeros in raw data
NaN means "Not a Number" and happens when you have errors in Bluetooth data transmission. If you're getting a lot of them, then it might be that your phones Bluetooth chip isn't compatible with the Muse. Interaxon list all Huawei phones as being incompatible with Muse for this reason.
You might also get it if you've got other Bluetooth devices using up the bandwidth, for example Bluetooth headphones/earpods. I know there was an issue with iPhones and AirPod Pro's both maxing out the Bluetooth bandwidth.
A few zeros are fine. If you lose connection to the head, you'll see static noise, not zeros. If you're getting constant zeros, then that sounds like a hardware/ bluetooth issue.
You might also get it if you've got other Bluetooth devices using up the bandwidth, for example Bluetooth headphones/earpods. I know there was an issue with iPhones and AirPod Pro's both maxing out the Bluetooth bandwidth.
A few zeros are fine. If you lose connection to the head, you'll see static noise, not zeros. If you're getting constant zeros, then that sounds like a hardware/ bluetooth issue.