CIFER®-MATLAB Interfaces: Development and ... - Cal Poly

CIFER ® main programs
The three main CIFER ® -MATLAB interface functions are designed to give users the
functionality of the CIFER ® programs FRESPID, MISOSA and COMPOSITE by making calls
from the MATLAB workspace. All the functions are structured in the same manner with two
required inputs. The first input is either the name of the desired CIFER ® case or a MATLAB
structure that contains information representing a CIFER ® case. The second input is the flag to
execute a particular command on that case. The commands that can be performed are to open a
case, save data to a case or run a case as a batch job.
CIFER ® # CIFER ® Program MATLAB Function
1 FRESPID frespid
2 MISOSA misosa
3 COMPOSITE composite
To facilitate the organization of information that goes into a CIFER ® case, MATLAB structures
are used to store case data. The fields in these structures correlate to the field entries of the
CIFER ® screen interface. The MATLAB interface has optional inputs that allow users to specify
values for a particular field using name-value pairs. This allows the user to modify parts of the
structure without dealing with the entire structure. Invoking the ‘help functionname’ command
from MATLAB will display examples of using each function as well as a detailed list of the
CIFER ® information each field stores. The contents of these help commands can also be found in
Appendix C.
CIFER ® should be set to the database to be used (by selecting the appropriate SIFDEF file) prior
to using these MATLAB functions. If the database is changed by changing the SIFDEF file,
MATLAB must be restarted.
Features common to all three main programs:
The structures for each of the programs contain many fields, thus the functions have been set up
to do as much of the work of filling the fields in as possible for the user. Each function can be
called with no inputs or outputs to return a list of what type of data is contained in each field;
integers, cell arrays, scalar arrays, etc. The default value for each field is also specified in this
call. This information can also be found in Appendix D. Users can initialize a mostly empty
69