Downloads & Free Reading Options - Results

Bibliography: l. 323

Bibliography: l. 323

Bibliography: l. 323

Bibliography: l. 323

A fault-tolerant multiprocessor computer system of the hypercube type comprising a hierarchy of computers of like kind which can be functionally substituted for one another as necessary is disclosed. Communication between the working nodes is via one communications network while communications between the working nodes and watch dog nodes and load balancing nodes higher in the structure is via another communications network separate from the first. A typical branch of the hierarchy reporting to a master node or host computer comprises, a plurality of first computing nodes; a first network of message conducting paths for interconnecting the first computing nodes as a hypercube. The first network provides a path for message transfer between the first computing nodes; a first watch dog node; and a second network of message connecting paths for connecting the first computing nodes to the first watch dog node independent from the first network, the second network provides an independent path for test message and reconfiguration affecting transfers between the first computing nodes and the first switch watch dog node. There is additionally, a plurality of second computing nodes; a third network of message conducting paths for interconnecting the second computing nodes as a hypercube. The third network provides a path for message transfer between the second computing nodes; a fourth network of message conducting paths for connecting the second computing nodes to the first watch dog node independent from the third network. The fourth network provides an independent path for test message and reconfiguration affecting transfers between the second computing nodes and the first watch dog node; and a first multiplexer disposed between the first watch dog node and the second and fourth networks for allowing the first watch dog node to selectively communicate with individual ones of the computing nodes through the second and fourth networks; as well as, a second watch dog node operably connected to the first multiplexer whereby the second watch dog node can selectively communicate with individual ones of the computing nodes through the second and fourth networks. The branch is completed by a first load balancing node; and a second multiplexer connected between the first load balancing node and the first and second watch dog nodes, allowing the first load balancing node to selectively communicate with the first and second watch dog nodes.

A fault-tolerant multiprocessor computer system of the hypercube type comprising a hierarchy of computers of like kind which can be functionally substituted for one another as necessary is disclosed. Communication between the working nodes is via one communications network while communications between the working nodes and watch dog nodes and load balancing nodes higher in the structure is via another communications network separate from the first. A typical branch of the hierarchy reporting to a master node or host computer comprises, a plurality of first computing nodes; a first network of message conducting paths for interconnecting the first computing nodes as a hypercube. The first network provides a path for message transfer between the first computing nodes; a first watch dog node; and a second network of message connecting paths for connecting the first computing nodes to the first watch dog node independent from the first network, the second network provides an independent path for test message and reconfiguration affecting transfers between the first computing nodes and the first switch watch dog node. There is additionally, a plurality of second computing nodes; a third network of message conducting paths for interconnecting the second computing nodes as a hypercube. The third network provides a path for message transfer between the second computing nodes; a fourth network of message conducting paths for connecting the second computing nodes to the first watch dog node independent from the third network. The fourth network provides an independent path for test message and reconfiguration affecting transfers between the second computing nodes and the first watch dog node; and a first multiplexer disposed between the first watch dog node and the second and fourth networks for allowing the first watch dog node to selectively communicate with individual ones of the computing nodes through the second and fourth networks; as well as, a second watch dog node operably connected to the first multiplexer whereby the second watch dog node can selectively communicate with individual ones of the computing nodes through the second and fourth networks. The branch is completed by a first load balancing node; and a second multiplexer connected between the first load balancing node and the first and second watch dog nodes, allowing the first load balancing node to selectively communicate with the first and second watch dog nodes.

The Joint Fleet Telecommunications Operations Center (JFTOC) acts, on behalf of the Naval Computer and Telecommunications Command, as the fleet's \"one-stop shop\" for information services. Effective fault management is vital to ensuring reliable network service. Currently, however, the JFTOC employs a Fault Management System (FMS) that consists primarily of manual processes and non- networked resources. Users require a system that provides a centralized and accessible source of near-real time fault management information. This thesis uses the methodology of the Department of Defense (DoD) Technical Architecture Framework for Information Management (TAFIM). TAFIM outlines a structured approach for migrating legacy systems to a open systems, standards-based target architecture. Through application of the TAFIM process, a target FMS architecture, termed HelpDesk On-Line Information System (HOLIS), is developed. HOLIS includes: the existing NCTAMS classified local area network and SIPRNet infrastructure; network operating system, office automation, e-mail and database software from the interim Navy Automated information System Standards list; and commercial off-the-shelf help desk software. Four migration paths are outlined, and one is selected as the best option for moving from the baseline system to the target FMS.

