机械毕业设计英文外文翻译4ADVISOR 使用说明

附录

ADVISOR Documentation

3.1 ADVISOR file structure

3.1.1 File interactions & data flow

The above schematic represents data flow in the ADVISOR file system. The four main agent types are:

◆Input Scripts define variables in the workspace and/or call other input

scripts. An example is MC_PM32.M.

◆Block Diagrams are Simulink files containing the equations used to

compute outputs such as fuel use from inputs such as an engine map.

They are the models. One example is BD_PAR.MDL.

◆Output Scripts post process the model outputs by querying the

workspace. These may include plotting routines or error checking

routines. chkoutputs.m is an example.

◆Control Scripts may both develop inputs and process outputs. Examples

include the ADVISOR GUI and optimization routines.

3.1.2 File locations

The main ADVISOR directory (e.g. c:\ADVISOR or c:\Program Files\ADVISOR) contains several sub directories. Among these are the data, GUI, and models directories that contain the corresponding files.

3.1.3 File naming conventions

All model and data files use a prefix followed by an underscore (‘_’) that is the same as the prefix used for (nearly all of) the variables it defines, which in turn is in pointy brackets (<>) at the end of the Simulink block in which those variables are used. Here are ADVISOR’s c omponent file types:

ACC_*.M Accessory load files

CYC_*.M Driving cycle files, which define variables starting with cyc_, used in the block labeled

ESS_*.M Energy storage system data files, which likewise define variables starting with ess_, used in the block labeled

EX_*.M Exhaust after treatment files (such as catalysts)

FC_*.M Fuel converter data files

TX_*.M Transmission data files (these include gearbox-gb and final drive-fd variables)

GC_*.M Generator/controller data files

MC_*.M Motor/controller data files

PTC_*.M Powertrain control data files, which define engine control, clutch control, and hybrid control strategy variables starting with vc_ and cs_, used in blocks labeled and

TC_*.M Torque coupler data files

VEH_*.M Vehicle data files

WH_*.M Wheel/axle data files

In addition to the above component data files, there is one other type that

use prefixes:

BD_*.MDL Simulink block diagrams (models)

All filenames that include prefixes are entirely in capital letters to avoid confusion with variable names, which are entirely in lower-case letters.

3.1.4 Adding files to ADVISOR

The easiest way to add a particular kind of file to ADVISOR is to modify an existing file of that kind and save it with a new file name, entirely in capital letters, in the appropriate ADVISOR directory. This will ensure that all variables necessary to fully define the particular component will be included in your new file. For adding vehicle component or drive cycle files, clicking the pushbutton in the graphical user interface brings up a window to guide the process.

3.1.5 Inspecting input files

Component files and nearly all other files in ADVISOR are text files (the exceptions are mat files, which contain Matlab-specific data), and can be viewed and edited in any text editor. A fixed pitch font helps. We recommend using the Matlab editor/debugger packaged with Matlab 5.3. Additionally, text files can be viewed in the Matlab command window by entering type filename at the MATLAB command line.

3.1.6 Deleting files from ADVISOR‟s database

Files can be removed from ADVISOR by either deleting them using your operating system or by entering the following at the Matlab command line: !rm filename