SEARCH · Engineering Papers

Results for “Guideline documentation”

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.

SourceResearch connectionFrom yearThrough year

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

354 records · Page 20

All sources NASA NTRS DOE OSTI

NASA NTRS2018

Human-Automation Allocations for Current Robotic Space Operations

Within the Human Research Program, one risk delineates the uncertainty surrounding crew working with automation and robotics in spaceflight. The Risk of Inadequate Design of Human and Automation/Robotic Integration (HARI) is concerned with the detrimental effects on crew performance due to ineffective user interfaces, system designs and/or functional task allocation, potentially compromising mission success and safety. Risk arises because we have limited experience with complex automation and robotics. One key gap within HARI, is the gap related to functional allocation. The gap states: We need to evaluate, develop, and validate methods and guidelines for identifying human-automation/robot task information needs, function allocation, and team composition for future long duration, long distance space missions. Allocations determine the human-system performance as it identifies the functions and performance levels required by the automation/robotic system, and in turn, what work the crew is expected to perform and the necessary human performance requirements. Allocations must take into account each of the human, automation, and robotic systems capabilities and limitations. Some functions may be intuitively assigned to the human versus the robot, but to optimize efficiency and effectiveness, purposeful role assignments will be required. The role of automation and robotics will significantly change in future exploration missions, particularly as crew becomes more autonomous from ground controllers. Thus, we must understand the suitability of existing function allocation methods within NASA as well as the existing allocations established by the few robotic systems that are operational in spaceflight. In order to evaluate future methods of robotic allocations, we must first benchmark the allocations and allocation methods that have been used. We will present 1) documentation of human-automation-robotic allocations in existing, operational spaceflight systems; and 2) To gather existing lessons learned and best practices in these role assignments, from spaceflight operational experience of crew and ground teams that may be used to guide development for future systems. NASA and other space agencies have operational spaceflight experience with two key Human-Automation-Robotic (HAR) systems: heavy lift robotic arms and planetary robotic explorers. Additionally, NASA has invested in high-fidelity rover systems that can carry crew, building beyond Apollo's lunar rover. The heavy lift robotic arms reviewed are: Space Station Remote Manipulator System (SSRMS), Japanese Remote Manipulator System (JEMRMS), and the European Robotic Arm (ERA, designed but not deployed in space). The robotic rover systems reviewed are: Mars Exploration Rovers, Mars Science Laboratory rover, and the high-fidelity K10 rovers. Much of the design and operational feedback for these systems have been communicated to flight controllers and robotic design teams. As part of the mitigating the HARI risk for future human spaceflight operations, we must document function allocations between robots and humans that have worked well in practice.

robotic allocation↗

NASA NTRS2003

Patent foramen ovale and paradoxical systemic embolism: a bibliographic review

A patent foramen ovale (PFO) has been reported to be an important risk factor for cardioembolic cerebrovascular accidents through paradoxical systemic embolization, and it provides one potential mechanism for the paradoxical systemic embolization of venous gas bubbles produced after altitude or hyperbaric decompressions. Here, we present in a single document a summary of the original findings and views from authors in this field. It is a comprehensive review of 145 peer-reviewed journal articles related to PFO that is intended to encourage reflection on PFO detection methods and on the possible association between PFO and stroke. There is a heightened debate on whether aviators, astronauts, and scuba divers should go through screening for PFO. Because it is a source of an important controversy, we prefer to present the findings in the format of a neutral bibliographic review independent of our own opinions. Each cited peer-reviewed article includes a short summary in which we attempt to present potential parallels with the pathophysiology of decompression bubbles. Two types of articles are summarized, as follows. First, we report the original clinical and physiological findings which focus on PFO. The consistent reporting sequence begins by describing the method of detection of PFO and goal of the study, followed by bulleted results, and finally the discussion and conclusion. Second, we summarize from review papers the issues related only to PFO. At the end of each section, an abstract with concluding remarks based on the cited articles provides guidelines.

NASA Discipline Environmental Health↗

NASA NTRS2000

Development of a Reference Dose for Perchlorate: Current Issues and Status

