Adding to CyberShake - Revision history

Scottcal at 18:11, 5 October 2018

2018-10-05T18:11:43Z

Scottcal: /* Register ruptures in the replica catalog (RC) */

2018-09-27T21:48:50Z

Scottcal: /* Database modifications */

2018-09-27T21:39:28Z

Database modifications

Scottcal: /* New ERF */

2018-09-27T20:03:37Z

New ERF

Scottcal: /* Register ruptures in the replica catalog (RC) */

2018-09-27T18:26:21Z

Scottcal: /* Register ruptures in the replica catalog (RC) */

2018-09-27T18:25:55Z

Scottcal: /* New ERF */

2018-09-27T18:25:43Z

New ERF

Scottcal: /* New ERF */

2018-09-27T18:25:22Z

New ERF

Scottcal at 18:25, 27 September 2018

2018-09-27T18:25:01Z

Scottcal at 18:01, 27 September 2018

2018-09-27T18:01:35Z

@@ Line 18: / Line 18: @@
 # Copy the ruptures (and rupture variations, if they exist) to the remote cluster, in the <CyberShake root>/ruptures/Rupture_erf<ERF_ID> directory.  I recommend using Globus to do the directory transfer.
-# Create a list of all the rupture files which can be used to register the ruptures into the RC.  To do this, run the script in <CyberShake root>/software/RuptureCodes/utils/rupture_geom_file_list.py.  A sample invocation is <pre>./rupture_geom_file_list.py 49 8 gsiftp://bw-gridftp.ncsa.illinois.edu/ bluewaters /projects/sciteam/baln/CyberShake/ruptures/Ruptures_erf49/ bluewaters-e49-rv8.rls .</pre>
+# Create a list of all the rupture files which can be used to register the ruptures into the RC.  To do this, run the script in <CyberShake root>/software/RuptureCodes/utils/rupture_geom_file_list.py.  A sample invocation is <pre>./rupture_geom_file_list.py 49 8 gsiftp://bw-gridftp.ncsa.illinois.edu/ bluewaters /projects/sciteam/baln/CyberShake/ruptures/Ruptures_erf49/ bluewaters-e49-rv8.rls </pre>
-# If the rupture variations are also supplied in the ERF, you need to create a list of those as well.  For this, run the script <CyberShake root>/software/RuptureCodes/utils/RLSFileGen_UsingFind.pl.  A sample invocation is <pre>./RLSFileGen_UsingFind.pl /projects/sciteam/baln/CyberShake/ruptures/Ruptures_erf49/ gsiftp://bw-gridftp.ncsa.illinois.edu/ bluewaters 49 8 .</pre>
+# If the rupture variations are also supplied in the ERF, you need to create a list of those as well.  For this, run the script <CyberShake root>/software/RuptureCodes/utils/RLSFileGen_UsingFind.pl.  A sample invocation is <pre>./RLSFileGen_UsingFind.pl /projects/sciteam/baln/CyberShake/ruptures/Ruptures_erf49/ gsiftp://bw-gridftp.ncsa.illinois.edu/ bluewaters 49 8 </pre>
 # Copy the list(s) back to shock, to the /home/scec-02/cybershk/runs/config directory.

← Older revision		Revision as of 21:48, 27 September 2018
Line 27:		Line 27:

	# For each list file created in the previous step, run <pre>pegasus-rc-client -i <file></pre>		# For each list file created in the previous step, run <pre>pegasus-rc-client -i <file></pre>
		+
		+	This may take some time to run.

	=== Make changes to DAX generator ===		=== Make changes to DAX generator ===

@@ Line 11: / Line 11: @@
 # A list of ruptures (or rupture variations) with magnitudes and probabilities must be created externally, and added to the Ruptures table (and Rupture_Variations, if variations are created).
 # The CyberShake_Site_Ruptures table must be populated for each site we plan to compute curves for with the new ERF, so CyberShake knows which ruptures to include.
-# The Rupture_Variations table must be populated (ideally including hypocenter locations).  This can either be done by using a rupture generator to create and count rupture variations, or the ERF which already supplies rupture variations, such as RSQSim-generated ERFs.  Note that Rupture Variation ID 8 is used for rupture variations which come from the ERF directly, rather than being generated.
+# The Rupture_Variations table must be populated (ideally including hypocenter locations).  This can either be done by using a rupture generator to create and count rupture variations, or the ERF which already supplies rupture variations, such as RSQSim-generated ERFs.  Note that Rupture Variation Scenario ID 8 is used for rupture variations which come from the ERF directly, rather than being generated.
 === Stage ruptures ===

@@ Line 3: / Line 3: @@
 == New ERF ==
-To add a new ERF - at a high level - the database needs to know about it, the rupture files have to be registered in the RC so Pegasus can symlink them, and the right XML file needs to be used in creating curves.  Here are detailed instructions:
+To add a new ERF, the database needs to know about it, the rupture files have to be registered in the RC so Pegasus can symlink them, and the right XML file needs to be used in creating curves.  Here are detailed instructions:
 === Database modifications ===

@@ Line 26: / Line 26: @@
 The ruptures on the remote system must be registered in the [[CyberShake_Workflow_Framework#Replica_Catalog_.28RC.29 | Replica Catalog]] on shock.
-# For each list file created in the previous step, run <pre>pegasus-rc-client -i <file><pre>
+# For each list file created in the previous step, run <pre>pegasus-rc-client -i <file></pre>
 === Make changes to DAX generator ===
@@ Line 39: / Line 39: @@
 # Update the file on shock (run 'svn update dax-generator' from the /home/scec-02/cybershk/runs directory).  It will get compiled automatically when a workflow is created.
-You should now be ready to create new worklfows b
+You should now be ready to perform CyberShake runs with the new ERF.

← Older revision		Revision as of 18:01, 27 September 2018
Line 5:		Line 5:
	To add a new ERF, the following steps are required:		To add a new ERF, the following steps are required:

−	# A list of ruptures (or rupture variations) with magnitudes and probabilities must be created externally, and added to the Ruptures table (and ~~RuptureVariations~~, if variations are created) in the [[~~CyberShake_Data~~#~~CyberShake_database_overview~~\| ~~CyberShake database~~]].	+	=== Database modifications ===
		+
		+	# A new ERF ID should be added to the ERF_IDs table of the [[CyberShake_Data#CyberShake_database_overview \| CyberShake database]].
		+	# An entry for the Rupture Surface Resolution (either the grid spacing, in km, or the element area, in km^2) must be added to the ERF_Metadata table for the new ERF ID, as this is required.
		+	# A list of ruptures (or rupture variations) with magnitudes and probabilities must be created externally, and added to the Ruptures table (and Rupture_Variations, if variations are created).
		+	# The CyberShake_Site_Ruptures table must be populated for each site we plan to compute curves for with the new ERF, so CyberShake knows which ruptures to include.
		+	# The Rupture_Variations table must be populated (ideally including hypocenter locations). This can either be done by using a rupture generator to create and count rupture variations, or the ERF which already supplies rupture variations, such as RSQSim-generated ERFs.
		+
		+	=== Stage ruptures ===
		+
		+	A physical copy of all the ruptures of interest must be staged on the remote clusters we plan to calculate curves on. I recommend using Globus to do the directory transfer.
		+
		+	=== Register ruptures in the replica catalog (RC) ===
		+
		+	The ruptures on the remote system must be registered in the [[CyberShake_Workflow_Framework#Replica_Catalog_.28RC.29 \| Replica Catalog]] on shock.