Search NASA⌕ Search

SEARCH · Search NASA

Results for “command line interface”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 181 records · Page 10

Radical is Temporary

I suspect that even if Ken had stayed on, we would have evolved to the state we're in right now. In terms of the nature of the work that we're doing, we've gone from development to maintenance, and so the project team needed to evolve to reflect that change. The analogy I use to describe Hubble is a data factory, and we provide the factory controller. The telescope takes in light and produces pictures, and we're the ones sending all of the control signals and monitoring the temperature, power, and voltages in the factory to make sure the production line is doing its job and that it's not reaching some sort of a stress point. That's basically it. We maintain the Hubble command and control system. I think we're still putting out a good quality product. We still meet our schedule and cost milestones. Every time we make a change to the ground system, we run a suite of tests to make sure that the system still runs as expected, and that it correctly controls the spacecraft. Other than that, provided the interfaces are controlled, everything is okay.

Barrett, Larry↗

Neutron Scattering Experiment Automation with Python

The Spallation Neutron Source (SNS) at Oak Ridge National Laboratory currently holds the Guinness World Record as the world most powerful pulsed spallation neutron source. Neutrons scattered off atomic nuclei in a sample yield important information about the position, motions, and magnetic properties of atoms in materials. A neutron scattering experiment usually involves sample environment control (temperature, pressure, etc.), mechanical alignment (slits, sample and detector position), magnetic field controllers, neutron velocity selection (choppers) and neutron detectors. The SNS Data Acquisition System (DAS) consists of real-time sub-system (detector read-out with custom electronics, chopper interface), data preprocessing (soft real-time) and a cluster of control and ancillary PCs. The real-time system runs FPGA firmware and programs running on PCs (C++, LabView) typically perform one task such as motor control and communicate via TCP/IP networks. PyDas is a set of Python modules that are used to integrate various components of the SNS DAS system. It enables customized automation of neutron scattering experiments in a rapid and flexible manner. It provides wxPython GUIs for routine experiments as well as IPython command line scripting. Matplotlib and numpy are used for data presentation and simple analysis. We will present an overview of SNS Data Acquisition System and PyDas architectures and implementation along with the examples of use. We will also discuss plans for future development as well as the challenges that have to be met while maintaining PyDas for 20+ different scientific instruments.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

Co-PylotDB - A Python-Based Single-Window User Interface for Transmitting Information to a Database

Co-PylotDB, written completely in Python, provides a user interface (UI) with which to select user and data file(s), directories, and file content, and provide or capture various other information for sending data collected from running any computer program to a pre-formatted database table for persistent storage. The interface allows the user to select input, output, make, source, executable, and qsub files. It also provides fields for specifying the machine name on which the software was run, capturing compile and execution lines, and listing relevant user comments. Data automatically captured by Co-PylotDB and sent to the database are user, current directory, local hostname, current date, and time of send. The UI provides fields for logging into a local or remote database server, specifying a database and a table, and sending the information to the selected database table. If a server is not available, the UI provides for saving the command that would have saved the information to a database table for either later submission or for sending via email to a collaborator who has access to the desired database.

Barnette, DanielW.↗

Interactive Scene Analysis Module - A sensor-database fusion system for telerobotic environments

Accomplishing a task with telerobotics typically involves a combination of operator control/supervision and a 'script' of preprogrammed commands. These commands usually assume that the location of various objects in the task space conform to some internal representation (database) of that task space. The ability to quickly and accurately verify the task environment against the internal database would improve the robustness of these preprogrammed commands. In addition, the on-line initialization and maintenance of a task space database is difficult for operators using Cartesian coordinates alone. This paper describes the Interactive Scene' Analysis Module (ISAM) developed to provide taskspace database initialization and verification utilizing 3-D graphic overlay modelling, video imaging, and laser radar based range imaging. Through the fusion of taskspace database information and image sensor data, a verifiable taskspace model is generated providing location and orientation data for objects in a task space. This paper also describes applications of the ISAM in the Intelligent Systems Research Laboratory (ISRL) at NASA Langley Research Center, and discusses its performance relative to representation accuracy and operator interface efficiency.

Cooper, Eric G.↗

