A list,

Based on MATLAB GUI barber shop queuing simulation system

Ii. Source code

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

% Last Modified by GUIDE v2. 0 15-Aug- 2020. 00:44:45

if nargin == 0  % LAUNCH GUI

	fig = openfig(mfilename,'reuse');

	% Use system color scheme for figure:
	set(fig,'Color',get(0.'defaultUicontrolBackgroundColor'));

	% 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 = lifashi_Callback(h, eventdata, handles, varargin)




% --------------------------------------------------------------------
function varargout = guke_Callback(h, eventdata, handles, varargin)




% --------------------------------------------------------------------
function varargout = pushbutton1_Callback(h, eventdata, handles, varargin)

ln=str2double(get(handles.lifashi,'string')); %a(j, I): the remaining time barber J was serving at minute I % C (I): the total number of customers in the barber shop % D (I): the number of customers waiting in the barber shop %S(j) : barber J's state,1Said busy,0Indicates idle % this program simulation from the first1At the end of the minute10The number of customers in the barber shop at the end of the minute, the state of the barber, etc. % Assume that the service of the barber to customers starts from the end of a minute. % Assume that the barber J has a higher priority than J +1;

c(1) =0; d(1) =0;
for j=1:ln 
    S(j)=0;
    a(j,1) =0;
end
Copy the code

3. Operation results

Fourth, note

Version: 2014 a