run_check

Sumarize a model run with python, ultimately generating an html file with various plots, etc.

Command line usage (if any):

run_check.py root1 [root2 …]

run_check.py root1.pf [root2.pf …]

run_check -all

run_check -h

Description:

This routine performs basic checks on one or more python runs and creates an html file for each that is intended to provide a quick summary of a run.

The user can enter the runs to be tested from the command line, either in the form of a set of root names or .pf names. Wildcarding, e.g *.pf can be used. *.out.pf files will be ignored.

Alternatively to process all of the files in a directory, one can use the switch -all (which supercedes anything else).

In all cases the routine checks to see if the appropriate wind_save file exists before attempting to run.

-h delivers this documentation

Primary routines:

doit - processes a single file steer - processes the command line and calls doit for each file.

Notes:

Functions

check_completion(root)	Verify that the run actually completed and provide information about the timeing, from the .sig file
doit([root, outputfile])	Create a summary of a Python run, which will enough information that one can assess whether the run was successful
how_many_dimensions(filename)	Check whether a windsave file is one or two dimenaions
make_html(root, converge_plot, te_plot, ...)	Make an html file that collates all the results
plot_converged(root, converged, converging, ...)	Make a plot of the convergence statistics in the diag directroy
py_error(root)	Run py_error.py and capture the output to the screen
read_diag(root)	Get convergence and possibly other information from the diag file
steer(argv)	Process the command line
windsave2table(root)	Run windsave2table
xwindsave2table(root)	Run windsave2table with the same version number (not commit) as the .spec files indicate was written)