DOCSLIB.ORG

SSF) Collection Document

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
SSF) Collection Document Clouds and the Earth's Radiant Energy System (CERES) Data Management System Single Satellite Footprint TOA/Surface Fluxes and Clouds (SSF) Collection Document Release 2 Version 1 Primary Authors Erika B. Geier, Richard N. Green, David P. Kratz, Patrick Minnis NASA Langley Research Center Climate Science Branch Science Directorate Hampton, VA 23681-2199 Walt F. Miller, Sandra K. Nolan, Carla B. Franklin Science Applications International Corporation (SAIC) One Enterprise Parkway, Suite 300 Hampton, VA 23666 NASA Langley Research Center Climate Science Branch Science Directorate 21 Langley Boulevard Hampton, VA 23681-2199 March 2003 DRAFT SSF Collection Guide 6/19/2013 Document Revision Record The Document Revision Record contains information pertaining to approved document changes. The table lists the date the Software Configuration Change Request (SCCR) was approved, the Release and Version Number, the SCCR number, a short description of the revision, and the revised sections. The document authors are listed on the cover. The Head of the CERES Data Management Team approves or disapproves the requested changes based on recommendations of the Configuration Control Board. Document Revision Record SCCR Release/ SCCR Section(s) Approval Version Description of Revision Number Affected Date Number 06/19/99 R1V1 xxxx • Initial draft document release for team review. All 01/09/01 R1V2 xxxx • Draft Document release for TRMM Edition1 All SSF. xxxx R1V3 xxxx • Modifications of these versions were not recorded in the Document Revision Record. xxxx R1V4 xxxx • Modifications of these versions were not recorded in the Document Revision Record. xxxx R1V5 xxxx • Modifications of these versions were not recorded in the Document Revision Record. 10/19/01 R1V6 302 • Switched from Edition1 to Edition2A Secs. 1.5, 4.2, parameter/product definitions and updated 4.3, 5.2, 8, & parameter definitions based on Science 15 inputs. • Updated format to comply with standards. All 03/28/02 R2V1 332 • Description of MODIS aerosol parameters Secs. 4.3, 5.2, added to Terra and Aqua SSF. App B., Index • Updated format to comply with standards. All 3/28/02 R2V1 332 • The CERES Top Level Data Flow Diagram Sec. 1.4 was modified (5/29/03). • This document was converted from All FrameMaker to Word. (01/28/2009) • The CERES Top Level Data Flow Diagram Fig. 1-1 was modified. (01/28/2009) ii DRAFT SSF Collection Guide 6/19/2013 Document Revision Record SCCR Release/ SCCR Section(s) Approval Version Description of Revision Number Affected Date Number 3/28/02 R2V1 332 • A small correction was made to the second Sec. 4.3.10 (Cont’d) equation on page 68. (02/08/2010) (SSF-73) • Updated Website links. Some were modified Secs. 4.3.8 & to new sites and some were unlinked as the 14.0 sites no longer exist. (06/19/2013) iii DRAFT SSF Collection Guide 6/19/2013 Preface The Clouds and the Earth’s Radiant Energy System (CERES) Data Management System supports the data processing needs of the CERES Science Team research to increase understanding of the Earth’s climate and radiant environment. The CERES Data Management Team works with the CERES Science Team to develop the software necessary to implement the science algorithms. This software, being developed to operate at the Langley Distributed Active Archive Center (DAAC), produces an extensive set of science data products. The Data Management System consists of 12 subsystems; each subsystem represents one or more stand-alone executable programs. Each subsystem executes when all of its required input data sets are available and produces one or more archival science products. This Collection Guide is intended to give an overview of the science product along with definitions of each of the parameters included within the product. The document has been reviewed by the CERES Working Group teams responsible for producing the product and by the Working Group Teams who use the product. Acknowledgment is given to Waldena Banks and Carol J. Tolson of Science Applications International Corporation (SAIC) for their support in the preparation of this document. iv DRAFT SSF Collection Guide 6/19/2013 TABLE OF CONTENTS Section Page Document Revision Record ............................................................................................................ ii Summary ....................................................................................................................................... 13 1.0 Collection Overview .......................................................................................................... 14 1.1 Collection Identification ................................................................................................. 14 1.2 Collection Introduction .................................................................................................. 14 1.3 Objective/Purpose .......................................................................................................... 14 1.4 Summary of Parameters ................................................................................................. 15 1.5 Discussion ...................................................................................................................... 17 1.6 Related Collections ........................................................................................................ 17 2.0 Investigators ....................................................................................................................... 19 2.1 Title of Investigation ...................................................................................................... 19 2.2 Contact Information ....................................................................................................... 19 3.0 Origination ......................................................................................................................... 20 4.0 Data Description ................................................................................................................ 22 4.1 Spatial Characteristics .................................................................................................... 22 4.1.1 Spatial Coverage ..................................................................................................... 22 4.1.2 Spatial Resolution ................................................................................................... 22 4.2 Temporal Characteristics................................................................................................ 22 4.2.1 Temporal Coverage ................................................................................................. 22 4.2.2 Temporal Resolution ............................................................................................... 23 4.3 Parameter Definitions ..................................................................................................... 23 4.3.1 SSF Header Definitions .......................................................................................... 23 4.3.2 Time and Position Definitions ................................................................................ 30 4.3.3 Viewing Angles Definitions ................................................................................... 37 v DRAFT SSF Collection Guide 6/19/2013 TABLE OF CONTENTS Section Page 4.3.4 Surface Map Definitions ......................................................................................... 38 4.3.5 Scene Type Definitions ........................................................................................... 41 4.3.6 Filtered Radiances Definitions ................................................................................ 42 4.3.7 Unfiltered Radiances Definitions ............................................................................ 47 4.3.8 TOA and Surface Fluxes Definitions ...................................................................... 49 4.3.9 Full Footprint Area Definitions .............................................................................. 55 4.3.10 Clear Footprint Area Definitions ............................................................................ 63 4.3.11 Cloudy Footprint Area Definitions ......................................................................... 70 4.3.12 Footprint Imager Radiance Statistics Definitions ................................................... 87 4.3.13 MODIS Land Aerosols ........................................................................................... 98 4.3.14 MODIS Ocean Aerosols ....................................................................................... 104 4.4 Fill Values .................................................................................................................... 110 4.5 Sample Data File .......................................................................................................... 110 5.0 Data Organization ............................................................................................................ 111 5.1 Data Granularity ........................................................................................................... 111 5.2 SSF HDF Scientific Data Sets (SDS) ........................................................................... 111 5.2.1 Time and Position ................................................................................................. 111 5.2.2 Viewing Angles ...................................................................................................
Load more

