Search NASA⌕ Search

SEARCH · Search NASA

Results for “Writing”

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 883 records · Page 49

Instrumentation & Data Acquisition System (D AS) Engineer

The primary job of an Instrumentation and Data Acquisition System (DAS) Engineer is to properly measure physical phenomenon of hardware using appropriate instrumentation and DAS equipment designed to record data during a specified test of the hardware. A DAS system includes a CPU or processor, a data storage device such as a hard drive, a data communication bus such as Universal Serial Bus, software to control the DAS system processes like calibrations, recording of data and processing of data. It also includes signal conditioning amplifiers, and certain sensors for specified measurements. My internship responsibilities have included testing and adjusting Pacific Instruments Model 9355 signal conditioning amplifiers, writing and performing checkout procedures, writing and performing calibration procedures while learning the basics of instrumentation.

Jackson, Markus Deon↗

Automated ISS Flight Utilities

During my internship at NASA Johnson Space Center, I worked in the Space Radiation Analysis Group (SRAG), where I was tasked with a number of projects focused on the automation of tasks and activities related to the operation of the International Space Station (ISS). As I worked on a number of projects, I have written short sections below to give a description for each, followed by more general remarks on the internship experience. My first project is titled "General Exposure Representation EVADOSE", also known as "GEnEVADOSE". This project involved the design and development of a C++/ ROOT framework focused on radiation exposure for extravehicular activity (EVA) planning for the ISS. The utility helps mission managers plan EVAs by displaying information on the cumulative radiation doses that crew will receive during an EVA as a function of the egress time and duration of the activity. SRAG uses a utility called EVADOSE, employing a model of the space radiation environment in low Earth orbit to predict these doses, as while outside the ISS the astronauts will have less shielding from charged particles such as electrons and protons. However, EVADOSE output is cumbersome to work with, and prior to GEnEVADOSE, querying data and producing graphs of ISS trajectories and cumulative doses versus egress time required manual work in Microsoft Excel. GEnEVADOSE automates all this work, reading in EVADOSE output file(s) along with a plaintext file input by the user providing input parameters. GEnEVADOSE will output a text file containing all the necessary dosimetry for each proposed EVA egress time, for each specified EVADOSE file. It also plots cumulative dose versus egress time and the ISS trajectory, and displays all of this information in an auto-generated presentation made in LaTeX. New features have also been added, such as best-case scenarios (egress times corresponding to the least dose), interpolated curves for trajectories, and the ability to query any time in the EVADES output. As mentioned above, GEnEVADOSE makes extensive use of ROOT version 6, the data analysis framework developed at the European Organization for Nuclear Research (CERN), and the code is written to the C++11 standard (as are the other projects). My second project is the Automated Mission Reference Exposure Utility (AMREU).Unlike GEnEVADOSE, AMREU is a combination of three frameworks written in both Python and C++, also making use of ROOT (and PyROOT). Run as a combination of daily and weekly cron jobs, these macros query the SRAG database system to determine the active ISS missions, and query minute-by-minute radiation dose information from ISS-TEPC (Tissue Equivalent Proportional Counter), one of the radiation detectors onboard the ISS. Using this information, AMREU creates a corrected data set of daily radiation doses, addressing situations where TEPC may be offline or locked up by correcting doses for days with less than 95% live time (the total amount time the instrument acquires data) by averaging the past 7 days. As not all errors may be automatically detectable, AMREU also allows for manual corrections, checking an updated plaintext file each time it runs. With the corrected data, AMREU generates cumulative dose plots for each mission, and uses a Python script to generate a flight note file (.docx format) containing these plots, as well as information sections to be filled in and modified by the space weather environment officers with information specific to the week. AMREU is set up to run without requiring any user input, and it automatically archives old flight notes and information files for missions that are no longer active. My other projects involve cleaning up a large data set from the Charged Particle Directional Spectrometer (CPDS), joining together many different data sets in order to clean up information in SRAG SQL databases, and developing other automated utilities for displaying information on active solar regions, that may be used by the space weather environment officers to monitor solar activity. I consulted my mentor Dr. Ryan Rios and Dr. Kerry Lee for project requirements and added features, and ROOT developer Edmond Offermann for advice on using the ROOT library. I also received advice and feedback from Dr. Janet Barzilla of SRAG, who tested my code. Besides these inputs, I worked independently, writing all of the code by myself. The code for all these projects is documented throughout, and I have attempted to write it in a modular format. Assuming that ROOT is updated accordingly, these codes are also Y2038-compliant (and Y10K-compliant). This allows the code to be easily referenced, modified and possibly repurposed for non-ISS missions in the future, should the necessary inputs exist. These projects have taught me a lot about coding and software design - I have become a much more skilled C++ programmer and ROOT user, and I also learned to code in Python and PyROOT (and its advantages and disadvantages compared to C++/ ROOT). Furthermore, I have learned about space radiation and radiation modeling, topics that greatly interest me as I pursue a degree in physics. Working alongside experimental physicists like Dr. Rios, I have developed a greater understanding and appreciation for experimental science, something I have always leaned towards but to which I lacked significant exposure. My work in SRAG has also given me the invaluable opportunity to witness the work environment for physicists at NASA, and what a career in academia may look like at a government laboratory such as NASA Johnson Space Center. As I continue my studies and look forward to graduate school and a future career, this experience at NASA has given me a meaningful and enjoyable opportunity to put my skills to use and see what my future career path might hold.