There the requirements to modern computer system for sound processing are formulated in the article, the structure of such a system and sound data storage organization are discussed. Also, object-oriented model of sound data processors sequence is showed as an intermediate milestone towards sound processor module architecture. 

There the requirements to modern computer system for sound processing are formulated in the article, the structure of such a system and sound data storage organization are discussed. Also, object-oriented model of sound data processors sequence is showed as an intermediate milestone towards sound processor module architecture. 

NASA's Space Station Freedom Program (SSFP) planning efforts have identified a need for a payload training simulator system to serve as both a training facility and as a demonstrator to validate operational concepts. The envisioned MSFC Payload Training Complex (PTC) required to meet this need will train the Space Station payload scientists, station scientists, and ground controllers to operate the wide variety of experiments that will be onboard the Space Station Freedom. The Simulation Computer System (SCS) is the computer hardware, software, and workstations that will support the Payload Training Complex at MSFC. The purpose of this SCS Study is to investigate issues related to the SCS, alternative requirements, simulator approaches, and state-of-the-art technologies to develop candidate concepts and designs.

Tri 1 2015/2016

Thesis advisors, Carl R. Jones, William J. Haga

Thesis advisors, Carl R. Jones, William J. Haga

An emulator is constructed in order to study the behaviour of a Tactical System in a distributed micro-computer architecture environment. This emulator represents Tactical Systems as a set of periodic and demand scheduled functional module processes that collaborate with each other. A special purpose operating system was implemented for the distributed micro-computer architecture that supports the emulator. It includes processor management and system wide input/output capabilities.

An emulator is constructed in order to study the behaviour of a Tactical System in a distributed micro-computer architecture environment. This emulator represents Tactical Systems as a set of periodic and demand scheduled functional module processes that collaborate with each other. A special purpose operating system was implemented for the distributed micro-computer architecture that supports the emulator. It includes processor management and system wide input/output capabilities.

An emulator is constructed in order to study the behaviour of a Tactical System in a distributed micro-computer architecture environment. This emulator represents Tactical Systems as a set of periodic and demand scheduled functional module processes that collaborate with each other. A special purpose operating system was implemented for the distributed micro-computer architecture that supports the emulator. It includes processor management and system wide input/output capabilities.

Tri 2 2019/2020

Tri 2 2018/2019

Tri 2 2022/2023 (Term Id 2220)

Tri 1 2017/2018

Tri 1 2018/2019

Tri 1 2016/2017

The NASA OPAD spectrometer system relies heavily on extensive software which repetitively extracts spectral information from the engine plume and reports the amounts of metals which are present in the plume. The development of this software is at a sufficiently advanced stage where it can be used in actual engine tests to provide valuable data on engine operation and health. This activity will continue and, in addition, the OPAD system is planned to be used in flight aboard space vehicles. The two implementations, test-stand and in-flight, may have some differing requirements. For example, the data stored during a test-stand experiment are much more extensive than in the in-flight case. In both cases though, the majority of the requirements are similar. New data from the spectrograph is generated at a rate of once every 0.5 sec or faster. All processing must be completed within this period of time to maintain real-time performance. Every 0.5 sec, the OPAD system must report the amounts of specific metals within the engine plume, given the spectral data. At present, the software in the OPAD system performs this function by solving the inverse problem. It uses powerful physics-based computational models (the SPECTRA code), which receive amounts of metals as inputs to produce the spectral data that would have been observed, had the same metal amounts been present in the engine plume. During the experiment, for every spectrum that is observed, an initial approximation is performed using neural networks to establish an initial metal composition which approximates as accurately as possible the real one. Then, using optimization techniques, the SPECTRA code is repetitively used to produce a fit to the data, by adjusting the metal input amounts until the produced spectrum matches the observed one to within a given level of tolerance. This iterative solution to the original problem of determining the metal composition in the plume requires a relatively long period of time to execute the software in a modern single-processor workstation, and therefore real-time operation is currently not possible. A different number of iterations may be required to perform spectral data fitting per spectral sample. Yet, the OPAD system must be designed to maintain real-time performance in all cases. Although faster single-processor workstations are available for execution of the fitting and SPECTRA software, this option is unattractive due to the excessive cost associated with very fast workstations and also due to the fact that such hardware is not easily expandable to accommodate future versions of the software which may require more processing power. Initial research has already demonstrated that the OPAD software can take advantage of a parallel computer architecture to achieve the necessary speedup. Current work has improved the software by converting it into a form which is easily parallelizable. Timing experiments have been performed to establish the computational complexity and execution speed of major components of the software. This work provides the foundation of future work which will create a fully parallel version of the software executing in a shared-memory multiprocessor system.