Recommended publications
  • Methods for Fitting the Linear Ballistic Accumulator
    Behavior Research Methods 2009, 41 (4), 1095-1110 doi:10.3758/BRM.41.4.1095 Getting more from accuracy and response time data: Methods for fitting the linear ballistic accumulator CHRIS DONKIN , LEE A VERE ll , SC OTT BROWN , A N D A N D REW HE ATH C OTE University of Newcastle, Callaghan, New South Wales, Australia Cognitive models of the decision process provide greater insight into response time and accuracy than do stan- dard ANOVA techniques. However, such models can be mathematically and computationally difficult to apply. We provide instructions and computer code for three methods for estimating the parameters of the linear ballistic accumulator (LBA), a new and computationally tractable model of decisions between two or more choices. These methods—a Microsoft Excel worksheet, scripts for the statistical program R, and code for implementation of the LBA into the Bayesian sampling software WinBUGS—vary in their flexibility and user accessibility. We also provide scripts in R that produce a graphical summary of the data and model predictions. In a simulation study, we explored the effect of sample size on parameter recovery for each method. The materials discussed in this article may be downloaded as a supplement from http://brm.psychonomic-journals.org/content/supplemental. Many tasks used in experimental psychology involve edly samples information from the environment and that participants making relatively simple decisions, for which this information is used as evidence for one of the potential the experimenter measures the response times (RTs) and responses. As soon as the evidence in favor of one potential the accuracy of the responses.
    [Show full text]
  • MODULA-2 TRANSLATOR USER's MANUAL First Edition May 1986
    LOGITECH SOFTWARE ENGINEERING LIBRARY PASCAL TO MODULA-2 TRANSLATOR USER'S MANUAL First Edition May 1986 Copyright (C) 1984, 1985, 1986, 1987 LOGITECH, Inc. All Rights Reserved. No part of this document may be copied or reproduced in any form or by any means without the prior written consent of LOGITECH, Inc. LOGITECH, MODULA-2186,and MODULA-2IVX86 are trademarks ofLOGITECH, Inc. Microsoft is a registered trademark of Microsoft Corporation. MS-DOS is a trademark of Microsoft Corporation. Intel is a registered trademark ofIntel Corporation. IBM is a registered trademark ofInternational Business Machines Corporation. Turbo Pascal is a registered trademark ofBorland International, Inc. LOGITECH, Inc. makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose. The information in this document is subject to change without notice. LOGITECH, Inc. assumes no responsibility for any errors that may appear in this document. From time to time changes may occur in the filenames and in the files actually included on the distribution disks. LOGITECH, Inc. makes no warranties that such files or facilities as mentioned in this documentation exist on the distribution disks or as part of the materials distributed. LU-GUllO-1 Initial issue: May 1986 Reprinted: September 1987 This edition applies to Release 1.00 or later of the software. ii TRANSLATOR Preface LOGITECH'S POLICIES AND SERVICES Congratulations on the purchase of your LOGITECH Pascal To Modula-2 Translator. Please refer to the following infonnation for details about LOGITECH's policies and services. We feel that effective communication with our customers is the key to quality service.
    [Show full text]
  • Clouds and the Earth's Radiant Energy System (CERES) Data Management System
    NASA'S MISSION TO PLANET EARTH EARTH PROBES EOS DATA INFORMATION SYSTEM EARTH OBSERVING SYSTEM National Aeronautics and Space Administration Langley Research Center Hampton, Virginia 23681-2199 Clouds and the Earth's Radiant Energy System (CERES) Data Management System View HDF User's Guide S RA TH DIA AR N E T E E N H E T R D G N Y A CERES S S Y D S U T E O M L Version 5.0 C November 2007 NASA Clouds and the Earth's Radiant Energy System (CERES) Data Management System View_Hdf User’s Guide Version 5.0 Primary Author Kam-Pui Lee Science Systems and Applications, Inc. (SSAI) One Enterprise Parkway Hampton, Virginia 23666 November 2007 TABLE OF CONTENTS Section Page 1.0 Introduction . 1 2.0 Installation . 2 3.0 How to Start . 4 4.0 GUI Description . 12 4.1 Main Menu . 15 4.2 Select Function Menu . 68 4.3 Plot Window Menu . 92 5.0 Recognized Variable Names . 107 6.0 Configuration File . 111 7.0 Examples . 114 8.0 References . 132 9.0 List of Acronyms . 133 10.0 Data Center/Data Access Information . 134 iii LIST OF FIGURES Figure Page Fig. 3-1. Main Menu . 4 Fig. 3-2. File Menu . 5 Fig. 3-3. Select File Window . 5 Fig. 3-4. List SDS and Vdata Names . 6 Fig. 3-5. SDS Range Input Window . 7 Fig. 3-6. Import SDS . 7 Fig. 3-7. Vdata Fields Window . 8 Fig. 3-8. Vdata Field Range Window . 8 Fig. 3-9.
    [Show full text]
  • Warum Unix-Ports Pascal Bis Oberon in Der Bremer Informatik
    Warum Unix-Ports Pascal bis Oberon in der Bremer Informatik Günter Feldmann Universität Bremen [email protected] 1970th, Dept. of Electrical Engineering ● 1974/75: first university computer CII-Honeywell Bull, IRIS-80 ● first Pascal port from a university in Paris. ● learned Pascal by reading the compiler sources ● engineers needed 64-bit REALS, compiler got modified accordingly ● compiling and linking the compiler took 2 days ● N. Wirth: Systematisches Programmieren Since 1981, Dept. of Mathematics and Computer Science ● first personal computers: DEC PDT 11 ● PDP11 instruction set, but some instructions were missing, these had to be emulated in software as the interpreters and compilers used them. ● UCSD Pascal and some times a Modula (not Modula-2) compiler under RT11. ● Small local area network via V24 connections Computer Science ● A series of different computers ● DEC PDP11/44, BSD Unix ● DEC VAX 750 with 8 VT100 terminals, BSD Unix ● 30 Atari 520 ST (M6800) ● 20 Sun3 Workstations (M6820) ● all machines were equipped with Pascal and/or Modula-2 compilers ● Some machines (Pascal Microengine, PERQ) were microprogrammed for Pascal (p-code, Q- code) Computer Science ● workstation pool for students ● 30 machines (1986), 100 machines today ● in the beginning of 1990th we acquired Sun4 workstations (SPARC). No Modula-2 compiler! ● ETHZ released the SPARC Oberon system hosted by SunOS. This system was used in the course “Software Projekt” until 1996. Then “Java” came … ● programming courses got replaced by courses in “internet programming” Keeping Oberon alive on our hardware ● OS change: SunOS (BSD) to Solaris (SYSVR4) ● despite binary compatibility SPARC Oberon failed. Oberon compiler used registers reserved for usage by the system.
    [Show full text]
  • Towards Mathix / Math-X, a Computer Algebra Language That Can Create Its Own Operating System, and That Is Amazingly User- Friendly and Secure
    Towards Mathix / Math-x, a computer algebra language that can create its own operating system, and that is amazingly user- friendly and secure Thomas Colignatus, August 19 2009, some clarifications August 23 2009 http://www.dataweb.nl/~cool Summary Given the current supply and demand for computer languages and systems, there is a clear window of opportunity for the software community to collaborate and create Mathix and Math-x. The base would be Oberon, which itself derives from Algol / Pascal / Modula and which is better designed than Unix / Linux, and which now has the system Bluebottle / A2 at http://bluebottle.ethz.ch. Mathix is defined as Oberon/A2 extended with a suitable computer algebra language (say, CAL). Math-x is defined as Minix ported to Oberon/A2 (via Cyclone) and extended with that CAL. Mathix and Math-x thus can create their own OS. Mathix and Math-x are flexible in that they contain both a strongly typed dialect relevant for OS creation (current Oberon) and a more flexible dialect relevant for the human user (CAL, to be created). The dialects have much syntax in common but the CAL allows more flexibility. The CAL is internally translated into Oberon/A2 which allows compilation as well. 2 2009-08-23-Math-x.nb Note This paper is best understood in the context of my book Elegance with Substance on mathematics education - see http://www.dataweb.nl/~cool/Papers/Math/Index.html. My book advises that each national parliament investigates the stagnation in doing mathematics on the computer in school. This paper suggests how the software community might anticipate on common sense conclusions and start working on improvement.
    [Show full text]
  • Report on the Programming Language Modula-2
    The Programming language Modula-2 133 Report on the Programming Language Modula-2 1. Introduction Modula-2 grew out of a practical need for a general, efficiently implementable systems programming language for minicomputers. Its ancestors are Pascal and Modula. From the latter It has inherited the name, the important module concept, and a systematic, modern syntax, from Pascal most of the rest. This includes in particular the data structures, I.e. arrays, records, variant records, sets, and pointers. Structured statements include the familiar if, case, repeat, while, for, and with statements. Their syntax is such that every structure ends with an explicit termination symbol. The language is essentially machine-independent, with the exception of limitations due to word size. This appears to be in contradiction to the notion of a system-programming language, in which it must be possible to express all operations inherent in the underlying computer. The dilemma is resolved with the aid of the module concept. Machine-dependent items can be introduced in specific modules, and their use can thereby effectively be confined and isolated. In particular, the language provides the possibility to relax rules about data type compatibility in these cases. In a capable system-programming language it is possible to express input/output conversion procedures, file handling routines, storage allocators, process schedulers etc. Such facilities must therefore not be included as elements of the language itself, but appear as (so-called low-level) modules which are components of most programs written. Such a collection of standard modules is therefore an essential part of a Modula-2 implementation.
    [Show full text]
  • Project Oberon the Design of an Operating System and Compiler
    1 Niklaus Wirth Jürg Gutknecht Project Oberon The Design of an Operating System and Compiler Edition 2005 2 Project Oberon Preface This book presents the results of Project Oberon, namely an entire software environment for a modern workstation. The project was undertaken by the authors in the years 1986-89, and its primary goal was to design and implement an entire system from scratch, and to structure it in such a way that it can be described, explained, and understood as a whole. In order to become confronted with all aspects, problems, design decisions and details, the authors not only conceived but also programmed the entire system described in this book, and more. Although there exist numerous books explaining principles and structures of operating systems, there is a lack of descriptions of systems actually implemented and used. We wished not only to give advice on how a system might be built, but to demonstrate how one was built. Program listings therefore play a key role in this text, because they alone contain the ultimate explanations. The choice of a suitable formalism therefore assumed great importance, and we designed the language Oberon as not only an effective vehicle for implementation, but also as a publication medium for algorithms in the spirit in which Algol 60 had been created three decades ago. Because of its structure, the language Oberon is equally well suited to exhibit global, modular structures of programmed systems. In spite of the small number of man-years spent on realizing the Oberon System, and in spite of its compactness letting its description fit a single book, it is not an academic toy, but rather a versatile workstation system that has found many satisfied and even enthusiastic users in academia and industry.
    [Show full text]
  • A2: Analog Malicious Hardware
    A2: Analog Malicious Hardware Kaiyuan Yang, Matthew Hicks, Qing Dong, Todd Austin, Dennis Sylvester Department of Electrical Engineering and Computer Science University of Michigan Ann Arbor, MI, USA fkaiyuan, mdhicks, qingdong, austin, [email protected] Abstract—While the move to smaller transistors has been a will require a $20,000,000,000 upfront investment [3]. To boon for performance it has dramatically increased the cost to amortize the cost of the initial tooling required to support fabricate chips using those smaller transistors. This forces the a given transistor size, most hardware companies outsource vast majority of chip design companies to trust a third party— often overseas—to fabricate their design. To guard against ship- fabrication. ping chips with errors (intentional or otherwise) chip design Outsourcing of chip fabrication opens-up hardware to companies rely on post-fabrication testing. Unfortunately, this attack. The most pernicious fabrication-time attack is the type of testing leaves the door open to malicious modifications dopant-level Trojan [4], [5]. Dopant-level Trojans convert since attackers can craft attack triggers requiring a sequence trusted circuitry into malicious circuitry by changing the of unlikely events, which will never be encountered by even the most diligent tester. dopant ratio on the input pins to victim transistors. This In this paper, we show how a fabrication-time attacker can effectively ties the input of the victim transistors to a leverage analog circuits to create a hardware attack that is logic level 0 or 1—a short circuit. Converting existing small (i.e., requires as little as one gate) and stealthy (i.e., circuits makes dopant-level Trojans very difficult to detect requires an unlikely trigger sequence before effecting a chip’s since there are no added or removed gates or wires.
    [Show full text]
  • Wirth Abstract an Entire Potpourri of Ideas Is Listed from the Past Decades of Computer Science and Computer Technology
    1 Zürich, 2. 2. 2005 / 15. 6. 2005 Good Ideas, Through the Looking Glass Niklaus Wirth Abstract An entire potpourri of ideas is listed from the past decades of Computer Science and Computer Technology. Widely acclaimed at their time, many have lost in splendor and brilliance under today’s critical scrutiny. We try to find reasons. Some of the ideas are almost forgotten. But we believe that they are worth recalling, not the least because one must try to learn from the past, be it for the sake of progress, intellectual stimulation, or fun. Contents 1. Introduction 2. Hardware Technology 3. Computer Architecture 3.1. Representation of numbers 3.2. Data addressing 3.3. Expression Stacks 3.4. Variable length data 3.5. Storing return addresses in the code 3.6. Virtual Addressing 3.7. Memory protection and user classes 3.8. Complex Instruction Sets 3.9. Register windows 4. Programming Language Features 4.1. Notation and Syntax 4.2. The GO TO statement 4.3. Switches 4.4. Algol’s complicated for statement 4.5. Own variables 4.6. Algol’s name parameter 4.7. Incomplete parameter specifications 4.8. Loopholes 5. Miscellaneus techniques 5.1. Syntax analysis 5.2. Extensible languages 5.3. Nested procedures and Dijkstra’s display 5.4. Tree-structured symbol tables 5.5. Using wrong tools 5.6. Wizards 6. Programming paradigms 6.1. Functional programming 6.2. Logic programming 2 6.3. Object-oriented programming 7. Concluding remarks 1. Introduction The history of Computing has been driven by many good and original ideas.
    [Show full text]
  • Proceedings of the NBS/IEEE/ACM Software Tool Fair Held in Conjunction with the 5Th International Conference on Software Engineering in San Diego
    U.S. Department of Commerce Computer Science National Bureau ot Standards and Technology NBS NBS Special Publication 500-80 PUBLICATIONS Proceedings of the '"le^.v of NBS/IEEE/ACM Software Tool Fair NATIONAL BUREAU OF STANDARDS The National Bureau of Standards' was established by an act of Congress on March 3, 1901. The Bureau's overall goal is to strengthen and advance the Nation's science and technology and facilitate their effective application for public benefit. To this end, the Bureau conducts research and provides: (1) a basis for the Nation's physical measurement system, (2) scientific and technological services for industry and government, (3) a technical basis for equity in trade, and (4) technical services to promote public safety. The Bureau's technical work is per- formed by the National Measurement Laboratory, the National Engineering Laboratory, and the Institute for Computer Sciences and Technology. THE NATIONAL MEASUREMENT LABORATORY provides the national system of physical and chemical and materials measurement; coordinates the system with measurement systems of other nations and furnishes essential services leading to accurate and uniform physical and chemical measurement throughout the Nation's scientific community, industry, and commerce; conducts materials research leading to improved methods of measurement, standards, and data on the properties of materials needed by industry, commerce, educational institutions, and Government; provides advisory and research services to other Government agencies; develops, produces,
    [Show full text]
  • Compact Control Builder AC 800M 5.1
    Compact 800 Engineering Compact Control Builder AC 800M 5.1 Planning Compact 800 Engineering Compact Control Builder AC 800M 5.1 Planning NOTICE The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document. In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use of any software or hard- ware described in this document. This document and parts thereof must not be reproduced or copied without written per- mission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive 89/336/EEC and in Low Voltage Directive 72/23/EEC. Copyright © 2003-2010 by ABB. All rights reserved. Release: June 2010 Document number: 3BSE044222-510 TRADEMARKS All rights to copyrights and trademarks reside with their respective owners. TABLE OF CONTENTS About This Book General ..............................................................................................................................9 Document Conventions ...................................................................................................10
    [Show full text]
  • Operating System Provision for Computer System
    ^ ^ ^ ^ I ^ ^ ^ ^ ^ ^ II ^ ^ ^ II ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ ^ I ^ European Patent Office Office europeen des brevets EP 0 867 806 A2 EUROPEAN PATENT APPLICATION (43) Date of publication: (51) |nt CI.6: G 06 F 9/445 30.09.1998 Bulletin 1998/40 (21) Application number: 98301425.9 (22) Date of filing: 26.02.1998 (84) Designated Contracting States: (72) Inventors: AT BE CH DE DK ES Fl FR GB GR IE IT LI LU MC • Mealey, Bruce Gerard NL PT SE Austin, Texas 78759 (US) Designated Extension States: • Swanberg, Randal Craig AL LT LV MK RO SI Round Rock, Texas 78664 (US) • Williams, Michael Stephen (30) Priority: 17.03.1997 US 820471 Austin, Texas 78759-4530 (US) (71) Applicant: International Business Machines (74) Representative: Moss, Robert Douglas Corporation IBM United Kingdom Limited Armonk, N.Y. 10504 (US) Intellectual Property Department Hursley Park Winchester Hampshire S021 2JN (GB) (54) Operating system provision for computer system (57) An improved operating system for a computer provides support for specific hardware components. The operating system is loaded by first loading a base 30 portion which initializes the operating system and deter- 2 mines the particular type of hardware components FIRMWARE present. Then, appropriate software components are SEEKS OPERATING loaded that are specifically associated with the hard- SYSTEM ware components. The hardware components can be detected by leaving a trace in the device that 32 memory 1 is associated with the software component and later re- trieving the trace, or by testing the computer for the hard- OPERATING SYSTEM ware component. The hardware component may be a INITIALIZES bus architecture selected from a group of bus architec- 34 tures, and bus-independent interfaces are defined 1 which are mapped to addresses in the kernel.
    [Show full text]