Overview of the SLS Core Stage Thrust Vector Control System Design

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) consists of four independent hydraulic systems. The SLS CS TVC system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Each hydraulic system nominally provides hydraulic power to one RS-25 engine and two actuators. Additionally, each system provides redundant control capability to one actuator on each of its neighboring systems. The RS-25 uses hydraulic power to control propellant valves, and the TVC actuators are used to move the engine in the pitch and yaw gimbal planes. The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Solid Rocket Booster APU turbines are powered by hot gas produced by a catalyzed hydrazine decomposition. The SLS Core Auxiliary Power Unit (CAPU) is derived from the Space Shuttle Orbiter Auxiliary Power Unit (APU); on the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. The remaining hardware in the TVC system (hydraulic Filter Manifold (FM), hydraulic Supply Accumulator (SA), hydraulic Return Accumulator (RA), Hydraulic Reservoir, Exhaust Gas Heat Exchanger (EGHE)) as well as the avionics providing control and telemetry (TVC Actuator Controller (TAC) and CAPU Controller (CAPUC) are new components developed for SLS. This paper is the first installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. In this paper, the overall design architecture of the CS TVC is presented, with a focus on the interfaces between the TVC actuators, the engines, their hydraulic power systems, and the avionics that provide commands from the SLS Vehicle Management (VM) software to effect stable and robust flight control for the integrated SLS launch vehicle.

Thrust Vector Control↗

Overview of the SLS Core Stage Thrust Vector Control System Design

The Space Launch System (SLS) Core Stage (CS) Thrust Vector Control (TVC) consists of four independent hydraulic systems. The SLS CS TVC system is comprised of 8 mechanical feedback Shuttle heritage Type III TVC actuators and four RS-25 engines, each attached to a Shuttle heritage gimbal block/bearing. Each hydraulic system nominally provides hydraulic power to one RS-25 engine and two actuators. Additionally, each system provides redundant control capability to one actuator on each of its neighboring systems. The RS-25 uses hydraulic power to control propellant valves, and the TVC actuators are used to move the engine in the pitch and yaw gimbal planes. The TVC system design leverages hardware from the Space Shuttle program as well as new hardware designed specifically for the Core Stage. The Space Shuttle heritage hardware directly reused on SLS includes the Orbiter TVC hydraulic servo-actuators (with two slight design modifications), the Orbiter hydraulic circulation pumps, the Orbiter gimbal block/bearing, and the Solid Rocket Booster hydraulic pumps. The Solid Rocket Booster APU turbines are powered by hot gas produced by a catalyzed hydrazine decomposition. The SLS Core Auxiliary Power Unit (CAPU) is derived from the Space Shuttle Orbiter Auxiliary Power Unit (APU); on the SLS Core Stage, the CAPU turbine is spun using cold gas tapped-off from the RS-25 to CS liquid hydrogen autogenous pressurization line. The remaining hardware in the TVC system (hydraulic Filter Manifold (FM), hydraulic Supply Accumulator (SA), hydraulic Return Accumulator (RA), Hydraulic Reservoir, Exhaust Gas Heat Exchanger (EGHE)) as well as the avionics providing control and telemetry (TVC Actuator Controller (TAC) and CAPU Controller (CAPUC) are new components developed for SLS. This paper is the first installment in a seven-paper series surveying the design, engineering, test validation, and flight performance of the Core Stage Thrust Vector Control system. In this paper, the overall design architecture of the CS TVC is presented, with a focus on the interfaces between the TVC actuators, the engines, their hydraulic power systems, and the avionics that provide commands from the SLS Vehicle Management (VM) software to effect stable and robust flight control for the integrated SLS launch vehicle.

Thrust Vector Control↗

Omics Tools

The Omics Tools package provides several small trivial tools for work in genomics. This single portable package, the “omics.jar” file, is a toolbox that works in any Java-based environment, including PCs, Macs, and supercomputers. The number of tools is expected to grow. One tool (called cmsearch.hadoop or cmsearch.local), calls the external cmsearch program to predict non-coding RNA in a genome. The cmsearch program is part of the third-party Infernal package. Omics Tools does not contain Infernal. Infernal may be installed separately. The cmsearch.hadoop subtool requires Apache Hadoop and runs on a supercomputer, though cmsearch.local does not and runs on a server. Omics Tools does not contain Hadoop. Hadoop mat be installed separartely The other tools (cmgbk, cmgff, fastats, pal, randgrp, randgrpr, randsub) do not interface with third-party tools. Omics Tools is written in Java and Scala programming languages. Invoking the “help” command shows currently available tools, as shown below: schaumbe@gpint06:~/proj/omics$ java -jar omics.jar help Known commands are: cmgbk : compare cmsearch and GenBank Infernal hits cmgff : compare hits among two GFF (version 3) files cmsearch.hadoop : find Infernal hits in a genome, on your supercomputer cmsearch.local : find Infernal hits in a genome, on your workstation fastats : FASTA stats, e.g. # bases, GC content pal : stem-loop motif detection by palindromic sequence search (code stub) randgrp : random subsample without replacement, of groups randgrpr : random subsample with replacement, of groups (fast) randsub : random subsample without replacement, of file lines For more help regarding a particular command, use: java -jar omics.jar command help Usage: java -jar omics.jar command args

Schaumberg, Andrew↗

Continuous Security and Configuration Monitoring of HPC Clusters

Continuous security and configuration monitoring of information systems has been a time consuming and laborious task for system administrators at the High Performance Computing (HPC) center. Prior to this project, system administrators had to manually check the settings of thousands of nodes, which required a significant number of hours rendering the old process ineffective and inefficient. This paper explains the application of Splunk Enterprise, a software agent, and a reporting tool in the development of a user application interface to track and report on critical system updates and security compliance status of HPC Clusters. In conjunction with other configuration management systems, the reporting tool is to provide continuous situational awareness to system administrators of the compliance state of information systems. Our approach consisted of the development, testing, and deployment of an agent to collect any arbitrary information across a massively distributed computing center, and organize that information into a human-readable format. Using Splunk Enterprise, this raw data was then gathered into a central repository and indexed for search, analysis, and correlation. Following acquisition and accumulation, the reporting tool generated and presented actionable information by filtering the data according to command line parameters passed at run time. Preliminary data showed results for over six thousand nodes. Further research and expansion of this tool could lead to the development of a series of agents to gather and report critical system parameters. However, in order to make use of the flexibility and resourcefulness of the reporting tool the agent must conform to specifications set forth in this paper. This project has simplified the way system administrators gather, analyze, and report on the configuration and security state of HPC clusters, maintaining ongoing situational awareness. Rather than querying each cluster independently, compliance checking can be managed from one central location.

97 MATHEMATICS AND COMPUTING↗

Intelligent data management

Intelligent data management is the concept of interfacing a user to a database management system with a value added service that will allow a full range of data management operations at a high level of abstraction using human written language. The development of such a system will be based on expert systems and related artificial intelligence technologies, and will allow the capturing of procedural and relational knowledge about data management operations and the support of a user with such knowledge in an on-line, interactive manner. Such a system will have the following capabilities: (1) the ability to construct a model of the users view of the database, based on the query syntax; (2) the ability to transform English queries and commands into database instructions and processes; (3) the ability to use heuristic knowledge to rapidly prune the data space in search processes; and (4) the ability to use an on-line explanation system to allow the user to understand what the system is doing and why it is doing it. Additional information is given in outline form.

Campbell, William J.↗

Development of the functional simulator for the Galileo attitude and articulation control system

A simulation program for verifying and checking the performance of the Galileo Spacecraft's Attitude and Articulation Control Subsystem's (AACS) flight software is discussed. The program, which is called Functional Simulator (FUNSIM), provides a simple method of interfacing user-supplied mathematical models coded in FORTRAN which describes spacecraft dynamics, sensors, and actuators; this is done with the AACS flight software, coded in HAL/S (High-level Advanced Language/Shuttle). It is thus able to simulate the AACS flight software accurately to the HAL/S statement level in the environment of a mainframe computer system. FUNSIM also has a command and data subsystem (CDS) simulator. It is noted that the input/output data and timing are simulated with the same precision as the flight microprocessor. FUNSIM uses a variable stepsize numerical integration algorithm complete with individual error bound control on the state variable to solve the equations of motion. The program has been designed to provide both line printer and matrix dot plotting of the variables requested in the run section and to provide error diagnostics.

Namiri, M. K.↗

A Fully Redundant On-Line Mass Spectrometer System Used to Monitor Cryogenic Fuel Leaks on the Space Shuttle

An on-line gas monitoring system was developed to replace the older systems used to monitor for cryogenic leaks on the Space Shuttles before launch. The system uses a mass spectrometer to monitor multiple locations in the process, which allows the system to monitor all gas constituents of interest in a nearly simultaneous manner. The system is fully redundant and meets all requirements for ground support equipment (GSE). This includes ruggedness to withstand launch on the Mobile Launcher Platform (MLP), ease of operation, and minimal operator intervention. The system can be fully automated so that an operator is notified when an unusual situation or fault is detected. User inputs are through personal computer using mouse and keyboard commands. The graphical user interface is very intuitive and easy to operate. The system has successfully supported four launches to date. It is currently being permanently installed as the primary system monitoring the Space Shuttles during ground processing and launch operations. Time and cost savings will be substantial over the current systems when it is fully implemented in the field. Tests were performed to demonstrate the performance of the system. Low limits-of-detection coupled with small drift make the system a major enhancement over the current systems. Though this system is currently optimized for detecting cryogenic leaks, many other gas constituents could be monitored using the Hazardous Gas Detection System (HGDS) 2000.

Griffin, Timothy P.↗

Computational fluid dynamics analysis of space shuttle main propulsion feed line 17-inch disconnect valves

A steady incompressible three-dimensional (3-D) viscous flow analysis was conducted for the Space Shuttle Main Propulsion External Tank (ET)/Orbiter (ORB) propellant feed line quick separable 17-inch disconnect flapper valves for liquid oxygen (LO2) and liquid hydrogen (LH2). The main objectives of the analysis were to predict and correlate the hydrodynamic stability of the flappers and pressure drop with available water test data. Computational Fluid Dynamics (CFD) computer codes were procured at no cost from the public domain, and were modified and extended to carry out the disconnect flow analysis. The grid generator codes SVTGD3D and INGRID were obtained. NASA Ames Research Center supplied the flow solution code INS3D, and the color graphics code PLOT3D. A driver routine was developed to automate the grid generation process. Components such as pipes, elbows, and flappers can be generated with simple commands, and flapper angles can be varied easily. The flow solver INS3D code was modified to treat interior flappers, and other interfacing routines were developed, which include a turbulence model, a force/moment routine, a time-step routine, and initial and boundary conditions. In particular, an under-relaxation scheme was implemented to enhance the solution stability. Major physical assumptions and simplifications made in the analysis include the neglect of linkages, slightly reduced flapper diameter, and smooth solid surfaces. A grid size of 54 x 21 x 25 was employed for both the LO2 and LH2 units. Mixing length theory applied to turbulent shear flow in pipes formed the basis for the simple turbulence model. Results of the analysis are presented for LO2 and LH2 disconnects.

Kandula, Max↗

Two-dimensional graphics tools for a transputer based display board

A package of 2-D graphics routines has been developed in an effort to standardize and simplify the user interface for a transputer based graphics display board. The routines available take advantage of the graphic board's capabilities while also presenting an intuitive approach for generating drawings. The routines allow a user to perform graphics rendering in a 2-D real-coordinate space without regard to the actual screen coordinates. Multiple windows, which can be placed arbitrarily on the screen as well as the ability to use double-buffering techniques for smooth animations are also supported. The routines are designed to be run on a transputer other than the graphics display board. The window and screen parameters are maintained locally. The conversion to device coordinates is also performed locally. The only data sent to the display board are control and device coordinate display commands. The routines available include: rotation translation, and scaling commands; absolute and relative point and line commands; circle, rectangle and polygon commands; and window and viewpoint definition commands.

Ellis, Graham K.↗

Advancing \textit{otsdaq}: Enhancements for Usability, Accuracy, and Robustness

High-energy physics (HEP) experiments require data acquisition (DAQ) systems that can orchestrate complex detector operations, high data throughput, and responsive, real-time feedback to operators. Traditional DAQ stacks, which are often bespoke, command-line driven and highly specific, impose large learning curves on users. The Off-The-Shelf Data Acquisition (\textit{otsdaq}) framework was created to address these issues by offering a highly customizable and scalable browser-based ’desktop’ environment, in which experiment-specific control and monitoring applications can be easily deployed and integrated. Although the initial development of the \textit{otsdaq} software was aimed at the Fermilab Test Beam Facility, \textit{otsdaq} is now being leveraged for broader deployment, including the upcoming Mu2e experiment, where real-time monitoring of field-programmable gate array (FPGA)-based Data Transfer Controllers (DTCs), Clock and Fanout (CFO) boards, and several other subsystems are critical. We contribute a set of targeted improvements to \textit{otsdaq}: bitmap visualization functionality for configured data, improved and corrected delta-based DTC throughput metrics, version control (VC)-backed source navigation for console messages, custom navigation hooks to eliminate disruptive user interface glitches, and copy-to-clipboard support for macro execution history. These changes improve usability, reduce debugging time, and increase accuracy in performance data as Mu2e moves toward commissioning.

Mohammed, A. [Unlisted, US]↗

Solar Anomalous and Magnetospheric Particle Explorer attitude control electronics box design and performance

The attitude Control Electronics (ACE) Box is the center of the Attitude Control Subsystem (ACS) for the Solar Anomalous and Magnetospheric Particle Explorer (SAMPEX) satellite. This unit is the single point interface for all of the Attitude Control Subsystem (ACS) related sensors and actuators. Commands and telemetry between the SAMPEX flight computer and the ACE Box are routed via a MIL-STD-1773 bus interface, through the use of an 80C85 processor. The ACE Box consists of the flowing electronic elements: power supply, momentum wheel driver, electromagnet driver, coarse sun sensor interface, digital sun sensor interface, magnetometer interface, and satellite computer interface. In addition, the ACE Box also contains an independent Safehold electronics package capable of keeping the satellite pitch axis pointing towards the sun. The ACE Box has dimensions of 24 x 31 x 8 cm, a mass of 4.3 kg, and an average power consumption of 10.5 W. This set of electronics was completely designed, developed, integrated, and tested by personnel at NASA GSFC. SAMPEX was launched on July 3, 1992, and the initial attitude acquisition was successfully accomplished via the analog Safehold electronics in the ACE Box. This acquisition scenario removed the excess body rates via magnetic control and precessed the satellite pitch axis to within 10 deg of the sun line. The performance of the SAMPEX ACS in general and the ACE Box in particular has been quite satisfactory.

Chamberlin, K.↗

Final Scientific/Technical Report, Multi-Sensor Inspection and Robotic Systems for Dry Storage Casks

Once removed from service, fuel rod assemblies are cooled in a pool and then placed in dry storage until they can be transported to a repository for disposal. The extended duration that used nuclear fuel spends in dry storage makes it prudent to be able to nondestructively inspect the dry storage casks. The degradation mechanisms of most concern are chloride-induced stress corrosion cracking of the stainless steel canister that confines the spent fuel and distributed cracking of the concrete in the overpack structure. Multi-sensor inspection and robotic systems were researched, developed, built, and tested. One system operates completely outside the cask to inspect the concrete. The other system, known as the PRINSE system, for Proactive Robotic Inspection of Nuclear Storage Enclosures, enters the cask through an outlet vent and navigates around the outer surface of the stainless steel canister. The PRINSE system delivers sensors for: (i) real-time characterization of the canister surface in order to assess whether chlorides are present, (ii) detecting the presence of cracks using shear-horizontal ultrasonic guided waves, (iii) measuring the temperature of the canister surface, and (iv) a gamma radiation counter. The four sensing modalities are applicable to any cask containing a stainless steel canister, however the robotic delivery system is designed specifically for Holtec’s HI-STORM family of casks. Horizontal axis casks have exposed concrete surfaces. A fully contactless air-coupled scanning ultrasonic test platform and a frequency-wavenumber domain data analysis method are used for these concrete structures. Analysis, numerical simulation and experimental results demonstrate that distributed cracks in concrete can be detected and cracked regions localized within a scanned region of concrete. Vertical axis casks (like the HI-STORM family) have steel-clad concrete overpacks. In a separate effort, a semi-coupled test platform and a guided wave attenuation-based data analysis method are used for disbond detection. Analysis, numerical simulation and experimental results show that the bonding conditions of steel-concrete interfaces can be quantitatively characterized using the guided wave signal analysis scheme. The PRINSE system is designed for vertical axis dry storage casks, specifically the HI-STORM family. The double pulse laser-induced breakdown spectroscopy (LIBS) system takes advantage of an optical fiber to deliver intense light to the canister surface that enables surface composition characterization in-situ in real time. Chlorine concentrations as low as 10 mg/m2 were detected on stainless steel. Additionally, a simpler laser setup was created to detect sodium as a surrogate for chlorine, and sodium was detectable when the chlorine concentration was as low as 0.5 mg/m2. The electromagnetic acoustic transducers (EMATs) enable detection of stress corrosion cracks. The EMATs generate shear-horizontal waves that propagate around the canister and are reflected by cracks enabling 100% of the canister weld lines to be inspected. The EMAT-based crack detection system was tested at the Pacific Northwest National Laboratory on a canister containing blind defects and was shown to detect the crack sizes it was designed to detect. The PRINSE system is a novel marsupial robot. The command center and winch outside the cask control the delivery arm and train of cars that traverse the outside of the canister from the cask ventilation system. The sensors are housed in the cargo bays of three cars that comprise the train, which is lowered to the bottom of the canister by the winch. Encoders on the winch enable the sensors to be delivered to a prescribed location, e.g., for re-inspection of a problem area. The PRINSE system does not mar the canister surface, can be extracted manually in the case of a power failure, and is designed for an elevated temperature and gamma radiation environment, although not all components of the prototype are made from the final materials. The PRINSE system was tested on a full canister that was placed inside a HI-STORM cask at the Holtec Manufacturing Division. It was also demonstrated on a full-height mockup at Penn State to a live audience.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

pyam: Python Implementation of YaM

pyam is a software development framework with tools for facilitating the rapid development of software in a concurrent software development environment. pyam provides solutions for development challenges associated with software reuse, managing multiple software configurations, developing software product lines, and multiple platform development and build management. pyam uses release-early, release-often development cycles to allow developers to integrate their changes incrementally into the system on a continual basis. It facilitates the creation and merging of branches to support the isolated development of immature software to avoid impacting the stability of the development effort. It uses modules and packages to organize and share software across multiple software products, and uses the concepts of link and work modules to reduce sandbox setup times even when the code-base is large. One sidebenefit is the enforcement of a strong module-level encapsulation of a module s functionality and interface. This increases design transparency, system stability, and software reuse. pyam is written in Python and is organized as a set of utilities on top of the open source SVN software version control package. All development software is organized into a collection of modules. pyam packages are defined as sub-collections of the available modules. Developers can set up private sandboxes for module/package development. All module/package development takes place on private SVN branches. High-level pyam commands support the setup, update, and release of modules and packages. Released and pre-built versions of modules are available to developers. Developers can tailor the source/link module mix for their sandboxes so that new sandboxes (even large ones) can be built up easily and quickly by pointing to pre-existing module releases. All inter-module interfaces are publicly exported via links. A minimal, but uniform, convention is used for building modules.

Myint, Steven↗

Event-Driven Random-Access-Windowing CCD Imaging System

A charge-coupled-device (CCD) based high-speed imaging system, called a realtime, event-driven (RARE) camera, is undergoing development. This camera is capable of readout from multiple subwindows [also known as regions of interest (ROIs)] within the CCD field of view. Both the sizes and the locations of the ROIs can be controlled in real time and can be changed at the camera frame rate. The predecessor of this camera was described in High-Frame-Rate CCD Camera Having Subwindow Capability (NPO- 30564) NASA Tech Briefs, Vol. 26, No. 12 (December 2002), page 26. The architecture of the prior camera requires tight coupling between camera control logic and an external host computer that provides commands for camera operation and processes pixels from the camera. This tight coupling limits the attainable frame rate and functionality of the camera. The design of the present camera loosens this coupling to increase the achievable frame rate and functionality. From a host computer perspective, the readout operation in the prior camera was defined on a per-line basis; in this camera, it is defined on a per-ROI basis. In addition, the camera includes internal timing circuitry. This combination of features enables real-time, event-driven operation for adaptive control of the camera. Hence, this camera is well suited for applications requiring autonomous control of multiple ROIs to track multiple targets moving throughout the CCD field of view. Additionally, by eliminating the need for control intervention by the host computer during the pixel readout, the present design reduces ROI-readout times to attain higher frame rates. This camera (see figure) includes an imager card consisting of a commercial CCD imager and two signal-processor chips. The imager card converts transistor/ transistor-logic (TTL)-level signals from a field programmable gate array (FPGA) controller card. These signals are transmitted to the imager card via a low-voltage differential signaling (LVDS) cable assembly. The FPGA controller card is connected to the host computer via a standard peripheral component interface (PCI).

Monacos, Steve↗