NAME
smrspalarm - strong motion response spectra alarm detector
SYNOPSIS
smrspalarm [-select select] [-reject reject] [-backup seconds] [-tstart start_time]
[-nscl_sift nscl_expr] [-status target_name interval staproc_pf]
[-state statefile] [-debug] [-verbose]
postalarm_twin orbin [orbout]
DESCRIPTION
smrspalarm compares spectra, from ORB parameter file objects as
output by
orbsmrsp(1), to a set of exceedance limit spectra, as specified by
the associated ORB stash buffers output by
orbsmrsp(1). The exceedance limit spectra
are specified when
orbsmrsp(1) is run. The algorithms used to determine
exceedances for the various limit types are specified in
Aramco Post Earthquake Alarm
System Antelope Design Specifications, Kinemetrics, Inc., January 2012. Limit exceedances
cause
smrspalarm to produce a set of output ORB parameter file packets with
observed spectra plus the exceedance spectra. Once the exceedances have subsided,
smrspalarm
will wait
postalarm_twin seconds before declaring the alarm is finished. All observed spectra
for a particular alarm are the peak values over the entire alarm duration.
OPTIONS
-
-select select
An ORB select expression that is applied to the pf packet ORB reads.
This argument is optional.
-
-reject reject
An ORB reject expression that is applied to the pf packet ORB reads.
This argument is optional.
-
-backup seconds
If this is specified, the ORB read pointer is backed up in time relative to the -tstart
parameter, or the current time when the program starts, if -tstart is not specified.
This argument is optional.
-
-tstart start_time
Where to start processing in the ORB that contains the pf packets.
This argument is optional.
-
-nscl_sift nscl_expr
This is a regular expression that is matched against input SEED net_sta_chan[_loc] codes to determine which channels are processed.
This argument is optional.
-
-status target_name interval staproc_pf
This option will cause the generation of regular status output ORB pf packets. The information in these status packets is
described below. target_name is used to assimilate the packet ORB srcnames, <target_name>/pf/alarmst. The status packets are produced
every interval seconds. A parameter file, <staproc_pf>.pf, lists the staprocs that will be reported. These are in addition to any staprocs
that are processed automatically.
-
-state statefile
State file name for preserving last status output ORB pf packet information over restarts of smrspalarm.
-
-debug
This causes logging of memory usage statistics and should not normally be enabled.
This argument is optional.
-
-verbose
This causes verbose logging of the alarm states.
This argument is optional.
-
postalarm_twin
This is the amount of time in seconds that any alarm will stay enabled after the exceedances have subsided.
This argument is required.
-
orbin
This is a required argument and specifies the input data source ORB name.
-
orbout
This specifies the ORB name for the output pf alarm packets. If this is not specified, then the output ORB name
is set to the same as the input ORB name.
ALARM STATES
Each alarm consists of a set of output pf ORB packets. Immediately, as soon as an input spectra packet causes
any exceedances of the limit spectra, a unique alarm string identifier is composed from the station-process name
and the start time of the alarm. This string identifier is used to tag all of the output packets associated with the
alarm, using the
pfstringident parameter. Each output alarm packet also contains a state string,
pfstate and an integer sequence number,
pfseq.
The state string,
pfstate, describes the alarm state. All alarms start with
pfstate =
inprogress and
pfseq =
0.
For subsequent input spectra packets that continue one or more limit exceedances, more output alarm packes are made
with
pfstate =
inprogress and with ordinal increasing
pfseq numbers. While the alarm is active, the output observed spectra
are always the peaks over the entire alarm time duration going back to the first alarm packet. If the input spectra stay below all of the limit exceedances,
the alarm continues to stay active for a period of
postalarm_twin seconds, or if the alarm becomes active again because of any limit exceedances.
During the time period while the alarm is still active but the input spectra are below the limit exceedances, the
pfstate parameter is
set to
postalarm. Once the input spectra have stayed below all limit exceedances for
postalarm_twin seconds, the alarm becomes
inactive and one final output paramater file packet is made with
pfstate set to
final.
EXAMPLE STAPROC_PF PARAMETER FILE
staprocs &Tbl{
BR_E3469_D5
BR_R130_D5
BR_Q113_D5
YN_DW01_D5
YN_DW02_D5
}
EXAMPLE ALARM PARAMETER FILE OUTPUT
#371703 'BR_Q113_D5/pf/ALARM': 8/13/2012 (226) 21:58:28.168 : 6391 bytes
parameter file data packet
channels &Tbl{
BR_Q113_HHE g 0.2362878 g 3.04825 cm/s
BR_Q113_HHN g 0.4332562 g 3.099615 cm/s
BR_Q113_HHZ g 1.055392 g 7.754836 cm/s
limit_STRUC1_DRS g DRS
limit_STRUC1_SSE g SSE
}
endtime 1344895100.000000
exceedances &Arr{
STRUC1_DRS &Arr{
channels &Tbl{
BR_Q113_HHE 19 50.000 439.121
BR_Q113_HHN 16 40.000 546.029
BR_Q113_HHZ 27 40.000 1988.249
}
type DRS
}
STRUC1_SSE &Arr{
channels &Tbl{
BR_Q113_HHE 13 50.000 183.038
BR_Q113_HHN 12 50.000 212.886
BR_Q113_HHZ 19 50.000 979.021
}
type SSE
}
}
facility BRTT1
pfseq 1
pfstate inprogress
pfstringident BR_Q113_D5/1344895080.000000
pftype alarm/spectra/smrsp
spectrum &Tbl{
100.000 0.2362877 0.4332562 1.055392 0.105 0.2
66.667 0.3745671 0.5454668 1.463748 0.105 0.2
50.000 0.5660767 0.6257718 2.158043 0.105 0.2
40.000 0.4290203 0.6783301 2.192661 0.105 0.2169815
33.333 0.3422364 0.5964985 2.056676 0.1119004 0.2319222
28.571 0.2914198 0.5411687 1.695246 0.1188008 0.2453539
25.000 0.3349479 0.466181 1.414307 0.1257 0.2576142
23.810 0.3443361 0.424672 1.338847 0.1285124 0.2622438
22.727 0.3410796 0.3861587 1.252273 0.1312556 0.2667405
21.739 0.3470068 0.3438042 1.151113 0.134011 0.2711056
...
0.100 0.0006228339 0.0006295502 7.323921e-05 0.006674708 0.02964608
0.091 0.0006341239 0.0005924439 7.193397e-05 0.006072445 0.02874599
0.083 0.0005781715 0.0005832599 6.910438e-05 0.005532241 0.02789411
0.077 0.0005108869 0.0005703068 6.347842e-05 0.005130011 0.02721819
0.071 0.0005043225 0.0005537322 5.64883e-05 0.004724767 0.02650582
0.067 0.0004911208 0.0005346747 4.96787e-05 0.004456689 0.02600808
0.050 0.0003980772 0.0004328681 2.462825e-05 0.003310074 0.02363501
0.040 0.0003155562 0.0003492777 1.311518e-05 0.002638245 0.02197224
0.033 0.0002540085 0.0002874199 7.608167e-06 0.0022 0.02063298
}
staproc BR_Q113_D5
time 1344895080.000000
>
EXAMPLE STATUS PARAMETER FILE OUTPUT
#374847 'alarm/pf/alarmst': 8/13/2012 (226) 22:03:22.205 : 1350 bytes
parameter file data packet
pfstringident alarm/1344895402.204442
pftype alarm/status/smrsp
staprocs &Arr{
BR_E3469_D5 &Arr{
alarm_data_time 1344895100.000000
alarm_pfseq 2
alarm_pfstate final
alarm_pfstringident BR_E3469_D5/1344895100.000000
alarm_pkt_time 1344895113.167957
spec_data_time 1344895410.000000
spec_pfstringident BR_E3469_D5:1344895400.000000
spec_pkt_time 1344895392.66
}
BR_Q113_D5 &Arr{
alarm_data_time 1344895080.000000
alarm_pfseq 2
alarm_pfstate final
alarm_pfstringident BR_Q113_D5/1344895080.000000
alarm_pkt_time 1344895118.482839
spec_data_time 1344895390.000000
spec_pfstringident BR_Q113_D5:1344895380.000000
spec_pkt_time 1344895398.14
}
BR_R130_D5 &Arr{
alarm_data_time 1344895080.000000
alarm_pfseq 2
alarm_pfstate final
alarm_pfstringident BR_R130_D5/1344895080.000000
alarm_pkt_time 1344895112.013724
spec_data_time 1344895390.000000
spec_pfstringident BR_R130_D5:1344895380.000000
spec_pkt_time 1344895392.47
}
YN_DW01_D5 &Arr{
alarm_data_time -
alarm_pfseq -
alarm_pfstate -
alarm_pfstringident -
alarm_pkt_time -
spec_data_time 1344895390.000000
spec_pfstringident YN_DW01_D5:1344895380.000000
spec_pkt_time 1344895392.3
}
YN_DW02_D5 &Arr{
alarm_data_time -
alarm_pfseq -
alarm_pfstate -
alarm_pfstringident -
alarm_pkt_time -
spec_data_time 1344895390.000000
spec_pfstringident YN_DW02_D5:1344895380.000000
spec_pkt_time 1344895392.25
}
}
>
SEE ALSO
orbsmrsp(1)
AUTHOR
Danny Harvey
Boulder Real Time Technologies, Inc.