CSEP 2 CATALOG FORMAT - Revision history

Wsavran: /* Example Catalog */

2020-06-11T23:35:45Z

Example Catalog

Wsavran: /* Example Catalog */

2020-06-01T17:11:31Z

Example Catalog

Wsavran: /* Example Catalog */

2020-06-01T17:08:33Z

Example Catalog

Wsavran: /* Example Catalog */

2020-06-01T16:27:01Z

Example Catalog

Wsavran: /* Summary */

2020-05-26T22:09:50Z

Summary

Wsavran: /* Example Catalog */

2020-05-26T21:44:41Z

Example Catalog

Wsavran: /* Summary */

2020-05-26T21:19:16Z

Summary

Wsavran: /* Example Catalog */

2020-05-26T21:00:08Z

Example Catalog

Wsavran: /* Example Catalog */

2020-05-26T20:59:29Z

Example Catalog

Wsavran: /* Example Catalog */

2020-05-26T20:55:46Z

Example Catalog

@@ Line 24: / Line 24: @@
 [[Media:Csep2_sample_catalog-comcat.csv|Downloadable Example]]
-The catalog at the above link contains 1552 events. This catalog requires 92kb of storage. The table below shows expected sizes of these catalogs for individual catalogs (middle) and forecast (right) assuming 100000 catalogs per forecast. Important: If event_id is not provided by the modeler there needs to be a ',' in the final column. See example below.
+The catalog at the above link contains 829 events. This catalog requires 52kb of storage. The table below shows expected sizes of these catalogs for individual catalogs (middle) and forecast (right) assuming 100000 catalogs per forecast. Important: If event_id is not provided by the modeler there needs to be a ',' in the final column. See example below.
 {| class = 'wikitable'

@@ Line 24: / Line 24: @@
 [[Media:Csep2_sample_catalog-comcat.csv|Downloadable Example]]
-The catalog at the above link contains 1552 events. This catalog requires 92kb of storage. The table below shows expected sizes of these catalogs for individual catalogs (middle) and forecast (right) assuming 100000 catalogs per forecast.
+The catalog at the above link contains 1552 events. This catalog requires 92kb of storage. The table below shows expected sizes of these catalogs for individual catalogs (middle) and forecast (right) assuming 100000 catalogs per forecast. Important: If event_id is not provided by the modeler there needs to be a ',' in the final column. See example below.
 {| class = 'wikitable'

@@ Line 57: / Line 57: @@
 |}
 <code>
-lon,lat,M,time_string,depth,catalog_id
+lon,lat,M,time_string,depth,catalog_id,event_id
 </code><br>
--117.43017,35.616665,4.73,2019-07-06T03:22:35.630000,9.35,-1<br>
+-117.43017,35.616665,4.73,2019-07-06T03:22:35.630000,9.35,-1,<br>
--117.7365,35.891,4.64,2019-07-06T03:22:48.300000,9.1,-1<br>
+-117.7365,35.891,4.64,2019-07-06T03:22:48.300000,9.1,-1,<br>
--117.617836,35.803165,4.84,2019-07-06T03:23:50.720000,11.44,-1<br>
+-117.617836,35.803165,4.84,2019-07-06T03:23:50.720000,11.44,-1,<br>
--117.67083,35.86067,4.61,2019-07-06T03:25:27.970000,10.32,-1<br>
+-117.67083,35.86067,4.61,2019-07-06T03:25:27.970000,10.32,-1,<br>
--117.72583,35.913834,4.5,2019-07-06T03:27:07.010000,8.0,-1<br>
+-117.72583,35.913834,4.5,2019-07-06T03:27:07.010000,8.0,-1,<br>
--117.431335,35.530334,4.57,2019-07-06T03:27:11.370000,3.83,-1<br>
+-117.431335,35.530334,4.57,2019-07-06T03:27:11.370000,3.83,-1,<br>
--117.7115,35.902832,4.51,2019-07-06T03:29:32.080000,3.18,-1<br>
+-117.7115,35.902832,4.51,2019-07-06T03:29:32.080000,3.18,-1,<br>
--117.35817,35.556667,4.49,2019-07-06T03:30:25.050000,8.71,-1<br>
+-117.35817,35.556667,4.49,2019-07-06T03:30:25.050000,8.71,-1,<br>
--117.73033,35.890335,4.17,2019-07-06T03:32:46.660000,6.15,-1<br>
+-117.73033,35.890335,4.17,2019-07-06T03:32:46.660000,6.15,-1,<br>
--117.505165,35.714832,4.13,2019-07-06T03:33:09.850000,1.74,-1<br>
+-117.505165,35.714832,4.13,2019-07-06T03:33:09.850000,1.74,-1,<br>
--117.466835,35.65217,4.09,2019-07-06T03:35:05.420000,1.97,-1<br>
+-117.466835,35.65217,4.09,2019-07-06T03:35:05.420000,1.97,-1,<br>
--117.73383,35.902832,4.35,2019-07-06T03:36:16.460000,7.27,-1<br>
+-117.73383,35.902832,4.35,2019-07-06T03:36:16.460000,7.27,-1,<br>

@@ Line 57: / Line 57: @@
 |}
 <code>
-lon,lat,M,time_string,depth,catalog_id,event_id
+lon,lat,M,time_string,depth,catalog_id
 </code><br>
 -117.43017,35.616665,4.73,2019-07-06T03:22:35.630000,9.35,-1<br>

@@ Line 6: / Line 6: @@
 The catalog will be defined as a (ASCII/utf-8) text-file in csv format. Each row corresponds to a single event. This file will have the following headers:<br><br>
 <code>
-longitude, latitude, '''M''', time_string format="%Y-%m-%dT%H:%M:%S.%f", depth, catalog_id
+longitude, latitude, '''M''', time_string format="%Y-%m-%dT%H:%M:%S.%f", depth, catalog_id, [event_id]
 </code>
@@ Line 15: / Line 15: @@
 <code>'''depth'''</code>: hypocenter depth in (km)</br>
 <code>'''catalog_id'''</code>: indicates type of catalog</br>
 * observed: -1
 * simulated: [0, n_cat-1]

@@ Line 28: / Line 28: @@
 |-
 ! event count
-!  size in (Mb)
+!  catalog size (Mb)
 |-
 | 1
 | 0.00006
 |-
 | 10
 | 0.00058
 |-
 | 100
 | 0.00582
 |-
 | 500
 | 0.02909
 |-
 | 1000
 | 0.05817
 |-
 | 5000
 | 0.29087
 |}
 <code>