Correct, it is micro volts.
I'm on holiday at the moment, so I don't have a Muse or sample data files to hand to confirm, but that sounds about right.
Bad connection
Re: Bad connection
Happy holidays 
Okey just to make sure a diviation of about 60 micro Volts that I can see throughout my graphs are considered normal?
Still can't rap my head around BF as they show no big spike.
At th moment I tend to say it is once 2 or more sensor get faulty at the same time.
As it would not be desirable for the muse app to register every single bad connection that muse monitor does.
That would be probably frustrating for the user.
Thanks and enjoy
Okey just to make sure a diviation of about 60 micro Volts that I can see throughout my graphs are considered normal?
Still can't rap my head around BF as they show no big spike.
At th moment I tend to say it is once 2 or more sensor get faulty at the same time.
As it would not be desirable for the muse app to register every single bad connection that muse monitor does.
That would be probably frustrating for the user.
Thanks and enjoy
Re: Bad connection
BF will show when either the headband is not detected as on, or any of the HSI values are 4. HSI values of 1 or 2 will not trigger the BF mark.
For reference: 1=Good, 2=Medium, 4=Bad (detailed in the CSV FAQ online).
For reference: 1=Good, 2=Medium, 4=Bad (detailed in the CSV FAQ online).
Re: Bad connection
HSI Habitat stability index?
That is a value known only by interaxon developer?
That is a value known only by interaxon developer?
Re: Bad connection
Horse shoe indicator.
Correct. Interaxon determine the values in their sdk
Correct. Interaxon determine the values in their sdk
Re: Bad connection
So one sensor reporting a value of 4 would trigger the BF?
And a value of 4 could be defined by for example lost completely connection for xy millisecond?
And a value of 4 could be defined by for example lost completely connection for xy millisecond?
Re: Bad connection
Yes.
Note that you will see GF(Good Fit) as soon as the connection is good, so you'll be able to tell how long the problem lasted.
Note that you will see GF(Good Fit) as soon as the connection is good, so you'll be able to tell how long the problem lasted.
Re: Bad connection
Good point.
One more question...o know you are in holiday and I am sorry I really appreciate it
In layman terms.
So the muse monitor graphs will show a rise in micro volte while it is trying to keep the communication with the sensor.
While a BF doesn't show any spike. That sounds like a sudden colaps of the connection? Like it's not even trying anymore.
I thought it would be a Bluetooth issue and did some tests but that flat lined the monitor.
One more question...o know you are in holiday and I am sorry I really appreciate it
In layman terms.
So the muse monitor graphs will show a rise in micro volte while it is trying to keep the communication with the sensor.
While a BF doesn't show any spike. That sounds like a sudden colaps of the connection? Like it's not even trying anymore.
I thought it would be a Bluetooth issue and did some tests but that flat lined the monitor.
Re: Bad connection
If the Bluetooth dies then you won't get any signals to record. BF is always going to mean the headband is not fitted correctly.
Re: Bad connection
That would cause a "waiting...please power on and pair your muse" right?
I get that since a couple of days a lot. Today I had 7 within a 30 session.
I hope the device is not broken.
Strangely the RAW stays in the diviation range. Looking at that alone would not indicated that the graph is compromised.
I get that since a couple of days a lot. Today I had 7 within a 30 session.
I hope the device is not broken.
Strangely the RAW stays in the diviation range. Looking at that alone would not indicated that the graph is compromised.