[wineeg] Re: Time clock error suspected in WinEEG1.4

  • From: "David E. Myer, Sr." <damyer@xxxxxxx>
  • To: wineeg@xxxxxxxxxxxxx
  • Date: Sat, 15 Mar 2003 07:12:04 -0500

Joe --

In my system, I used the USB port to connect the Mitsar unit, along with  a=
USB driver that came with the Mitsar. My main concern at the moment is=20
whether my recorded data are any good. That will depend upon whether the=20
error is confined to labelling epochs in the display, or whether the=20
acquisition  software truly does not know the correct elapsed  time.

I will try to supply a signal of known frequency and see what WinEEG=20
reports. I will also check to see what our Dell laptop (500MHz on AC/200MHz=
on battery) can tell us.

Dave Myer

At 10:48 AM 3/15/03 +0100, you wrote:

>Using WinEEG 1.4 and Windows 98 SE on a slow Toshiba satellite PC
>(processor speed 2-300 Mhz)
>I get the similar results after 500 seconds the EEG shows the no.
>157, and is not changed by changing "paper speed".  We have been
>basing freq evaluation in the raw EEG on the number of wave tops seen
>in a "one second epoch"..., which actually is more like a 3 second
>F=E5 den nye Yahoo! Messenger p=E5 http://no.messenger.yahoo.com/
>Nye ikoner og bakgrunner, webkamera med superkvalitet og dobbelt s=E5=

Other related posts: