Results for “user support” — Page 13

NASA NTRS2023

Easy, Scalable Subsetting of GEDI Point Clouds

The GEDI Subsetter, a Python tool developed for NASA’s Multi-mission Algorithm and Analysis Platform (MAAP), optimizes the accessibility and visualization of GEDI point clouds by enabling users to efficiently subset data in a convenient, scalable manner. Complex science data often requires users to learn new software skills and handle many large files. Handling and cleaning large data sets is tedious and error-prone. These challenges significantly impede analysis. One of the goals of NASA's MAAP is to provide a platform that lowers the barrier to conducting research and analysis at scale. When a group of MAAP users wanted to conduct above-ground biomass estimation using GEDI data, we found that their existing workflow for leveraging GEDI data suffered from the barriers mentioned above. Furthermore, their workflow did not scale easily beyond a small number of granules. We found that existing tools related to GEDI data retrieval and subsetting were too limiting, so the GEDI Subsetter was written to support MAAP users’ needs. Being able to run many subsetting jobs simultaneously in the MAAP, and parallelizing the code itself, has led to significant speed improvements in obtaining relevant data, reducing subsetting time from hours to minutes. MAAP users can now more quickly and easily obtain only the data relevant to their research, by choosing which GEDI collection they want to work with (L1A, L2A, L2B, or L4A), and how they want to subset it, by specifying an area of interest, a temporal range, and relevant attributes. This has significantly reduced the feedback loop for users, allowing them to much more quickly subset GEDI data and begin their analysis. Although the GEDI Subsetter originally targeted users of the MAAP, it is generalized such that it can also be used outside of the MAAP and includes a command-line interface for convenience. Furthermore, with minor modifications, it should be possible to use it with non-GEDI data as the general pattern should be applicable to other sparse/track-based sensors.

Charles Daniels↗

NASA NTRS2013

An Upgrade of the Aeroheating Software "MINIVER"

Many software packages assist engineers with performing flight vehicle analysis, but some of these packages have gone many years without updates or significant improvements to their workflows. One such software, known as MINIVER, is a powerful yet lightweight tool that is used for aeroheating analyses. However, it is an aging program that has not seen major improvements within the past decade. As part of a collaborative effort with Florida Institute of Technology, MINIVER has received a major user interface overhaul, a change in program language, and will be continually receiving updates to improve its capabilities. The user interface update includes a migration from a command-line interface to that of a graphical user interface supported in the Windows operating system. The organizational structure of the preprocessor has been transformed to clearly defined categories to provide ease of data entry. Helpful tools have been incorporated, including the ability to copy sections of cases as well as a generalized importer which aids in bulk data entry. A visual trajectory editor has been included, as well as a CAD Editor which allows the user to input simplified geometries in order to generate MINIVER cases in bulk. To demonstrate its continued effectiveness, a case involving the JAXA OREX flight vehicle will be included, providing comparisons to captured flight data as well as other computational solutions. The most recent upgrade effort incorporated the use of the CAD Editor, and current efforts are investigating methods to link MINIVER projects with SINDA/Fluint and Thermal Desktop.

Louderback, Pierce M.↗

NASA NTRS2013

Challenges of Integrating NASAs Space Communication Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Reinert, Jessica M.↗

NASA NTRS2013

Challenges of Integrating NASA's Space Communications Networks

