Difference between revisions of "EEW Evaluation"
| Line 5: | Line 5: | ||
We separate the summaries into "Event" Summaries and "Catalog" Summaries where catalog means any set of earthquakes, and the summary must make it clear what criteria were used to define the catalog. | We separate the summaries into "Event" Summaries and "Catalog" Summaries where catalog means any set of earthquakes, and the summary must make it clear what criteria were used to define the catalog. | ||
| + | |||
| + | == CISN On Site Trigger == | ||
| + | An example CISN Trigger file is posted here: | ||
| + | |||
| + | We noted several things about the current formatting. | ||
| + | #The report id never changes. The intention was that this uniquely identified the file. But it is currently fixed. | ||
| + | #Forecasts PGV and Mag only | ||
| + | #Reports both algorithm and alert time, which always seem to have a delta of 2 seconds. This may mean difference between the two is the amount of data needed to produce the alert | ||
| + | #Multiple forecasts per trigger file | ||
| + | #Multiple events per trigger file | ||
| + | #Seems to report duplicate forecast information for each trigger. One copy of the trigger also contains observational data for the trigger. It is unclear how the trigger is match to the event id. We noted that in some cases the event id reported in the trigger file is not the final ANSS event id. | ||
| + | |||
== ShakeMap Data == | == ShakeMap Data == | ||
Revision as of 02:52, 1 May 2011
Contents
Performance Evaluation Summaries
Two descriptions of performance summaries include:
- CISN Testing Document
- CTC Group Evaluation Collection
We separate the summaries into "Event" Summaries and "Catalog" Summaries where catalog means any set of earthquakes, and the summary must make it clear what criteria were used to define the catalog.
CISN On Site Trigger
An example CISN Trigger file is posted here:
We noted several things about the current formatting.
- The report id never changes. The intention was that this uniquely identified the file. But it is currently fixed.
- Forecasts PGV and Mag only
- Reports both algorithm and alert time, which always seem to have a delta of 2 seconds. This may mean difference between the two is the amount of data needed to produce the alert
- Multiple forecasts per trigger file
- Multiple events per trigger file
- Seems to report duplicate forecast information for each trigger. One copy of the trigger also contains observational data for the trigger. It is unclear how the trigger is match to the event id. We noted that in some cases the event id reported in the trigger file is not the final ANSS event id.
ShakeMap Data
We are currently working with the ShakeMap stationlist txt file. We may convert to the stationlist xml files, but it was easier to parse the column oriented to start.
We have identified several formats to the ShakeMap. Two main formats are the CI: and NN: events, and ECX events. ECX events have their pgv and pga values in different columns than the others, so this type of ShakeMap report must be checked for while parsing.
ShakeMap files also have different number of columns populated. Currently we require that both PGA and PGV are listed before we use it as a authorized data observation. The goal is to maximize the number of observations we have to compare to forecasts. Right now, we don't have forecasts at PGV or PGA only sites. Once we do, we should add small modification to track observations even if they only have one component of data.
Processing Flow
Current design is based on processing one or more trigger reports. Currently two types of trigger reports are supported CIT On Site, and ETH Virtual Seismologist.
- Init CISN Station list, ANSS EQ catalog, ShakeMap catalog
- For each Trigger File
- Mapped to One or More ANSS Events and observed data from ShakeMap
- For each event in trigger file
- write event summary
- Add to catalog summaries
- write catalog summaries
ANSS Catalog Files
Software Download
CTC Software is posted in git repository on github. maechlin:ctc
