Quick update.

Good news:
1) There were no errors or crashes, and the Muse S battery lasted throughout the night.
2) The eeg processor did indeed seem to pick up all my eye movements! More specifically, I watched the video recordings from the night, and found many cases of eye-movements in the video which were matched by eeg-detections (and no definite misses, from the portions I checked).

Bad news:
1) Either I set the eeg detection to be a bit too sensitive, or I move my eyes in non-rem sleep a lot as well, as there were a considerable number of detections in-between the regular 90-minute sleep cycle. I began looking into this more, but found it inefficient because...
2) My program does not currently record the raw EEG samples, only the eeg movement detection times.

Because of #2, it was hard for me to see exactly what was going on, to then be able to fine-tune the settings. Because of that, I realized the next thing I need to do is add recording of all raw EEG samples, for full-detailed analysis each morning (at least while optimizing things).

Thus, I set to work today on improving the session-data storage procedure (it was basically only storing the video-recording files before today), and adding the recording of eeg samples -- using "append mode", so that if the process ever crashes mid-session (due to bugs, Windows restarting, etc.), the data will remain.

Anyway, I just got that done, so now tonight I should be able to obtain the data I need to properly fine-tune the system in the future.

However, I only managed to finish adding the eeg-recording today. I don't yet have the user-interface created for efficiently going back and analyzing that recorded data. Thus, tonight will just be for recording the raw data, followed by another day or two of work where I build up the user-interface to then look through that data.

So it may still be a while before I, eg. have a screen capture showing me having real in-dream eye-movements, with the camera feed, the raw eeg samples, and my program's analysis data displayed on top of that...

Will be fun (and informative) once the program gets to that point, though. (should be just a few days, as I work out the UI)