Changes between Initial Version and Version 1 of ShmDocFilterSimulation


Ignore:
Timestamp:
01/22/2009 02:24:36 PM (14 years ago)
Author:
MarcusWalther
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ShmDocFilterSimulation

    v1 v1  
     1= Working with simulation filters = 
     2 
     3Simulation filters transform records of an instrument, preferably a broadband instrument, into a simulated record of another instrument. Before generating such simulation filters it should be cleared whether the transfer function of the recording instrument allows the simulation of the desired one. The recording system must provide enough signal energy in all frequency ranges of the simulated instrument. E.g. from records of STS-2 seismometers simulations of short- and longperiod instruments like WWSSN-SP and SRO-LP may be computed, but inversely, e.g. from WWSSN-SP to STS-1 is definitely not possible. In principle, the construction of simulation filters is rather simple if we use the poles-and-zeros definition of filters. These numbers can be directly written into an SH-FFT-filter file (see [ShmDocFilterFiles filter formats]). A simulation filter is created by taking the transfer function of the recording instrument (e.g. an STS-2), inverting it (take reciprocal value of the normalization, exchange poles and zeros), multiply it with the transfer function of the simulated instrument (e.g. WWSSN-SP) and shorten all possible values of the rational expression. The resulting filter (example: STS2-to-WWSSN-SP) may be used for application in SHM. Please make sure that all elements (normalization constants, poles-and-zeros definition of the filter) refer to the same recording input (usually either velocity or displacement). In practice, this is quite often a reason for confusion. For a quick view of the amplitude response of your FFT filters use [ShmDocFilterDisplay graphic display] of FFT filters. If you want to create recursive simulation filters, use the utility programs of SH/SHM (in ''$SH_UTIL'', programs ''butrec'', ''simrec'') for some standard cases or follow instructions for computing recursive filters given e.g. in ???. A [ShmDocFilterCreateSim tool] for creating a set of FFT filters for your recording equipment is provided in ''$SH_UTIL''. 
     4 
     5When using SHM, the filter files need to match a naming convention so that the files can be found on request. The filter files must be located either in ''$PWD'' or in ''$SH_FILTER''. Looking for the filter files SHM assumes file names of a defined format: 
     6 
     7FFT-files: ''<rec-instr>_S+<sim-filter>.FLF'' 
     8 
     9 <rec-instr>:: 
     10  Descriptor of the recording instrument. By default this is <station>:<channel>:<comp>  
     11 <station>:: 
     12  Station name (examples: BFO, GEC2)  
     13 <channel>:: 
     14  2-character SEED channel code (examples: BH, HH)  
     15 <comp>:: 
     16  Component (examples: Z, N)  
     17 <sim-filter>:: 
     18  Descriptor of simulated instrument (examples: WOODAND, G_WWSSN_SP)  
     19 
     20recursive files: ''<smprate>HZ_<rec-instr>_S+<sim-filter>.FLR'' 
     21 
     22 <smprate>:: 
     23  Integer sample rate in Hz (examples: 20, 40)  
     24 <rec-instr>:: 
     25  See above  
     26 <sim-filter>:: 
     27  See above  
     28 
     29All filenames must have uppercase letter only! Hyphens in filter filenames are not supported by SHM. As an example, a legal filename for an FFT simulation filter for `WWSSN-LP` recorded at station `RAR-BH-Z` would be ''RAR:BH:Z_S+WWSSN_LP.FLF''. Since it is rather inconvenient to have separate filter files for each stream, it is possible to combine several streams to a single class name within a lookup table. Class names found in the lookup table replace the individual stream names within the filenames. SHM searches two lookup tables:  
     30 1. an internal table (implemented in the source code) and an  
     31 2. external table in the file ''$SH_INPUTS/filter_lookup.txt''.  
     32The internal table maps all GRF-BH-streams (e.g. `GRA1-BH-Z`, `GRB1-BH-N`) to the name `GRF`, all GRSN-BH-streams (e.g. `BFO-BH-Z`, `CLZ-BH-E`) to the name `GRSN` and all GERESS-HH-streams (e.g. `GEA0-HH-Z`) to the name `GERESS`. Due to this lookup table the simulation filter for `WWSSN-LP` on stream `BFO-BH-Z` is ''GRSN_S+WWSSN_LP.FLF'' instead of ''BFO:BH:Z_S+WWSSN_LP.FLF''. In the external lookup table arbitrary mappings of additional stations can be added. For example if you have two stations `XYZ` and `XXX`, both with an instrument `CMG40T` which has the same transfer function for all three components then you should add the lines 
     33 
     34{{{ 
     35XYZ-BH-Z CMG40T 
     36XYZ-BH-N CMG40T 
     37XYZ-BH-E CMG40T 
     38XXX-BH-Z CMG40T 
     39XXX-BH-N CMG40T 
     40XXX-BH-E CMG40T 
     41}}} 
     42 
     43to the external table. Then the appropriate simulation filter for `WWSSN-LP` would be ''CMG40T_S+WWSSN_LP.FLF''. 
     44 
     45The general systax of a line in filter_lookup.txt is since version SHM-2.2f: 
     46 
     47{{{ 
     48<chan> <filname> [[<stime> <etime>] <flags>]  
     49}}} 
     50 
     51where <chan> is the channel string (like XYZ-BH-Z in example above), <filname> is the name given to the filter (like `CMG40T` in the example above), <stime> and <etime> specifies the valid time window (start and end time in [ShmDocTimeFormat SH time format]) of the information given in this line. Three dots (...) as time value indicate an empty time, which means no time boundary. If the equipment at a station site changes at some time a new entry for this station has to be added in filter_lookup.txt. <flags> may contain the following strings: 
     52 
     53 -FORCETAB-:: 
     54  indicates that the simulation filters of this station are given as tabulated (FAP) filter files (.FLT-files). A utility for creating these files is ''$SH_UTIL/make_sim4fap.csh''.  
     55 -FORCEFFT-:: 
     56  indicates that the simulation filters of this station are given as FFT filter files (.FLF-files) regardless of what default filter type is set.  
     57 -ALERT-:: 
     58  marks output traces of this filter entry in red. This could be used to remind the user that this entry is possibly incorrect if you are testing filters or if you have incomplete information on your recording system.  
     59 
     60Example entries of a filter_lookup.txt file are given below: 
     61 
     62{{{ 
     63XYZ-BH-Z CMG40T ... 23-Jul-2002 
     64XYZ-BH-Z STS2 23-Jul-2002 ... 
     65OLD-SH-Z OLDINSTR ... ... -FORCETAB-ALERT-  
     66}}} 
     67 
     68back to [ShmDocIndex documentation index]