AmaSeis “Glitch” Problem.

12/24/2004

Every week or so my system develops the problem illustrated below. One sample has a very large negative value. There is no instrument response to the glitch, so clearly the noise is introduced after the AS1 filter electronics. Stopping and starting AmaSeis doesn’t help, but rebooting the computer does. On 12/24/2004 I rebooted at about 04:21 and, as one can see below, the “glitches” stopped right away.

I’m wondering if this could be due to an error reading the serial port.  Could there be a slow memory leak in as1.exe, or some other program running on the PC,  that slows down the program and causes one sample to be misread? I wonder if there is some way to check out the “state of health” of the PC before and after a reboot to see if this could be the case?

Any suggestions for debugging this?  Let me know!

 

5/14/2005

I've been trying lots of things to get to the bottom of the glitch problem. I upgraded to WinME and ran a test with just AmaSeis, starting 4/30/2005.  There were no glitches through 5/12/2005.  The problem only shows up when SnagIt and the LinkSys wireless/USB transmitter are running. 

5/12/2005 13:22 UT   I upgraded the memory from 64 MB to 256 MB.  Started up AmaSeis, LinkSys, and SnagIt and the glitches returned right away.

5/13/2005

04:30 UT  Ran just AmaSeis.
12:51 UT  No glitches yet, so added SnagIt
19:38 UT Still no glitches, so added LinkSys
Lots of glitches started to appear.
22:47 UT  Turned off Snagit.  Still lots of glitches.

5/14/2005

03:08 UT  Turned off LinkSys and unplugged USB wireless transmitter
12:08 UT  Since 03:08 there have been far fewer glitches, but still a problem.
Noticed that "automatic updates" feature is turned on, so turned it off.  It was asking for a check to look for updates.
I noticed that the CD disk started to spin a few times as I ran the System Information program.  Each time I heard it start up, there was a glitch. 
12:14 UT I had left the WinME CD in the drive, so I removed it.

Heliccorder record for the last day.

Tasks running a 12:10 UT on 5/14/2005

System Information exported at about 12:10 UT on 5/14/2005.

 

 

12/24/2004

Every week or so my system develops the problem illustrated below. One sample has a very large negative value. There is no instrument response to the glitch, so clearly the noise is introduced after the AS1 filter electronics. Stopping and starting AmaSeis doesn’t help, but rebooting the computer does. On 12/24/2004 I rebooted at about 04:21 and, as one can see below, the “glitches” stopped right away.

I’m wondering if this could be due to an error reading the serial port.  Could there be a slow memory leak in as1.exe, or some other program running on the PC,  that slows down the program and causes one sample to be misread? I wonder if there is some way to check out the “state of health” of the PC before and after a reboot to see if this could be the case?

Any suggestions for debugging this?  Let me know!

Back