Dear SAC users,
I am facing a problem with rdseed. I want to convert miniSEED data
into SAC. I have both a miniSEED file and a dataless file, and I used
the command:
rdseed -d -f file.miniSEED -g file.DATALESS
Instead of getting a single output SAC file, I have many of them.
There are no gaps in my miniSEED data but within the volume there are
as many blocks of data spanning different time intervals as output SAC
files.
I would like to know if there is an option with rdseed to tell the
program to make a unique output file. If not, is there a way to "cat"
the output SAC files in order to create a single one?
I don't know if I correctly explain my problem, since I am a new user
of SEED data maybe my vocabulary is not very accurate.
Best Regards,
Stéphane Drouet
--------------------------------
Seismologist, PhD
Observatório Nacional
Rua General José Cristino 77
CEP: 20921-400
Bairro Imperial de São Cristóvão
Rio de Janeiro - RJ - Brazil
I am facing a problem with rdseed. I want to convert miniSEED data
into SAC. I have both a miniSEED file and a dataless file, and I used
the command:
rdseed -d -f file.miniSEED -g file.DATALESS
Instead of getting a single output SAC file, I have many of them.
There are no gaps in my miniSEED data but within the volume there are
as many blocks of data spanning different time intervals as output SAC
files.
I would like to know if there is an option with rdseed to tell the
program to make a unique output file. If not, is there a way to "cat"
the output SAC files in order to create a single one?
I don't know if I correctly explain my problem, since I am a new user
of SEED data maybe my vocabulary is not very accurate.
Best Regards,
Stéphane Drouet
--------------------------------
Seismologist, PhD
Observatório Nacional
Rua General José Cristino 77
CEP: 20921-400
Bairro Imperial de São Cristóvão
Rio de Janeiro - RJ - Brazil
-
Hi Stephane-
If the SAC files split along channels and stations, this is normal.
The SAC format will only allow one station/channel per file. If you
encounter multiple files for a single station/channel, it would
suggest that there are time tears in the data. They can be very small
sometimes, so you can adjust this gap sensitivity out by setting the
SEEDTOLERANCE value to a high number like 10000. The danger of this
is that the data will be pressed together in one file and you won't be
aware of either the time breaks for the resultant shift in time that
begins to accumulate.
I am not aware of a way to have all of the SAC output piped to stdout
or to a single unique output file. rdseed is designed to create
specially named files when writing SAC.
-Rob
On Jul 18, 2012, at 12:06 PM, stephane<at>on.br wrote:
Dear SAC users,
I am facing a problem with rdseed. I want to convert miniSEED data
into SAC. I have both a miniSEED file and a dataless file, and I
used the command:
rdseed -d -f file.miniSEED -g file.DATALESS
Instead of getting a single output SAC file, I have many of them.
There are no gaps in my miniSEED data but within the volume there
are as many blocks of data spanning different time intervals as
output SAC files.
I would like to know if there is an option with rdseed to tell the
program to make a unique output file. If not, is there a way to
"cat" the output SAC files in order to create a single one?
I don't know if I correctly explain my problem, since I am a new
user of SEED data maybe my vocabulary is not very accurate.
Best Regards,
Stéphane Drouet
--------------------------------
Seismologist, PhD
Observatório Nacional
Rua General José Cristino 77
CEP: 20921-400
Bairro Imperial de São Cristóvão
Rio de Janeiro - RJ - Brazil
_______________________________________________
sac-help mailing list
sac-help<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/sac-help