The perchlorate anion (ClO4) is typically manufactured as the ammonium salt. The most common use of ammonium perchlorate is in the aerospace program as a component of solid rocket fuel. The perchlorate anion is exceedingly stable under environmental conditions and has been found in ground and surface waters in CA, NV, UT, AZ, TX, AK, NY, MD, WV and FL. The National Center for Environmental Assessment (NCEA) of the U.S. Environmental Protection Agency (US EPA) is in the process of developing an oral reference dose (RfD) for perchlorate. An oral RfD is a body-weight-adjusted dose that can be consumed daily over an entire lifetime with the expectation of no adverse health effects. Once developed, the new RfD will be used by US EPA as the basis of a safe-drinking-water level (SDWL) guideline. US EPA and regional regulatory agencies will then jointly or separately propose clean-up action levels for ground and surface waters at contaminated sites. The toxicological database on CIO4- as of March 1997 was determined by an expert peer-review panel to be inadequate for the purpose of deriving an oral RfD. For example, little or no experimental data existed on the subchronic, reproductive, or developmental toxicity of perchlorate. To fill gaps in the toxicological database, eight animal studies were designed by a government-industry consortium that included US EPA and AFRL. These studies were performed in 1997-1998. It has been known for many years that in the thyroid, high doses of perchlorate block the function of iodide by competing for iodide binding sites. Perchlorate was used in the 1950s-60s as a treatment for Graves' disease (a hyperthyroid condition). Because of what was already known about the pharmacological mode of action of perchlorate, specific concerns addressed in the design of the recent animal studies included the potential for developmental toxicity, notably neurological development. Upon review of complete study reports from four of the studies and incomplete data from the other two, US EPA/NCEA issued a document in December 1998 stating that the critical effects were hormone and histology data from the neurodevelopmental/behavioral toxicity study that had been performed in rats; an RfD was proposed based upon the observation of thyroid-follicular-cell hypertrophy in the 5-day-old pups (PND) of dams given perchlorate in drinking water at 0.1 mg/kg-day (the lowest dose tested) in this study. US EPA/NCEA also focused attention on a nonsignificant increase in motor activity observed in 14-day-old male pups in the same study at the same dose. In February 1999, a public workshop was convened at which an external peer-review panel determined that there was still insufficient data to support the development of a RfD. Additional studies were recommended. Since that time a clinical study revealed significant depression of thyroidal uptake of iodide in volunteers receiving potassium perchlorate at 10 mg/day for 14 days. Follow-up studies currently underway include a pathology working-group review of histology slides from the all of the previous studies, a motor activity study similar to the first behavioral study, an additional immunotoxicity study, male and female rat kinetic studies, a hormone interlaboratory study, and an effects study for thyroid and brain in developing rats. These studies are expected to be complete by mid-2000. A clinical study is planned to determine inhibition of iodide uptake and kinetic parameters in humans following 14-day perchlorate ingestion. The kinetics studies will provide data for developing physiologically based pharmacokinetic (PBPK) models for rats and humans needed to establish the RfD.

Pleus, R. C.↗

NASA NTRS2006

Thermal Cycle Reliability of PBGA/CCGA 717 I/Os

Status of thermal cycle test results for a nonfunctional daisy-chained peripheral ceramic column grid array (CCGA) and its plastic ball grid array (PBGA) version. both having 560 I/Os. were presented in last year's conference. Test results included environmental data for three different thermal cycle regimes (-55 C/125 C, -55 C/100 C, and -50 C /75 C). Update information on these - especially failure type for assemblies with high and low solder volumes-were presented. The thermal cycle test procedure followed those recommended IPC-9701 for tin-lead solder joint assemblies. Revision A of this specification covers guideline thermal cycle requirements for Pb-free solder joints. Some background information discussed during release of this specification with its current guideline recommendations were also presented. In a recent reliability investigation a fully populated CCGA with 717 I/Os was also considered for assembly reliability. evaluation. The functional package is a field-programmable gate array that has much higher processing power than its previous version. This new package is smaller in dimension, has no interposer, and has a thinner column wrapped with copper for reliability improvement. This paper will also present thermal cycle test results for this package assembly and its plastic version with 728 I/Os. both of which were exposed to three different cycle regimes. Two cycle profiles were those specified by IPC- 9701A for tin-lead, i.e. -55 to 100 C and -55 to 125 C and one was a cycle profile specified by Mil-Std-883, i.e.. -65 C/150 C which is generally used for ceramic hybrid packages. Per IPC-9701 A, test vehicles were built using daisy chain packages and were continuously monitored. The effects of many process and assembly variables-including corner staking commonly used for improving resistance to mechanical loading such as drop and vibration loads--were also considered as part of the test matrix. Optical photomicrographs were taken at various thermal cycle intervals to document damage progress and behavior. Representative samples of these along with cross-sectional photomicrographs at higher magnification taken by scanning electron microscopy (SEM) to determine crack propagation and failure analyses for packages are also presented.

