Pyclaw Utility Module¶
pyclaw.util¶
Pyclaw utility methods
| Authors: | Kyle T. Mandli (2008-08-07) Initial version Randall J. LeVeque (2009-01-01) Added svn revision Kyle T. Mandli (2009-03-01) Added topo file utilities |
|---|
- class pyclaw.util.FrameCounter¶
Simple frame counter
Simple frame counter to keep track of current frame number. This can also be used to keep multiple runs frames seperated by having multiple counters at once.
Initializes to 0
- get_counter()¶
Get the current frame number
- increment()¶
Increment the counter by one
- reset_counter()¶
Reset the counter to 0
- set_counter(new_frame_num)¶
Set the counter to new_frame_num
- pyclaw.util.compile_library(source_list, module_name, interface_functions=[], local_path='./', library_path='./', f2py_flags='', FC=None, FFLAGS=None, recompile=False, clean=False)¶
Compiles and wraps fortran source into a callable module in python.
This function uses f2py to create an interface from python to the fortran sources in source_list. The source_list can either be a list of names of source files in which case compile_library will search for the file in local_path and then in library_path. If a path is given, the file will be checked to see if it exists, if not it will look for the file in the above resolution order. If any source file is not found, an IOException is raised.
The list interface_functions allows the user to specify which fortran functions are actually available to python. The interface functions are assumed to be in the file with their name, i.e. claw1 is located in ‘claw1.f95’ or ‘claw1.f’.
The interface from fortran may be different than the original function call in fortran so the user should make sure to check the automatically created doc string for the fortran module for proper use.
Source files will not be recompiled if they have not been changed.
One set of options of note is for enabling OpenMP, it requires the usual fortran flags but the OpenMP library also must be compiled in, this is done with the flag -lgomp. The call to compile_library would then be:
compile_library(src,module_name,f2py_flags=’-lgomp’,FFLAGS=’-fopenmp’)
For complete optimization use:
FFLAGS=’-O3 -fopenmp -funroll-loops -finline-functions -fdefault-real-8’
Input : - source_list - (list of strings) List of source files, if these are just names of the source files, i.e. ‘bc1.f’ then they will be searched for in the default source resolution order, if an explicit path is given, i.e. ‘./bc1.f’, then the function will use that source if it can find it.
- module_name - (string) Name of the resulting module
- interface_functions - (list of strings) List of function names to provide access to, if empty, all functions are accessible to python. Defaults to [].
- local_path - (string) The base path for source resolution, defaults to ‘./’.
- library_path - (string) The library path for source resolution, defaults to ‘./’.
- f2py_flags - (string) f2py flags to be passed
- FC - (string) Override the environment variable FC and use it to compile, note that this does not replace the compiler that f2py uses, only the object file compilation (functions that do not have interfaces)
- FFLAGS - (string) Override the environment variable FFLAGS and pass them to the fortran compiler
- recompile - (bool) Force recompilation of the library, defaults to False
- clean - (bool) Force a clean build of all source files
- pyclaw.util.construct_function_handle(path, function_name=None)¶
Constructs a function handle from the file at path.
This function will attempt to construct a function handle from the python file at path.
Input : - path - (string) Path to the file containing the function
- function_name - (string) Name of the function defined in the file that the handle will point to. Defaults to the same name as the file without the extension.
Output : - (func) Function handle to the constructed function, None if this has failed.
- pyclaw.util.convert_fort_double_to_float(number)¶
Converts a fortran format double to a float
Converts a fortran format double to a python float.
number: is a string representation of the double. Number should be of the form “1.0d0”
- pyclaw.util.create_topo_func(loc, verbose=False)¶
Given a set of (x,z) locations, create a lambda function
Create a lambda function that when evaluated will give the topgraphy height at the point (x,y).
Example : >>> f = create_topo_profile_func(loc) >>> b = f(x,y)
Input : loc (list) - Create a topography file with the profile denoted by the tuples inside of loc. A sample set of points are shown below. Note that the first value of the list is the x location and the second is the height of the topography.
- pyclaw.util.read_data_line(inputfile, num_entries=1, type='float')¶
Read data a single line from an input file
Reads one line from an input file and returns an array of values
inputfile: a file pointer to an open file object num_entries: number of entries that should be read, defaults to only 1 type: Type of the values to be read in, they all most be the same type
This function will return either a single value or an array of values depending on if num_entries > 1
- pyclaw.util.read_topo_file(path, topo_type, verbose=False)¶
Read in a topography file from path of type topo_type.
This utility function is for use with GeoClaw. Please to refer to GeoClaw’s documentation for more details.
Input : - path - (string) Path to topography file
- topo_type - (int) Type of topography file, see write_topo_file() for valid types.
- verbose - (bool) Verbose output, default = False
Output : - (ndarray(:)) X-Coordinate array
- (ndarray(:)) Y-Coordinate array
- (ndarray(:,:)) Z values stored in topography file
- pyclaw.util.svn_revision(dir='CLAW')¶
Determine the svn revision number of the version of code being used. If dir=”CLAW” it returns the revision number of the claw directory. This only checks the top most level and assumes this is accurate.
- pyclaw.util.write_topo_file(path, z_func, nx, ny, lower_coord, upper_coord, topo_type=1)¶
Write out a topo1 file to the file at path.
This utility function is for use with GeoClaw. Please to refer to GeoClaw’s documentation for more details.
Input : - path - (string) Path to file
- z_func - (func) Funtion determining z values (depth or topography)
- nx - (int) Number of x points
- ny - (int) Number of y points
- lower_coord - (float) Lower left coordinate of the domain
- upper_coord - (float) Upper right coordinate of the domain
- topo_type - (int) Type of topography file to write, can be one of the following types.
Topo Type Description 1 Standard GIS format: 3 columns with longitude, latitude, and z in meters or x, y, z in one row 2 One z value per line with header 3 One row of z values per line with header Header format is
xxxx ncols xxxx nrows xxxx xllcorner xxxx yllcorner xxxx cellsize xxxx NODATA_value
z values are positive for topography, negative for bathymetry.
Values are ordered from upper left corner, moving east across each row (y fixed, x increasing) and then south (y decreasing).
The region covered by this file should be refined to at least minlevel and at most maxlevel over the time interval specified.
If a point is covered by several regions, the largest values of minlevel and maxlevel from all such regions are used.
Refinement may also be forced or allowed by the minlevel and maxlevel parameters for the regions specified in setregions.data or setmovetopo.data.
At points that lie far from shore (where h is greater than depthdeep), refinement is only allowed to level maxleveldeep. These parameters are set in setgeo.data.
In setting topography in a computation, the finest topography available will be used for each grid cell. If a grid cells lies partially but not entirely in a topo file then a coarser topo file will be used for the remainder of the cell (with area-weighted averaging).
The order of topo files in the list above should not matter.
