Input file specification

The application requires a single file of type Data Catalog. The type is a generic representation of object in a shape of a catalog, so you may use a file of type Catalog (for a seismic events catalog), Ground Motion Catalog, or any other similar type - check other possible catalog data formats documentation.

Figure 1. Application input file specification

Filling form values

The application form contains entries for each column present in the input catalog file (marked with (1) in Figure 2). The values might be filled by hand or populated from an event present in the input catalog or from another catalog or event properties file. For the second option, use the Select entry from catalog button (marked with (2) in Figure 2) and choose the event to be modified (Figure 3). To load external event values, use the Load values from file button (marked with (3) in Figure 2) and choose the file from which the event should be loaded (Figure 4) - it might be a file of one the following types: Catalog, Seismic Event (can be obtained as a result of the Signal download tool application) or Extracted relocalized event properties (can be obtained as a result of the Localization application). Note, that if the chosen file is a seismic catalog, you will be also prompted to choose a single event from that file (similarly as in Figure 3). 

Figure 2. Application form with entries for catalog columns filled.

Figure 3. Dialog allowing for choosing an event from the input catalog

Figure 4. Dialog allowing for choice of an external file to load the values from

Depending on the ID specified in the form (marked with (4) in Figure 2), an event will either be modified or added to the input catalog. If the specified ID already exist in the catalog, the event with this ID will be modified by setting the provided values. If the ID didn't already exist in the catalog, a new event with the provided values will be added. Note, that the resulting catalog will be sorted by time, therefore, the event will not be added at the end, but at the right place considering its time. In case of an event modification, if its time changes, it will also be moved within the catalog, to retain the correct sorting.

Produced output

The result file will have the same name as the input with additional _mod suffix (e.g., if the input catalog file was called sample_catalog.mat, the result catalog will be named sample_catalog_mod.mat), and it will be visualized within the application outputs. 

Figure XX. Result file visualization

Back to top

Related Documents

• Page:
  Catalog Merger user guide
• Page:
  Catalog Editor user guide