staking↗

NASA NTRS1990

Suspension systems for ground testing large space structures

A research program is documented for the development of improved suspension techniques for ground vibration testing of large, flexible space structures. The suspension system must support the weight of the structure and simultaneously allow simulation of the unconstrained rigid-body movement as in the space environment. Exploratory analytical and experimental studies were conducted for suspension systems designed to provide minimum vertical, horizontal, and rotational degrees of freedom. The effects of active feedback control added to the passive system were also investigated. An experimental suspension apparatus was designed, fabricated, and tested. This test apparatus included a zero spring rate mechanism (ZSRM) designed to support a range of weights from 50 to 300 lbs and provide vertical suspension mode frequencies less than 0.1 Hz. The lateral suspension consisted of a pendulum suspended from a moving cart (linear bearing) which served to increase the effective length of the pendulum. The torsion suspension concept involved dual pendulum cables attached from above to a pivoting support (bicycle wheel). A simple test structure having variable weight and stiffness characteristics was used to simulate the vibration characteristics of a large space structure. The suspension hardware for the individual degrees of freedom was analyzed and tested separately and then combined to achieve a 3 degree of freedom suspension system. Results from the exploratory studies should provide useful guidelines for the development of future suspension systems for ground vibration testing of large space structures.

Gold, Ronald R.↗

NASA NTRS2007

Integrating Human Factors into Crew Exploration Vehicle Design

With NASA's new Vision for Exploration to send humans beyond Earth orbit, it is critical to consider the human as a system that demands early and continuous user involvement, and an iterative prototype/test/redesign process. Addressing human-system interface issues early on can be very cost effective even cost reducing when performed early in the design and development cycle. To achieve this goal within Crew Exploration Vehicle (CEV) Project Office, human engineering (HE) team is formed. Key tasks are to apply HE requirements and guidelines to hardware/software, and provide HE design, analysis and evaluation of crew interfaces. Initial activities included many practice-orientated evaluations using low-fidelity CEV mock-ups. What follows is a description of such evaluations that focused on a HE requirement regarding Net Habitable Volume (NHV). NHV is defined as the total remaining pressurized volume available to on-orbit crew after accounting for the loss of volume due to deployed hardware and structural inefficiencies which decrease functional volume. The goal of the NHV evaluations was to develop requirements providing sufficient CEV NHV for crewmembers to live and perform tasks in support of mission goals. Efforts included development of a standard NHV calculation method using computer models and physical mockups, and crew/ stakeholder evaluations. Nine stakeholders and ten crewmembers participated in the unsuited evaluations. Six crewmembers also participated in a suited evaluation. The mock-up was outfitted with volumetric representation of sub-systems such as seats, and stowage bags. Thirteen scenarios were developed to represent mission/crew tasks and considered to be primary volume drivers (e.g., suit donning) for the CEV. Unsuited evaluations included a structured walkthrough of these tasks. Suited evaluations included timed donning of the existing launch and entry suit to simulate a contingency scenario followed by doffing/ stowing of the suits. All mockup evaluations were videotaped. Structured questionnaires were used to document user interface issues and volume impacts of layout configuration. Computer model and physical measures of the NHV agreed within 1 percent. This included measurement of the gross habitable volume, subtraction of intrusive volumes, and other non-habitable spaces. Calculation method developed was validated as a standard means of measuring NHV, and was recommended as a verification method for the NHV requirements. Evaluations confirmed that there was adequate volume for unsuited scenarios and suit donning/ doffing activity. Seats, suit design stowage and waste hygiene system noted to be critical volume drivers. The low-fidelity mock-up evaluations along with human modeling analysis generated discussions that will lead to high-level systems requirements and human-centered design decisions. This approach allowed HE requirements and operational concepts to evolve in parallel with engineering system concepts and design requirements. As the CEV design matures, these evaluations will continue and help with design decisions, and assessment, verification and validation of HE requirements.

Whitmore, Mihriban↗

NASA NTRS2013

A Validated Set of MIDAS V5 Task Network Model Scenarios to Evaluate Nextgen Closely Spaced Parallel Operations Concepts

The Closely Spaced Parallel Operations (CSPO) scenario is a complex, human performance model scenario that tested alternate operator roles and responsibilities to a series of off-nominal operations on approach and landing (see Gore, Hooey, Mahlstedt, Foyle, 2013). The model links together the procedures, equipment, crewstation, and external environment to produce predictions of operator performance in response to Next Generation system designs, like those expected in the National Airspaces NextGen concepts. The task analysis that is contained in the present report comes from the task analysis window in the MIDAS software. These tasks link definitions and states for equipment components, environmental features as well as operational contexts. The current task analysis culminated in 3300 tasks that included over 1000 Subject Matter Expert (SME)-vetted, re-usable procedural sets for three critical phases of flight; the Descent, Approach, and Land procedural sets (see Gore et al., 2011 for a description of the development of the tasks included in the model; Gore, Hooey, Mahlstedt, Foyle, 2013 for a description of the model, and its results; Hooey, Gore, Mahlstedt, Foyle, 2013 for a description of the guidelines that were generated from the models results; Gore, Hooey, Foyle, 2012 for a description of the models implementation and its settings). The rollout, after landing checks, taxi to gate and arrive at gate illustrated in Figure 1 were not used in the approach and divert scenarios exercised. The other networks in Figure 1 set up appropriate context settings for the flight deck.The current report presents the models task decomposition from the tophighest level and decomposes it to finer-grained levels. The first task that is completed by the model is to set all of the initial settings for the scenario runs included in the model (network 75 in Figure 1). This initialization process also resets the CAD graphic files contained with MIDAS, as well as the embedded operator models that comprise MIDAS. Following the initial settings, the model progresses to begin the first tasks required of the two flight deck operators, the Captain (CA) and the First Officer (FO). The task sets will initialize operator specific settings prior to loading all of the alerts, probes, and other events that occur in the scenario. As a note, the CA and FO were terms used in developing this model but the CA can also be thought of as the Pilot Flying (PF), while the FO can be considered the Pilot-Not-Flying (PNF)or Pilot Monitoring (PM). As such, the document refers to the operators as PFCA and PNFFO respectively.

task network model↗

NASA NTRS2001

Mars Sample Handling Protocol Workshop Series: Workshop 2

Numerous NASA reports and studies have identified Planetary Protection (PP) as an important part of any Mars sample return mission. The mission architecture, hardware, on-board experiments, and related activities must be designed in ways that prevent both forward- and back-contamination and also ensure maximal return of scientific information. A key element of any PP effort for sample return missions is the development of guidelines for containment and analysis of returned sample(s). As part of that effort, NASA and the Space Studies Board (SSB) of the National Research Council (NRC) have each assembled experts from a wide range of scientific fields to identify and discuss issues pertinent to sample return. In 1997, the SSB released its report on recommendations for handling and testing of returned Mars samples. In particular, the NRC recommended that: a) samples returned from Mars by spacecraft should be contained and treated as potentially hazardous until proven otherwise, and b) rigorous physical, chemical, and biological analyses [should] confirm that there is no indication of the presence of any exogenous biological entity. Also in 1997, a Mars Sample Quarantine Protocol workshop was convened at NASA Ames Research Center to deal with three specific aspects of the initial handling of a returned Mars sample: 1) biocontainment, to prevent 'uncontrolled release' of sample material into the terrestrial environment; 2) life detection, to examine the sample for evidence of organisms; and 3) biohazard testing, to determine if the sample poses any threat to terrestrial life forms and the Earth's biosphere. In 1999, a study by NASA's Mars Sample Handling and Requirements Panel (MSHARP) addressed three other specific areas in anticipation of returning samples from Mars: 1) sample collection and transport back to Earth; 2) certification of the samples as non-hazardous; and 3) sample receiving, curation, and distribution. To further refine the requirements for sample hazard testing and the criteria for subsequent release of sample materials from quarantine, the NASA Planetary Protection Officer convened an additional series of workshops beginning in March 2000. The overall objective of these workshops was to develop comprehensive protocols to assess whether the returned materials contain any biological hazards, and to safeguard the purity of the samples from possible terrestrial contamination. This document is the report of the second Workshop in the Series. The information herein will ultimately be integrated into a final document reporting the proceedings of the entire Workshop Series along with additional information and recommendations.

Rummel, John D.↗

NASA NTRS2014

International Space Station (ISS) Plasma Contactor Unit (PCU) Utilization Plan Assessment Update

The International Space Station (ISS) vehicle undergoes spacecraft charging as it interacts with Earth's ionosphere and magnetic field. The interaction can result in a large potential difference developing between the ISS metal chassis and the local ionosphere plasma environment. If an astronaut conducting extravehicular activities (EVA) is exposed to the potential difference, then a possible electrical shock hazard arises. The control of this hazard was addressed by a number of documents within the ISS Program (ISSP) including Catastrophic Safety Hazard for Astronauts on EVA (ISS-EVA-312-4A_revE). The safety hazard identified the risk for an astronaut to experience an electrical shock in the event an arc was generated on an extravehicular mobility unit (EMU) surface. A catastrophic safety hazard, by the ISS requirements, necessitates mitigation by a two-fault tolerant system of hazard controls. Traditionally, the plasma contactor units (PCUs) on the ISS have been used to limit the charging and serve as a "ground strap" between the ISS structure and the surrounding ionospheric plasma. In 2009, a previous NASA Engineering and Safety Center (NESC) team evaluated the PCU utilization plan (NESC Request #07-054-E) with the objective to assess whether leaving PCUs off during non-EVA time periods presented risk to the ISS through assembly completion. For this study, in situ measurements of ISS charging, covering the installation of three of the four photovoltaic arrays, and laboratory testing results provided key data to underpin the assessment. The conclusion stated, "there appears to be no significant risk of damage to critical equipment nor excessive ISS thermal coating damage as a result of eliminating PCU operations during non- EVA times." In 2013, the ISSP was presented with recommendations from Boeing Space Environments for the "Conditional" Marginalization of Plasma Hazard. These recommendations include a plan that would keep the PCUs off during EVAs when the space environment forecast input to the ISS charging model indicates floating potentials (FP) within specified limits. These recommendations were based on the persistence of conditions in the space environment due to the current low solar cycle and belief in the accuracy and completeness of the ISS charging model. Subsequently, a Noncompliance Report (NCR), ISS-NCR-232G, Lack of Two-fault Tolerance to EVA Crew Shock in the Low Earth Orbit Plasma Environment, was signed in September 2013 specifying new guidelines for the use of shock hazard controls based on a forecast of the space environment from ISS plasma measurements taken prior to the EVA [ISS-EVA-312-AC, 2012]. This NESC assessment re-evaluates EVA charging hazards through a process that is based on over 14 years of ISS operations, charging measurements, laboratory tests, EMU studies and modifications, and safety reports. The assessment seeks an objective review of the plasma charging hazards associated with EVA operations to determine if any of the present hazard controls can safely change the PCU utilization plan to allow more flexibility in ISS operations during EVA preparation and execution.

Hernandez-Pellerano, Amri↗

NASA NTRS2013

NASA Software Engineering Benchmarking Study