The transition to new technology, innovative ideas, and resistance to change is something that every industry experiences. Recent examples of this shift are changing to using robots in the assembly line construction of automobiles or the increasing use of robotics for medical procedures. Most often this is done with cost-reduction in mind, though ease of use for the customer is also a driver. All industries experience the push to increase efficiency of their systems; National Aeronautics and Space Administration (NASA) and the commercial space industry are no different. NASA space communication services are provided by three separately designed, developed, maintained, and operated communications networks known as the Deep Space Network (DSN), Near Earth Network (NEN) and Space Network (SN). The Space Communications and Navigation (SCaN) Program is pursuing integration of these networks and has performed a variety of architecture trade studies to determine what integration options would be the most effective in achieving a unified user mission support organization, and increase the use of common operational equipment and processes. The integration of multiple, legacy organizations and existing systems has challenges ranging from technical to cultural. The existing networks are the progeny of the very first communication and tracking capabilities implemented by NASA and the Jet Propulsion Laboratory (JPL) more than 50 years ago and have been customized to the needs of their respective user mission base. The technical challenges to integrating the networks are many, though not impossible to overcome. The three distinct networks provide the same types of services, with customizable data rates, bandwidth, frequencies, and so forth. The differences across the networks have occurred in effort to satisfy their user missions' needs. Each new requirement has made the networks more unique and harder to integrate. The cultural challenges, however, have proven to be a significant obstacle for integration. Over the past few decades of use, user missions and network personnel alike have grown accustomed to the processes by which services are provided by the NASA communications and navigation networks. The culture established by each network has created several challenges that need to be overcome in order to effectively integrate the networks. As with any change, there has been resistance, an apprehension to explore automation of existing processes, and a working environment that attempts to indirectly influence change without mandating compliance. Overcoming technical and cultural challenges is essential to successfully integrating the networks and although the challenges are numerous, the integration of the networks promises a more efficient space communications network for NASA and its customers, as well as potential long-term cost savings to the agency. This paper, Challenges of Integrating NASA Legacy Communications Networks, will provide a brief overview of the current NASA space communications networks as well as the an overview of the process implemented while performing the SCaN Trade Studies and an introduction to the requirements driving integration of the SCaN Networks. This paper will describe in detail the challenges experienced, both technical and cultural, while working with NASA space communications network-specific personnel. The paper will also cover lessons learned during the performance of architecture trade studies and provide recommendations for ways to improve the process.

Systems Integration↗

NASA NTRS2013

A Upgrade of the Aeroheating Software "MINIVER"

Many software packages assist engineers with performing flight vehicle analysis, but some of these packages have gone many years without updates or significant improvements to their workflows. One such software package, known as MINIVER, is a powerful yet lightweight tool used for aeroheating analyses. However, it is an aging program that has not seen major improvements within the past decade. As part of a collaborative effort with the Florida Institute of Technology, MINIVER has received a major user interface overhaul, a change in program language, and will be continually receiving updates to improve its capabilities. The user interface update includes a migration from a command-line interface to that of a graphical user interface supported in the Windows operating system. The organizational structure of the pre-processor has been transformed to clearly defined categories to provide ease of data entry. Helpful tools have been incorporated, including the ability to copy sections of cases as well as a generalized importer which aids in bulk data entry. A visual trajectory editor has been included, as well as a CAD Editor which allows the user to input simplified geometries in order to generate MINIVER cases in bulk. To demonstrate its continued effectiveness, a case involving the JAXA OREX flight vehicle will be included, providing comparisons to captured flight data as well as other computational solutions. The most recent upgrade effort incorporated the use of the CAD Editor, and current efforts are investigating methods to link MINIVER projects with SINDA/Fluint and Thermal Desktop.

Louderback, Pierce↗

DOE OSTI2024

Human readiness levels and Human Views as tools for user-centered design

The Human Readiness Level (HRL) scale is a simple nine-level scale that brings structure and consistency to the real-world application of user-centered design. It enables multidisciplinary consideration of human-focused elements during the system development process. Use of the standardized set of questions comprising the HRL scale results in a single human readiness number that communicates system readiness for human use. The Human Views (HVs) are part of an architecture framework that provides a repository for human-focused system information that can be used during system development to support the evaluation of HRL levels. Here, this paper illustrates how HRLs and HVs can be used in combination to support user-centered design processes. A real-world example for a U.S. Army software modernization program is described to demonstrate application of HRLs and HVs in the context of user-centered design.

42 ENGINEERING↗

DOE OSTI2024

Investigate the Security of Electric Vehicle (EV) Ecosystem Applications