The NASA OPAD spectrometer system relies heavily on extensive software which repetitively extracts spectral information from the engine plume and reports the amounts of metals which are present in the plume. The development of this software is at a sufficiently advanced stage where it can be used in actual engine tests to provide valuable data on engine operation and health. This activity will continue and, in addition, the OPAD system is planned to be used in flight aboard space vehicles. The two implementations, test-stand and in-flight, may have some differing requirements. For example, the data stored during a test-stand experiment are much more extensive than in the in-flight case. In both cases though, the majority of the requirements are similar. New data from the spectrograph is generated at a rate of once every 0.5 sec or faster. All processing must be completed within this period of time to maintain real-time performance. Every 0.5 sec, the OPAD system must report the amounts of specific metals within the engine plume, given the spectral data. At present, the software in the OPAD system performs this function by solving the inverse problem. It uses powerful physics-based computational models (the SPECTRA code), which receive amounts of metals as inputs to produce the spectral data that would have been observed, had the same metal amounts been present in the engine plume. During the experiment, for every spectrum that is observed, an initial approximation is performed using neural networks to establish an initial metal composition which approximates as accurately as possible the real one. Then, using optimization techniques, the SPECTRA code is repetitively used to produce a fit to the data, by adjusting the metal input amounts until the produced spectrum matches the observed one to within a given level of tolerance. This iterative solution to the original problem of determining the metal composition in the plume requires a relatively long period of time to execute the software in a modern single-processor workstation, and therefore real-time operation is currently not possible. A different number of iterations may be required to perform spectral data fitting per spectral sample. Yet, the OPAD system must be designed to maintain real-time performance in all cases. Although faster single-processor workstations are available for execution of the fitting and SPECTRA software, this option is unattractive due to the excessive cost associated with very fast workstations and also due to the fact that such hardware is not easily expandable to accommodate future versions of the software which may require more processing power. Initial research has already demonstrated that the OPAD software can take advantage of a parallel computer architecture to achieve the necessary speedup. Current work has improved the software by converting it into a form which is easily parallelizable. Timing experiments have been performed to establish the computational complexity and execution speed of major components of the software. This work provides the foundation of future work which will create a fully parallel version of the software executing in a shared-memory multiprocessor system.

The Internet Small Computer System Interface (iSCSI) is a SCSI transport protocol that maps the SCSI family of application protocols onto TCP/IP. Datamover Architecture for iSCSI (DA) defines an abstract model in which the movement of data between iSCSI end nodes is logically separated from the rest of the iSCSI protocol in order to allow iSCSI to adapt to innovations available in new IP transports. While DA defines the architectural functions required of the class of Datamover protocols, it does not define any specific Datamover protocols. Each such Datamover protocol, defined in a separate document, provides a reliable transport for all iSCSI PDUs, but actually moves the data required for certain iSCSI PDUs without involving the remote iSCSI layer itself. This document begins with an introduction of a few new abstractions, defines a layered architecture for iSCSI and Datamover protocols, and then models the interactions within an iSCSI end node between the iSCSI layer and the Datamover layer that happen in order to transparently perform remote data movement within an IP fabric. It is intended that this definition will help map iSCSI to generic Remote Direct Memory Access (RDMA)-capable IP fabrics in the future comprising TCP, the Stream Control Transmission Protocol (SCTP), and possibly other underlying network transport layers, such as InfiniBand. This memo provides information for the Internet community.

A book for Computer organisation and architecture

A book for Computer organisation and architecture

Tri 1 2019/2020

First of all, this paper summarizes the key technical directions of satellite-ground deep integration, new spectrum communication, distributed cooperative MIMO and intelligent communication that may be involved in the future 6G, and focuses on the space-ground integrated network (SGIN) based on satellite-ground deep integration; Then, aiming at the two typical network topology architectures that may exist. This paper is devoted to the research on the architecture and development of the video teaching system based on streaming media technology in modern distance education, providing learners with a "learner-centered" networked learning environment. Based on the educational technology theory of streaming media technology and system development, the whole system development process from system requirements analysis to system design, to the production and release of streaming media data, and the production and release of web pages is described in detail.

Tri 2 2022/2023 (Term Id 2215)