To identify best practices for the improvement of software engineering on projects, NASA's Offices of Chief Engineer (OCE) and Safety and Mission Assurance (OSMA) formed a team led by Heather Rarick and Sally Godfrey to conduct this benchmarking study. The primary goals of the study are to identify best practices that: Improve the management and technical development of software intensive systems; Have a track record of successful deployment by aerospace industries, universities [including research and development (R&D) laboratories], and defense services, as well as NASA's own component Centers; and Identify candidate solutions for NASA's software issues. Beginning in the late fall of 2010, focus topics were chosen and interview questions were developed, based on the NASA top software challenges. Between February 2011 and November 2011, the Benchmark Team interviewed a total of 18 organizations, consisting of five NASA Centers, five industry organizations, four defense services organizations, and four university or university R and D laboratory organizations. A software assurance representative also participated in each of the interviews to focus on assurance and software safety best practices. Interviewees provided a wealth of information on each topic area that included: software policy, software acquisition, software assurance, testing, training, maintaining rigor in small projects, metrics, and use of the Capability Maturity Model Integration (CMMI) framework, as well as a number of special topics that came up in the discussions. NASA's software engineering practices compared favorably with the external organizations in most benchmark areas, but in every topic, there were ways in which NASA could improve its practices. Compared to defense services organizations and some of the industry organizations, one of NASA's notable weaknesses involved communication with contractors regarding its policies and requirements for acquired software. One of NASA's strengths was its software assurance practices, which seemed to rate well in comparison to the other organizational groups and also seemed to include a larger scope of activities. An unexpected benefit of the software benchmarking study was the identification of many opportunities for collaboration in areas including metrics, training, sharing of CMMI experiences and resources such as instructors and CMMI Lead Appraisers, and even sharing of assets such as documented processes. A further unexpected benefit of the study was the feedback on NASA practices that was received from some of the organizations interviewed. From that feedback, other potential areas where NASA could improve were highlighted, such as accuracy of software cost estimation and budgetary practices. The detailed report contains discussion of the practices noted in each of the topic areas, as well as a summary of observations and recommendations from each of the topic areas. The resulting 24 recommendations from the topic areas were then consolidated to eliminate duplication and culled into a set of 14 suggested actionable recommendations. This final set of actionable recommendations, listed below, are items that can be implemented to improve NASA's software engineering practices and to help address many of the items that were listed in the NASA top software engineering issues. 1. Develop and implement standard contract language for software procurements. 2. Advance accurate and trusted software cost estimates for both procured and in-house software and improve the capture of actual cost data to facilitate further improvements. 3. Establish a consistent set of objectives and expectations, specifically types of metrics at the Agency level, so key trends and models can be identified and used to continuously improve software processes and each software development effort. 4. Maintain the CMMI Maturity Level requirement for critical NASA projects and use CMMI to measure organizations developing software for NASA. 5.onsolidate, collect and, if needed, develop common processes principles and other assets across the Agency in order to provide more consistency in software development and acquisition practices and to reduce the overall cost of maintaining or increasing current NASA CMMI maturity levels. 6. Provide additional support for small projects that includes: (a) guidance for appropriate tailoring of requirements for small projects, (b) availability of suitable tools, including support tool set-up and training, and (c) training for small project personnel, assurance personnel and technical authorities on the acceptable options for tailoring requirements and performing assurance on small projects. 7. Develop software training classes for the more experienced software engineers using on-line training, videos, or small separate modules of training that can be accommodated as needed throughout a project. 8. Create guidelines to structure non-classroom training opportunities such as mentoring, peer reviews, lessons learned sessions, and on-the-job training. 9. Develop a set of predictive software defect data and a process for assessing software testing metric data against it. 10. Assess Agency-wide licenses for commonly used software tools. 11. Fill the knowledge gap in common software engineering practices for new hires and co-ops.12. Work through the Science, Technology, Engineering and Mathematics (STEM) program with universities in strengthening education in the use of common software engineering practices and standards. 13. Follow up this benchmark study with a deeper look into what both internal and external organizations perceive as the scope of software assurance, the value they expect to obtain from it, and the shortcomings they experience in the current practice. 14. Continue interactions with external software engineering environment through collaborations, knowledge sharing, and benchmarking.

Rarick, Heather L.↗

NASA NTRS2015

High Performance EVA Glove Collaboration: Glove Injury Data Mining Effort

