Brain-wave measures of workload in advanced cockpits: The transition of technology from laboratory to cockpit simulator, phase 2

The present Phase 2 small business innovation research study was designed to address issues related to scalp-recorded event-related potential (ERP) indices of mental workload and to transition this technology from the laboratory to cockpit simulator environments for use as a systems engineering tool. The project involved five main tasks: (1) Two laboratory studies confirmed the generality of the ERP indices of workload obtained in the Phase 1 study and revealed two additional ERP components related to workload. (2) A task analysis' of flight scenarios and pilot tasks in the Advanced Concepts Flight Simulator (ACFS) defined cockpit events (i.e., displays, messages, alarms) that would be expected to elicit ERPs related to workload. (3) Software was developed to support ERP data analysis. An existing ARD-proprietary package of ERP data analysis routines was upgraded, new graphics routines were developed to enhance interactive data analysis, and routines were developed to compare alternative single-trial analysis techniques using simulated ERP data. (4) Working in conjunction with NASA Langley research scientists and simulator engineers, preparations were made for an ACFS validation study of ERP measures of workload. (5) A design specification was developed for a general purpose, computerized, workload assessment system that can function in simulators such as the ACFS

Does "thin client" mean "energy efficient"?

The thick client –a personal computer with integral disk storage and local processing capability, which also has access to data and other resources via a network connection – is accepted as the model for providing computing resource in most office environments. The Further and Higher Education sector is no exception to that, and therefore most academic and administrative offices are equipped with desktop computers of this form to support users in their day to day tasks. This system structure has a number of advantages: there is a reduced reliance on network resources; users access a system appropriate to their needs, and may customise “their” system to meet their own personal requirements and working patterns. However it also has disadvantages: some are outside the scope of this project, but of most relevance to the green IT agenda is the fact that relatively complex and expensive (in first cost and in running cost) desktop systems and servers are underutilised – especially in respect of processing power. While some savings are achieved through use of “sleep” modes and similar power reducing mechanisms, in most configurations only a small portion of the overall total available processor resource is utilised. This realisation has led to the promotion of an alternative paradigm, the thin client. In a thin client system, the desktop is shorn of most of its local processing and data storage capability, and essentially acts as a terminal to the server, which now takes on responsibility for data storage and processing. The energy benefit is derived through resource sharing: the processor of the server does the work, and because that processor is shared by all users, a number of users are supported by a single system. Therefore – according to proponents of thin client – the total energy required to support a user group is reduced, since a shared physical resource is used more efficiently. These claims are widely reported: indeed there are a number of estimation tools which show these savings can be achieved; however there appears to be little or no actual measured data to confirm this. The community does not appear to have access to measured data comparing thin and thick client systems in operation in the same situation, allowing direct comparisons to be drawn. This is the main goal of this project. One specific question relates to the overall power use, while it would seem to be obvious that the thin client would require less electricity, what of the server? Two other variations are also considered: it is not uncommon for thin client deployments to continue to use their existing PCs as thin client workstations, with or without modification. Also, attempts by PC makers to reduce the power requirements of their products have given rise to a further variation: the incorporation of low power features in otherwise standard PC technology, working as thick clients. This project was devised to conduct actual measurements in use in a typical university environment. We identified a test area: a mixed administrative and academic office location which supported a range of users, and we made a direct replacement of the current thick client systems with thin client equivalents; in addition, we exchanged a number of PCs operating in thin and thick client mode with devices specifically branded as “low power” PCs and measured their power requirements in both thin and thick modes. We measured the energy consumption at each desktop for the duration of our experiments, and also measured the energy draw of the server designated to supporting the thin client setup, giving us the opportunity to determine the power per user of each technology. Our results show a significant difference in power use between the various candidate technologies, and that a configuration of low power PC in thick client mode returned the lowest power use during our study. We were also aware of other factors surrounding a change such as this: we have addressed the technical issues of implementation and management, and the non-technical or human factors of acceptance and use: all are reported within this document. Finally, our project is necessarily limited to a set of experiments carried out in a particular situation, therefore we use estimation methods to draw wider conclusions and make general observations which should allow others to select appropriate thick or thin client solutions in their situation

Requirements specification for nickel cadmium battery expert system

The requirements for performance, design, test, and qualification of a computer program identified as NICBES, Nickel Cadmium Battery Expert System, is established. The specific spacecraft power system configuration selected was the Hubble Space Telescope (HST) Electrical Power System (EPS) Testbed. Power for the HST comes from a system of 13 Solar Panel Arrays (SPAs) linked to 6 Nickel Cadmium Batteries which are connected to 3 Busses. An expert system, NICBES, will be developed at Martin Marietta Aerospace to recognize a testbed anomaly, identify the malfunctioning component and recommend a course of action. Besides fault diagnosis, NICBES will be able to evaluate battery status, give advice on battery status and provide decision support for the operator. These requirements are detailed

Impact of change on Attitudes, Skills and Professional Learning Requirements: Survey of secondary teachers of Craft, Design, Engineering and Graphics

This is an independent report based on a national survey. It forms part of a funded project with Education Scotland. It is designed to capture the attitudes and thoughts of teachers currently involved in the implementation of the new curriculum arrangements and the teaching, learning and assessment inherent in delivery. The purpose of this report is to guide and inform future support, advice and guidance for professional learning and further research enquiry. Critically, it offers an overview of current thoughts, as a snap shot of time, set in the context of the roll out of the senior phase of DET

Investigation of Air Transportation Technology at Princeton University, 1989-1990

The Air Transportation Technology Program at Princeton University proceeded along six avenues during the past year: microburst hazards to aircraft; machine-intelligent, fault tolerant flight control; computer aided heuristics for piloted flight; stochastic robustness for flight control systems; neural networks for flight control; and computer aided control system design. These topics are briefly discussed, and an annotated bibliography of publications that appeared between January 1989 and June 1990 is given