Skip to main content

Currently Skimming:


Pages 9-21

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 9...
... 2-1 CHAPTER 2. BUILD REQUIREMENTS In this section, requirements of the six Builds are discussed in detail.
From page 10...
... 2-2 2.3. Details of Each Build As previously stated, each Build will be a usable tool, with an accompanying technical manual and user guide.
From page 11...
... 2-3 Build 1. Output post processor.
From page 12...
... 2-4 The other vital testing is to demonstrate the capabilities of the tool using actual case studies, which applied existing single mode models. This testing would help address ease of use of tool versus multiple runs of single mode models and the value of assessing the combined effects from all modes.
From page 13...
... 2-5 Build 3. 1 st generation AEDT-based tool.
From page 14...
... 2-6 databases would be open to the user and the more advanced users' could write their own tools to write directly to a study specific database and avoid the GUI. In such cases, it is recommended that preapproval of any developed tools by the lead agency during the analysis would be a prerequisite.
From page 15...
... 2-7 Build 4. 2nd The next large change in terms of effort is the expansion of the environmental impact and economic analysis tools in the APMT assumed to be completed by this time, which work in conjunction with AEDT (see Figure 1)
From page 16...
... 2-8 All architecture and software updates should account for the fact that later Builds will be focused on simulation modeling. Any programming decisions that could directly help the transition to simulation modeling should be considered and implemented if resources permit.
From page 17...
... 2-9 comparison to "gold standard" measurement data should be conducted for any source for which the processing is changed in any way. The level of risk for this Build is moderate.
From page 18...
... 2-10 analyses should be realized. A rule base to combine the outputs will be required because of differences in sources, metrics, and modal regulations.
From page 19...
... 2-11 Technical methodology testing. Regardless of the test method chosen it must be verified that methodologies have been implemented correctly and provide accurate results.
From page 20...
... 2-12 could well change so that the PC is only used as a control point to receive input and return output. Reasons for this change would include program security, the large run times that would be expected on PCs, and the large data bases and model base that would result when the models are combined.
From page 21...
... 2-13 would be much less work and effort than originally required for model development. The second option would not require any changes to Build 1 or additional resources.

Key Terms



This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More information on Chapter Skim is available.