search

sccn / lsl_archived

Multi-modal time-synched data transmission over local network
242 stars 133 forks source link

LabRecorder should warn users when no clock_offsets are being recorded #331

Closed dmedine closed 6 years ago

dmedine commented 6 years ago

I was thinking about @sahin-ozsoy and the clock_offsets not being recorded problem today (https://github.com/sccn/labstreaminglayer/issues/329#issuecomment-411084342).

This has sometimes happened to me even on a local host---although I didn't realize at the time that this was the problem because it only happens when I run a particular BCILab experiment and I thought it had something to do with BCILab.

I don't know why this is happening in my case, but it would be nice if LabRecorder could warn me if this was occurring. I think somebody proposed this feature already somewhere else. This would be a good project for the upcoming LSL workshop in Delmenhorst!

tstenner commented 6 years ago

More general: establish a way to display log messages?

dmedine commented 6 years ago

Yes.

On 08/10/2018 07:59 PM, Tristan Stenner wrote:

More general: establish a way to display log messages?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sccn/labstreaminglayer/issues/331#issuecomment-412159680, or mute the thread https://github.com/notifications/unsubscribe-auth/ADch7tWCvKEF8wSXAoDdhdNs3IrfJNsGks5uPcoQgaJpZM4V1vwO.

cboulay commented 6 years ago

This feature was added by @tstenner to the labrecorder subrepo here: https://github.com/labstreaminglayer/App-LabRecorder/commit/19202145c6ea0462932210a72f47208eb53a1d6b

The work is done. As soon as we finish the repo migration then it'll be an included feature. So I'm closing this issue.

(This does not mean that the clock offset problem is fixed)