Visualization recipes - Revision history

Knarf: /* AHFinderdirect */

2015-11-10T09:46:38Z

‎AHFinderdirect

Knarf: /* AHFinderdirect */

2015-11-10T09:46:12Z

‎AHFinderdirect

Knarf at 09:44, 10 November 2015

2015-11-10T09:44:45Z

Hinder: /* Horizons */

2015-10-27T08:34:36Z

‎Horizons

Hinder at 08:32, 27 October 2015

2015-10-27T08:32:19Z

New page

====Horizons====

If one activates QuasiLocalMeasures, you can get each surface (which doesn't need to be an AH) output as VTK polygonal data, along with the various quantities that the thorn calculates, defined as fields on the surface. These can be then read by, e.g., VisIt. No postprocessing needed.

@@ Line 13: / Line 13: @@
 <pre>
 $ AH2xdmf.py --help
-Usage: /home/knarf/bin/AH2xdmf.py [filename]
+Usage: AH2xdmf.py [filename]
 Collect information about apparent horizon shape files within the current
 directory and store them in hdf5 files. This assumes that the filename

←Older revision		Revision as of 09:46, 10 November 2015
Line 10:		Line 10:

	Note: The script actually generates two files per horizon: an HDF5 file with the raw horizon data, and an .xml file with the meta-data (time steps, 6-patch system). Load the .xml file in visit, using the xdmf reader.		Note: The script actually generates two files per horizon: an HDF5 file with the raw horizon data, and an .xml file with the meta-data (time steps, 6-patch system). Load the .xml file in visit, using the xdmf reader.
		+
		+	<pre>
		+	$ AH2xdmf.py --help
		+	Usage: /home/knarf/bin/AH2xdmf.py [filename]
		+	Collect information about apparent horizon shape files within the current
		+	directory and store them in hdf5 files. This assumes that the filename
		+	scheme in AHFinderDirect (for ASCII output) has not been changed from the
		+	default one.
		+
		+	The optional argument [filename] specifies another hdf5 file from which
		+	timestep information will be read and used to create (if necessary dummy)
		+	horizons for all timesteps in that file also in the apparent horizon output
		+	files. The intend here is to allow visualization tools (like VisIt) to
		+	automatically combine time sliders opon opening the specified file and the
		+	created apparent horizon files.
		+
		+	The output files will be named AH_%d.[h5,xml], with %d being the number of each
		+	horizon. The .h5 files contain the raw shape information, while the .xml files
		+	describe its layout (and should be the one to open in a visualization tool).
		+	</pre>

←Older revision		Revision as of 08:34, 27 October 2015
Line 2:		Line 2:

	If one activates QuasiLocalMeasures, you can get each surface (which doesn't need to be an AH) output as VTK polygonal data, along with the various quantities that the thorn calculates, defined as fields on the surface. These can be then read by, e.g., VisIt. No postprocessing needed.		If one activates QuasiLocalMeasures, you can get each surface (which doesn't need to be an AH) output as VTK polygonal data, along with the various quantities that the thorn calculates, defined as fields on the surface. These can be then read by, e.g., VisIt. No postprocessing needed.
		+
		+	(Eloisa Bentivegna, http://lists.einsteintoolkit.org/pipermail/users/2015-October/004582.html)

@@ Line 1: / Line 1: @@
-====Horizons====
+=Horizons=
 If one activates QuasiLocalMeasures, you can get each surface (which doesn't need to be an AH) output as VTK polygonal data, along with the various quantities that the thorn calculates, defined as fields on the surface. These can be then read by, e.g., VisIt. No postprocessing needed.
 (Eloisa Bentivegna, http://lists.einsteintoolkit.org/pipermail/users/2015-October/004582.html)