shiyan4.m

基于matlab实现窗函数设计滤波器

function varargout = shiyan4(varargin)
% SHIYAN4 Application M-file for shiyan4.fig
%    FIG = SHIYAN4 launch shiyan4 GUI.
%    SHIYAN4('callback_name', ...) invoke the named callback.

% Last Modified by GUIDE v2.0 06-May-2003 08:32:48

if nargin == 0  % LAUNCH GUI

	fig = openfig(mfilename,'reuse');

	% Generate a structure of handles to pass to callbacks, and store it. 
	handles = guihandles(fig);
	guidata(fig, handles);

	if nargout > 0
		varargout{1} = fig;
	end

elseif ischar(varargin{1}) % INVOKE NAMED SUBFUNCTION OR CALLBACK

	try
		if (nargout)
			[varargout{1:nargout}] = feval(varargin{:}); % FEVAL switchyard
		else
			feval(varargin{:}); % FEVAL switchyard
		end
	catch
		disp(lasterr);
	end

end


%| ABOUT CALLBACKS:
%| GUIDE automatically appends subfunction prototypes to this file, and 
%| sets objects' callback properties to call them through the FEVAL 
%| switchyard above. This comment describes that mechanism.
%|
%| Each callback subfunction declaration has the following form:
%| <SUBFUNCTION_NAME>(H, EVENTDATA, HANDLES, VARARGIN)
%|
%| The subfunction name is composed using the object's Tag and the 
%| callback type separated by '_', e.g. 'slider2_Callback',
%| 'figure1_CloseRequestFcn', 'axis1_ButtondownFcn'.
%|
%| H is the callback object's handle (obtained using GCBO).
%|
%| EVENTDATA is empty, but reserved for future use.
%|
%| HANDLES is a structure containing handles of components in GUI using
%| tags as fieldnames, e.g. handles.figure1, handles.slider2. This
%| structure is created at GUI startup using GUIHANDLES and stored in
%| the figure's application data using GUIDATA. A copy of the structure
%| is passed to each callback.  You can store additional information in
%| this structure at GUI startup, and you can change the structure
%| during callbacks.  Call guidata(h, handles) after changing your
%| copy to replace the stored original so that subsequent callbacks see
%| the updates. Type "help guihandles" and "help guidata" for more
%| information.
%|
%| VARARGIN contains any extra arguments you have passed to the
%| callback. Specify the extra arguments by editing the callback
%| property in the inspector. By default, GUIDE sets the property to:
%| <MFILENAME>('<SUBFUNCTION_NAME>', gcbo, [], guidata(gcbo))
%| Add any extra arguments after the last argument, before the final
%| closing parenthesis.

% --------------------------------------------------------------------
function varargout = pushbutton1_Callback(h, eventdata, handles, varargin)
N=get(handles.T_edit1,'string'); N=str2num(N);
w=get(handles.T_edit2,'string'); w=str2num(w);
B=boxcar(N);
string=['Boxcar','N=',num2str(N)];
e_printf(N,B,w,string);
% --------------------------------------------------------------------
function varargout = pushbutton2_Callback(h, eventdata, handles, varargin)
N=get(handles.T_edit1,'string'); N=str2num(N);
w=get(handles.T_edit2,'string'); w=str2num(w);
B=hanning(N);
string=['Hanning','N=',num2str(N)];
e_printf(N,B,w,string)
% --------------------------------------------------------------------
function varargout = pushbutton4_Callback(h, eventdata, handles, varargin)
N=get(handles.T_edit1,'string'); N=str2num(N);
w=get(handles.T_edit2,'string'); w=str2num(w);
B=blackman(N);
string=['Blackman','N=',num2str(N)];
e_printf(N,B,w,string);
% --------------------------------------------------------------------
function varargout = pushbutton3_Callback(h, eventdata, handles, varargin)
N=get(handles.T_edit1,'string'); N=str2num(N);
w=get(handles.T_edit2,'string'); w=str2num(w);
B=hamming(N);
string=['Hamming','N=',num2str(N)];
e_printf(N,B,w,string);