TODO

[atomashpolskiy]

List of stuff, which should be done eventually:

• configurable thresholds for time synchronization (separate for client-server and server-server)
• optimal GC parameters (we need low latency GC)
• remove redundant queryHeadsets call (currently it's done from two different places)
• reconnect to Cortex on the fly? (it's already done in CortexClientImpl, but not utilized by polling/subscription code)
• notify admin UI, when connection to Cortex is lost
• monitoring headset connection/signal quality and providing this information to clients and admin UI
• distribution, shell wrappers

Might also want to switch to embeddable database like sqlite, but that's not decided yet

[jpollet]

Not a TO DO but to not lost track of the info, got the answer from Emotiv support regarding "IED_RAW_CQ" column and monitoring headset contact quality :

"it's raw value send from firmware. We use it to run contact quality detection. It is not overall headset contact quality."

So it's not the overall headset contact quality, don't really understand what it is...
To get each electrode contact quality we can use : https://emotiv.github.io/cortex-docs/#dev-event

And after I asked Cuong how to get overall contact quality, he said :

"I think you can have a formula base on the contact quality of each sensor, may use median."

Shall we use it for overall contact quality ? And display a percentage on the Web API ?