| Wiki Markup |
|---|
----
{toc}
----
h3. Background
To start EPHUS, one must invoke a _startup_ file at the MATLAB command line. The file is a MATLAB function file |
| Table of Contents |
|---|
Background
...
(i.e., .m extension), located in the current directory or somewhere on the user's MATLAB path. |
...
Every user/rig requires a customized startup file. The best way to create this file is to modify one of the supplied [example files|Startup Files], which are constantly maintained on this site. |
...
The startup files contain both _configuration_ and _application_ information. The vast majority of users only need to adjust the _configuration_ information, which |
...
resides in clearly demarcated sections of the startup |
...
Some power-users may find occasion to modify the application information within the startup file. This will not generally be supported, but is relatively straightforward.
This guide steps through a typical startup file: gephus.m. For completeness, both the configuration and application sections are described. Most users should ignore the latter sections.
...
file.
This guide steps through a typical startup file ([^gephus.m]). For completeness, both the _configuration_ and _application_ sections are described. Only power-users, however, should modify the _application_ sections, and limited support can be provided in this case.
{center} h5. [Download the file|^gephus.m]
_It is best to view the file in the MATLAB editor, for helpful syntax coloring_
h3. The Beginning
Here's the beginning of our startup file 'specimen':
{code}
function gephus
%% STARTUP BOILERPLATE
%Set up a wait bar to show the progress.
wb = waitbarWithCancel(0, 'Starting ephus...', 'Name', 'Loading software...');
pos = get(wb, 'Position');
pos(2) = pos(2) - pos(4);
set(wb, 'Position', pos);
{code}
The
h3. Device/Channel _Configuration_
h3. _Configuration_ Variables
h3. Program Startup (_Application_)
h3. User Fcns (_Application_)
h3. The End
h3. Final Comments
|