Human hands play a significant role during Extravehicular Activity (EVA) missions and Neutral Buoyancy Lab (NBL) training events, as they are needed for translating and performing tasks in the weightless environment. Because of this high frequency usage, hand and arm related injuries are known to occur during EVA and EVA training in the NBL. The primary objectives of this investigation were to: 1) document all known EVA glove related injuries and circumstances of these incidents, 2) determine likely risk factors, and 3) recommend interventions where possible that could be implemented in the current and future glove designs. METHODS: The investigation focused on the discomforts and injuries of U.S. crewmembers who had worn the pressurized Extravehicular Mobility Unit (EMU) spacesuit and experienced 4000 Series or Phase VI glove related incidents during 1981 to 2010 for either EVA ground training or in-orbit flight. We conducted an observational retrospective case-control investigation using 1) a literature review of known injuries, 2) data mining of crew injury, glove sizing, and hand anthropometry databases, 3) descriptive statistical analyses, and finally 4) statistical risk correlation and predictor analyses to better understand injury prevalence and potential causation. Specific predictor statistical analyses included use of principal component analyses (PCA), multiple logistic regression, and survival analyses (Cox proportional hazards regression). Results of these analyses were computed risk variables in the forms of odds ratios (likelihood of an injury occurring given the magnitude of a risk variable) and hazard ratios (likelihood of time to injury occurrence). Due to the exploratory nature of this investigation, we selected predictor variables significant at p≤0.15. RESULTS: Through 2010, there have been a total of 330 NASA crewmembers, from which 96 crewmembers performed 322 EVAs during 1981-2010, resulting in 50 crewmembers being injured inflight and 44 injured during 11,704 ground EVA training events. Of the 196 glove related injury incidents, 106 related to EVA and 90 to EVA training. Over these 196 incidents, 277 total injuries (126 flight; 151 training) were reported and were then grouped into 23 types of injuries. Of EVA flight injuries, 65% were commonly reported to the hand (in general), metacarpophalangeal (MCP) joint, and finger (not including thumb) with fatigue, abrasion, and paresthesia being the most common injury types (44% of total flight injuries). Training injuries totaled to more than 70% being distributed to the fingernail, MCP joint, and finger crotch with 88% of the specific injuries listed as pain, erythema, and onycholysis. Of these training injuries, when reporting pain or erythema, the most common location was the index finger, but when reporting onycholysis, it was the middle finger. Predictor variables specific to increased risk of onycholysis included: female sex (OR=2.622), older age (OR=1.065), increased duration in hours of the flight or training event (OR=1.570), middle finger length differences in inches between the finger and the EVA glove (OR=7.709), and use of the Phase VI glove (OR=8.535). Differentiation between training and flight and injury reporting during 2002-2004 were significant control variables. For likelihood of time to first onycholysis injury, there was a 24% reduction in rate of reporting for each year increase in age. Also, more experienced crewmembers, based on number of EVA flight or training events completed, were less likely to report an onycholysis injury (3% less for every event). Longer duration events also found reporting rates to occur 2.37 times faster for every hour of length. Crewmembers with larger hand size reported onycholysis 23% faster than those with smaller hand size. Finally, for every 1/10th of an inch increase in difference between the middle finger length and the glove, the rate of reporting increased by 60%. DISCUSSION: One key finding was that the Series 4000 glove had a lower injury risk than the Phase VI, which provides a platform for further evaluation. General interventions that reduce hand overexertion and repetitive use exposure through tool development, procedural changes and shorter exposures may be one mitigation path, but due to the way the training event times were reported, we cannot provide a guideline for a specific event duration change. When the finger length was different from the glove length, the risk of injury increased indicating that the use of larger finger take-ups could be contributing to injury and therefore may not be recommended. Prior to this investigation, there was one previous investigation indicating hand anthropometry may be related to onycholysis. We found different hand anthropometry variables indicated by this investigation as compared to the prior, specifically differences in middle finger length compared to glove finger length, which point more towards a sizing issue than a specific anthropometry issue. Additionally, although this investigation has identified sizing as an issue, the force and environmental-related variables of the EVA glove that could also cause injury were not accounted for.

Reid, C. R.↗

NASA NTRS2003

HEASARC Software Archive

