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

frespid('XVLATSWP',3);
Job file: /usr/cifer/jobs/FRE_XVLATSWP.COM.01 submitted
Waiting for batch to finish...
Batch completed.
The log file is:/usr/cifer/jobs/FRE_XVLATSWP.OUT.01
No error detected.
>> misosa('XVLATSWP',3);
>> composite('XVLATSWP',3);
The example below will take the XVLATSWP case, copy it to TEST and then run it as a batch
job all with a single command. The batch command always saves the case before it sends it to the
batch job. To verify the name change was correct, the structure, which will contain information
for TEST, is returned.
>> out_f = frespid('XVLATSWP',3,'casename','TEST','caseout','TEST');
frespid:
This section contains information specific to the frespid function and will primarily cover the
mechanics that mimic the functionality of FRESPID screens 7 and 8: conditioning and
windowing of data.
Data conditioning in screen 7 is handled with two fields in the frespid structure. The first field,
‘conditioning,’ contains two rows; the first row stores a flag for the type of conditioning desired
and the second row stores the value. The convention is that ‘1’ denotes expansion of data, ‘2’
denotes decimation, and ‘3’ denotes filtering. The second field, ’condunit,’ contains the units to
use in the case of filtering. The example below illustrates these variables.
>> in
>> in.conditioning(1:2,1:2)
= frespid;
= [3, 2; 4, 25];
>> in.condunit(1) = 'Hz';
The data in the example will be filtered at 4 Hertz and decimated to 25 Hertz. These operations
are lumped into one somewhat ungainly variable because of how CIFER ® internally processes the
data. The default value for ‘condunit’ is Hertz so it need not be specified unless Radians or nondimensional
values are used. When returning conditioning output from CIFER ® to MATLAB, the
function also defaults the units to Hertz. If cases created using conditioning are opened in
CIFER ® , there may appear to be a small error in the ten or hundred thousandth decimal place.
This is due to MATLAB using double precision while Fortran uses a combination of precisions.
Numerous checks have verified that the end results are the same.
72