mano-m-m-computer-system-architecture

Tri 2 2015/2016

This report presents an example of the application of multi-criteria decision analysis to the selection of an architecture for a safety-critical distributed computer system. The design problem includes constraints on minimum system availability and integrity, and the decision is based on the optimal balance of power, weight and cost. The analysis process includes the generation of alternative architectures, evaluation of individual decision criteria, and the selection of an alternative based on overall value. In this example presented here, iterative application of the quantitative evaluation process made it possible to deliberately generate an alternative architecture that is superior to all others regardless of the relative importance of cost.

NASA's Space Station Freedom Program (SSFP) planning efforts have identified a need for a payload training simulator system to serve as both a training facility and as a demonstrator to validate operational concepts. The envisioned MSFC Payload Training Complex (PTC) required to meet this need will train the Space Station payload scientists, station scientists, and ground controllers to operate the wide variety of experiments that will be onboard the Space Station Freedom. The Simulation Computer System (SCS) is made up of the computer hardware, software, and workstations that will support the Payload Training Complex at MSFC. The purpose of this SCS Study is to investigate issues related to the SCS, alternative requirements, simulator approaches, and state-of-the-art technologies to develop candidate concepts and designs.

The article suggests an approach to the software system development, dedicated to the synthesis and the animation of the gestures and facial expressions of the emotions, based on the three-dimensional pattern of a human body. It describes main requirements for the system, analyzing basic problems and the implements for their solution. The article shows a basic architecture of the system, emphasizing in details its modules, especially these ones that are responsible of the generation of the animation, its structure, the algorithm of gestures’ combination and their graphical processing.

Trimester 2 2016/2017

Trimester 2 2016/2017

Trimester 2 2016/2017

An emulator is constructed in order to study the behaviour of a Tactical System in a distributed micro-computer architecture environment. This emulator represents Tactical Systems as a set of periodic and demand scheduled functional module processes that colaborate with each other. A special purpose operating system was implemented for the distributed micro-computer architecture that supports the emulator. It includes processor management and system wide input/output capabilities. (Author)

This IDA Paper was prepared at the request of the Strategic Defense Initiative Organization. The paper documents findings of an evaluation on the capabilities of certain computer software/computer-aided software engineering (CASE) tools to provide computer-aided graphic design of Battle Management/C3 for the SDIO. Each tool (of the five selected on the basis of the best available at this time), was installed at IDA. After training by vendor tool staff, an IDA team, using a hands-on design exercise determined the merits of the tools for SDI application. A comparative summary of the tools is given relative to envisaged SDI requirements and an extensive questionnaire is answered for each.

This IDA Paper was prepared at the request of the Strategic Defense Initiative Organization. The paper documents findings of an evaluation on the capabilities of certain computer software/computer-aided software engineering (CASE) tools to provide computer-aided graphic design of Battle Management/C3 for the SDIO. Each tool (of the five selected on the basis of the best available at this time), was installed at IDA. After training by vendor tool staff, an IDA team, using a hands-on design exercise determined the merits of the tools for SDI application. A comparative summary of the tools is given relative to envisaged SDI requirements and an extensive questionnaire is answered for each.

The Computer Aided Prototyping System (CAPS) developed at the Naval Postgraduate School is a powerful Computer Aided Software Engineering (CASE) tool for examining requirements and timing constraints for hard real time systems. However, it remains a stand alone system. Even if it is running on machines in multiple locations, there is no way to coordinate the efforts between the different locations. In today's software development environment, that proves to be a significant disadvantage. Additionally, providing support for more than just hard real time software development would tremendously enhance CAPS. Our analysis details the requirements needed to make a distributed CAPS feasible. A distributed CAPS functioning over a network in a coordinated manner would be an invaluable asset to those developing software today, especially in the Department of Defense (DOD). Our work also produced an initial design architecture based on a three tiered client server model and utilizing Java and the Common Object Request Broker Architecture (CORBA). The Java/CORBA combination greatly simplifies deploying a distributed CAPS over any heterogeneous network. Our preliminary implementation of CAPS with a NT client and a Solaris server demonstrates the efficacy of this design.

REEM

