series_filter(display) Display Classes series_filter(display)
NAME
series_filter - ordered list of filters sharing common
display_data
DESCRIPTION
series_filter takes a list of filter classes, instantiates
each, and sends its input display data through each filter, while having them all share a common data_out. This
does not add any specific functionality to what is already
available by linking filter objects together via "filter_n
data_in= filter_n-1", but instead saves storage space for
all that instances of display_data that would otherwise be
created. It also relieves the user from having to create
instances of all the filters. The user need only specify
the list of filter classes.
SUPERCLASS
filter
INSTANCE VARIABLES
num_filters
The number of filters in the filter list (read-
only)
current_filter
The filter that subsequent messages will be redirected to (write only)
MESSAGES
generate_data!
Takes its data_in, filters it through each of the
filters in the filter list, and leaves the result
in its data_out.
filters=
Takes a list of filter classes to be used to filter
the data. The classes are then instantiated. If
class instances are supplied, an error message is
printed to stderr and the instance's class is used
to create a new instance.
filters?
Returns the list of filter classes
num_filters?
Returns the number of filter classes in the filter
list
@ Takes one numeric argument between 0 and
num_filters. Specifies the filter that future messages (until end_of_message) are forwarded to. "0"
causes future messages to be received by the
series_filter instance. This allows modifying the
instance variables of the filter instances created
by the series filter.
EXAMPLE
grid_geometry new: case1_geo
data_in=case1_gridset01
extent=(15,15,1,18,1,16);
series_filter new:sf1
filters=(warp_scalar,contour_filter,ribbon_filter)
@1 scale_factor=100
@2 range=(.01,.03)
num_divisions=10
@3 scale_factor=.20
@0 data_in=case1_geo;
surface new: s2
range=(.01,.03)
data_in=sf1;
SEE ALSO
filter, ribbon_filter, warp_scalar, contour_filter
Please send comments and suggestions toconsult@rpi.edu