Accessing CyberShake Peak Acceleration Data - Revision history

Scottcal: /* RotD data */

2017-10-24T20:23:28Z

RotD data

2017-10-24T20:20:31Z

RotD data

2017-10-24T20:16:05Z

Using the retrieval script

2017-10-24T16:03:58Z

Reading Peak Acceleration Files

2017-10-24T16:01:37Z

RotD data

2017-10-23T17:39:50Z

RotD data

2017-10-23T17:39:32Z

PeakVals data

2017-10-17T18:12:17Z

2017-10-12T19:53:56Z

Finding files by hand

2017-10-12T19:04:22Z

@@ Line 67: / Line 67: @@
 Each RotD file may have results from 1 or more rupture variations, which are not necessarily sorted by rupture variation ID.  The headers must be parsed to find the rupture variations of interest.
-The current list of periods we perform RotD calculations for in CyberShake runs can be found in [http://source.usc.edu/svn/cybershake/import/trunk/DirectSynth/src/rotd/rotd.c rotd.c]; they are 1.0, 1.2, 1.4, 1.5, 1.6, 1.8, 2.0, 2.2, 2.4, 2.6, 2.8, 3.0, 3.5, 4.0, 4.4, 5.0, 5.5, 6.0, 6.5, 7.5, 8.5, 10.0.
+The current list of periods we perform RotD calculations for in CyberShake runs can be found in [http://source.usc.edu/svn/cybershake/import/trunk/DirectSynth/src/rotd/rotd.c rotd.c]; they are 1.0, 1.2, 1.4, 1.5, 1.6, 1.8, 2.0, 2.2, 2.4, 2.6, 2.8, 3.0, 3.5, 4.0, 4.4, 5.0, 5.5, 6.0, 6.5, 7.5, 8.5, 10.0.  Previously, we omitted the periods from 1.0-1.8 Hz, so you should not assume these are the available periods; you should parse the records.
 So the overall format for a RotD file is:

← Older revision		Revision as of 20:20, 24 October 2017
Line 66:		Line 66:

	Each RotD file may have results from 1 or more rupture variations, which are not necessarily sorted by rupture variation ID. The headers must be parsed to find the rupture variations of interest.		Each RotD file may have results from 1 or more rupture variations, which are not necessarily sorted by rupture variation ID. The headers must be parsed to find the rupture variations of interest.
		+
		+	The current list of periods we perform RotD calculations for in CyberShake runs can be found in [http://source.usc.edu/svn/cybershake/import/trunk/DirectSynth/src/rotd/rotd.c rotd.c]; they are 1.0, 1.2, 1.4, 1.5, 1.6, 1.8, 2.0, 2.2, 2.4, 2.6, 2.8, 3.0, 3.5, 4.0, 4.4, 5.0, 5.5, 6.0, 6.5, 7.5, 8.5, 10.0.

	So the overall format for a RotD file is:		So the overall format for a RotD file is:

@@ Line 22: / Line 22: @@
 === Using the retrieval script ===
-To help in finding PSA data, there is a Python script, /home/scec-02/cybershk/utils/retrieve_psa.py, which takes the run ID, source ID, rupture ID, rupture variation ID, output file, whether you want RotD data or PSA data, and a flag to include the header information in the output.  It works similarly to the seismogram retrieval script.
+To help in finding PSA data, there is a Python script, /home/scec-02/cybershk/utils/retrieve_psa.py (and in SVN at https://source.usc.edu/svn/cybershake/import/trunk/Utils/retrieve_psa.py), which takes the run ID, source ID, rupture ID, rupture variation ID, output file, whether you want RotD data or PSA data, and a flag to include the header information in the output.  It works similarly to the seismogram retrieval script.
 === Finding files by hand ===

@@ Line 32: / Line 32: @@
 === PeakVals data ===
-'New' (Run_ID > 1309) PeakVals files begin with a header, specified in [[https://scec.usc.edu/scecpedia/CyberShake_output_data_headers#PSA_header]], followed by the data.  This data is given as the PSA values as 4-byte floats for 44 periods, first the X component, then the Y component.  A PeakVals file may have information for one or more rupture variations.  Like the seismogram files, the rupture variations are not necessarily in order, so the headers must be read to find the rupture variations of interest.  Overall, the layout is:
+'New' (Run_ID > 1309) PeakVals files begin with a header, specified [[CyberShake_output_data_headers#PSA_header|here]], followed by the data.  This data is given as the PSA values as 4-byte floats for 44 periods, first the X component, then the Y component.  A PeakVals file may have information for one or more rupture variations.  Like the seismogram files, the rupture variations are not necessarily in order, so the headers must be read to find the rupture variations of interest.  Overall, the layout is:
   <PSA header for 1st rupture variation(RV)>

@@ Line 56: / Line 56: @@
 === RotD data ===
-RotD data files begin with a header, specified in [[CyberShake_output_data_headers#RotD_header]], followed by a 4-byte integer giving the number of periods, followed by the data.  This data is bundled as individual RotD records, which represent RotD results for a given period.  These records are specified in C as:
+RotD data files begin with a header, specified [[CyberShake_output_data_headers#RotD_header|at this link]], followed by a 4-byte integer giving the number of periods, followed by the data.  This data is bundled as individual RotD records, which represent RotD results for a given period.  These records are specified in C as:
   struct rotD_record {

@@ Line 82: / Line 82: @@
   ...
   <last RV, record P>
 == Plotting PSA data ==

← Older revision		Revision as of 17:39, 23 October 2017
Line 51:		Line 51:

	'Old' (Run_ID < 1310) PeakVals files are in the same format, but omit the header.		'Old' (Run_ID < 1310) PeakVals files are in the same format, but omit the header.
		+
		+	The units are centimeters per second squared.

	=== RotD data ===		=== RotD data ===

← Older revision		Revision as of 18:12, 17 October 2017
Line 80:		Line 80:
	...		...
	<last RV, record P>		<last RV, record P>
		+
		+	== Plotting PSA data ==
		+
		+	To plot PeakVals data, you can use the script /home/scec-00/cybershk/scripts/plot_N_peakVals.py , which will produce a comparison plot of an arbitrary number of PeakVals files, with X and Y separate.
		+
		+	Note that the PeakVals files MUST have header information to be used in this script.

@@ Line 26: / Line 26: @@
 === Finding files by hand ===
-If for some reason you need to find files by hand, you should follow the instructions for finding seismogram files by hand, given here: [[Accessing_CyberShake_Seismograms#Locating_Seismogram_Files_by_Hand]].  For PSA files, the filename convention is PeakVals_*.bsa, and *_PSA.zip for zipped files.  We didn't start creating RotD files until Study 15.4, so all RotD files are in the 'new' format, and can be found in the /home/scec-04/tera3d/CyberShake/data/PPFiles/<site>/<runID> root.
+If for some reason you need to find acceleration files by hand, you should follow the instructions for finding seismogram files by hand, given here: [[Accessing_CyberShake_Seismograms#Locating_Seismogram_Files_by_Hand]].  For PSA files, the filename convention is PeakVals_*.bsa, and *_PSA.zip for zipped files.  We didn't start creating RotD files until Study 15.4, so all RotD files are in the 'new' format, and can be found in the /home/scec-04/tera3d/CyberShake/data/PPFiles/<site>/<runID> root.
 == Reading Peak Acceleration Files ==