Apps that run on mobile devices are one of critical components of the electric vehicle (EV) ecosystem and pose possible threat actor points of entry that may impact the trust and security of EV charging systems in the future. Mobile apps often rely on communication between cloud servers and users, thereby creating potential points of entry for cyberattacks. Although app stores such as Apple App Store or Google Play Store generally test the security of apps, the cyber aspects may not be sufficient for many entities including DOD, federal fleets, and commercial entities. A more thorough inspection and the ability to influence developers is imminently needed. This research studies security attributes and vulnerabilities of a sample of mobile applications that support key user functions in the EV ecosystem. The study shows that all analyzed apps have security risks, categorized as either high or medium or both and a comprehensive cybersecurity guideline for developing mobile apps is necessary.

33 ADVANCED PROPULSION SYSTEMS↗

NASA NTRS1973

Feasibility study of an Integrated Program for Aerospace vehicle Design (IPAD). Volume 3: Support of the design process

The user requirements for computer support of the IPAD design process are identified. The user-system interface, language, equipment, and computational requirements are considered.

Gillette, W. B.↗

NASA NTRS1983

Tracking and data acquisition system for the 1990's. Volume 8: TDAS frequency planning

Current planning calls for the TDAS to support new user and crosslink services, in addition to TDRSS-compatible services. TDRSS-compatible services would operate in current S-band and K-band channels used by TDRSS. New services, however, can take advantage of technology advances at microwave and optical frequencies. For augmented space-to-space services, 60 GHz and GaAs laser systems offer technical advantages, relative freedom from RFI, and a benign regulatory environment (i.e., minimal congestion and, in the case of 60 GHz, maximum regulatory support for TDAS-type services). For TDAS Earth-to-space and space-to-Earth services, the 30/20 GHz band offers the best mix of technical and regulatory advantages. But use of these bands would have to be coordinated with the U.S. military.

Heppe, S. B.↗

NASA NTRSDate not supplied

The Evolution of NASA’s Land, Atmosphere Near real-time Capability for Earth Observing Systems (LANCE) to Support an Increasingly Diverse Range of User Needs

NASA’s Land, Atmosphere Near Real-Time Capability for Earth Observing Systems (LANCE) supports a host of near real-time (NRT) monitoring applications from air quality to wildfires to flooding to droughts to severe storms. LANCE distributes 40-75 TB of data per week from 13 instruments to a wide range of users in over 200 countries. Most of the data and imagery served through LANCE are available within three hours of satellite overpass. Leveraging the existing NASA infrastructure and science teams has made LANCE unique in its ability to provide data from instruments onboard Earth observing satellites rapidly, accurately, and consistently. LANCE continually ensures these data are findable, readily accessible, and freely available. The evolution of LANCE is ongoing, as it strives to enable researchers and applications users to quickly incorporate the latest satellite data into their work, leading to more timely and accurate understanding of the Earth’s land and atmosphere.

Jenny Hewson↗

NASA NTRSDate not supplied

The Evolution of NASA's Land, Atmosphere Near Real-Time Capability for EOS (LANCE) to Support an Increasingly Diverse Range of User Needs

NASA’s Land, Atmosphere Near Real-Time Capability for Earth Observing Systems (LANCE) supports a host of near real-time (NRT) monitoring applications from air quality to wildfires to flooding to droughts to severe storms. LANCE distributes 40-75 TB of data per week from 13 instruments to a wide range of users in over 200 countries. Most of the data and imagery served through LANCE are available within three hours of satellite overpass. Leveraging the existing NASA infrastructure and science teams has made LANCE unique in its ability to provide data from instruments onboard Earth observing satellites rapidly, accurately, and consistently. LANCE continually ensures these data are findable, readily accessible, and freely available. The evolution of LANCE is ongoing, as it strives to enable researchers and applications users to quickly incorporate the latest satellite data into their work, leading to more timely and accurate understanding of the Earth’s land and atmosphere.

Jenny Hewson↗

DOE OSTI2025

rcsb-api : Python Toolkit for Streamlining Access to RCSB Protein Data Bank APIs

The Protein Data Bank (PDB) was founded in 1971 as the first open-access digital data resource in biology to serve as the single global archive for three-dimensional (3D) macromolecular structure data. Current PDB holdings exceed 230,000 experimentally determined structures of proteins, nucleic acids, viruses, and macromolecular machines. The RCSB Protein Data Bank RCSB.org research-focused web portal facilitates search, analyses, and visualization of every PDB structure along with more than one million Computed Structure Models from AlphaFold DB and the ModelArchive. It is powered by a set of publicly available Application Programming Interfaces (APIs) that both support RCSB.org users and provide programmatic access to PDB data. Given the breadth and levels of granularity encompassed in this rich data collection, efficiently accessing the information programmatically may be challenging for new users. RCSB PDB has developed a Python software package, rcsb-api , that facilitates easy and efficient use of RCSB PDB APIs within a Python environment. This software tool is designed to streamline access to the extensive corpus of data housed within the PDB, enabling researchers to search, retrieve, and analyze 3D biostructure data seamlessly. Its use will accelerate research in structural biology, molecular biology and biochemistry, drug discovery, and bioinformatics by providing more efficient tools for data integration and analysis. The new toolkit is available on GitHub (github.com/rcsb/py-rcsb-api) and published to the public Python package repository (PyPI) to foster wider usage and support basic and applied research in fundamental biology, biomedicine, and the energy sciences.

FAIR principles↗

NASA NTRS2018

Use of Nack Oriented Reliable Multicast (NORM) Protocol for Transport of Spacecraft Telemetry in Ground Networks

Frequently it is necessary to distribute spacecraft telemetry to multiple destinations on Internet Protocol (IP) networks. There are various methods of delivering this data, but when the data is high rate and there are many destinations IP multicast provides the best solution from a network perspective. However, IP multicast only supports the User Datagram Protocol (UDP) which is connectionless and unreliable. This nature of UDP and by extension the low priority treatment of UDP packets by some network hardware creates a difficult environment for distribution of high rate telemetry to a number of recipients over IP networks. NACK (Negative ACKnowledgment) Oriented Reliable Multicast (NORM) is defined by IETF (Internet Engineering Task Force) RFC (Request for Comments) 5740 in 2009 by B. Adamson et al. NORM provides a mechanism of retransmission and or forward error correction for UDP packets, potentially overcoming the limits of UDP for the transmission of spacecraft telemetry. Marshall Space Flight Center’s (MSFC) Huntsville Operations Support Center (HOSC) manages the delivery of the International Space Station (ISS) payload science and health data. The ISS IP Ground Routed (IIGoR) network provides the delivery of the data from the ground stations to the control centers. HOSC personnel have been experimenting with the use of NORM on the link between the ground stations and the front end processor equipment in Huntsville, AL.

Baldwin, Patrick A.↗

DOE OSTI2023

Accelerator Physics at NSLS-II: Research Accomplishments in 2023

NSLS-II accelerator physicists provided operation support for user operations and machine start-ups, carried out routine lattice characterization, and produced regular reports on beam dynamics. The commissioning of a superconducting wiggler for the HEX beamline is complete, and the wiggler effects on beam dynamics have been studied. A Facility Improvement Project for absolute lattice characterization has been approved and funded. We implemented and tested a new orbit-based technique of lattice characterization and correction. We developed a theory to calculate the beam-induced power in ceramic vacuum chambers and a new convergence map technique for nonlinear lattice characterization. We continued working on the NSLS-II upgrade including lattice development, commissioning a low-energy complex bend prototype, analyzing beam sensitivity to various errors, implementing higher-harmonic RF cavities, studying collective effects, and assessing FEL options. We also supported lattice optimization and beam diagnostics development for the EIC project. Main research accomplishments achieved in 2023, are summarized in this report.

