Visualizing AWP-ODC Output - Revision history

Scottcal at 22:15, 23 February 2026

2026-02-23T22:15:28Z

Scottcal: /* Create traces */

2018-05-01T04:05:04Z

Create traces

Scottcal: /* Create movie */

2018-05-01T03:51:49Z

Create movie

Scottcal: /* Create series of snapshots */

2018-04-30T21:33:32Z

Create series of snapshots

Scottcal: /* Save state */

2018-04-30T21:32:44Z

Save state

Scottcal at 19:57, 30 April 2018

2018-04-30T19:57:50Z

Scottcal: /* Modify visuals */

2018-04-30T19:53:16Z

Modify visuals

Scottcal: /* Modify visuals */

2018-04-30T19:51:56Z

Modify visuals

Scottcal: /* Load datasets */

2018-04-30T19:38:32Z

Load datasets

Scottcal: /* Load datasets */

2018-04-30T19:27:39Z

Load datasets

@@ Line 17: / Line 17: @@
 Once the simulation is complete, we must create a configuration file which tells Paraview how the velocity data is laid out in memory.
-For this, run the script [http://source.usc.edu/svn/cybershake/import/trunk/AWP-ODC/visualizer/create_timeseries_file.py create_timeseries_file.py].
+For this, run the script [https://github.com/SCECcode/cybershake-core/blob/main/Utils/visualizer/create_timeseries_file.py create_timeseries_file.py].
 <pre>
 Usage: ./create_timeseries_file.py <X dim in output> <Y dim in output> <grid decimation> <NT in sim> <DT of sim> <NTISKP> <timesteps output per file> <prefix> <output file>
@@ Line 28: / Line 28: @@
 Often, other visual references are needed to make the visualization meaningful.  The approach outlined uses a Cartesian grid projection to display the velocity results.  This means that to display other data, we have to convert the data from (lat, lon) into (X index, Y index).
-To do this, use the code get_grid_values.c, in https://source.usc.edu/svn/cybershake/import/trunk/PreCVM/GenGrid_py/src/get_grid_values.c .  It takes a path to a gridfile generated from PreCVM; the modellat, modellon, and modelrot; an input CSV file in lat,lon format; a path to the output file; the grid spacing; and the xshift and yshift from the model_params file.  geoproj should always be set to 1, which is Rob's great circle projection.  Here's a sample invocation:
+To do this, use the code get_grid_values.c, in https://github.com/SCECcode/cybershake-core/blob/main/PreCVM/GenGrid_py/src/get_grid_values.c .  It takes a path to a gridfile generated from PreCVM; the modellat, modellon, and modelrot; an input CSV file in lat,lon format; a path to the output file; the grid spacing; and the xshift and yshift from the model_params file.  geoproj should always be set to 1, which is Rob's great circle projection.  Here's a sample invocation:
 <pre>
@@ Line 34: / Line 34: @@
 </pre>
-The directory http://source.usc.edu/svn/cybershake/import/trunk/AWP-ODC/visualizer/ contains trace files for California, CCA, USGS, and cvms4/cvms4.26/cvms5 models in lat,lon format, ready for use with get_grid_values.
+The directory https://github.com/SCECcode/cybershake-core/blob/main/Utils/visualizer/ contains trace files for California, CCA, USGS, and cvms4/cvms4.26/cvms5 models in lat,lon format, ready for use with get_grid_values.
 == Use local Paraview to connect to remote nodes ==

@@ Line 28: / Line 28: @@
 Often, other visual references are needed to make the visualization meaningful.  The approach outlined uses a Cartesian grid projection to display the velocity results.  This means that to display other data, we have to convert the data from (lat, lon) into (X index, Y index).
-To do this, use the code get_grid_values.c .
+To do this, use the code get_grid_values.c, in https://source.usc.edu/svn/cybershake/import/trunk/PreCVM/GenGrid_py/src/get_grid_values.c .  It takes a path to a gridfile generated from PreCVM; the modellat, modellon, and modelrot; an input CSV file in lat,lon format; a path to the output file; the grid spacing; and the xshift and yshift from the model_params file.  geoproj should always be set to 1, which is Rob's great circle projection.  Here's a sample invocation:
 <pre>
-</pre>
+The directory http://source.usc.edu/svn/cybershake/import/trunk/AWP-ODC/visualizer/ contains trace files for California, CCA, USGS, and cvms4/cvms4.26/cvms5 models in lat,lon format, ready for use with get_grid_values.
 == Use local Paraview to connect to remote nodes ==

← Older revision		Revision as of 03:51, 1 May 2018
Line 111:		Line 111:

	== Create movie ==		== Create movie ==
		+
		+	On Linux, you can use ffmpeg to string together the PNGs to create a movie, with a command like:
		+	ffmpeg -framerate <fps> -i fileprefix.%04d.png <output movie.mp4>

@@ Line 108: / Line 108: @@
 '''If the connection terminates in the middle, or your local machine goes to sleep, you may end up with rendered frames in which the content wasn't updated.  Check your last frames to be sure they have the correct timestamp.'''
-I think the speed of rendering is a function of your internet connection, the number of remote nodes, and the image size.  It typically takes me 90-120 minutes to render a 2000-timestep animation at ~1280x800.
+I think the speed of rendering is a function of your internet connection, the number of remote nodes, and the image size.  It typically takes me 90-120 minutes to render a 2000-timestep animation at ~1280x800.  I use PNG files.
 == Create movie ==

← Older revision		Revision as of 21:32, 30 April 2018
Line 99:		Line 99:

	Before starting your animation, save a state file. That way, if there are any issues, you don't have to reload everything again. Go to File->Save State.		Before starting your animation, save a state file. That way, if there are any issues, you don't have to reload everything again. Go to File->Save State.
		+
		+	In the future, you should reconnect before you try to load it. It may take 15-20 seconds to load once you confirm the file paths.

	== Create series of snapshots ==		== Create series of snapshots ==

@@ Line 96: / Line 96: @@
 If you want to alter the color legend, click on the 'Edit Color Legend Parameters' button, near the top right of the Color Map Editor.  It's the button with an 'e' on it.
-== Create series of PNGs ==
+== Save state ==
 == Create movie ==

@@ Line 91: / Line 91: @@
 #If you want to change the color scheme, click on the 'Choose Preset' button in the Color Map Editor on the right.  It's the one with a heart on it.  Select a new color scheme.
 #If you want to alter how quickly the color changes from neutral to red or blue, you can click on the horizontal bar (not the triangle part, that controls opacity) to add new reference points.  Then, you can edit the 'Color transfer function values' table to set new R,G,and B values for it.
 == Create series of PNGs ==

@@ Line 71: / Line 71: @@
 == Modify visuals ==
 === Add timestamp ===
 === Change plot colors ===
 == Create series of PNGs ==

@@ Line 46: / Line 46: @@
 === Velocity data ===
-To load velocity data, go to File->Open and select the XDMF file you previously made.  It will appear in the 'Pipeline Browser' window in the upper left.  You may need to click on the eye next to it to get it to display. Additionally, the data is rendered on the Y/Z plane (there is a reason I had to set it up this way, but now I forget why), so click on the '-X' icon to the right of the Slice pull-down in the toolbar.  You should see the rectangle defined by your simulation region.  You can change the timestep you're looking at by changing the value in the
+To load velocity data, go to File->Open and select the XDMF file you previously made.  It will appear in the 'Pipeline Browser' window in the upper left.  You may need to click on the eye next to it to get it to display. Additionally, the data is rendered on the Y/Z plane (there is a reason I had to set it up this way, but now I forget why), so click on the '-X' icon to the right of the Slice pull-down in the toolbar.  You should see the rectangle defined by your simulation region.  You can change the timestep you're looking at by changing the value in the text box to the right of "Time:".
-=== Traces ===
+Repeat this until all your traces have been loaded.
 == Modify visuals ==

← Older revision		Revision as of 19:27, 30 April 2018
Line 42:		Line 42:
	== Load datasets ==		== Load datasets ==

		+	Once the job starts on Titan, you can begin loading data.

	=== Velocity data ===		=== Velocity data ===
		+
		+	To load velocity data, go to File->Open and select the XDMF file you previously made. It will appear in the 'Pipeline Browser' window in the upper left. You may need to click on the eye next to it to get it to display. Additionally, the data is rendered on the Y/Z plane (there is a reason I had to set it up this way, but now I forget why), so click on the '-X' icon to the right of the Slice pull-down in the toolbar. You should see the rectangle defined by your simulation region. You can change the timestep you're looking at by changing the value in the