[obspy-users] Beamforming Interpolation

UCSC echavess at ucsc.edu
Thu Apr 24 02:17:12 CEST 2014


Hi Martin, 

I’m using the sonic function of Obspy to perform the Beamforming 
analysis and Matplotlib to make the plot: http://docs.obspy.org/tutorial/code_snippets/beamforming_fk_analysis.html
Any hint to include the interpolation using this code? I’ll try your previous suggestions. 

Thanks in advance, 

Esteban





On Apr 23, 2014, at 4:41 PM, obspy-users-request at lists.swapbytes.de wrote:

> Send obspy-users mailing list submissions to
> 	obspy-users at lists.swapbytes.de
> 
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.swapbytes.de/mailman/listinfo/obspy-users
> or, via email, send a message with subject or body 'help' to
> 	obspy-users-request at lists.swapbytes.de
> 
> You can reach the person managing the list at
> 	obspy-users-owner at lists.swapbytes.de
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of obspy-users digest..."
> 
> 
> Today's Topics:
> 
>   1. Empty sac file object (yaman ozakin)
>   2. Re: Beamforming Interpolation (mgal)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 23 Apr 2014 14:57:52 -0700
> From: yaman ozakin <dandik at gmail.com>
> To: users at obspy.org
> Subject: [obspy-users] Empty sac file object
> Message-ID:
> 	<CALNFkZHLPLE3JRy0mVYGOF4v75rxVgA-7jwgwd4-gSg39Asg8g at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hello,
> 
> I've been struggling to convert raw binary data into a sac file.
> 
> Is there a way to create an empty object with default SAC header values
> easily? If there is, I can just put the time series that I got from the
> binary file into the data array of the trace object and write the file,
> which would be great.
> 
> Cheers,
> ---
> Yaman ?zak?n *<:^)
> PhD Candidate - Geophysics
> earth.usc.edu/~ozakin/
> University of Southern California
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.swapbytes.de/pipermail/obspy-users/attachments/20140423/bae1fa14/attachment-0001.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 24 Apr 2014 09:41:40 +1000
> From: mgal <Martin.Gal at utas.edu.au>
> To: users at obspy.org
> Subject: Re: [obspy-users] Beamforming Interpolation
> Message-ID: <fad3b6894b66.5358dc54 at utas.edu.au>
> Content-Type: text/plain; charset="windows-1252"
> 
> Hi Esteban,
> 
> what function are you using to plot your data (I am assuming matplotlib here)? If it is pcolor() or pcolormesh(), here is a small guide on how to accomplish what you are looking for, http://stackoverflow.com/questions/12081932/interpolation-with-matplotlib-pcolor . imshow() interpolates between gridpoints automatically, but I am not sure of its support with polar plots.
> 
> You also could increase the bin number in your calculations to achieve a better resolution? To my experience, the fk algorithm is quite fast and results can be obtained within seconds for a reasonable resolution. 
> 
> Cheers,
> Martin
> 
> 
> 
> ----- Original Message -----
> From: UCSC <echavess at ucsc.edu>
> Date: Thursday, April 24, 2014 6:31
> Subject: [obspy-users] Beamforming Interpolation
> To: obspy-users at lists.swapbytes.de
> 
>> Dear all; 
>> 
>> I?m working on F-k analysis (with seismic noise) using the polar 
>> plot representation
>> and I?d like to know if is it possible to apply interpolation 
>> between the gridded bins;
>> if so, may I have an example how to do it?
>> 
>> Thanks in advance, 
>> 
>> Esteban
>> 
>> 
>> 
>> On Apr 22, 2014, at 3:00 AM, obspy-users-
>> request at lists.swapbytes.de wrote:
>> 
>>> Send obspy-users mailing list submissions to
>>> 	obspy-users at lists.swapbytes.de
>>> 
>>> To subscribe or unsubscribe via the World Wide Web, visit
>>> 	http://lists.swapbytes.de/mailman/listinfo/obspy-users
>>> or, via email, send a message with subject or body 'help' to
>>> 	obspy-users-request at lists.swapbytes.de
>>> 
>>> You can reach the person managing the list at
>>> 	obspy-users-owner at lists.swapbytes.de
>>> 
>>> When replying, please edit your Subject line so it is more specific
>>> than "Re: Contents of obspy-users digest..."
>>> 
>>> 
>>> Today's Topics:
>>> 
>>>  1. Re: SeedLink protocol details (Chad Trabant)
>>> 
>>> 
>>> ---------------------------------------------------------------
>> -------
>>> 
>>> Message: 1
>>> Date: Mon, 21 Apr 2014 14:39:02 -0700
>>> From: Chad Trabant <chad at iris.washington.edu>
>>> To: users at obspy.org
>>> Subject: Re: [obspy-users] SeedLink protocol details
>>> Message-ID: <7E86D1EA-0486-41C8-91E3-
>> BE4AF4CA49DF at iris.washington.edu>> Content-Type: text/plain; 
>> charset=windows-1252
>>> 
>>> 
>>>>> This is a good resource:
>>>>> http://www.seiscomp3.org/doc/seattle/current/apps/seedlink.html
>>>>> 
>>>>> Otherwise the 2.1 manual is all that I know exists.
>>>> 
>>>> Thank you for your response. Unfortunately I have already 
>> worked through those two.
>>> 
>>> Hi Bernhard,
>>> 
>>> The given sources are the only documentation that I know of 
>> and as far as I know are accurate representations of the 
>> seedlink server maintained by GEOFON as a component of 
>> SeisComP.  Extensions of the protocol were mostly done by 
>> me for IRIS needs and are reflected in libslink and 
>> ringserver.  Care was taken to ensure that clients based on 
>> libslink and ringserver were compatible with GEOFON?s implementation.
>>> 
>>> I will try to help with some of the questions below (mostly by 
>> reading the libslink source code):
>>> 
>>>> They leave a few lower-level questions unanswered:
>>>> 
>>>> - At what version did which feature become available?
>>> 
>>> Notable changes (based on sl_checkversion() usage in 
>> libslink): 
>>> 
>>> version >= 2.5 support multi-station capability in addition to 
>> uni-station mode.  I do uni-station mode servers are common 
>> any more.
>>> 
>>> version >= 2.92 supports the INFO command
>>> 
>>> version >= 2.92 supports TIME command for time window selection.
>>> 
>>> version >= 2.93 supports adding the packet time stamp to the 
>> FETCH and DATA commands
>>> 
>>> version >= 3.1 supports the BATCH command
>>> 
>>> As far as I know only ringserver & libslink support the 
>> CAPABILITY client reporting feature and the capability flag for 
>> the server.
>>> 
>>>> - Does a server need to advertise its version number?
>>> 
>>> Not strictly, but it is useful for libslink (and maybe other 
>> client libraries) for identification of features.  For 
>> libslink, the identification returned for the HELLO command 
>> should be of the form:
>>> 
>>> "SeedLink v#.# <optional text> <:: capability flags>?
>>> 
>>> where the capability flags are:
>>> 
>>> 
>> SLPROTO:#.# == SeedLink protocol version
>>>         CAP == 
>> Supports CAPABILITY command
>>>         EXTREPLY 
>> == Extended reply messages supported
>>> 
>> NSWILDCARD == Network & station code wildcarding
>>> 
>>> So the version should definitely be in the ?v#.#? part of the 
>> identification string.  If the optional capabilities part 
>> of the identifier is to be supported the version can also be 
>> reported using the SLPROTO flag.  Again, this is how 
>> libslink deals with a server, not sure how many other clients do so.
>>> 
>>>> How should a
>>>> version of 0.0 be handled?
>>> 
>>> In libslink this translates to version unknown, in which case 
>> the server is treated as 3.0 capability.  For a long time 
>> 3.0 version servers were prevalent, older ones are probably not 
>> around much more.
>>> 
>>>> - What are the allowed contents of the 8 bit SeedLink header?
>>> 
>>> I am not sure to what 8-bit header you are referring to, each 
>> miniSEED record is prefixed by an 8-byte header, which I presume 
>> you mean.  This is documented at 
>> http://www.seiscomp3.org/doc/seattle/current/apps/seedlink.html#data-transfer as:
>>> 
>>> 'The SeedLink header is an ASCII string consisting of the 
>> letters "SL" followed by a six-digit hexadecimal packet sequence 
>> number.?> 
>>> The exception to this is when first 6 characters of a packet 
>> are ?SLINFO", in which case it is an INFO packet.  In this 
>> case, the 8th byte of the header, the so-called termination 
>> flag, indicates when the packet is the last of a potential 
>> series of INFO packets.  When the termination flag is a ?*? 
>> character more INFO packets are expected, when it is not an ?*? 
>> character (e.g. a space) it is the last INFO packet for a given 
>> request.> 
>>>> - What wildcards are allowed in a selector? (E.g. the docs 
>> above don't
>>>> mention '*' which is implemented in Ringserver.)
>>> 
>>> For clarity: in SeedLink a selector refers to a pattern used 
>> to match location IDs and channels for a given network-station 
>> pair.  The STATION command is given by a client and 
>> includes the network and station code desired, subsequent SELECT 
>> commands can be given with selectors to subset the location IDs 
>> and channel codes desired for the network-station specified in 
>> the most recent STATION command.
>>> 
>>> I believe the GEOFON server supports only ??? for a single 
>> character wildcard in selectors (see the description of the 
>> SELECT command in the protocol doc on seiscomp3.org).  
>> Also, I do not believe the GEFON server allows any wildcards in 
>> the station and network values passed with the STATION command.
>>> 
>>> ringserver also accepts ??? for a single character in 
>> selectors, it does NOT accept ?*? as you imply above.  
>> ringserver does accept ?*? and ??? in the network and station 
>> values passed with the STATION command, this is an extension 
>> added by IRIS.
>>> 
>>>> - What are the allowed encodings for XML payloads in INFO 
>> responses?> 
>>> Undefined as far as I know.  I don?t think the protocol 
>> cares and it only matters what the client is able to parse 
>> usefully.  For widest compatibility I would recommend 
>> keeping it UTF-8.
>>> 
>>>> - What is the EXTREPLY feature?
>>> 
>>> That allows the server to report extra information (?EXTended 
>> REply?) back to the client.  In the case of ringserver, the 
>> client must report that it supports EXTREPLY in the capabilities 
>> information or such extra content is not sent.  This extra 
>> information contains details of WHY a command failed, the 
>> original protocol only allows ?OK? or ?ERROR?.
>>> 
>>> I believe this extension is only implemented in ringserver and 
>> libslink, but I?m not certain. 
>>> 
>>>> - Are begin_time and end_time time zone dependent or UTC?
>>> 
>>> I?m pretty sure all date-times in the protocol are UTC to 
>> match the time base of data, SEED records are always expected to 
>> be in UTC.
>>> 
>>> cheers,
>>> Chad
>>> 
>>> 
>>> 
>>> ------------------------------
>>> 
>>> _______________________________________________
>>> obspy-users mailing list
>>> obspy-users at lists.swapbytes.de
>>> http://lists.swapbytes.de/mailman/listinfo/obspy-users
>>> 
>>> End of obspy-users Digest, Vol 41, Issue 14
>>> *******************************************
>> 
>> _______________________________________________
>> obspy-users mailing list
>> obspy-users at lists.swapbytes.de
>> http://lists.swapbytes.de/mailman/listinfo/obspy-users
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.swapbytes.de/pipermail/obspy-users/attachments/20140424/ee860120/attachment.html>
> 
> ------------------------------
> 
> _______________________________________________
> obspy-users mailing list
> obspy-users at lists.swapbytes.de
> http://lists.swapbytes.de/mailman/listinfo/obspy-users
> 
> End of obspy-users Digest, Vol 41, Issue 16
> *******************************************



More information about the obspy-users mailing list