The redesigned Advanced Unmanned Search System (AUSS) surface control van has been based on the IBM PC/AT, a well-known, commercially available computer. Its installed market base has made hardware add-on components widely available. The market dominance of Microsoft's DOS has standardized the operating system software. The surface control van computers' functions have been split among several machines to provide for some modularity of the software design and accommodate possible increased processing demands. Operating system software and hardware architecture for these six 7552-based PCs are detailed. The author recommends redefining the AUSS surface computer to be an X Window Platform, an architecture that can provide a virtual display environment. The virtual display environment would protect the software development investment from obsolescence due to hardware technology advances, reduce sparing requirements, and simplify the control van wiring. Appendices describe board jumpers, switch settings, and boot configurations for the six 7552-based PCs.... IBM 7552 PC, X Window system, MULTIBUS I and II.

This volume describes, discusses, and assesses a performance assessment and development methodology for computer-based systems comprised of MSI (medium scale integration) and LSI (large scale integration) computers. The report is not meant to be user's manual or a detailed documentation description of the methodology. In addition to describing the methodology one chapter is devoted to a discussion of testing versus analytic assessment.

The Joint Fleet Telecommunications Operations Center (JFTOC) acts, on behalf of the Naval Computer and Telecommunications Command, as the fleet's "one-stop shop" for information services. Effective fault management is vital to ensuring reliable network service. Currently, however, the JFTOC employs a Fault Management System (FMS) that consists primarily of manual processes and non-networked resources. Users require a system that provides a centralized and accessible source of near-real time fault management information. This thesis uses the methodology of the Department of Defense (DoD) Technical Architecture Framework for Information Management (TAFIM). TAFIM outlines a structured approach for migrating legacy systems to a open systems, standards-based target architecture. Through application of the TAFIM process, a target FMS architecture, termed HelpDesk On-Line Information System (HOLIS), is developed. HOLIS includes: the existing NCTAMS classified local area network and SIPRNet infrastructure; network operating system, office automation, e-mail and database software from the interim Navy Automated information System Standards list; and commercial off-the-shelf help desk software. Four migration paths are outlined, and one is selected as the best option for moving from the baseline system to the target FMS.

Information superiority is identified as an Air Force core competency and is recognized as a key enabler for the success of future missions. Information protection and information assurance are vital components required for achieving superiority in the Infosphere, but these goals are threatened by the exponential birth rate of new computer viruses. The increased global interconnectivity that is empowering advanced information systems is also increasing the spread of malicious code and current anti-virus solutions are quickly becoming overwhelmed by the burden of capturing and classifying new viral stains. To overcome this problem, a distributed computer virus immune system (CVIS) based on biological strategies is developed. The biological immune system (BIS) offers a highly parallel defense-in-depth solution for detecting and eliminating foreign invaders. Each component of the BIS can be viewed as an autonomous agent. Only through the collective actions of this multi-agent system can non-self entities be detected and removed from the body. This research develops a model of the BIS and utilizes software agents to implement a CVIS.

The Navy is funding two areas called combat system architecture (CSA) and combat system engineering (CSE). The question most often asked about these two areas is where does CSA stop and the design begin, and what are the specific functions of CSE. This report attempts to answer these questions by integrating CSA and CSE into a comprehensive system development process. In addition the report recommends which agency should be assigned specific responsibilities within the development process.

A highly interactive, integrated and multi-level simulator has been developed specifically to support both the teachers and the learners of modern computer technologies at undergraduate level. The simulator provides a highly visual and user configurable environment with many pedagogical features aimed at facilitating deep understanding of concepts which are often difficult to grasp by the students. The rational behind the development is explained and the main features of the simulator are described. A brief account of the ways in which the simulator has been used to support undergraduate lectures and tutorials is given. The current state of the research in assessing and evaluating the value of the simulations at undergraduate levels is presented.

The Computer Aided Prototyping System (CAPS) developed at the Naval Postgraduate School is a powerful Computer Aided Software Engineering (CASE) tool for examining requirements and timing constraints for hard real time systems. However, it remains a stand alone system. Even if it is running on machines in multiple locations, there is no way to coordinate the efforts between the different locations. In today's software development environment, that proves to be a significant disadvantage. Additionally, providing support for more than just hard real time software development would tremendously enhance CAPS. Our analysis details the requirements needed to make a distributed CAPS feasible. A distributed CAPS functioning over a network in a coordinated manner would be an invaluable asset to those developing software today, especially in the Department of Defense (DOD). Our work also produced an initial design architecture based on a three tiered client server model and utilizing Java and the Common Object Request Broker Architecture (CORBA). The Java/CORBA combination greatly simplifies deploying a distributed CAPS over any heterogeneous network. Our preliminary implementation of CAPS with a NT client and a Solaris server demonstrates the efficacy of this design.