CSEP2 Storing Stochastic Event Sets - Revision history

Wsavran: /* Introduction */

2019-04-24T22:27:04Z

Introduction

2018-10-29T17:04:07Z

Introduction

2018-10-26T19:56:03Z

2018-10-26T19:52:08Z

Introduction

2018-10-26T18:10:13Z

Binary File Format (Stochastic Event Set)

2018-10-26T18:09:58Z

Binary File Format (Stochastic Event Set)

2018-10-26T18:09:39Z

UCERF3-ETAS

2018-10-26T18:05:34Z

File Size Calculations

2018-10-26T17:54:24Z

UCERF3-ETAS

2018-10-26T17:53:38Z

UCERF3-ETAS

@@ Line 1: / Line 1: @@
 __TOC__
-= Introduction =
+= ZMAP Format =
 This page reflects the work on dealing with stochastic event sets within CSEP2.

@@ Line 19: / Line 19: @@
 # Minute
 # Second
 The fields above can be represented on the computer using a number of different file formats. However, we will focus on a binary representation that aims to reduce the total file size.

@@ Line 7: / Line 7: @@
 In order to maintain inter-operability between models and the international testing centers we must adopt a standard format for stochastic event sets that contains the necessary and sufficient information needed to perform CSEP evaluations of the forecasts.
-The most straightforward approach would be to continue with a catalog format supported by CSEP1. The likely candidate for CSEP2 catalog format would be the so-called ZMAP format which has the following format:
+The most straightforward approach would be to continue with a catalog format supported by CSEP1. The likely candidate for CSEP2 synthetic catalog format would be the so-called ZMAP format which has the following format:
 # Longitude [deg]
@@ Line 68: / Line 68: @@
   NBYTES_SES: 4B + ''M'' * NBYTES_CATALOG
 where ''M'' is the number of synthetic catalogs in the stochastic event set.

@@ Line 11: / Line 11: @@
 # Longitude [deg]
 # Latitude [deg]
-# Decimal year (e.g., 2005.5 for July 1st, 2005)
+# Year
 # Month
 # Day

@@ Line 55: / Line 55: @@
 # Header [4 bytes]
 #* Number of Catalogs in SES: [4 byte Integer]
-#* ''M'' Binary Single Catalogs: [76 bytes]
+#* ''M'' Binary Single Catalogs: [76 byte Struct]
 === File Size Calculations ===

@@ Line 33: / Line 33: @@
 '''Note''': java.io.DataOutputStream stores binary variables in Big Endian notation.
-=== Binary File Format ===
+=== Binary File Format (Single Catalog) ===
 UCERF3-ETAS uses a binary format with the following configuration:
 # Header [6 bytes]
@@ Line 51: / Line 51: @@
 #* FSS Index: [4 byte Integer]
 #* Grid Node Index: [4 byte Integer]
 === File Size Calculations ===

@@ Line 61: / Line 61: @@
 We can compute the size of the stochastic event set using:
-  NBYTES_SES: ''M'' * NBYTES_CATALOG
+  NBYTES_SES: 4B + ''M'' * NBYTES_CATALOG
 where ''M'' is the number of synthetic catalogs in the stochastic event set.

@@ Line 30: / Line 30: @@
 == UCERF3-ETAS ==
 '''Note''': java.io.DataOutputStream stores binary variables in Big Endian notation.
 # Header [6 bytes]
 #* File Version: [2 byte short]

@@ Line 52: / Line 52: @@
 #* Grid Node Index: [4 byte Integer]
-''' File Size Calculations '''
+=== File Size Calculations ===
 We can calculate the total file size of a single catalog using the following formula: