On Mon, 9 Mar 2009 18:01:23 -0700 Geoffrey  wrote:

> FYI:
> 
> There Is Only One Way I can Get Winquake to
> see right times for my data.
> 
> It is necessary to crop the data to the nearest
> second before giving it to Winquake.
> 
> No matter what I do WQ will not see fractions of seconds
> for the start time.
> 
> No matter what the precision is of the numbers
> WQ only will show the first sample to a whole second.
> 
> Like if I tell it 23:49: 20.4 for the first second
> it will show only 23:49:20 for the first sample
> 
> SO you must run your data until it gets to
> 23:49:21 then crop it from there to the end
> before giving it to wq and tell wq
> it is 23:49:21.0 and you can forget the fractions
> your start time may be a couple milliseconds off
> but WTHeck.
> 
> Otherwise if you do not do this things just aint right.
> 
> Also, the various filters in the WQ3 FFT used to work fine
> but since installing the new WQ3  those filters dont work (all grayed out) ??
> What am I doing wrong ?
> 
> cheers
> geoff

Hi,

I'm starting back here, rather than following on from the other posts, because 
I want to ask you to describe the format of the data that you are putting into 
WinQuake. By this, I *don't* mean the exact arrangement of bytes in the input 
file, but rather the "conceptual" format of the data.

Why I'm asking is because from what you have written, it almost sounds as if 
you are supplying a file containing only the samples and are trying to tell 
WinQuake what the time the data starts separately. If we can get onto the same 
wavelength on this, it will make things clearer.

I don't run WinQuake (nor indeed a seismic sensor at the moment) but it looks 
to me as if WinQuake wants to display the data starting at a round second. (It 
makes the divisions on the time axis regular.) I think that if you tell it to 
start in the middle of a second, it will wind back to the sample that was taken 
closest to the "start" of the second, and start displaying from there. This is 
not the same as what you are describing, which is why I'm asking about your 
data input.

Kevin 


__________________________________________________________

Public Seismic Network Mailing List (PSN-L)