SEARCH · Search NASA
Results for “tool”
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.
Tool for Insertion of a Fiber-Optic Terminus in a Connector
A tool has been developed for the special purpose of inserting the terminus of an optical fiber in a cable connector that conforms to NASA Specification SSQ- 21635. What prompted the development of the tool was the observation that because of some aspects of the designs of fiber-optic termini and of springs, sealing rings, and a grommet inside the shell of such a connector, there is a tendency for the grommet to become damaged and detached from the sealing rings during installation. It is necessary to ensure the integrity of the grommet for proper sealing and proper functioning of the connector. The special-purpose tool provides the needed protection for the grommet. The grommet-protection tool resembles a funnel into which an axial slit has been cut (see figure). Prior to insertion, the grommet-protection tool is rolled so that one side of the slit overlaps the other side. The rolled-up grommet-protection tool is inserted in one of the connector holes that accommodate the fiber-optic termini and is pushed in until the flange (the wider of the two conical portions) of the tool becomes seated on the connector grommet. Then a special-purpose installation tool is inserted in the flange of the grommet-protection tool and pressed in until it becomes seated in the flange. This operation expands the narrower of the two conical portions of the grommet-protection tool. The installation tool is removed and the grommet-protection tool remains expanded due to the flat surfaces on the axial slit. By use of a standard contact-insertion tool, a fiber-optic terminus is inserted, through the grommet-protection tool, into the connector cavity. By use of a pair of forceps or needle-nose pliers, the grommet-protection tool is then pulled out of the cavity. Finally, the grommet-protection tool is removed from around the installed fiber-optic cable by pulling the cable through the axial slit. Unlike in some prior procedures for installing the fiber-optic termini in the connector, the procedure that involves the use of the present grommet-protection tool does not include the use of lubricants that can contaminate the interior of the connector. The grommet-protection tool is made of a fluoropolymer, taking advantage of the flexibility of such polymers and further taking advantage of the inherent slipperiness of fluoropolymers. Although the tool is designed primarily for insertion of a fiber-optic terminus, it might also be useful for extracting a previously installed fiber-optic terminus.
Support for Systematic Code Reviews with the SCRUB Tool
SCRUB is a code review tool that supports both large, team-based software development efforts (e.g., for mission software) as well as individual tasks. The tool was developed at JPL to support a new, streamlined code review process that combines human-generated review reports with program-generated review reports from a customizable range of state-of-the-art source code analyzers. The leading commercial tools include Codesonar, Coverity, and Klocwork, each of which can achieve a reasonably low rate of false-positives in the warnings that they generate. The time required to analyze code with these tools can vary greatly. In each case, however, the tools produce results that would be difficult to realize with human code inspections alone. There is little overlap in the results produced by the different analyzers, and each analyzer used generally increases the effectiveness of the overall effort. The SCRUB tool allows all reports to be accessed through a single, uniform interface (see figure) that facilitates brows ing code and reports. Improvements over existing software include significant simplification, and leveraging of a range of commercial, static source code analyzers in a single, uniform framework. The tool runs as a small stand-alone application, avoiding the security problems related to tools based on Web browsers. A developer or reviewer, for instance, must have already obtained access rights to a code base before that code can be browsed and reviewed with the SCRUB tool. The tool cannot open any files or folders to which the user does not already have access. This means that the tool does not need to enforce or administer any additional security policies. The analysis results presented through the SCRUB tool s user interface are always computed off-line, given that, especially for larger projects, this computation can take longer than appropriate for interactive tool use. The recommended code review process that is supported by the SCRUB tool consists of three phases: Code Review, Developer Response, and Closeout Resolution. In the Code Review phase, all tool-based analysis reports are generated, and specific comments from expert code reviewers are entered into the SCRUB tool. In the second phase, Developer Response, the developer is asked to respond to each comment and tool-report that was produced, either agreeing or disagreeing to provide a fix that addresses the issue that was raised. In the third phase, Closeout Resolution, all disagreements are discussed in a meeting of all parties involved, and a resolution is made for all disagreements. The first two phases generally take one week each, and the third phase is concluded in a single closeout meeting.
Meta-tools for software development and knowledge acquisition
The effectiveness of tools that provide support for software development is highly dependent on the match between the tools and their task. Knowledge-acquisition (KA) tools constitute a class of development tools targeted at knowledge-based systems. Generally, KA tools that are custom-tailored for particular application domains are more effective than are general KA tools that cover a large class of domains. The high cost of custom-tailoring KA tools manually has encouraged researchers to develop meta-tools for KA tools. Current research issues in meta-tools for knowledge acquisition are the specification styles, or meta-views, for target KA tools used, and the relationships between the specification entered in the meta-tool and other specifications for the target program under development. We examine different types of meta-views and meta-tools. Our current project is to provide meta-tools that produce KA tools from multiple specification sources--for instance, from a task analysis of the target application.
Anvil Tool in the Advanced Weather Interactive Processing System
Meteorologists from the 45th Weather Squadron (45 WS) and Spaceflight Meteorology Group (SMG) have identified anvil forecasting as one of their most challenging tasks when predicting the probability of violations of the lightning Launch Commit Criteria and Space Shuttle Flight Rules. As a result, the Applied Meteorology Unit (AMU) created a graphical overlay tool for the Meteorological Interactive Data Display Systems (MIDDS) to indicate the threat of thunderstorm anvil clouds, using either observed or model forecast winds as input. In order for the Anvil Tool to remain available to the meteorologists, the AMU was tasked to transition the tool to the Advanced Weather interactive Processing System (AWIPS). This report describes the work done by the AMU to develop the Anvil Tool for AWIPS to create a graphical overlay depicting the threat from thunderstorm anvil clouds. The AWIPS Anvil Tool is based on the previously deployed AMU MIDDS Anvil Tool. SMG and 45 WS forecasters have used the MIDDS Anvil Tool during launch and landing operations. SMG's primary weather analysis and display system is now AWIPS and the 45 WS has plans to replace MIDDS with AWIPS. The Anvil Tool creates a graphic that users can overlay on satellite or radar imagery to depict the potential location of thunderstorm anvils one, two, and three hours into the future. The locations are based on an average of the upper-level observed or forecasted winds. The graphic includes 10 and 20 nm standoff circles centered at the location of interest, in addition to one-, two-, and three-hour arcs in the upwind direction. The arcs extend outward across a 30 degree sector width based on a previous AMU study which determined thunderstorm anvils move in a direction plus or minus 15 degrees of the upper-level (300- to 150-mb) wind direction. This report briefly describes the history of the MIDDS Anvil Tool and then explains how the initial development of the AWIPS Anvil Tool was carried out. After testing was performed by SMG, 45 WS, and AMU, a number of needed improvements were identified. A bug report document was created that showed the status of each bug and desired improvement. This report lists the improvements that were made to increase the accuracy and user-friendliness of the tool. Final testing was carried out and documented and then the final version of the software and Users Guide was provided to SMG and the 45 WS. Several possible future improvements to the tool are identified that would increase the flexibility of the tool. This report contains a brief history of the development of the Anvil Tool in MIDDS, and then describes the transition and development of software to AWIPS.
Flow in the Proximity of the Pin-Tool in Friction Stir Welding and Its Relation to Weld Homogeneity
In the Friction Stir Welding (FSW) process a rotating pin inserted into a seam literally stirs the metal from each side of the seam together. It is proposed that the flow in the vicinity of the pin-tool comprises a primary rapid shear over a cylindrical envelope covering the pin-tool and a relatively slow secondary flow taking the form of a ring vortex about the tool circumference. This model is consistent with a plastic characterization of metal flow, where discontinuities in shear flow are allowed but not viscous effects. It is consistent with experiments employing several different kinds of tracer: atomic markers, shot, and wire. If a rotating disc with angular velocity w is superposed on a translating continuum with linear velocity omega, the trajectories of tracer points become circular arcs centered upon a point displaced laterally a distance v/omega from the center of rotation of the disc in the direction of the advancing side of the disc. In the present model a stream of metal approaching the tool (taken as the coordinate system of observation) is sheared at the slip surface, rapidly rotated around the tool, sheared again on the opposite side of the tool, and deposited in the wake of the tool. Local shearing rates are high, comparable to metal cutting in this model. The flow patterns in the vicinity of the pin-tool determine the level of homogenization and dispersal of contaminants that occurs in the FSW process. The approaching metal streams enfold one another as they are rotated around the tool. Neglecting mixing they return to the same lateral position in the wake of the tool preserving lateral tracer positions as if the metal had flowed past the tool like an extrusion instead of being rotated around it. (The seam is, however, obliterated.) The metal stream of thickness approximately that of the tool diameter D is wiped past the tool at elevated temperatures drawn out to a thickness of v/2(omega) in the wiping zone. Mixing distances in the wiping zone are multiplied in the unfolded metal. Inhomogeneities on a smaller scale than the mixing length are obliterated, but structure on a larger scale may be transmitted to the wake of a FSW weld.
Programming Tools: Status, Evaluation, and Comparison
In this tutorial I will first describe the characteristics of scientific applications and their developers, and describe the computing environment in a typical high-performance computing center. I will define the user requirements for tools that support application portability and present the difficulties to satisfy them. These form the basis of the evaluation and comparison of the tools. I will then describe the tools available in the market and the tools available in the public domain. Specifically, I will describe the tools for converting sequential programs, tools for developing portable new programs, tools for debugging and performance tuning, tools for partitioning and mapping, and tools for managing network of resources. I will introduce the main goals and approaches of the tools, and show main features of a few tools in each category. Meanwhile, I will compare tool usability for real-world application development and compare their different technological approaches. Finally, I will indicate the future directions of the tools in each category.
Template for Systems Engineering Tools Trade Study
A discussion of Systems Engineering tools brings out numerous preferences and reactions regarding tools of choice as well as the functions those tools are to perform. A recent study of Systems Engineering Tools for a new Program illustrated the need for a generic template for use by new Programs or Projects to determine the toolset appropriate for their use. This paper will provide the guidelines new initiatives can follow and tailor to their specific needs, to enable them to make their choice of tools in an efficient and informed manner. Clearly, those who perform purely technical functions will need different tools than those who perform purely systems engineering functions. And, everyone has tools they are comfortable with. That degree of comfort is frequently the deciding factor in tools choice rather than an objective study of all criteria and weighting factors. This paper strives to produce a comprehensive list of criteria for selection with suggestions for weighting factors based on a number of assumptions regarding the given Program or Project. In addition, any given Program will begin with assumptions for its toolset based on Program size, tool cost, user base and technical needs. In providing a template for tool selection, this paper will guide the reader through assumptions based on Program need; decision criteria; potential weighting factors; the need for a compilation of available tools; the importance of tool demonstrations; and finally a down selection of tools. While specific vendors cannot be mentioned in this work, it is expected that this template could serve other Programs in the formulation phase by alleviating the trade study process of some of its subjectivity.
Tool for Two Types of Friction Stir Welding
A tool that would be useable in both conventional and self-reacting friction stir welding (FSW) has been proposed. The tool would embody both a prior tooling concept for self-reacting FSW and an auto-adjustable pin-tool (APT) capability developed previously as an augmentation for conventional FSW. Some definitions of terms are prerequisite to a meaningful description of the proposed tool. In conventional FSW, depicted in Figure 1, one uses a tool that includes (1) a rotating shoulder on top (or front) of the workpiece and (2) a rotating pin that protrudes from the shoulder into the depth of the workpiece. The main axial force exerted by the tool on the workpiece is reacted through a ridged backing anvil under (behind) the workpiece. When conventional FSW is augmented with an APT capability, the depth of penetration of the pin into the workpiece is varied in real time by a position- or force-control system that extends or retracts the pin as needed to obtain the desired effect. In self-reacting (also known as self-reacted) friction stir welding (SR-FSW), there are two rotating shoulders: one on top (or front) and one on the bottom (or back) of the workpiece. In this case, a threaded shaft protrudes from the tip of the pin to beyond the back surface of the workpiece. The back shoulder is held axially in place against tension by a nut on the threaded shaft. The main axial force exerted on the workpiece by the tool and front shoulder is reacted through the back shoulder and the threaded shaft, back into the FSW machine head, so that a backing anvil is no longer needed. A key transmits torque between the bottom shoulder and the threaded shaft, so that the bottom shoulder rotates with the shaft. A tool for SRFSW embodying this concept was reported in "Mechanism for Self-Reacted Friction Stir Welding" (MFS-31914), NASA Tech Briefs, Vol. 28, No. 10 (October 2004), page 53. In its outward appearance, the proposed tool (see Figure 2) would fit the above description of an SR-FSW tool. In this case, the FSW machine would have an APT capability and the pin would be modified to accept a bottom shoulder. The APT capability could be used to vary the distance between the front and back shoulders in real time to accommodate process and workpiece-thickness variations. The tool could readily be converted to a conventional FSW tool, with or without APT capability, by simply replacing the modified pin with a conventional FSW pin.
The Way Point Planning Tool: Real Time Flight Planning for Airborne Science
Airborne real time observation are a major component of NASA's Earth Science research and satellite ground validation studies. For mission scientist, planning a research aircraft mission within the context of meeting the science objective is a complex task because it requires real time situational awareness of the weather conditions that affect the aircraft track. Multiple aircraft are often involved in the NASA field campaigns the coordination of the aircraft with satellite overpasses, other airplanes and the constantly evolving dynamic weather conditions often determine the success of the campaign. A flight planning tool is needed to provide situational awareness information to the mission scientist and help them plan and modify the flight tracks successfully. Scientists at the University of Alabama Huntsville and the NASA Marshal Space Flight Center developed the Waypoint Planning Tool (WPT), an interactive software tool that enables scientist to develop their own flight plans (also known as waypoints), with point and click mouse capabilities on a digital map filled with time raster and vector data. The development of this Waypoint Planning Tool demonstrates the significance of mission support in responding to the challenges presented during NASA field campaigns. Analyses during and after each campaign helped identify both issues and new requirements, initiating the next wave of development. Currently the Waypoint Planning Tool has gone through three rounds of development and analysis processes. The development of this waypoint tool is directly affected by the technology advances on GIS/Mapping technologies. From the standalone Google Earth application and simple KML functionalities to the Google Earth Plugin and Java Web Start/Applet on web platform, as well as to the rising open source GIS tools with new JavaScript frameworks, the Waypoint planning Tool has entered its third phase of technology advancement. The newly innovated, cross-platform, modular designed JavaScript-controled Waypoint tool is planned to be integrated with the NASA Airborne Science Mission Tool Suite. Adapting new technologies for the Waypoint Planning Tool ensures its success in helping scientist reach their mission objectives. This presentation will discuss the development process of the Waypoint Planning Tool in responding to field campaign challenges, identifying new information technologies, and describing the capabilities and features of the Waypoint Planning Tool with the real time aspect, interactive nature, and the resultant benefits to the airborne science community.
Development of Waypoint Planning Tool in Response to NASA Field Campaign Challenges
Airborne real time observations are a major component of NASA's Earth Science research and satellite ground validation studies. For mission scientists, planning a research aircraft mission within the context of meeting the science objectives is a complex task because it requires real time situational awareness of the weather conditions that affect the aircraft track. Multiple aircrafts are often involved in NASA field campaigns. The coordination of the aircrafts with satellite overpasses, other airplanes and the constantly evolving, dynamic weather conditions often determines the success of the campaign. A flight planning tool is needed to provide situational awareness information to the mission scientists, and help them plan and modify the flight tracks. Scientists at the University of Alabama-Huntsville and the NASA Marshall Space Flight Center developed the Waypoint Planning Tool, an interactive software tool that enables scientists to develop their own flight plans (also known as waypoints) with point -and-click mouse capabilities on a digital map filled with real time raster and vector data. The development of this Waypoint Planning Tool demonstrates the significance of mission support in responding to the challenges presented during NASA field campaigns. Analysis during and after each campaign helped identify both issues and new requirements, and initiated the next wave of development. Currently the Waypoint Planning Tool has gone through three rounds of development and analysis processes. The development of this waypoint tool is directly affected by the technology advances on GIS/Mapping technologies. From the standalone Google Earth application and simple KML functionalities, to Google Earth Plugin and Java Web Start/Applet on web platform, and to the rising open source GIS tools with new JavaScript frameworks, the Waypoint Planning Tool has entered its third phase of technology advancement. The newly innovated, cross ]platform, modular designed JavaScript ]controlled Way Point Tool is planned to be integrated with NASA Airborne Science Mission Tool Suite. Adapting new technologies for the Waypoint Planning Tool ensures its success in helping scientists reach their mission objectives. This presentation will discuss the development processes of the Waypoint Planning Tool in responding to field campaign challenges, identify new information technologies, and describe the capabilities and features of the Waypoint Planning Tool with the real time aspect, interactive nature, and the resultant benefits to the airborne science community.
Core-Cutoff Tool
A tool makes a cut perpendicular to the cylindrical axis of a core hole at a predetermined depth to free the core at that depth. The tool does not damage the surrounding material from which the core was cut, and it operates within the core-hole kerf. Coring usually begins with use of a hole saw or a hollow cylindrical abrasive cutting tool to make an annular hole that leaves the core (sometimes called the plug ) in place. In this approach to coring as practiced heretofore, the core is removed forcibly in a manner chosen to shear the core, preferably at or near the greatest depth of the core hole. Unfortunately, such forcible removal often damages both the core and the surrounding material (see Figure 1). In an alternative prior approach, especially applicable to toxic or fragile material, a core is formed and freed by means of milling operations that generate much material waste. In contrast, the present tool eliminates the damage associated with the hole-saw approach and reduces the extent of milling operations (and, hence, reduces the waste) associated with the milling approach. The present tool (see Figure 2) includes an inner sleeve and an outer sleeve and resembles the hollow cylindrical tool used to cut the core hole. The sleeves are thin enough that this tool fits within the kerf of the core hole. The inner sleeve is attached to a shaft that, in turn, can be attached to a drill motor or handle for turning the tool. This tool also includes a cutting wire attached to the distal ends of both sleeves. The cutting wire is long enough that with sufficient relative rotation of the inner and outer sleeves, the wire can cut all the way to the center of the core. The tool is inserted in the kerf until its distal end is seated at the full depth. The inner sleeve is then turned. During turning, frictional drag on the outer core pulls the cutting wire into contact with the core. The cutting force of the wire against the core increases with the tension in the wire and, hence, with the frictional drag acting on the outer sleeve. As the wire cuts toward the center of the core, the inner sleeve rotates farther with respect to the outer sleeve. Once the wire has cut to the center of the core, the tool and the core can be removed from the hole. The proper choice of cutting wire depends on the properties of the core material. For a sufficiently soft core material, a nonmetallic monofilament can be used. For a rubber-like core material, a metal wire can be used. For a harder core material, it is necessary to use an abrasive wire, and the efficiency of the tool can be increased greatly by vacuuming away the particles generated during cutting. For a core material that can readily be melted or otherwise cut by use of heat, it could be preferable to use an electrically heated cutting wire. In such a case, electric current can be supplied to the cutting wire, from an electrically isolated source, via rotating contact rings mounted on the sleeves.
Users Guide for the Anvil Threat Corridor Forecast Tool V1.7.0 for AWIPS
The Applied Meteorology Unit (AMU) originally developed the Anvil Threat Sector Tool for the Meteorological Interactive Data Display System (MIDDS) and delivered the capability in three phases beginning with a feasibility study in 2000 and delivering the operational final product in December 2003. This tool is currently used operationally by the 45th Weather Squadron (45 WS) Launch Weather Officers (LWO) and Spaceflight Meteorology Group (SMG) forecasters. Phase I of the task established the technical feasibility of developing an objective, observations-based tool for short-range anvil forecasting. The AMU was subsequently tasked to develop short-term anvil forecasting tools to improve predictions of the threat of triggered lightning to space launch and landing vehicles. Under the Phase II effort, the AMU developed a nowcasting anvil threat sector tool, which provided the user with a threat sector based on the most current radiosonde upper wind data from a co-located or upstream station. The Phase II Anvil Threat Sector Tool computes the average wind speed and direction in the layer between 300 and 150 mb from the latest radiosonde for a user-designated station. The following threat sector properties are consistent with the propagation and lifetime characteristics of thunderstorm anvil clouds observed over Florida and its coastal waters (Short et al. 2002): a) 20 n mi standoff circle, b) 30 degree sector width, c) Orientation given by 300 to 150 mb average wind direction, d) 1-, 2-, and 3- hour arcs in upwind direction, and e) Arc distances given by 300 to 150 mb average wind speed. Figure 1 is an example of the MIDDS Anvil Threat Sector tool overlaid on a visible satellite image at 2132 UTC 13 May 2001. Space Launch Complex 39A was selected as the center point and the Anvil Threat Sector was determined from upper-level wind data at 1500 UTC in the preconvective environment. Narrow thunderstorm anvil clouds extend from central Florida to the space launch and landing facilities at the Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) and beyond. The anvil clouds were generated around 1930 UTC (1430 EDT) by thunderstorm activity over central Florida and transported 90 n mi east-northeastward within 2 hours, as diagnosed by the anvil forecast tool. Phase III, delivered in February 2003, built upon the results of Phase II by enhancing the Anvil Threat Sector Tool with the capability to use national model forecast winds for depiction of potential anvil lengths and orientations over the KSC/CCAFS area with lead times from 3 through 168 hours (7 days). In September 2003, AMU customers requested the capability to use data from the KSC 50 MHz Doppler Radar Wind Profiler (DRWP) in the Anvil Threat Sector Tool and this capability was delivered by the AMU in December 2003. In March 2005, the AMU was tasked to migrate the MIDDS Anvil Threat Sector Tool capabilities onto the Advanced Weather Interactive Processing System (AWIPS) as the Anvil Threat Corridor Forecast Tool.
Robotic tool change mechanism
An assembly of three major components is disclosed which included a wrist interface plate which is secured to the wrist joint of a robotic arm, a tool interface plate which is secured to each tool intended for use by the robotic arm, and a tool holster for each tool attached to the interface plate. The wrist interface plate and a selected tool interface plate are mutually connectable together through an opening or recess in the upper face of the interface plate by means of a notched tongue protruding from the front face of the wrist interface plate which engages a pair of spring-biased rotatable notched wheels located within the body of the tool interface plate. The tool holster captures and locks onto the tool interface plate by means of a pair of actuation claws including a locking tab and an unlocking wedge which operate respective actuation bosses on each of the notched wheels in response to a forward and backward motion of the tool interface plate as a result of motion of the robotic arm to either park the tool or use the tool.
Software Tools to Support the Assessment of System Health
This presentation provides an overview of three software tools that were developed by the NASA Glenn Research Center to support the assessment of system health: the Propulsion Diagnostic Method Evaluation Strategy (ProDIMES), the Systematic Sensor Selection Strategy (S4), and the Extended Testability Analysis (ETA) tool. Originally developed to support specific NASA projects in aeronautics and space, these software tools are currently available to U.S. citizens through the NASA Glenn Software Catalog. The ProDiMES software tool was developed to support a uniform comparison of propulsion gas path diagnostic methods. Methods published in the open literature are typically applied to dissimilar platforms with different levels of complexity. They often address different diagnostic problems and use inconsistent metrics for evaluating performance. As a result, it is difficult to perform a one ]to ]one comparison of the various diagnostic methods. ProDIMES solves this problem by serving as a theme problem to aid in propulsion gas path diagnostic technology development and evaluation. The overall goal is to provide a tool that will serve as an industry standard, and will truly facilitate the development and evaluation of significant Engine Health Management (EHM) capabilities. ProDiMES has been developed under a collaborative project of The Technical Cooperation Program (TTCP) based on feedback provided by individuals within the aircraft engine health management community. The S4 software tool provides a framework that supports the optimal selection of sensors for health management assessments. S4 is structured to accommodate user ]defined applications, diagnostic systems, search techniques, and system requirements/constraints. One or more sensor suites that maximize this performance while meeting other user ]defined system requirements that are presumed to exist. S4 provides a systematic approach for evaluating combinations of sensors to determine the set or sets of sensors that optimally meet the performance goals and the constraints. It identifies optimal sensor suite solutions by utilizing a merit (i.e., cost) function with one of several available optimization approaches. As part of its analysis, S4 can expose fault conditions that are difficult to diagnose due to an incomplete diagnostic philosophy and/or a lack of sensors. S4 was originally developed and applied to liquid rocket engines. It was subsequently used to study the optimized selection of sensors for a simulation ]based aircraft engine diagnostic system. The ETA Tool is a software ]based analysis tool that augments the testability analysis and reporting capabilities of a commercial ]off ]the ]shelf (COTS) package. An initial diagnostic assessment is performed by the COTS software using a user ]developed, qualitative, directed ]graph model of the system being analyzed. The ETA Tool accesses system design information captured within the model and the associated testability analysis output to create a series of six reports for various system engineering needs. These reports are highlighted in the presentation. The ETA Tool was developed by NASA to support the verification of fault management requirements early in the Launch Vehicle process. Due to their early development during the design process, the TEAMS ]based diagnostic model and the ETA Tool were able to positively influence the system design by highlighting gaps in failure detection, fault isolation, and failure recovery.
Scheduling and Delivering Aircraft to Departure Fixes in the NY Metroplex with Controller-Managed Spacing Tools
In this paper, successful Time-Based Flow Management (TBFM) scheduling systems for arrivals are considered and adapted to apply to departures. We present a concept of operations that integrates Controller-Managed Spacing tools for departures (CMS-D) with existing tactical departure scheduling tools to coordinate demand at departure fixes in a metroplex environment. We tested our concept in a Human-in-the-Loop simulation and compared the effect of two scheduling conditions: 1) "Departure Scheduling" consisting of an emulation of the Integrated Departure and Arrival Capability (IDAC) where Towers and a Planner (Traffic Management Coordinator at the appropriate facility) coordinate aircraft scheduled takeoff times to departure fixes; and 2) "Arrival Sensitive Departure Scheduling" where, in addition, the Tower and Planner also consider arrival Scheduled Time of Arrivals (STAs) at the airport's dependent runway. Results indicate little difference between the two scheduling conditions, but a large difference between the No Tools and the two scheduling conditions with CMS-D tools. The scheduling/CMS-D tools conditions markedly reduced heading, speed clearances, and workload for controllers who were merging flows at the departure fixes. In the tool conditions, departure controllers conditioned departures earlier rather than later when aircraft were tied near the departure fixes. In the scheduling/CMS-D tools conditions, departures crossed the departure fixes 50 seconds earlier and with an 8% error rate (consisting of time ahead or behind desired time of arrival) compared to a 19% error rate in the No Tool condition. Two exploratory runs showed that similar beneficial effects can be obtained only with the CMS-D tools without scheduling takeoff times, but at the cost of a somewhat higher workload for controllers, indicating the benefits of pre-departure scheduling of aircraft with minimal delays. Hence, we found that CMS-D tools were very beneficial in the metroplex environment we tested but that further research is needed to clarify the benefits of the various scheduling approaches.
Comparative Analysis of TCR and TCR-pMHC Complex Structure Prediction Tools
The rapid development of computational approaches for predicting the structures of T cell receptors (TCRs) and TCR-peptide-major histocompatibility (TCR-pMHC) complexes, accelerated by AI breakthroughs such as AlphaFold, has made it feasible to calculate these structures with increasing accuracy. Although these tools show great potential, their relative accuracy and limitations remain unclear due to the lack of standardized benchmarks. Here, we systematically evaluate seven tools for predicting isolated TCR structures together with six tools for predicting TCR-pMHC complex structures. The methods include homology-based approaches, general prediction tools using AlphaFold, TCR-specific tools derived from AlphaFold2, and the newly developed tFold-TCR model. The evaluation uses a post-training data set comprising 40 αβ TCRs and 27 TCR-pMHC complexes (21 Class I and 6 Class II). Model accuracy is assessed at global, local, and interface levels using a variety of metrics. We find that each tool offers distinct advantages in various aspects of its predictions. AlphaFold2, AlphaFold3, and tFold-TCR excel in overall accuracy of TCR structure prediction, and TCRmodel2 and AlphaFold2 perform well in overall accuracy of TCR-pMHC structure prediction. However, TCR-specific tools derived from AlphaFold2 show lower accuracy in the framework region than both homology-based methods and general-purpose tools such as AlphaFold, and challenges remain for all in modeling CDR3 loops, docking orientations, TCR-peptide interfaces, and Class II MHC-peptide interfaces. Furthermore, these findings will guide researchers in selecting appropriate tools, emphasize the importance of using multiple evaluation metrics to assess model performance, and offer suggestions for improving TCR and TCR-pMHC structure prediction tools.
Tool for Inspecting Alignment of Twinaxial Connectors
A proposed tool would be used to inspect alignments of mating twinaxial-connector assemblies on interconnecting wiring harnesses. More specifically, the tool would be used to inspect the alignment of each contact pin of each connector on one assembly with the corresponding socket in the corresponding connector on the other assembly. It is necessary to inspect the alignment because if mating of the assemblies is attempted when any pin/socket pair is misaligned beyond tolerance, the connection will not be completed and the dielectric material in the socket will be damaged (see Figure 1). Although the basic principle of the tool is applicable to almost any type of mating connector assemblies, the specific geometry of the tool must match the pin-and-socket geometry of the specific mating assemblies to be inspected. In the original application for which the tool was conceived, each of the mating assemblies contains eight twinaxial connectors; the pin diameter is 0.014 in. (.0.35 mm), and the maximum allowable pin/socket misalignment is 0.007 in. (.0.18 mm). Incomplete connections can result in loss of flight data within the functional path to the space shuttle crew cockpit displays. The tool (see Figure 2) would consist mainly of a transparent disk with alignment clocking tabs that can be fitted onto either connector assembly. Sets of circles or equivalent reference markings are affixed to the face of the tool, located at the desired positions of the mating contact pairs. An inspector would simply fit the tool onto a connector assembly, engaging the clocking tabs until the tool fits tightly. The inspector would then align one set of circles positioning a line of sight perpendicular to one contact within the connector assembly. Mis alignments would be evidenced by the tip of a pin contact straying past the inner edge of the circle. Socket contact misalignments would be evidenced by a crescent-shaped portion of the white dielectric appearing within the circle. The tool could include a variable magnifier plus an illuminator that could be configured so as not to cast shadows.