Results for “Data Management Platform” — Page 15

DOE OSTI2024

Operational experience and R&D results using the Google Cloud for High-Energy Physics in the ATLAS experiment

The ATLAS experiment at CERN relies on a Worldwide Distributed Computing Grid infrastructure to support its physics program at the Large Hadron Collider. ATLAS has integrated cloud computing resources to complement its Grid infrastructure and conducted an R&D program on Google Cloud Platform. These initiatives leverage key features of commercial cloud providers: lightweight configuration and operation, elasticity and availability of diverse infrastructures. Here this paper examines the seamless integration of cloud computing services as a conventional Grid site within the ATLAS workflow management and data management systems, while also offering new setups for interactive, parallel analysis. It underscores pivotal results that enhance the on-site computing model and outlines several R&D projects that have benefited from large-scale, elastic resource provisioning models. Furthermore, this study discusses the impact of cloud-enabled R&D projects in three domains: accelerators and AI/ML, ARM CPUs and columnar data analysis techniques.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

NASA NTRS2023

Exploration Medical Capability Clinical Decision Support System Architecture Recommendation

A new era in space exploration has arrived with the goal of establishing a long-term presence on the Moon and using those learning to take the next giant leap: sending the first astronauts to Mars. These ambitious goals will require significant changes in in-flight medical care due to constraints on mass, volume, power, crew time, and medical evacuation capabilities. Furthermore, while crews currently rely on real-time communications with ground-based medical providers, as distance from Earth increases, so do communication delays and disruptions. The crew will need to autonomously detect, diagnose, treat, and prevent medical events. These constraints require development of transformative solutions and new technologies. Through participation in the Human Research Program’s (HRP) Exploration Medical Capability (ExMC) research, NASA has developed and demonstrated a Medical Data Architecture (MDA), a platform upon which a robust capability of Clinical Decision Support (CDS) can be built. As a result, NASA is now positioned to build an advanced autonomous CDS System (CDSS) which will aid in crew health decision-making. The CDSS combines data management aspects of a system that would lead to the autonomy required by NASA-STD-3001, Section 3, Health and Medical Care Standards. The project addresses the ExMC gap Medical-701: We need to increase inflight medical capabilities and identify new capabilities that (a) maximize benefit and/or (b) reduce “costs” on human system/mission/vehicle resources. This architecture recommendation document introduces an integrated data architecture that provides self-sufficient medical care for crews on long-duration spaceflight missions.

ExMC↗

NASA NTRSDate not supplied

Summary of Technical Interchange Meetings (TIMs) Designed to Enable Earth Independent Medical Operations (EIMO)

The Exploration Medical Capability Element (ExMC) in NASA’s Human Research Program hosted a series of TIMs in 2023-2024 designed to stimulate discussion around specific topics with the goal of enabling EIMO. In context of the thematic constituent elements of EIMO, namely pre-mission planning, acute/emergent/prolonged medical decision making, supply/resource management and task load management, subject matter experts from industry, academia and government (NASA and other Agencies) provided valuable and actionable guidance and recommendations. Earth-based medical experts will remain indispensable for pre-mission planning, however, management of acute/emergent medical contingencies will require a gradual transition of medical care and decision making from terrestrial to space-based assets to enable support of astronaut health and performance and reduce overall mission risk. Key to achieving these enhancements is providing an integrated data system platform capable of utilizing multiple data streams in concert with a variety of on-board databases and passive monitoring of video and wearable sensors to enable a multi-modal, agentic AI-based clinical decision support system (CDSS) to support crew medical officer (CMO) medical decision-making. The EIMO series of TIMs (I-V) have proven to be instructive and portend a significant paradigm shift will be necessary to maintain crew health and performance on exploration class missions. Importantly, since the expected paradigm shift will be significantly different from the methods of operation that have been employed for the majority of missions from the inception of human spaceflight to date, any proposed methods must be deployed in the setting of ongoing operations early and be “tested, reviewed and practiced” while reliable back-up is available to facilitate an Enterprise-wide level of comfort and acceptance. Serious constraints on data transmission coupled with a large and expanding universe of on-board medical informatics data streams will necessitate implementation of a CDSS to supplant the current reliance on support provided by ground-based SMEs. Establishment of trust in the system by CMO/crew and the ground-based medical support team will be essential. Co-development of a CDSS with industry partners will assure that state of the art tools can be employed, and industry efficiencies can be leveraged. Training regimens, materials and tools must evolve to be responsive (just-in-time training) and facilitate autonomous execution of procedures. Proficiency metrics should be established and be based on validated competencies or milestones as opposed to a prescribed number of training hours. Training should be prioritized for broad, translatable skills that have universal application across a variety of medical conditions. Repetition was deemed to be the key to achieving proficiency and emphasis should lie in procedural training which is known to extinguish more rapidly than diagnostic skills. Advanced tools, e.g., extended reality, can provide more realistic and effective training. Use of advanced probabilistic risk assessment tools will be essential to optimize the medical system capability while carefully balancing risk relative to mass/power/volume limitations. Importance of factoring use-life of medical supplies and maintaining awareness of redundancy and opportunity to re-purpose under off nominal situations was emphasized. Consideration of adopting optimized performance standards vs. “good-enough” performance thresholds is warranted. The use of legacy systems as opposed to creating new systems may be preferable. Managing task load and associated cognitive load will be essential to maintain operational safety and behavioral health. ExMC aspires to create a shared EIMO paradigm and strategic vision for advancing medical system design through novel technologies, training, protocols, and support capabilities, built upon the spirit of successful strategies and innovations over the past six decades of space medicine operations.

Jay Lemery↗

NASA NTRS1975

Design criteria for a multiple input land use system

A design is presented that proposes the use of digital image processing techniques to interface existing geocoded data sets and information management systems with thematic maps and remote sensed imagery. The basic premise is that geocoded data sets can be referenced to a raster scan that is equivalent to a grid cell data set, and that images taken of thematic maps or from remote sensing platforms can be converted to a raster scan. A major advantage of the raster format is that x, y coordinates are implicitly recognized by their position in the scan, and z values can be treated as Boolean layers in a three-dimensional data space. Such a system permits the rapid incorporation of data sets, rapid comparison of data sets, and adaptation to variable scales by resampling the raster scans.

Billingsley, F. C.↗

NASA NTRS2007

Grid Task Execution

IPG Execution Service is a framework that reliably executes complex jobs on a computational grid, and is part of the IPG service architecture designed to support location-independent computing. The new grid service enables users to describe the platform on which they need a job to run, which allows the service to locate the desired platform, configure it for the required application, and execute the job. After a job is submitted, users can monitor it through periodic notifications, or through queries. Each job consists of a set of tasks that performs actions such as executing applications and managing data. Each task is executed based on a starting condition that is an expression of the states of other tasks. This formulation allows tasks to be executed in parallel, and also allows a user to specify tasks to execute when other tasks succeed, fail, or are canceled. The two core components of the Execution Service are the Task Database, which stores tasks that have been submitted for execution, and the Task Manager, which executes tasks in the proper order, based on the user-specified starting conditions, and avoids overloading local and remote resources while executing tasks.

Hu, Chaumin↗

NASA NTRS1988

Knowledge-based assistance in costing the space station DMS

The Software Cost Engineering (SCE) methodology developed over the last two decades at IBM Systems Integration Division (SID) in Houston is utilized to cost the NASA Space Station Data Management System (DMS). An ongoing project to capture this methodology, which is built on a foundation of experiences and lessons learned, has resulted in the development of an internal-use-only, PC-based prototype that integrates algorithmic tools with knowledge-based decision support assistants. This prototype Software Cost Engineering Automation Tool (SCEAT) is being employed to assist in the DMS costing exercises. At the same time, DMS costing serves as a forcing function and provides a platform for the continuing, iterative development, calibration, and validation and verification of SCEAT. The data that forms the cost engineering database is derived from more than 15 years of development of NASA Space Shuttle software, ranging from low criticality, low complexity support tools to highly complex and highly critical onboard software.

Henson, Troy↗

NASA NTRS2004

Transitioning to Intel-based Linux Servers in the Payload Operations Integration Center

The MSFC Payload Operations Integration Center (POIC) is the focal point for International Space Station (ISS) payload operations. The POIC contains the facilities, hardware, software and communication interface necessary to support payload operations. ISS ground system support for processing and display of real-time spacecraft and telemetry and command data has been operational for several years. The hardware components were reaching end of life and vendor costs were increasing while ISS budgets were becoming severely constrained. Therefore it has been necessary to migrate the Unix portions of our ground systems to commodity priced Intel-based Linux servers. hardware architecture including networks, data storage, and highly available resources. This paper will concentrate on the Linux migration implementation for the software portion of our ground system. The migration began with 3.5 million lines of code running on Unix platforms with separate servers for telemetry, command, Payload information management systems, web, system control, remote server interface and databases. The Intel-based system is scheduled to be available for initial operational use by August 2004 The overall migration to Intel-based Linux servers in the control center involves changes to the This paper will address the Linux migration study approach including the proof of concept, criticality of customer buy-in and importance of beginning with POSlX compliant code. It will focus on the development approach explaining the software lifecycle. Other aspects of development will be covered including phased implementation, interim milestones and metrics measurements and reporting mechanisms. This paper will also address the testing approach covering all levels of testing including development, development integration, IV&V, user beta testing and acceptance testing. Test results including performance numbers compared with Unix servers will be included. need for a smooth transition while maintaining real-time support. An important aspect of the paper will involve challenges and lessons learned. product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support. This paper will also address the deployment approach including user involvement in testing and the , This includes COTS product compatibility, implications of phasing decisions and tracking of dependencies, particularly non- software dependencies. The paper will also discuss scheduling challenges providing real-time flight support during the migration and the requirement to incorporate in the migration changes being made simultaneously for flight support.

Guillebeau, P. L.↗

NASA NTRSDate not supplied

Crew Health and Performance Integrated Data System Platform Project Updates

Future human exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting crew autonomy for future exploration missions. An integrated data system platform is needed to mitigate these risks by supporting a new generation of technologies and employing advanced analytical and predictive modeling techniques to enable crew autonomy for future exploration missions. The Crew Health and Performance Integrated Data System Platform (CHP-IDSP) project is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. This cohesive integration point will streamline the management of CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.) and facilitate situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the ongoing development effort of the path-to-flight CHP-IDSP software and the demonstration of its core capabilities. This includes a brief history of the project, the human-centered process used to identify data needs and workflows feeding the development of scenarios and requirements, and current subsystem development status. Current integrations, including the Chiron exploration electronic health record application, will be discussed. Future work includes collaboration with additional CHP domains and a flight technology demonstration.

Data integration↗

NASA NTRSDate not supplied

Crew Health and Performance Integrated Data Service Platform (CHP-IDSP): Project Updates

Future human exploration missions introduce a new paradigm as crews move further from the resupply and near real-time ground support typical of Low Earth Orbit missions today. Without immediate support from ground-based personnel, exploration crews will be more reliant on inflight data and technology to respond to emergencies and anomalies. Today, in-flight data is often siloed, unsynchronized, and largely inaccessible in real time. Many data sets require manual entry and/or data transfer between vehicles and the ground. These issues contribute to risks in supporting crew autonomy for future exploration missions. An integrated data services platform is needed to mitigate these risks by supporting a new generation of technologies and employing advanced analytical and predictive modeling techniques to enable crew autonomy for future exploration missions. The Crew Health and Performance Integrated Data System Platform (CHP-IDSP) project is laying a foundation for future in-flight informatics by providing a back-end architecture for collecting, storing, and integrating multiple sources of data generated by and around the crew. This cohesive integration point will streamline the management of CHP data (e.g., environmental, exercise, medical, sleep, performance, etc.) and facilitate situation awareness and decision support required by the crew and remote support of exploration missions. This presentation will describe the ongoing development effort of the path-to-flight CHP-IDSP software and the demonstration of its core capabilities. This includes a brief history of the project, the human-centered process used to identify data needs and workflows feeding the development of scenarios and requirements, and current subsystem development status. Current integrations, including the Chiron exploration electronic health record application, will be discussed. Future work includes collaboration with additional CHP domains and a flight technology demonstration.

Software↗

NASA NTRS2024

Idaho & Oregon Agriculture: Monitoring Vegetation Impacts of Livestock Management Practices Used to Reduce Predator Conflicts on Idaho and Oregon Grazing Allotments

The practice of night penning, which involves corralling livestock into a fenced, secure area overnight, aims to safeguard animals from predators. Although this method has proven successful in minimizing interactions between livestock and wildlife, the extent of its impact on vegetation communities is still being explored. This project examines the feasibility of using Net Primary Productivity (NPP) values from the Rangeland Analysis Platform (RAP) to quantify the impacts of night penning on rangeland vegetation communities. RAP provides spatially distributed values of vegetation composition, cover, and productivity, and is derived from imagery from Landsat 5, Landsat 7 & Landsat 8 at a 30m resolution for rangelands across the United States. Our DEVELOP team partnered with Alderspring Ranch, Krebs Livestock, and the U.S Department of Agriculture Animal & Plant Health Inspection Service (APHIS) to analyze the impacts of night penning on vegetation communities. We identified control sites that captured the topographic characteristics of night pen sites used by our partners. We then quantified and compared changes in annual NPP between night pen and control sites. Our analysis of RAP NPP data, using a control-treatment design did not find impacts of night penning on vegetation. However, this was a preliminary analysis, and does not conclusively quantify the impacts of night penning on rangeland vegetation. Our analysis indicated that RAP may be a feasible tool to study livestock management impacts on rangeland vegetation; however, future studies could further validate these findings through ground observations.

Rangeland Analysis Platform (RAP)↗

NASA NTRS1976

OAST Space Theme Workshop. Volume 2: Theme summary. 5: Global service (no. 11). A. Statement. B. 26 April 1976 presentation. C. Summary

The benefits to be obtained from cost-effective global observation of the earth, its environment, and its natural and man-made features are examined using typical spacecraft and missions which could enhance the benefits of space operations. The technology needs and areas of interest include: (1) a ten-fold increase in the dimensions of deployable and erectable structures to provide booms, antennas, and platforms for global sensor systems; (2) control and stabilization systems capable of pointing accuracies of 1 arc second or less to locate targets of interest and maintain platform or sensor orientation during operations; (3) a factor of five improvements in spacecraft power capacity to support payloads and supporting electronics; (4) auxiliary propulsion systems capable of 5 to 10 years on orbit operation; (5) multipurpose sensors; and (6) end-to-end data management and an information system configured to accept new components or concepts as they develop.

Source record↗

NASA NTRSDate not supplied

BioSentinel: Mission Summary and Lessons Learned From the First Deep Space Biology CubeSat Mission

Launched on Artemis-1, BioSentinel carries a biology experiment into deep space for the first time in 50 years. A 6U CubeSat form factor was utilized for the spacecraft which included technologies newly developed or adapted for operations beyond Earth orbit. The spacecraft carries onboard budding yeast, Saccharomyces cerevisiae, as an analog to human cells to test the biological response to deep space radiation. This was the maiden deep-space voyage for many of the subsystems, and the first time to evaluate their performance in flight operation. Flying a CubeSat beyond LEO comes with unique challenges with respect to trajectory uncertainty and mission operations planning. The nominal plan was a lunar fly-by, followed by an insertion into Heliocentric orbit. However, some possible scenarios included lunar eclipses that could have severely impacted the power budget during that phase of the mission, while others could have resulted in a “Retrograde” hyperbola at swing-by resulting in the spacecraft traveling inward toward Earth or even towards a collision with the lunar surface. The commissioning phase of the mission was successful and completed a week ahead of schedule. It did not come without its exciting moments and challenges. First contact with the spacecraft uncovered that the vehicle was unexpectedly tumbling after deployment, a situation that needed to be corrected urgently. The mission operations team executed a contingency plan to stabilize the spacecraft, with just moments to spare before the battery ran out of power. The BioSensor payload onboard the spacecraft is a complex instrument that includes microfluidics, fluid systems, sensor control electronics, as well at the living yeast cells. BioSentinel also included a TimePix radiation sensor implemented by JSC’s RadWorks group. Dose and Linear Energy Transfer (LET) data is compared directly to the rate of DSB-and repair events measured by the S. cerevisiae cells. BioSentinel mature nanosatellite technologies included: deep space communications and navigation, autonomous attitude control and momentum management, and micro-propulsion systems, to provide an adaptable nanosatellite platform for deep space uses. This paper discusses the performance of the BioSentinel spacecraft through the mission phase, and includes lessons learned from challenges and anomalies. BioSentinel had many successes and will be a pathfinder for future deep space CubeSats and biology missions.

BioSentinel↗

NASA NTRSDate not supplied

Biosentinel: Mission Summary and Lessons Learned From the First Deep Space Biology CubeSat Mission

Launched on Artemis-1, BioSentinel carries a biology experiment into deep space for the first time in 50 years. A 6U CubeSat form factor was utilized for the spacecraft which included technologies newly developed or adapted for operations beyond Earth orbit. The spacecraft carries onboard budding yeast, Saccharomyces cerevisiae, as an analog to human cells to test the biological response to deep space radiation. This was the maiden deep-space voyage for many of the subsystems, and the first time to evaluate their performance in flight operation. Flying a CubeSat beyond LEO comes with unique challenges with respect to trajectory uncertainty and mission operations planning. The nominal plan was a lunar fly-by, followed by an insertion into Heliocentric orbit. However, some possible scenarios included lunar eclipses that could have severely impacted the power budget during that phase of the mission, while others could have resulted in a “Retrograde” hyperbola at swing-by resulting in the spacecraft traveling inward toward Earth or even towards a collision with the lunar surface. The commissioning phase of the mission was successful and completed a week ahead of schedule. It did not come without its exciting moments and challenges. First contact with the spacecraft uncovered that the vehicle was unexpectedly tumbling after deployment, a situation that needed to be corrected urgently. The mission operations team executed a contingency plan to stabilize the spacecraft, with just moments to spare before the battery ran out of power. The BioSensor payload onboard the spacecraft is a complex instrument that includes microfluidics, fluid systems, sensor control electronics, as well at the living yeast cells. BioSentinel also included a TimePix radiation sensor implemented by JSC’s RadWorks group. Dose and Linear Energy Transfer (LET) data is compared directly to the rate of DSB-and repair events measured by the S. cerevisiae cells. BioSentinel mature nanosatellite technologies included: deep space communications and navigation, autonomous attitude control and momentum management, and micro-propulsion systems, to provide an adaptable nanosatellite platform for deep space uses. This paper discusses the performance of the BioSentinel spacecraft through the mission phase, and includes lessons learned from challenges and anomalies. BioSentinel had many successes and will be a pathfinder for future deep space CubeSats and biology missions.

BioSentinel↗

NASA NTRSDate not supplied

Biosentinel: The First Deep Space Biology CubeSat Mission- Mission Summary and Lessons Learned

Launched on Artemis-1, BioSentinel carries a biology experiment into deep space for the first time in 50 years. A 6U CubeSat form factor was utilized for the spacecraft which included technologies newly developed or adapted for operations beyond Earth orbit. The spacecraft carries onboard budding yeast, Saccharomyces cerevisiae, as an analog to human cells to test the biological response to deep space radiation. This was the maiden deep-space voyage for many of the subsystems, and the first time to evaluate their performance in flight operation. Flying a CubeSat beyond LEO comes with unique challenges with respect to trajectory uncertainty and mission operations planning. The nominal plan was a lunar fly-by, followed by an insertion into Heliocentric orbit. However, some possible scenarios included lunar eclipses that could have severely impacted the power budget during that phase of the mission, while others could have resulted in a “Retrograde” hyperbola at swing-by resulting in the spacecraft traveling inward toward Earth or even towards a collision with the lunar surface. The commissioning phase of the mission was successful and completed a week ahead of schedule. It did not come without its exciting moments and challenges. First contact with the spacecraft uncovered that the vehicle was unexpectedly tumbling after deployment, a situation that needed to be corrected urgently. The mission operations team executed a contingency plan to stabilize the spacecraft, with just moments to spare before the battery ran out of power. The BioSensor payload onboard the spacecraft is a complex instrument that includes microfluidics, fluid systems, sensor control electronics, as well at the living yeast cells. BioSentinel also included a TimePix radiation sensor implemented by JSC’s RadWorks group. Dose and Linear Energy Transfer (LET) data is compared directly to the rate of DSB-and repair events measured by the S. cerevisiae cells. BioSentinel mature nanosatellite technologies included: deep space communications and navigation, autonomous attitude control and momentum management, and micro-propulsion systems, to provide an adaptable nanosatellite platform for deep space uses. This paper discusses the performance of the BioSentinel spacecraft through the mission phase, and includes lessons learned from challenges and anomalies. BioSentinel had many successes and will be a pathfinder for future deep space CubeSats and biology missions.

BioSentinel↗

NASA NTRS2009

Work Coordination Engine

The Work Coordination Engine (WCE) is a Java application integrated into the Service Management Database (SMDB), which coordinates the dispatching and monitoring of a work order system. WCE de-queues work orders from SMDB and orchestrates the dispatching of work to a registered set of software worker applications distributed over a set of local, or remote, heterogeneous computing systems. WCE monitors the execution of work orders once dispatched, and accepts the results of the work order by storing to the SMDB persistent store. The software leverages the use of a relational database, Java Messaging System (JMS), and Web Services using Simple Object Access Protocol (SOAP) technologies to implement an efficient work-order dispatching mechanism capable of coordinating the work of multiple computer servers on various platforms working concurrently on different, or similar, types of data or algorithmic processing. Existing (legacy) applications can be wrapped with a proxy object so that no changes to the application are needed to make them available for integration into the work order system as "workers." WCE automatically reschedules work orders that fail to be executed by one server to a different server if available. From initiation to completion, the system manages the execution state of work orders and workers via a well-defined set of events, states, and actions. It allows for configurable work-order execution timeouts by work-order type. This innovation eliminates a current processing bottleneck by providing a highly scalable, distributed work-order system used to quickly generate products needed by the Deep Space Network (DSN) to support space flight operations. WCE is driven by asynchronous messages delivered via JMS indicating the availability of new work or workers. It runs completely unattended in support of the lights-out operations concept in the DSN.

Zendejas, Silvino↗

NASA NTRS2003

An On-line Technology Information System (OTIS) for Advanced Life Support