43 PARTICLE ACCELERATORS↗

DOE OSTI2021

Utilizing Additive Manufacturing to Create Prototype and Functional Beamline Instrumentation and Support Components

The world of beamline science is often fast-paced and dynamic. One of the major challenges in this environment is to be able to design, manufacture and then implement new items for use on the beamlines in a fast and accurate manner. Many times, this involves iterating the design to address unknown or new variables which were not pre- sent at the beginning of the project planning task. Through the use of additive manufacturing, I have been able to support the user programs of various (APS) Ad- vanced Photon Source beamlines* across multiple scien- tific disciplines. I will provide a few detailed examples of Items that were created for specific beamline applications and discuss what benefits they provided to the pertinent project. I will also talk about why choosing consumer- level printer options to produce the parts has been the direction I went and the pros and cons of this decision. Pri marily, this choice allowed for quicker turnaround times and the ability to make more frequent changes in an efficient manner. Currently, we are utilizing only the fused deposition modelling (FDM) type printers but I am exploring the addition of UV-activated resin printing, exotic materials that can be utilized using the current toolset, and the possibility of commercial metal printing systems. This technology has been a game-changer for the implementation of new support items and instrumentation over the last couple of years for the different disciplines I am sup- porting. I will discuss how the roadmap ahead and what the evolving technologies could potentially allow us to do.

Jensen, D.↗

NASA NTRS2016

Launch Pad in a Box

NASA Kennedy Space Center (KSC) is developing a new deployable launch system capability to support a small class of launch vehicles for NASA and commercial space companies to test and launch their vehicles. The deployable launch pad concept was first demonstrated on a smaller scale at KSC in 2012 in support of NASA Johnson Space Center's Morpheus Lander Project. The main objective of the Morpheus Project was to test a prototype planetary lander as a vertical takeoff and landing test-bed for advanced spacecraft technologies using a hazard field that KSC had constructed at the Shuttle Landing Facility (SLF). A steel pad for launch or landing was constructed using a modular design that allowed it to be reconfigurable and expandable. A steel flame trench was designed as an optional module that could be easily inserted in place of any modular steel plate component. The concept of a transportable modular launch and landing pad may also be applicable to planetary surfaces where the effects of rocket exhaust plume on surface regolith is problematic for hardware on the surface that may either be damaged by direct impact of high speed dust particles, or impaired by the accumulation of dust (e.g., solar array panels and thermal radiators). During the Morpheus free flight campaign in 2013-14, KSC performed two studies related to rocket plume effects. One study compared four different thermal ablatives that were applied to the interior of a steel flame trench that KSC had designed and built. The second study monitored the erosion of a concrete landing pad following each landing of the Morpheus vehicle on the same pad located in the hazard field. All surfaces of a portable flame trench that could be directly exposed to hot gas during launch of the Morpheus vehicle were coated with four types of ablatives. All ablative products had been tested by NASA KSC and/or the manufacturer. The ablative thicknesses were measured periodically following the twelve Morpheus free flight tests. The thermal energy from the Morpheus rocket exhaust plume was only found to be sufficient to cause appreciable ablation of one of the four ablatives that were tested. The rocket exhaust plume did cause spalling of concrete during each descent and landing on a landing pad in the hazard field. The Extended Abstract ASE Earth and Space Conference April, 2016 - Orlando, FL concrete surface was laser scanned following each Morpheus landing, and the total volume of spalled concrete that eroded between the first and final landings of the Morpheus Project's test campaign was estimated. This paper will also describe a new deployable launch system (DLS) capability that is being developed at KSC and was publicly announced in May 2015 (KSC Partnerships, 2015). The DLS is a set of multi-user Ground Support Equipment that will be used to test and launch small class launch vehicles. The system is comprised of four main elements: the Launch Stand, the Flame Deflector, the Pad Apron and the KAMAG transporter. The system elements are designed to be deployed at launch or test sites within the KSC/CCAFS boundaries. The DLS is intended to be used together with the Fluid and Electrical System of the Universal Propellant Servicing Systems and Mobile Power Data and Communications Unit.

Ablatives Testing↗

NASA NTRS2016

Launch Pad in a Box

NASA Kennedy Space Center (KSC) is developing a new deployable launch system capability to support a small class of launch vehicles for NASA and commercial space companies to test and launch their vehicles. The deployable launch pad concept was first demonstrated on a smaller scale at KSC in 2012 in support of NASA Johnson Space Center's Morpheus Lander Project. The main objective of the Morpheus Project was to test a prototype planetary lander as a vertical takeoff and landing test-bed for advanced spacecraft technologies using a hazard field that KSC had constructed at the Shuttle Landing Facility (SLF). A steel pad for launch or landing was constructed using a modular design that allowed it to be reconfigurable and expandable. A steel flame trench was designed as an optional module that could be easily inserted in place of any modular steel plate component. The concept of a transportable modular launch and landing pad may also be applicable to planetary surfaces where the effects of rocket exhaust plume on surface regolith is problematic for hardware on the surface that may either be damaged by direct impact of high speed dust particles, or impaired by the accumulation of dust (e.g., solar array panels and thermal radiators). During the Morpheus free flight campaign in 2013-14, KSC performed two studies related to rocket plume effects. One study compared four different thermal ablatives that were applied to the interior of a steel flame trench that KSC had designed and built. The second study monitored the erosion of a concrete landing pad following each landing of the Morpheus vehicle on the same pad located in the hazard field. All surfaces of a portable flame trench that could be directly exposed to hot gas during launch of the Morpheus vehicle were coated with four types of ablatives. All ablative products had been tested by NASA KSC and/or the manufacturer. The ablative thicknesses were measured periodically following the twelve Morpheus free flight tests. The thermal energy from the Morpheus rocket exhaust plume was only found to be sufficient to cause appreciable ablation of one of the four ablatives that were tested. The rocket exhaust plume did cause spalling of concrete during each descent and landing on a landing pad in the hazard field. The Extended Abstract ASE Earth and Space Conference April, 2016 - Orlando, FL concrete surface was laser scanned following each Morpheus landing, and the total volume of spalled concrete that eroded between the first and final landings of the Morpheus Project's test campaign was estimated. This paper will also describe a new deployable launch system (DLS) capability that is being developed at KSC and was publicly announced in May 2015 (KSC Partnerships, 2015). The DLS is a set of multi-user Ground Support Equipment that will be used to test and launch small class launch vehicles. The system is comprised of four main elements: the Launch Stand, the Flame Deflector, the Pad Apron and the KAMAG transporter. The system elements are designed to be deployed at launch or test sites within the KSC/CCAFS boundaries. The DLS is intended to be used together with the Fluid and Electrical System of the Universal Propellant Servicing Systems and Mobile Power Data and Communications Unit

Mobile Launch Pad Development↗

DOE OSTI2022

The IMG/M data management and analysis system v.7: content updates and new features

The Integrated Microbial Genomes & Microbiomes system at the Department of Energy (DOE) Joint Genome Institute (JGI) continues to provide support for users to perform comparative analysis of isolate and single cell genomes, metagenomes, and metatranscriptomes. In addition to datasets produced by the JGI, IMG v.7 also includes datasets imported from public sources such as NCBI Genbank, SRA, and the DOE National Microbiome Data Collaborative (NMDC), or submitted by external users. In the past couple years, we have continued our effort to help the user community by improving the annotation pipeline, upgrading the contents with new reference database versions, and adding new analysis functionalities such as advanced scaffold search, Average Nucleotide Identity (ANI) for high-quality metagenome bins, new cassette search, improved gene neighborhood display, and improvements to metatranscriptome data display and analysis. Here, we also extended the collaboration and integration efforts with other DOE-funded projects such as NMDC and DOE Biology Knowledgebase (KBase).

59 BASIC BIOLOGICAL SCIENCES↗