No description available.

No description available.

International Telemetering Conference Proceedings / October 25-28, 1993 / Riviera Hotel and Convention Center, Las Vegas, Nevada / With the move toward design and interface standards in data acquisition and processing hardware and software, the development of open architecture telemetry processing systems has moved from a goal to a reality. The potential for a system to support hardware and software from a variety of vendors, allow inclusion of user-written software and user-provided interfaces, and provide a scalable, growth oriented processing capability can now be realized. This paper discusses the open architecture concept throughout the hardware and software components of the typical telemetry processing system. Utilizing such a system ensures flexibility to support different configurations, better and faster analysis through greater user programmability, and overall reduced costs by providing a system that can grow as future hardware and software components are brought to market.

The diversity in observed planets and planetary systems has raised the question of whether they can be explained by a single model of planet formation or whether multiple models are required. The work presented in this thesis aims to examine the oligarchic growth scenario, to determine whether the core accretion model, where planets form bottom-up, can recreate the observed diversity. I begin by exploring how changing model parameters such as disc mass and metallicity influence the types of planetary systems that emerge. I show that rapid inward migration leads to very few planets with masses mp > 10M⊕ surviving, with surviving planetary systems typically containing numerous low-mass planets. I examine what conditions are required for giant planets to form and survive migration, finding that for a planet similar to Jupiter to form and survive, it must form at an orbital radius rp > 10 au. In the second project in this thesis, I update the physical models before examining whether a broader range of parameters can produce planetary systems similar to those observed. I find that compact systems of low-mass planets form in simulations if there is sufficient solid material in the disc or if planetesimals are small, thus having increased mobility. I also find that giant planets can form when the solid abundance and mobility of planetesimals are high, however they all undergo largescale migration into the magnetospheric cavity located close to the star. For the final project of this thesis, I examined the effects that disc radial structuring has on the formation of giant planets. I find that by including radial structures, numerous giant planets are able to form at large orbital radii and survive migration. The observed period valley between 10-100 days is also recreated, of which I attribute to disc dispersal late in the disc's lifetime.

Thesis (M.S.)--Oregon Graduate Center, 1988.

M.S. / Computer Science & Engineering / The Oregon Graduate Center's Cognitive Architecture Project (CAP) is developing a flexible architecture to evaluate and implement several types of neural networks. Wafer-scale integrated silicon is the targeted technology, allowing higher density and larger networks to be implemented more cheaply than with discrete components. The large size of networks implemented in wafer-scale technology makes it difficult to assess the effects of manufacturing faults on network behavior. Since neural networks degrade gracefully in the presence of faults, and since in larger networks faults tend to interact with each other, it is difficult to determine these effects analytically. This paper discusses a program, FltSim, that simulates wafer manufacturing faults. By building an abstract model of the CAP architecture, the effects of these manufacturing faults can be determined long before proceeding to implementation. In addition, the effects of architectural design trade-offs can be studied during the design process.

The importance of building maintainable software is being recognized in the community of software development. By developing software that is easy to maintain, the time and resources needed to perform the modifications may be decreased. This will in turn mean economical savings and increased profits. Architectural software patterns are said to promote the development of maintainable software. The aim of this project was therefore to investigate whether architectural software patterns possess this property or not. A case study was performed where two candidate architectures were compared using a method called Architectural analysis of modifiability. This method uses change scenarios and modification ratios to identify differences between candidate architectures. A system developed at Ericsson Microwave Systems AB was used for the case study. One of the candidate architectures consisted of two architectural software patterns: the Layers pattern and the Model-View-Controller pattern. The architecture analysis showed that the Layers pattern did promote maintainability whereas the Model-View-Controller pattern did not, from the basis of judgement associated with the method.

Building Collaboration, Building Community: A Home for Northern Learning explores the potential for architecture to support learning endeavors in the Canadian North. Informed by traditional approaches to northern learning for cultural continuity, alongside the assimilative effects of the residential school experience, the thesis strives to develop an environment for contemporary northern learning where both Aboriginal cultures and values can thrive alongside current educational endeavors. Situated within a context plagued by imposed and unsuccessful architectural models, the thesis advocates for a design process rooted in collaborative ideals. At its core, the thesis asserts that both the local knowledge of the community and the training of the architect are vital components in the design process. In the development of an environment for northern learning, both the socio-cultural visions of a northern people and the skill sets of the architect are of necessity. Local stories and perspectives - both past and present - guide project developments. As directed by the community, the scope of work does not focus solely upon the formal learning environment, but rather upon a series of social and cultural structures designed to support learners within the northern educational context. Technically, as informed by traditional architectural predecessors, the contemporary forms are developed in accordance with the local climate: the proposed architecture invites its inhabitants to thrive within the immediate northern landscape. Ultimately, these explorations – of community vision and technical design - are synthesized into a series of design vignettes for a student living community in Yellowknife, Northwest Territories. The ideas housed within the architectural translations and the broader thesis documentations are not finite conclusions but rather they form the foundation for future investigations: they provide a starting point for continued dialogues and developments.

Building Collaboration, Building Community: A Home for Northern Learning explores the potential for architecture to support learning endeavors in the Canadian North. Informed by traditional approaches to northern learning for cultural continuity, alongside the assimilative effects of the residential school experience, the thesis strives to develop an environment for contemporary northern learning where both Aboriginal cultures and values can thrive alongside current educational endeavors. Situated within a context plagued by imposed and unsuccessful architectural models, the thesis advocates for a design process rooted in collaborative ideals. At its core, the thesis asserts that both the local knowledge of the community and the training of the architect are vital components in the design process. In the development of an environment for northern learning, both the socio-cultural visions of a northern people and the skill sets of the architect are of necessity. Local stories and perspectives - both past and present - guide project developments. As directed by the community, the scope of work does not focus solely upon the formal learning environment, but rather upon a series of social and cultural structures designed to support learners within the northern educational context. Technically, as informed by traditional architectural predecessors, the contemporary forms are developed in accordance with the local climate: the proposed architecture invites its inhabitants to thrive within the immediate northern landscape. Ultimately, these explorations – of community vision and technical design - are synthesized into a series of design vignettes for a student living community in Yellowknife, Northwest Territories. The ideas housed within the architectural translations and the broader thesis documentations are not finite conclusions but rather they form the foundation for future investigations: they provide a starting point for continued dialogues and developments.

<p>The importance of building maintainable software is being recognized in the community of software development. By developing software that is easy to maintain, the time and resources needed to perform the modifications may be decreased. This will in turn mean economical savings and increased profits.</p><p>Architectural software patterns are said to promote the development of maintainable software. The aim of this project was therefore to investigate whether architectural software patterns possess this property or not. A case study was performed where two candidate architectures were compared using a method called Architectural analysis of modifiability. This method uses change scenarios and modification ratios to identify differences between candidate architectures. A system developed at Ericsson Microwave Systems AB was used for the case study.</p><p>One of the candidate architectures consisted of two architectural software patterns: the Layers pattern and the Model-View-Controller pattern. The architecture analysis showed that the Layers pattern did promote maintainability whereas the Model-View-Controller pattern did not, from the basis of judgement associated with the method.</p>