OTIS is an on-line communication platform designed for smooth flow of technology information between advanced life support (ALS) technology developers, researchers, system analysts, and managers. With pathways for efficient transfer of information, several improvements in the ALS Program will result. With OTIS, it will be possible to provide programmatic information for technology developers and researchers, technical information for analysts, and managerial decision support. OTIS is a platform that enables the effective research, development, and delivery of complex systems for life support. An electronic data collection form has been developed for the solid waste element, drafted by the Solid Waste Working Group. Forms for other elements (air revitalization, water recovery, food processing, biomass production and thermal control) will also be developed, based on lessons learned from the development of the solid waste form. All forms will be developed by consultation with other working groups, comprised of experts in the area of interest. Forms will be converted to an on-line data collection interface that technology developers will use to transfer information into OTIS. Funded technology developers will log in to OTIS annually to complete the element- specific forms for their technology. The type and amount of information requested expands as the technology readiness level (TRL) increases. The completed forms will feed into a regularly updated and maintained database that will store technology information and allow for database searching. To ensure confidentiality of proprietary information, security permissions will be customized for each user. Principal investigators of a project will be able to designate certain data as proprietary and only technical monitors of a task, ALS Management, and the principal investigator will have the ability to view this information. The typical OTIS user will be able to read all non-proprietary information about all projects.Interaction with the database will occur over encrypted connections, and data will be stored on the server in an encrypted form. Implementation of OTIS will initiate a community-accessible repository of technology development information. With OTIS, ALS element leads and managers will be able to carry out informed technology selection for programmatic decisions. OTIS will also allow analysts to make accurate evaluations of technology options. Additionally, the range and specificity of information solicited will help educate technology developers of program needs. With augmentation, OTIS reporting is capable of replacing the current fiscal year-end reporting process. Overall, the system will enable more informed R&TD decisions and more rapid attainment of ALS Program goals.

Levri, Julie A.↗

NASA NTRS1992

ASpect: A new spectrum and line analysis package for IRAF

We examined several publicly available spectral analysis software packages looking for one with enough functionality and versatility to meet the analysis needs of astronomers during the next decade. None of those examined can satisfactorily support the wide variety of panchromatic science programs that are now becoming possible. Furthermore, we concluded that none of these packages can be simply modified to include critical functions because of their original (limited) designs. During the next two years we will write a new spectral analysis package, ASpect, that will incorporate the latest analysis techniques for astronomical spectra in all wavelength domains. The ASpect package has several functional requirements. It must operate on spectra from a wide variety of ground-based and space-based instruments spanning wavelengths from radio to gamma rays. It must accommodate non-linear dispersion relations. It must provide a variety of functions, individually or in combination, with which to fit spectral features and the continuum. It is vitally important that known bad data be masked and that, uncertainties be propagated throughout the calculations in order for astronomers to evaluate the reliability of results. Finally, this new package must provide a powerful, intuitive graphical user interface to handle the burden of data input/output (I/O), on-line 'help,' selection of relevant features for analysis, plotting and graphical interaction, and data base management--all in a comprehensible environment. We anticipate that ASpect will take the form of an external package in IRAF (such as the NOAO and STSDAS packages) and will be layered upon the IRAF virtual Operating System to make it available on as many platforms as possible, while making it resistant to changes in operating systems and compilers. Our choice of IRAF is motivated by its portability, its wide use within the astronomical community, and its rich set of existing user applications.

Hulbert, S. J.↗

NASA NTRS2005

STS-114: Discovery Mission Status Briefing

Phil Engelauf, STS-114 Mission Operations Representative reports: the orbital rendezvous was successful, and today's activities includes initial preparations of the next day's extravehicular activities (EVA); he specifically mentioned tile repair, wiring on the outside of the vehicle to try to recover CMG2 (Control Moment Gyro), and preparation for the external stowage platform. John Shannon, Manager of the Space Shuttle Operations and Integration reports from Engineering standpoint that the composites of the underside of the tile surface seen from pictures taken during the pitch maneuver were extremely clean; the Engineering staff continues to look at the focus inspection data from the orbital boom sensor system (OBSS) and other data to assess the condition of the vehicle. Solid rocket boosters were retrieved and are towed back to the Air Force hangar in Cape Carneval. Six target inspection (nose gear doors, gap fillers, chine area, external tank doors, trailing edge, and ice), and arm operations, foam, conservation measures, shuttle air lock, aerodynamics assessment and re-entry were topics covered with the News media.

Source record↗