Difference between revisions of "Visualization of simulation results"

From Einstein Toolkit Documentation
Jump to: navigation, search
 
Line 1: Line 1:
The current state of people producing quick-and-dirty, overview-like visualizations from their running and run simulations seems to be that everyone has their own scripts/tools, usually just barely doing the specific task they are designed to do. It would be beneficial to have a set of common tools helping with at least some parts of this process of a) retrieving parts of the files, and b) producing some overview of the state of a simulation. To get this started, everyone interested is asked to shortly describe below what they currently do in that respect.
+
The current state of people producing quick-and-dirty, overview-like visualizations from their running and run simulations seems to be that everyone has their own scripts/tools, usually just barely doing the specific task they are designed to do. It would be beneficial to have a set of common tools helping with at least some parts of this process of a) retrieving parts of the files, and b) producing some overview of the state of a simulation. The task in question is not to create high-quality plots for e.g. publications, but more a jobsitting/debugging kind of overview.
 +
 
 +
To get this started, everyone interested is asked to shortly describe below what they currently do in that respect.
 +
 
 +
Frank Löffler: rsync (smaller) files by hand, use gnuplot/ygraph/VisIt to look at current results, often using e.g. scripts for
 +
              plotting multiple things with gnuplot

Revision as of 17:01, 31 January 2011

The current state of people producing quick-and-dirty, overview-like visualizations from their running and run simulations seems to be that everyone has their own scripts/tools, usually just barely doing the specific task they are designed to do. It would be beneficial to have a set of common tools helping with at least some parts of this process of a) retrieving parts of the files, and b) producing some overview of the state of a simulation. The task in question is not to create high-quality plots for e.g. publications, but more a jobsitting/debugging kind of overview.

To get this started, everyone interested is asked to shortly describe below what they currently do in that respect.

Frank Löffler: rsync (smaller) files by hand, use gnuplot/ygraph/VisIt to look at current results, often using e.g. scripts for

              plotting multiple things with gnuplot