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

More documents

Recommendations

Info

simulation and wind tunnel testing. DERIVID works in a fashion similar to NAVFIT, using a cost function to notify the user of the accuracy of the fit. The final main program, VERIFY, allows users to validate a state-space model found in DERIVID with new time history data in the time domain. Typically the validation employs flight data taken from a doublet maneuver as opposed to a frequency sweep. VERIFY will run the statespace model using the time history inputs and compare the model outputs to the measured outputs. This is an important step to provide confidence in the state-space solution. DERIVID and VERIFY use a combination of the screen interface and the prompt interface. There are 17 and 18 screens, respectively, that accept user input and a lengthy series of prompts that guide the user through the calculations of the state-space model. Due to this complexity they were excluded from the scope of the current feasibility project. 18
Chapter 3: Programming and Code Development The programming requirements set by the Army for this project included the development of a command-line interface for three main CIFER ® programs: FRESPID, MISOSA, and COMPOSITE, and an additional seven utilities: RMS, Bandwidth, Frequency Response Arithmetic, plotting, case listing, data storage and data retrieval. These programs constitute a “light” version of CIFER ® that takes the user through all the frequency response conditioning and allows assorted manipulation and analysis of the responses. The goal was to generate functional building blocks that had stand alone capability and upon which further development could take place. In addition to the command-line interface, development of a GUI interface was also required. The goal of the GUI development was to create a feasibility study to show how advances in GUIs could improve on the existing Curses interface. Thus, the development was focused on one main program, COMPOSITE. The primary concern was the layout and interface, thus once one program was shown to work as a GUI, others could be adapted fairly quickly. This chapter discusses the process of development of both new interfaces for CIFER ® and the major problems encountered during the development process. 3.1 Command-Line Development A function in MATLAB accepts a list of inputs, returns a list of outputs, and typically is called from a single line, often referred to as “command-line.” The key advantage of creating such an interface for CIFER ® is the ability to script multiple calls to the function. The scripting ability greatly reduces the amount of time needed to create and run the large numbers of CIFER ® cases typical of any detailed analysis. The error checking associated with the data entry process for 19
Page 1 and 2: CIFER ® -MATLAB Interfaces: Develo
Page 3 and 4: Approval Page TITLE: AUTHOR: CIFER
Page 5 and 6: Acknowledgements The author would l
Page 7 and 8: 4.4 ANALYSIS ON SHADOW 200 TUAV....
Page 9 and 10: Figure 4.21: Comparisons with Exact
Page 11 and 12: Chapter 1: Introduction The focus o
Page 13 and 14: 1.1.1 What CIFER ® Encompasses CIF
Page 15 and 16: Figure 1.3: Doublet Example (UAV Fl
Page 17 and 18: One almost universal concern with t
Page 19 and 20: involving handling qualities analys
Page 21 and 22: One key feature of frequency respon
Page 23 and 24: and high-frequency content is captu
Page 25 and 26: Thus the low-frequency content of l
Page 27: consistency by reconstructing respo
Page 31 and 32: interpret it, how to condition it,
Page 33 and 34: Figure 3.1: Name-value Pairs and St
Page 35 and 36: Figure 3.2: Percent Error Compariso
Page 37 and 38: command-line-based interface that r
Page 39 and 40: 3.2.1 Development Process The most
Page 41 and 42: The third screen is used to match w
Page 43 and 44: Chapter 4: Validation and Applicati
Page 45 and 46: Figure 4.2: SISO Mass-Spring-Damper
Page 47 and 48: 4.3 UH-60 Simulation The first in-d
Page 49 and 50: The differences between the two cal
Page 51 and 52: Table 4.3: Cutoff Frequency Results
Page 53 and 54: Two sets of data were used: one was
Page 55 and 56: Figure 4.14: Roll Angle to Rate Com
Page 57 and 58: The same checks were run on the fli
Page 59 and 60: Figure 4.20: Vertical Velocity Pert
Page 61 and 62: Figure 4.22: Aileron - Roll Rate Re
Page 63 and 64: CIFER ® offers a utility for analy
Page 65 and 66: La Length: Lm = [4.14] N τ a Time
Page 67 and 68: UAV might conceivably achieve bandw
Page 69 and 70: FRESPID and MISOSA have been create
Page 71 and 72: Bibliography Works Cited: 1.) Hamel
Page 73 and 74: Appendix A: Screen Layout Compariso
Page 75 and 76: New GUI Interface: Figure A6: MATLA
Page 77 and 78: Figure A10: MATLAB GUI: Final Scree
Page 79 and 80:
CIFER ® main programs The three ma
Page 81 and 82:
out_f = frespid('XVLATSWP',1); >> o
Page 83 and 84:
The variables that support screen 8
Page 85 and 86:
as input and up to five outputs to
Page 87 and 88:
All the information is displayed to
Page 89 and 90:
to either the linearized phase and
Page 91 and 92:
CIFER ® support utilities: Three f
Page 93 and 94:
Appendix C: Online Help for Main Pr
Page 95 and 96:
id.maxfft SCREEN 9 id.plotopt id.pl
Page 97 and 98:
[out] = composite('TEST',2,'casenam
Page 99 and 100:
misosa Structure fields are: casena
Page 101 and 102:
Function: cifhq Description: This f
Page 103 and 104:
the results will be displayed in th
Page 105 and 106:
in.source SCREEN 2 in.pminfrq in.pm
Page 107 and 108:
cifarith Structure fields are: name
Page 109 and 110:
and magnitude must be included. Oth
Page 111 and 112:
c_in.outputs(1) c_in.frcalc(1,1) c_
Page 113:
% Set up blank composite case c_in
show all

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?