Too Many Mini-SEED Files?

Good day!  I’m a software guy who’s been busy slaying seismology problems on and off since the mid ‘80’s.  As a Seismo-Guy blogger, I’ll be mostly addressing issues related to software, programming and data.

For the first post, something lightweight that falls into the “Did You Know?” category:

There are many consequences of the mini-SEED specification one must reckon with when handling this format.  Thankfully, these days we programmers can make use of the indispensable mini-SEED library libmseed (available from IRIS DMC Software Library).  This library silently handles all specification considerations, making reading and writing these file types a fairly trivial adventure.

One consequence of the specification, however, provides end-users with an easy method to join files together.  Very simply described, a file formatted as Mini-SEED  is nothing but a bunch of data packets all strung together, each containing a header section and corresponding data values.

Because of this, if you ever want a collection of mini-SEED files that, for whatever reason, works better as a single file, all you have to do is ‘cat’ the files together on a command line prompt, directing the output to the single file.

Say, for example, we have a directory containing one day of data as 24 hour-long mini-SEED files, but we would rather have this day of data contained within a single file.  Using the ‘cat’ command, we can create our day-long Mini-SEED file like this:

bash> cat 2013-4-12-*.ms > 2013-4-12.ms

And that’s it!

 – Richard Boaz, Boaz Consultancy

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>