High gamma reading flatline

Post Reply
sskelton
Posts: 3
Joined: Fri Mar 22, 2019 11:42 pm

High gamma reading flatline

Post by sskelton »

Hi James

A friend and I meditate in the high gamma regions of amplitude 140+ but whenever we get to 130 circa the graph flatlines.

Is this something built into the Muse Monitor algorithm or the Muse headset sensors algorithm?

We have tested it over many sessions with the same result, flatline around 130.

See the graph attached.

Sincerely

Stephen
Stephen Short Kriya 135.png
Stephen Short Kriya 135.png (125.16 KiB) Viewed 3642 times
User avatar
James
Site Admin
Posts: 1103
Joined: Wed Jan 02, 2013 9:06 pm

Re: High gamma reading flatline

Post by James »

If it's flatlined then you may have lost connection. Please email me the recording file and I will take a look.
sskelton
Posts: 3
Joined: Fri Mar 22, 2019 11:42 pm

Re: High gamma reading flatline

Post by sskelton »

Hi James

I have emailed you the CSV file.

I look forward to your reply.

Best regards

Stephen
User avatar
James
Site Admin
Posts: 1103
Joined: Wed Jan 02, 2013 9:06 pm

Re: High gamma reading flatline

Post by James »

You have bad sensor contact. It's worst on the ear sensors, but also bad on the forehead sensors. The flatlines are when the data becomes unusable.

To check your data quality, switch to the raw eeg view in Muse Monitor. On this graph you should see thin crisp lines, with well defined spikes when you blink. Just like in this screenshot from the home page: https://musemonitor.com/img/mm-screen-3.jpg

To get good sensor contact you must have an electrically conductive path from your skin to the sensor; this means a thin band of salty sweat must form. If you skin is dry, or hair is in the way, then you will get a bad signal. To help it get started I recommend that you dip a finger in clean water and wipe the sensor band to get it moist.
sskelton
Posts: 3
Joined: Fri Mar 22, 2019 11:42 pm

Re: High gamma reading flatline

Post by sskelton »

Hi James,

Thank you so much for your comments about bad sensor contact.

I truly understand what you are saying but we have used that "clean water" technique many times with no success.

It still drops out at EXACTLY the same point for both of us, circa 130. Every time, over dozens of tests, all with the care to get good sensor contact exactly as you say.

We approached a neuroscientist who thinks it could be to do with the MUSE sampling rate of 256 HZ as follows.

What do you think? This is from him.

"It's true that flat lines usually indicate signal loss, but my suspicion is that in your case, this is not a signal loss issue. I think the core of this issue could be due to what's called the sampling rate of an EEG. Typically, you need double the sampling rate of the highest brain frequency you'd like to study to effectively get data on the frequency. For example, most full EEGs have a sampling rate of either 250hz or 500hz. A 250hz sampling rate basically means the electrode is taking data 250 times/second and is capable of reliably measuring up to 125hz of brain activity. Anything more and it is too much to capture. I don't know the sampling rate of the muse or the exact frequency of your gamma activity, but it is completely possible that your brain is simply too fast for the muse to read, which makes sense if you look at the graph. It rises steeply, gets that same relative marker of around 130 and then all of a sudden flat-lines (your gamma is likely going "off the charts" at this point) and then once you lower the energy back down it begins to read it again once it reaches 130 and goes lower. I'm not certain if this is the truth quite yet, I'd look into the csv file and check for signal loss."

Thank you so much in advance.

Stephen
User avatar
James
Site Admin
Posts: 1103
Joined: Wed Jan 02, 2013 9:06 pm

Re: High gamma reading flatline

Post by James »

He's correct about why the flatline occurs at 130, but the reason it's getting so high is that your data is bad due to bad sensor contact.

If you truly believe it's not bad sensor contact, then your Muse may be broken.
Post Reply