----- Original Message ----- 
From: "Kevin Brunt" 
To: 
Sent: Tuesday, March 10, 2009 2:41 PM
Subject: Re: WinQuake


> 
> 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

Hello Master Kevin;

This header is for a PSN TEXT FILE which I preferr to use.
THE other called PSN4 which I believe is a binary file mifgr work
differently.
I have not yet tried the PSN4 format because text is so much easier to deal with.
( Its all relative my dear einstein/watson)


Heres the headers of which I speak, One is named work and the other Dont_Work
********************************** CUT HERE********************************************
In this one your data has also been cropped to start at the right second
or as close as possible to that second.

WORKS.TXT
! PSN ASCII Event File Format 2.0
Start Time: 2009/03/10 19:56:00
Start Time Offset: 26
Number of Samples:  65560
SPS: 18.2058
Time Reference Type: Oth
Comment:[GVA] 
A/D Converter Bits: 8
Data Minimum: -33.8
Data Maximum:  38.2
Data Mean:  0
! Sensor Information:
Sensor Location: GVA
Sensor Description: HS10-1
Sensor Latitude: 33.42138
Sensor Longitude: -111.57477
Sensor Elevation: 507.5
Sensor Incident: 0
Sensor Azimuth: 0
Sensor Orientation: Z
Sensor Type: Velocity
Sensor Sensitivity:  7.100e-008
Sensor ID: HS-10
Magnitude Correction: 0.00235574
Component Name: SPZ
Network Affiliation: IRSS
Pick Information:
Pick Information:
Data:

***************************************CUT HERE***************************************
          DONT WORK
In this one your data starts at the exact time you are trying to tell
winquake to use.

! PSN ASCII Event File Format 2.0
Start Time: 2009/03/10 19:56:25.250000000
Start Time Offset: 0.000
Number of Samples:  65560
SPS: 18.2058
Time Reference Type: Oth
Comment:[GVA] 
A/D Converter Bits: 8
Data Minimum: -33.8
Data Maximum:  38.2
Data Mean:  0
! Sensor Information:
Sensor Location: GVA
Sensor Description: HS10-1
Sensor Latitude: 33.42138
Sensor Longitude: -111.57477
Sensor Elevation: 507.5
Sensor Incident: 0
Sensor Azimuth: 0
Sensor Orientation: Z
Sensor Type: Velocity
Sensor Sensitivity:  7.100e-008
Sensor ID: HS-10
Magnitude Correction: 0.00235574
Component Name: SPZ
Network Affiliation: IRSS
Pick Information:
Pick Information:
Data:

*************************************CUT HERE**************************



 
> 
> 
> __________________________________________________________
> 
> Public Seismic Network Mailing List (PSN-L)
> 
> To leave this list email PSN-L-REQUEST@.............. with 
> the body of the message (first line only): unsubscribe
> See http://www.seismicnet.com/maillist.html for more information.
>
__________________________________________________________

Public Seismic Network Mailing List (PSN-L)