Search NASA⌕ Search

SEARCH · Search NASA

Results for “PEP”

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

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

At least 19 records

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 3: PEP analysis and tradeoffs

The objectives, conclusions, and approaches for accomplishing 19 specific design and analysis activities related to the installation of the power extension package (PEP) into the Orbiter cargo bay are described as well as those related to its deployment, extension, and retraction. The proposed cable handling system designed to transmit power from PEP to the Orbiter by way of the shuttle remote manipulator system is described and a preliminary specification for the gimbal assembly, solar array drive is included.

Source record↗

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 4: PEP functional specification

The functional, performance, design, and test requirements for the Orbiter power extension package and its associated ground support equipment are defined. Both government and nongovernment standards and specifications are cited for the following subsystems: electrical power, structural/mechanical, avionics, and thermal control. Quality control assurance provisions and preparation for delivery are also discussed.

Source record↗

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 5: PEP environmental specification

This specification establishes the natural and induced environments to which the power extension package may be exposed during ground operations and space operations with the shuttle system. Space induced environments are applicable at the Orbiter attach point interface location. All probable environments are systematically listed according to each ground and mission phase.

Source record↗

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 7: PEP logistics and training plan requirements

Recommendations for logistics activities and logistics planning are presented based on the assumption that a system prime contractor will perform logistics functions to support all program hardware and will implement a logistics system to include the planning and provision of products and services to assure cost effective coverage of the following: maintainability; maintenance; spares and supply support; fuels; pressurants and fluids; operations and maintenance documentation training; preservation, packaging and packing; transportation and handling; storage; and logistics management information reporting. The training courses, manpower, materials, and training aids required will be identified and implemented in a training program.

Source record↗

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 12: PEP data item descriptions

Contractor information requirements necessary to support the power extension package project of the space shuttle program are specified for the following categories of data: project management; configuration management; systems engineering and test; manufacturing; reliability, quality assurance and safety; logistics; training; and operations.

Source record↗

Advanced Utilization of the Payload Executive Processor (PEP) Ethernet Port to Support JSL Based Payloads

Increased interest by Payload Developers in utilization of the Joint Station LAN (Local Area Network) (JSL) for command and data transactions has driven the investigation of providing bi-directional Ethernet communication with PEP (Payload Executive Processor). Ethernet-only payload developers are interested in taking advantage of the services provided by PEP. Enabling Ethernet communications within PEP requires more than just turning on the hardware. PEP contains no Operating System (OS) or Ethernet stack so it does not inherit any built in functionality for Ethernet support. Both hardware drivers and application software must be developed from scratch. In the absence of an OS (Operating System) the design must address security issues in terms of access and data transferred, i.e. blocking unauthorized users and preventing denial of service. Developing a design to process Ethernet data within the existing real-time constraints of PEP requires a few compromises: data rates, supported protocols, custom packet format and limited client connections to name a few. Integration of the light weight internet protocol (LwIP). Ethernet stack provides a customizable solution for the embedded real-time environment. As utilization of the JSL increases, the successful implementation of an Ethernet interface enhances the utilization of PEP, and provides a new path for future Ethernet-only payloads to gain access to around the clock command and data services.

Guyette, Greg↗

A PEPS Plugin for TNQVM

This work introduces an extension to the Tensor Network Quantum Virtual Machine (TNQVM) tool, enhancing the existing stack of ExaScale Tensor Network (ExaTN), ExaScale Accelerator (XACC), and TNQVM. It features a new plugin that enables efficient simulation of a Projected Entangled Pair State (PEPS), a 2D tensor network. To improve simulation efficiency for PEPS, we have implemented the snake boundary contraction algorithm. By integrating this capability into the existing stack, we enhance the overall functionality and versatility of the framework. We tested this new PEPS topology for a simple GHZ bell-pair generation quantum circuit and saw that its runtime is very close to that of the MPS topology. We estimate that the real potential of the PEPS topology becomes discernible when quantum circuits with multidimensional entanglement are simulated using tensor networks. In such cases, 1D tensor networks fail to represent or contract them efficiently.

Chundury, Srikar↗

Power Extension Package (PEP) system definition extension, orbital service module systems analysis study. Volume 1: Executive summary

An array deployment assembly, power regulation and control assembly, the necessary interface, and display and control equipment comprise the power extension package (PEP) which is designed to provide increased power and duration, as well as reduce fuel cell cryogen consumption during Spacelab missions. Compatible with all currently defined missions and payloads, PEP imposes minimal weight and volume penalties on sortie missions, and can be installed and removed as needed at the launch site within the normal Orbiter turnaround cycle. The technology on which it is based consists of a modified solar electric propulsion array, standard design regulator and control equipment, and a minimally modified Orbiter design. The requirements from which PEP was derived, and the system and its performance capabilities are described. Features of the recommended project are presented.

Source record↗

Simulating Large PEPs Tensor Networks on Small Quantum Devices

We systematically map low bond dimension PEPs tensor networks to quantum circuits. By measuring and reusing qubits, we are in principle able to simulate an N×M square lattice PEPs network (for arbitrary M) of bond dimension 2 using N+ 2 qubits. We then seek to determine if this mapping can yield useful values for long-range loop observables in the presence of quantum device noise in the topological Wen plaquette model by mapping a 3×3 PEPs tensor network to a 5-qubit quantum circuit and executing it on the Honeywell System Model H1-1 trapped-ion device. We find that, for this system size, the noisy observable values are indeed sufficient for diagnosing topological vs. trivial order as the Wen model is perturbed by a magnetic field term in the Hamiltonian. We provide an overview of the experimental procedure and its results. We then explain in greater detail our method for mapping 2D tensor networks to quantum circuits and its scaling properties. This serves as a proof-of-concept of the utilty of the measure-and-reuse approach for simulating large 2D quantum systems on small quantum devices.

MacCormack, Ian↗

PEP solar array definition study

The power extension package (PEP) is a solar array system that will be used on the space transportation system to augment the power of the Orbiter vehicle and to extend the time the vehicle may stay in orbit. The baseline configuration of the PEP is reviewed. The programmatic aspects of the design covering the development plan, the manufacturing facility plan and the estimated costs and risks are presented.

Source record↗

Implementing Ethernet Services on the Payload Executive Processor (PEP)

The Ethernet interface is more common and easier interface to implement for payload developers already familiar with Ethernet protocol in their labs. The Ethernet interface allows for a more distributed payload architecture. Connections can be placed in locations not serviced by the PEP 1553 bus. The Ethernet interface provides a new access port into the PEP so as to use the already existing services. Initial capability will include a subset of services with a plan to expand services later.

Pruett, David↗

The Herschel* PEP-HERMES Luminosity Function- I. Probing the Evolution of PACS Selected Galaxies to z approx. equal to 4

We exploit the deep and extended far-IR data sets (at 70, 100 and 160 μm) of the Herschel Guaranteed Time Observation (GTO) PACS Evolutionary Probe (PEP) Survey, in combination with the Herschel Multi-tiered Extragalactic Survey data at 250, 350 and 500 μm, to derive the evolution of the rest-frame 35-, 60-, 90- and total infrared (IR) luminosity functions (LFs) up to z ∼ 4.We detect very strong luminosity evolution for the total IR LF (LIR ∝ (1 + z)(sup 3.55 +/- 0.10) up to z ∼ 2, and ∝ (1 + z)(sup 1.62 +/- 0.51) at 2 less than z less than approximately 4) combined with a density evolution (∝ (1 + z)(sup −0.57 +/- 0.22) up to z ∼ 1 and ∝ (1 + z)(sup −3.92 +/- 0.34) at 1 less than z less than approximately 4). In agreement with previous findings, the IR luminosity density (ρIR) increases steeply to z ∼ 1, then flattens between z ∼ 1 and z ∼ 3 to decrease at z greater than approximately 3. Galaxies with different spectral energy distributions, masses and specific star formation rates (SFRs) evolve in very different ways and this large and deep statistical sample is the first one allowing us to separately study the different evolutionary behaviours of the individual IR populations contributing to ρIR. Galaxies occupying the well-established SFR-stellar mass main sequence (MS) are found to dominate both the total IR LF and ρIR at all redshifts, with the contribution from off-MS sources (≥0.6 dex above MS) being nearly constant (∼20 per cent of the total ρIR) and showing no significant signs of increase with increasing z over the whole 0.8 < z <2.2 range. Sources with mass in the range 10 ≤ log(M/solar mass) ≤ 11 are found to dominate the total IR LF, with more massive galaxies prevailing at the bright end of the high-z (greater than approximately 2) LF. A two-fold evolutionary scheme for IR galaxies is envisaged: on the one hand, a starburst-dominated phase in which the Super Massive Black Holes (SMBH) grows and is obscured by dust (possibly triggered by a major merging event), is followed by an AGN-dominated phase, then evolving towards a local elliptical. On the other hand, moderately star-forming galaxies containing a low-luminosity AGN have various properties suggesting they are good candidates for systems in a transition phase preceding the formation of steady spiral galaxies.

Herschel↗