(1) Chandra Archive: SAO has maintained the interfaces through which HEASARC gains access to the Chandra Data Archive. At HEASARC's request, we have implemented an anonymous ftp copy of a major part of the public archive and we keep that archive up-to- date. SAO has participated in the ADEC interoperability working group, establishing guidelines or interoperability standards and prototyping such interfaces. We have provided an NVO-based prototype interface, intending to serve the HEASARC-led NVO demo project. HEASARC's Astrobrowse interface was maintained and updated. In addition, we have participated in design discussions surrounding HEASARC's Caldb project. We have attended the HEASARC Users Group meeting and presented CDA status and developments. (2) Chandra CALDB: SA0 has maintained and expanded the Chandra CALDB by including four new data file types, defining the corresponding CALDB keyword/identification structures. We have provided CALDB upgrades for the public (CIAO) and for Standard Data Processing. Approximately 40 new files have been added to the CALDB in these version releases. There have been in the past year ten of these CALDB upgrades, each with unique index configurations. In addition, with the inputs from software, archive, and calibration scientists, as well as CIAO/SDP software developers, we have defined a generalized expansion of the existing CALDB interface and indexing structure. The purpose of this is to make the CALDB more generally applicable and useful in new and future missions that will be supported archivally by HEASARC. The generalized interface will identify additional configurational keywords and permit more extensive calibration parameter and boundary condition specifications for unique file selection. HEASARC scientists and developers from SAO and GSFC have become involved in this work, which is expected to produce a new interface for general use within the current year. (3) DS9: One of the decisions that came from last year's HEADCC meeting was to make the ds9 image display program the primary vehicle for displaying line graphics (as well as images). The first step required to make this possible was to enhance the line graphics capabilities of ds9. SAO therefore spent considerable effort upgrading ds9 to use Tcl 8.4 so that the BLT line graphics package could be built and imported into ds9 from source code, rather than from a pre-built (and generally outdated) shared library. This task, which is nearly complete, allows us to extend BLT as needed for the HEAD community. Following HEADCC discussion concerning archiving and the display of archived data, we extended ds9 to support full access to many astronomical Web-based archives sites, including HEASARC, MAST, CHANDRA, SKYVIEW, ADS, NED, SIMBAD, IRAS, NVRO, SAO TDC, and FIRST. Using ds9's new internal Web access capabilities, these archives can be accessed via their Web page. FITS images, plots, spectra, and journal abstracts can be referenced, down-loaded, and displayed directly and easily in ds9. For more information, see: http://hea-www.harvard.edu/saord/ds9. Also after the HEADCC discussion concerning region filtering, we extended the Funtools sample implementation of region filtering as described in: http://hea-www.harvard.edu/saord/funtools/regions.html. In particular, we added several new composite regions for event and image filtering, including elliptical and box annuli. We also extended the panda (Pie AND Annulus) region support to include box pandas and elliptical pandas. These new composite regions are especially useful in programs that need to count photons in each separate region using only a single pass through the data. Support for these new regions was added to ds9. In the same vein, we developed new region support for filtering images using simple FITS image masks, i.e. 8-bit or 16-bit FITS images where the value of a pixel is the region id number for that pixel. Other important enhancements to DS9 this year, include supporor multiple world coordinate systems, three dimensional event file binning, image smoothing, region groups and tags, the ability to save images in a number of image formats (such as JPEG, TIFF, PNG, FITS), improvements in support for integrating external analysis tools, and support for the virtual observatory. In particular, a full-featured web browser has been implemented within D S 9 . This provides support for full access to HEASARC archive sites such as SKYVIEW and W3BROWSE, in addition to other astronomical archives sites such as MAST, CHANDRA, ADS, NED, SIMBAD, IRAS, NVRO, SA0 TDC, and FIRST. From within DS9, the archives can be searched, and FITS images, plots, spectra, and journal abstracts can be referenced, downloaded and displayed The web browser provides the basis for the built-in help facility. All DS9 documentation, including the reference manual, FAQ, Know Features, and contact information is now available to the user without the need for external display applications. New versions of DS9 maybe downloaded and installed using this facility. Two important features used in the analysis of high energy astronomical data have been implemented in the past year. The first is support for binning photon event data in three dimensions. By binning the third dimension in time or energy, users are easily able to detect variable x-ray sources and identify other physical properties of their data. Second, a number of fast smoothing algorithms have been implemented in DS9, which allow users to smooth their data in real time. Algorithms for boxcar, tophat, and gaussian smoothing are supported.

White, Nicholas↗