毕业设计&课设-一个Java包，名义上构建在NetBeans中，允许在Mathwork的Simulink（R）和M等工.zip

// This file can be turned into XHTML using AsciiDoc DAVEtools 0.9.7 README ====================== Bruce Jackson, NASA Langley Research Center <bruce.jackson@nasa.gov> README Version 8, 2015-03-02 :TOC: Introduction ------------ DAVEtools is a Java package that can be used to operate on DAVE-ML models; these are XML files with a custom grammar specific to the exchange of dynamic model data, such as flight simulation physics models (see link:http://daveml.org[http://daveml.org]). The package is intended for command-line use as there is no GUI, but the ModelSweeper tool does use a graphical interface. use a graphical interface. Key features of DAVEtools: * NASA open-source code written in Java * Validates checkcases within a DAVE-ML models * Obtains information about a DAVE-ML model * Allows use of DAVE-ML models from within Matlab(R) * Converts a DAVE-ML model into a Simulink(R) model, with a validation script * Plots a 3-D response surface for any output, based on any two inputs in a DAVE-ML model Components ---------- DAVEtools includes three products in one +DAVEtools.jar+ file .DAVEtools.jar contains: DAVE:: Parses a DAVE-ML file (running any embedded verification tests) and creates a +Model+ object representing the model defined in the DAVE-ML source file. Also can be used to provide information about the model and set inputs/get outputs from the model. This class can be called from within the Mathworks Matlab(R) environment to allow use of a DAVE-ML model within the Matlab workspace. A demo script is available link:dave_demo.html[here]. DAVE2SL:: Generates a Matlab(R) script that, when executed in Mathwork's Simulink(R) environment, creates a Simulink realization of the provided DAVE-ML model. It also creates and runs a verification script, if the DAVE-ML model included checkcases. DAVE2OTIS:: Generates an OTIS4 input deck (*.dat) and scenario file (*.inl) DAVE2POST:: Generates appropriate POST II table (*.pos2) and model (*.f) files. ModelSweeper:: Provides a GUI-based tool to inspect the outputs of the DAVE-ML model by plotting a 3D response surface of any output with respect to a range of values for any two inputs (while holding other inputs at nominal values). Catalogs: Parsing/validating against a local copy of +DAVEfunc.dtd+ ------------------------------------------------------------------- One of the less attractive features of working with XML files is dealing with the appropriate Document Type Definition (DTD) or XML Schema Definition (XSD) files, which provide various XML utilities the rules of grammar for that type of XML file. DAVE-ML makes exclusive use of the older DTD schema for several reasons which are out-of-scope of this document. However, DTD rules are powerful enough to provide adequate validation of a DAVE-ML file. These rules are in the +DAVEfunc.dtd+, available for download from link:http://daveml.org/DTDs/index.html[this page]. This file should be placed somewhere convenient for you; you might consider putting it in a central +XML/DTD+ directory on your computer. Unfortunately, there is no clear consensus on where to place such local copies, and there are several competing mechanisms available to notify XML-based parsers (such as used by DAVEtool) where to find appropriate files. The one we recommend is link:http://www.oasis-open.org/committees/entity/spec-2001-08-06.html[XML Catalogs]. If you don't want to download the DTD and set up a catalog file, DAVEtools will use information found in the DAVE-ML model file (such as +F106.dml+) to try to fetch the latest DTD over the network at run-time. This is much slower than having a local copy of the DTD but it avoids having to manually download newer copies as the DAVE-ML specification evolves. If you don't have a network connection, the DAVEtools will still work but should advise you that the model was successfully parsed without validation. If you do want to do 'local' validation, after downloading +DAVEfunc.dtd+ somewhere convenient, you will also want to download the tarball +mathml2.tgz+ MathML2 DTD set from http://www.w3.org/Math/DTD/. The +mathml2.dtd+ has several related parts which need to be stored in a particular directory structure (shown later). Next, you need to define an *XML catalog* file which will tell DAVEtools where to find a local copy of these DTDs. In the example +catalog.xml+ file listing below, it is assumed that the DTDs have been stored in a +schemas+ subdirectory under the working directory: .Example +catalog.xml+ file .... <?xml version="1.0"?> <!-- commented out to prevent network access !DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd" --> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> <group prefer="public" xml:base="schemas"> <public publicId="-//AIAA//DTD for Flight Dynamic Models - Functions 2.0//EN" uri="DAVEfunc.dtd"/> <rewriteSystem systemIdStartString="http://www.w3.org/Math/DTD/" uri=""/> </group> </catalog> .... Continuing with this example, the working directory contents should be something like what is shown below. The working directory contains a model file, +F106_aero.dml+ and the +catalog.xml+ file, and a +schemas+ subdirectory, which is expanded below to show its contents. Note that all the files in +schemas/mathml2+ were extracted from the +mathml2.tgz+ tarball: .Example working directory structure .... F106_aero.dml catalog.xml schemas/ DAVEfunc.dtd mathml2/ html/ lat1.ent special.ent symbol.ent iso8879/ isoamsa.ent . . . isotech.ent iso9573-13/ isoamsa.ent . . . isotech.ent mathml/ mmlalias.ent mmlextra.ent mathml2-qname-1.mod mathml2.dtd .... Examples -------- Shown below are typical use cases for DAVEtools in working with any DAVE-ML model. The examples all use the aerodynamics model of the HL-20 lifting body, a concept vehicle studied in the 1980s and 1990s by NASA as a `space taxi.' This open-source aero model has been realized in DAVE-ML and is available on the link:http://daveml.org/examples/index.html#HL-20[examples page]). This database was used in an approach and landing simulation as described in link:http://dscb.larc.nasa.gov/DCBStaff/ebj/Papers/TM-107580.pdf[NASA TM 107580]. .Command aliases [NOTE] ===================================================================== For the following examples (and for general daily use) it is helpful to define these aliases in your +.cshrc+ or +.bashrc+ file: +alias *dave*="java -cp 'path_to/DAVEtools.jar' gov.nasa.daveml.dave.DAVE"+ + +alias *dave2sl*="java -cp _path_to/DAVEtools.jar_ gov.nasa.daveml.dave2sl.DAVE2SL"+ + +alias *dave2post*="java -cp _path_to/DAVEtools.jar_ gov.nasa.daveml.dave2post.DAVE2POST"+ + +alias *dave2otis*="java -cp _path_to/DAVEtools.jar_ gov.nasa.daveml.dave2otis.DAVE2OTIS"+ + +alias *sweep*="java -cp 'path_to/DAVEtools.jar' gov.nasa.daveml.sweeper.ModelSweeperUI"+ + ===================================================================== Simple help ~~~~~~~~~~~ ---- $ dave -h Usage: java DAVE [options] DAVE-ML_document where options is one or more of the following: --version (-v) print version number and exit --count (-c) count number of elements --debug (-d) generate debugging information --eval (-e) do prompted model I/O evaluation --list (-l) output text description to optional output file --internal (-i) show intermediate results in calcs and checkcases --no-checkcase (-x) ignore failing checkcases ---- Verify and count elements in a DAVE-ML file ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (the example HL-20 aero model is availabl