Offermann, Jan Tuzlic↗

Electronics and Software Engineer for Robotics Project Intern

I was assigned to mentor high school students for the 2017 First Robotics Competition. Using a team based approach, I worked with the students to program the robot and applied my electrical background to build the robot from start to finish. I worked with students who had an interest in electrical engineering to teach them about voltage, current, pulse width modulation, solenoids, electromagnets, relays, DC motors, DC motor controllers, crimping and soldering electrical components, Java programming, and robotic simulation. For the simulation, we worked together to generate graphics files, write simulator description format code, operate Linux, and operate SOLIDWORKS. Upon completion of the FRC season, I transitioned over to providing full time support for the LCS hardware team. During this phase of my internship I helped my co-intern write test steps for two networking hardware DVTs , as well as run cables and update cable running lists.

Teijeiro, Antonio↗

Aperture, A Large Telescope Using Magnetostriction For Post Deployment Corrections: Final Technical Report of NASA Innovative Advanced Concepts (NIAC) Phase I

In summary, astronomical as well as Earth observing applications of the future are counting on larger aperture telescopes than are currently available. Several groups have been working on the topic of enabling large (about 16-m diameter) UV-Vis telescopes for many years. The unique feature of our concept is that magnetic films are used rather than electrostatic films or piezo-electrostatic pads. Our magnetic film concept allows for contiguous correction along the surface, does not require a hard wire connection, and does not require continuous external application of the field. There are many unknowns related to the initial accuracy of the deployed figure prior to the magnetic write head corrections. The length scale over which the corrections need to be applied is also of concern. For, although approximately mm length scale corrections can be made with the MSM plus write head technology, the number of 1 mm² patches in a 16 m diameter mirror is too large to contemplate applying individual corrections to each individual patch. However, deployment strategies and the materials available continue to evolve, in particular shape memory composites (SMCs) [34] or alloys (SMAs) [41], such that at this time we see no show-stoppers for this concept. Furthermore, the ability to tune deformations down to much (factors of 10-100) smaller (m) scale opens the futuristic possibility of improving the figure well beyond Strehl values of 90%.

APERTURE↗

Adaptive Control Law for PID

This paper is the final report for my Spring 2019 internship at the Kennedy Space Center in Cape Canaveral, Florida. The official title of my internship is 'Launch Vehicle Control Study internship,' and I spent the spring working in GMRO- Granular Mechanics and Regolith Operations. There are two components to my project involving developing an adaptive control law for a PID controller. The first component involves performing a deep study and analysis of adaptive control laws, with the goal of developing stability proofs about the control law and the gain and phase margins. The second component involves analyzing the data received after implementing the adaptive control law. Unfortunately, as of the time of writing this paper, the data is not considered ‘clean' enough to analyze. Therefore, in this paper I will give an overview of adaptive control law stability proofs and will write about the data analysis separately. Section II includes several general definitions, and the later sections have additional definitions at the end of each section.A PID (proportional integral derivative) controller is a common control algorithm which isimplemented in NASA’s rocket launch system. The idea behind the PID controller is to calculatethe error (current position – desired position) and drive it to zero by using proportional, integral,and derivative influences on the controller. For example, when a sailor steers a ship which isheading towards location 𝑥 but would like to turn the ship to reach location 𝑥∗, he/she wouldinitially turn the wheel significantly, and as the ship proceeds towards 𝑥∗ the sailor would slowlyshift the wheel back to its original position, and thereby drive the error, 𝑥∗ − 𝑥, to zero.

Eisenberg, Yael↗

Formal Requirements Elicitation with FRET

FRET is a tool for writing, understanding, formalizing and analyzing requirements. Users write requirements in an intuitive, restricted natural language, called FRETISH, with precise, unambiguous meaning. For a FRETISH requirement, FRET: 1) produces natural language and diagrammatic explanations of its exact meaning, 2) formalizes the requirement in logics, and 3) supports interactive simulation of produced logic formulas to ensure that they capture user intentions. FRET connects to analysis tools by facilitating the mapping between requirements and models/code, and by generating verification code. FRET is available open source at https://github.com/NASA-SW-VnV/fret; a video can be accessed at : https://tinyurl.com/fretForREFSQ.

Giannakopoulou, Dimitra↗

Trajectory Simulation Using Multi Model Monte Carlo with Python (MXMCPy)

EDL (Entry, Descent and Landing) is the process from a vehicle approaching a surface to landing on it, such as a Mars rover approaching the planet before landing. POST2 (Program to Optimize Simulated Trajectories 2) is Langley’s primary EDL simulation tool and is used NASA-wide for simulations. POST2 can generate highly accurate results by running a precise, but time consuming, Monte Carlo (MC) simulation hundreds or thousands of times. Though POST2 can produce highly accurate results, it can take unrealistic time spans to generate these results, which has created a need to speed up the simulations. The new NASA software MXMCPy offers various ways to speed up the simulations while getting just as precise results. Instead of running high-precision POST2 simulations many times for traditional MC, MXMCPy can run fewer high-precision POST2 simulations and many less precise POST2 simulations and merge the results. MXMCPy contains 30+ different methods which will each suggest different allocations between model precision levels, which result in results of varying precision based on the POST2 simulation. I created Python and Bash code to automate the 5 steps of MXMCPy’s application to POST2. I also tested the precision of traditional Monte Carlo simulations to MXMCPy aided simulations and found that MXMCPy can achieve substantially more precise solutions at the same computer runtime. I learned Test Driven Development (TDD), a software programming workflow which involves writing computer-automated tests before writing the code which is being tested. These tests are ran every time the code is changed and they can find glitches in the code much quicker than a human can. This programming workflow saved me a lot of time because the automated tests could tell me exactly where the code had stopped working. I plan on using this software development method for future academic and professional software projects. I have greatly enjoyed my work at NASA, so I have been applying to NASA internships and Pathways positions. In addition, I plan on applying what I have learned about Test Driven Development to my computer science courses next semester

James Warner↗

Paths of Partial Coherence: Jim Wyant’s Influence on my Profession Career

Writing a tribute paper is fraught with peril. While it is supposed to be about the other’s impact upon your life, in really it cannot help but be all about the author. Back in 2012, after my initial reluctance, the paper I wrote for the Bill Wolfe tribute[1]was so cathartic, that I had to write one for Jim Wyant–to add a chapter to my story, to explain how a path of successes and failures have lead me to the present, and in the process to exorcise more ghosts from my subconscious. While our relationship is complicated, it has always been respectful. In many regards, Jim Wyant may be one of the most important people helping me reach my potential. I am NOT ‘A’ Wyant Student. I am ‘a’ Wyant student. I took three classes from Jim: Interference and Diffraction, Holography and Optical Testing. As a result of those classes, I found something that I loved, something at which I was good, something that became apart of me–I found my technical bliss. And beyond the classroom, my professional career has been inescapably connected with Jim Wyant.

history↗

Enabling International Data Relay at Mars

The most commonly used mode of communications be-tween Earth and a Mars surface mission is ultra-high fre-quency (UHF) radio relay via a Mars orbiter. There are four orbiters and two surface rovers operating at Mars and by October there should be five orbiters and three landers or rovers. There has been some collaboration between ESA’s Mars Express orbiter and NASA’s rovers, but 2016 is when Mars relay becomes fully international. In October, ESA will deliver the ExoMars Trace Gas Orbiter (TGO) and En-try, Descent, and Landing (EDL) Demonstrator Module (EDM) lander to Mars. The ExoMars program includes both ESA and ROSCOSMOS, with NASA participation (the Electra UHF transceiver on TGO). NASA orbiters will pro-vide relay for EDM and future ESA Mars landers and rov-ers. TGO will provide relay for NASA's current and future surface assets (as Mars Express will continue to do). Inter-national collaboration is enabled in several steps. At the in-struction of the space agencies, the Mars mission projects negotiate and write a “Service Agreement.” This describes at a high level how a new Mars orbiter would operate with its corresponding surface missions or how a new surface mis-sion would operate with its corresponding orbiters. It in-cludes the roles of the different projects, how the new mis-sion would communicate with existing or planned missions, the general flow of data and commands, and the capabilities or requirements of the new mission. After completing the Service Agreement, the projects write Interface Control Doc-uments (ICDs), each of which describes data and command flow in greater detail and quantitative aspects of the relay link and operations timeline between an orbiter and a cor-responding lander/rover. Interfaces and operations are test-ed before a new mission arrives at Mars. Once at Mars, a new orbiter performs some “practice” relay contacts with its partners. For a new lander (e.g. EDM), relay operations gen-erally begin before atmospheric entry at Mars, with record-ing of the UHF relay signal from the lander (including open-loop wide-bandwidth recording) as it enters and traverses Mars’s atmosphere and lands on its surface. After Mars EDL or orbit injection, each relay contact is negotiat-ed and scheduled using the Mars Relay Operations Service (MaROS). This paper describes the international approach to develop inter-agency agreements, inter-project interfaces, and specifics of how MaROS is used in actual relay opera-tions between international partners.

Winton, Alistair J.↗

Capturing and Analyzing Requirements with FRET

FRET is an open source tool, developed at NASA Ames, for writing, understanding, formalizing, and analyzing requirements. In practice, requirements are typically written in natural language, which is ambiguous and consequently not amenable to formal analysis. Since formal, mathematical notations are unintuitive, requirements in FRET are entered in a restricted, natural language, called FRETish with precise unambiguous meaning. FRET helps users write FRETish requirements both by providing grammar information and examples during editing, but also through English and diagrammatic explanations to clarify subtle semantic issues. For each requirement, FRET automatically produces formalizations and supports interactive simulation of produced formalizations to ensure that they capture user intentions. Through its analysis portal, FRET connects to analysis tools by exporting verification code. Currently FRET connects to (1) the CoCoSim automated analysis tool for the verification of Simulink and Stateflow models, and (2) the Copilot runtime monitoring tool for the analysis of C programs. FRET also supports the consistency/realizability analysis of requirements for identifying conflicting requirements. In this tutorial, we introduce FRET and learn to speak and analyze FRETish through several examples.

FRET↗

Enabling Innovative Research on the International Space Station to Solve the Challenges of A Human Mission to Mars: Results of the ISS4Mars International Workshops 2020–2021

During the ISS4Mars workshops in 2020–2021, personnel from the International Space Station (ISS) partner agencies convened to reflect on scenarios for how the ISS could be used and its operations possibly modified to simulate aspects of a human mission to Mars. Scientific leaders, operations experts, crewmembers, managers, and flight surgeons discussed the five hazards of human spaceflight—gravity transitions, radiation, isolation and confinement, distance from Earth, and hostile closed environments—and considered how an ISS-based analog of Mars transit could benefit assessments and mitigations of these hazards. A focused writing team then discussed the advantages and disadvantages of each approach identified by the workshop participants before developing a set of eight use cases to consider the feasibility of implementing on the ISS. The writing team also identified the prerequisites needed, including ground analog studies simulating a mission to Mars required to verify measurements and procedures, before testing could begin on the ISS. Five of the use cases were considered feasible to assess in simulations using an ISS-based analog of Mars transit if some ground rules and assumptions were met. These five use cases were Earth-independent medical operations, Earth-independent integrated operations, life support and food for a one year duration, lower-body negative pressure as a countermeasure against the effects of exposure to microgravity, and fitness levels after landing. In addition, three more extensive interventions—extended Mars surface operations, a small-volume transit analog, and artificial gravity—were deemed unfeasible for testing on the ISS. Experience gained from the five use cases executed on the ISS may help answer some of the questions in the deferred scenarios, or it may be possible to complete them on another platform (e.g. commercial space station, lunar habitat). Simulating conditions during a Mars mission on the ISS will afford higher fidelity for assessing multiple integrated hazards of human spaceflight, however, ground analogs of Mars missions can be used to ensure effective measures and experimental design before testing begins on the ISS. The strategic concepts refined as part of these workshops were brought to a multilateral forum, Mulitlateral Human Research Planel for Exploration (MHRPE), where ISS partner agencies are now discussing implementation plans to provide new opportunities to use the ISS to prepare for deep space exploration over the coming decade. In this publication we present a summary of the international strategic plans for future research that will enable operations, software, and countermeasures to be developed that will reduce the risk to humans during future crewed missions to Mars.

Human space exploration↗

Equitable Letters for Space Physics

Equitable Letters in Space Physics (ELSP) is an organization that aims to encourage merit-based recommendations and nominations in the space physics community by providing resources and reviews. Recommendation and award nomination letters are a known source of bias that affect education and job opportunities, career progression, and recognition for scientists from underrepresented backgrounds. ELSP was founded to mitigate this bias within the current system by providing a proof-reading service that focuses on identifying phrasing and structure within letters that unintentionally undermines the purpose of the recommendation or nomination. If you are writing a recommendation letter for someone you know professionally, you can send it to us and we will send it out to our reviewers. They will provide recommendations on how you can make your letter more equitable and less biased, using a combination of the techniques and resources described on our site, with the aim to make unbiased recommendation letters more accessible to all. If you are interested in being a reviewer or having your writing reviewed, please reach out to us. We're a relatively young initiative and are keen to engage with and involve many diverse voices. Our website with more information, sample letters, and other resources can be found at https://equitableletterssp.github.io/ELSP/

Angeline G. Burrell↗

Atmospheric Research 2020 Technical Highlights

Welcome to the 2020 Atmospheres Highlights report. Here we summarize research and scientific communication/outreach accomplishments from the portion of atmospheric science activities at NASA’s Goddard Space Flight Center (GSFC) that comprises the Earth Science Division’s Atmospheres organization. As in previous years, this report is intended for a broad audience, including colleagues within NASA, scientists outside the Agency, science graduate students, and members of the public. Organizationally, the report covers research activities under the Office of Deputy Organizationally, the report covers research activities under the Office of Deputy Director for Atmospheres (610AT), which is within Earth Sciences Division (Code Director for Atmospheres (610AT), which is within Earth Sciences Division (Code 610) in the Sciences and Exploration Directorate (600). Laboratories and office within 610) in the Sciences and Exploration Directorate (600). Laboratories and office within 610AT include: Mesoscale Atmospheric Processes Laboratory (612), Climate and 610AT include: Mesoscale Atmospheric Processes Laboratory (612), Climate and Radiation Laboratory (613), Atmospheric Chemistry and Dynamics Laboratory (614), Radiation Laboratory (613), Atmospheric Chemistry and Dynamics Laboratory (614), and the Wallops Field Support Office (610.W). As of this writing, the 277 personnel and the Wallops Field Support Office (610.W). As of this writing, the 277 personnel in Code 610AT consist of 53 civil servants and 224 cooperative agreement associates, in Code 610AT consist of 53 civil servants and 224 cooperative agreement associates, postdoctoral fellows and contractors, postdoctoral fellows and contractors.

Annual Report↗

Flight Rule Design, Implementation, Verification, and Validation for the Psyche Mission

NASA Jet Propulsion Lab (JPL)’s upcoming mission Psyche will begin its journey to the asteroid (16) Psyche in late 2022 in an effort to better understand its origins and, in turn, better understand our own. Operating the spacecraft safely will require the dedicated efforts of a small team that understands the spacecraft’s operational constraints, as well as a set of powerful spacecraft models designed to catch command errors that can pose risks to mission success. One of the responsibilities of the operations team is to ensure adherence to a set of Flight Rules written by spacecraft and instrument experts that are designed to mitigate these risks. Psyche’s innovations in Flight Rule design principles and advancements in the tools and processes used to implement and check Flight Rules are discussed. A comparison of Psyche’s approach to Flight Rules to other JPL missions will provide lessons learned for future missions that must perform constraint checking during operations. Flight Rule development faces several major challenges. First, flight rule developers must work with Subject Matter Experts (SME) to write the rules in a way that captures the intent of the constraint in a straightforward, enforceable manner. Second, software implementers must correctly interpret flight rules into code so that it meets the original intent of the SME. Finally, a means must be provided for SMEs to validate flight rule implementations without requiring them to understand the underlying software. Innovative processes intended to efficiently close the loop between stakeholders and software developers are described, such as the use of test-driven development to provide stakeholders with easy-to-review implementations. New guidelines for flight rule writing, designed to address these challenges, are described for future missions to adopt and build upon. Psyche Mission System has a variety of new and heritage tools that improve in the Flight Rule validation and checking process. Psyche developed a powerful, new tool called RandSEQ and made significant improvements to Octopusjam, two valuable tools that aid the development of Flight Rule unit tests. Advancements in the models and processes for performing sequence validation with SEQuence GENerator (SEQGEN), the primary, high-heritage tool used for automated flight rule checks on Psyche, are described. The development of new software and the advancements to existing software put Psyche at the forefront of Flight Rule technology. All missions must perform detailed constraint checking, so a comparison of Psyche’s approach to some of these items to the approaches taken by other missions such as Dawn, M2020, and Europa Clipper is done, specifically to examine SME-developer communication, tools used, and development process. Lessons learned from this comparison will be provided.

Weise, Tim↗

On-Demand Manufacturing of Electronics

The On-Demand Manufacturing of Electronics (ODME) project develops materials, processes, and device designs to enable electronics, sensors, and semiconductors to be produced in microgravity environments. The demonstration of these technologies provides a pathway for space-based manufacturing of circuits, wearables, energy storage devices, and other electronics. This has facilitated the terrestrial production of devices including a wide range of sensors, printed batteries, and circuits that are additively manufactured using techniques available on the Advanced Toolplate System (ATS). Recent parabolic flight campaigns conducted with the ATS suggest that direct ink write (DIW) technology is suitable for depositing functional material inks in reduced gravity environments. The development of the Advanced Toolplate system also includes several other new tools, including miniaturized versions of the direct write head, fused filament fabrication head, micro-mill, component pick & place head, and two newly developed deposition technologies, the Electrohydrodynamic (EHD) inkjet head (for semiconductors), and the Electrodeposition head (for high performance circuits). These experiments are designed to compare processing and material behavior in zero gravity versus ground-based data for validation of microgravity advantages and de-risking of future orbital demonstrations of these technologies. The ability to conduct experiments in microgravity is a pivotal step in enabling electronic manufacturing technology in space for both terrestrial and deep space applications.

Cadre Francis↗

Towards a fully printable battery : robocast deposition of separators.

The development of thin batteries has presented several interesting problems which are not seen in traditional battery sizes. As the size of a battery reaches a minimum, the usable capacity of the battery decreases due to the fact that the major constituent of the battery becomes the package and separator. As the size decreases, the volumetric contribution from the package and separator increases. This can result in a reduction of capacity from these types of batteries of nearly all of the available power. The development of a method for directly printing the battery layers, including the package, in place would help to alleviate this problem. The technology used in this paper to directly print battery components is known as robocasting and is capable of direct writing of slurries in complex geometries. This method is also capable of conformally printing on three dimensional surfaces, opening up the possibility of novel batteries based on tailoring battery footprints to conform to the available substrate geometry. Interfacial resistance can also be reduced by using the direct write method. Each layer is printed in place on the battery stack instead of being stacked one at a time. This ensures an intimate contact and seal at every interface within the cell. By limiting the resistance at these interfaces, we effectively help increase the useable capacity of our battery through increase transport capability. We have developed methodology for printing several different separator materials for use in a lithium cell. When combined with a printable cathode comprised of LiFePO{sub 4} (as seen in Figure 1) and a lithium anode, our battery is capable of delivering a theoretical capacity of 170 mAh g{sup -1}. This capacity is diminished by transport phenomena within the cell which limit the transport rate of the lithium ions during the discharge cycle. The material set chosen for the printable separator closely resemble those used in commercially available separators in order to keep the transport rates high within the cell during charge and discharge. In order to evaluate the effect of each layer being printed using the robocasting technique, coin cells using printed separator materials were assembled and cycled vs. Li/Li{sup +}. This allows for the standardization of a test procedure in order to evaluate each layer of a printed cell one layer at a time. A typical charge/discharge curve can be seen in Figure 2 using a printed LiFePO{sub 4} cathode and a printed separator with a commercial Celgard separator. This experiment was run to evaluate the loss in capacity and slowdown of transport within the cell due to the addition of the printed separator. This cell was cycled multiple times and showed a capacity of 75 mAh/g. The ability for this cell to cycle with good capacity indicates that a fully printable separator material is viable for use in a full lithium cell due to the retention of capacity. Most of the fully printed cathode and separator cells exhibit working capacities between 65 and 95 mAh/g up to this point. This capacity should increase as the efficiency of the printed separator increases. The ability to deposit each layer within the cell allows for intimate contact of each layer and ensures for a reduction of interfacial impedance of each layer within the cell. The overall effect of printing multiple layers within the cell will be an overall increase in the ionic conductivity during charge and discharge cycles. Several different polymer membranes have been investigated for use as a printed separator. The disadvantage of using polymer separators or solid electrolyte batteries is that they have relatively low conductivities at room temperature (10{sup -6} - 10{sup -8} S cm{sup -1}). This is orders of magnitude lower than the typically accepted 10{sup -3} S cm{sup -1} needed for proper ionic transport during battery discharge Because of their low conductivity, typical polymer separators such as polyethylene oxide (PEO) have a normal operational temperature well above ambient. At elevated temperature the conductivity of these polymers increases. These polymer membranes are, however, ideal for printable applications due to their ease of fabrication using the robocasting process and their ability to conform to surfaces uniformly. While the ability to print cathodes and separators is advantageous as a technology, several of the components still need to be fully optimized. The overall design for the full printed lithium cell can be seen in Figure 3. The printed cathode and separator will interface with a printed anode and current collector, using the LiFePO{sub 4} cycling to plate out a metallic lithium anode on the current collector during cycling. The ability to print every layer of the cell conformally using the robocasting technique will allow for ultimate flexibility in the application of a printed battery.

74 ATOMIC AND MOLECULAR PHYSICS↗

Harmonia: A Globally Coordinated Garbage Collector for Arrays of Solid-state Drives

Solid-State Drives (SSDs) offer significant performance improvements over hard disk drives (HDD) on a number of workloads. The frequency of garbage collection (GC) activity is directly correlated with the pattern, frequency, and volume of write requests, and scheduling of GC is controlled by logic internal to the SSD. SSDs can exhibit significant performance degradations when garbage collection (GC) conflicts with an ongoing I/O request stream. When using SSDs in a RAID array, the lack of coordination of the local GC processes amplifies these performance degradations. No RAID controller or SSD available today has the technology to overcome this limitation. This paper presents Harmonia, a Global Garbage Collection (GGC) mechanism to improve response times and reduce performance variability for a RAID array of SSDs. Our proposal includes a high-level design of SSD-aware RAID controller and GGC-capable SSD devices, as well as algorithms to coordinate the global GC cycles. Our simulations show that this design improves response time and reduces performance variability for a wide variety of enterprise workloads. For bursty, write dominant workloads response time was improved by 69% while performance variability was reduced by 71%.

99 GENERAL AND MISCELLANEOUS↗

RISK COMMUNICATION FOR ES&H PROFESSIONALS AND LINE SUPERVISORS PARTICIPANT MANUAL COURSE NUMBER 004111 REV 0.1 JULY 2011

This course will help you successfully apply risk communication principles when interacting with workers regarding work hazards. What Is the Difference Between a Risk and a Hazard? In many cases, the terms 'risk' and 'hazard' are incorrectly used interchangeably. A hazard is a physical condition or practice with the potential for causing harm/adverse effects. A risk is the probability of harm/adverse effects occurring from an exposure to a hazard. It is modified by the severity of harm (the consequence). Once a hazard is identified, a risk assessment is conducted to determine the severity of the risk. It uses scientific methods and rigorous tests to determine the effects of the risk on people and the environment. Risk Management takes data from the risk assessment and writes policies to help protect people and the environment against the risk. Risk communication is an ongoing process that starts soon after a hazard is identified and continues through the writing of policies. In the past, governing agencies did not do a good job of communicating risk; they would only communicate about risk after studies had been conducted and policies written.

99 GENERAL AND MISCELLANEOUS↗