Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Notes”

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 1,333 records · Page 74
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

Surviving High-temperature Components in CI Chondrites

The CI1 chondrites, while having the most solar-like compo-sition of any astromaterial available for laboratory analysis, have also been considerably altered by asteroidal processes including aqueous alteration. It is of fundamental importance to determine their pre-alteration mineralogy, so that the state of matter in the early Solar System can be better determined. In the course of a re-examination of the compositional range of olivine and low-Ca pyroxene in CI chondrites Orgueil, Ivuna and Alais [1] we found the first reported complete CAI, as already reported [2], with at-tached rock consisting mainly of olivine and low-Ca pyroxene. The range of residual olivine major element compositions we have determined in the CIs (Fig. 1) may now be directly com-pared with those of other astromaterials, including Wild 2 grains. The abundance of olivine and low-Ca pyroxene in CIs is higher than is generally appreciated, and in fact much higher than for some CMs [1]. We also noted numerous rounded objects varying in shape from spheres to oblate spheroids, and ranging up to 100μm in size (Fig. 2), which have been previously noted [3] but have not been well documented or appreciated. We characterized the mineralogy by transmission electron microscopy and found that they consist mainly of rather fine-grained, flaky single phase to intergrown serpentine and saponite. These two materials in fact dominate the bulk of the host CI1 chondrites. With the exception of sparse spinels, the rounded phyllosilicate objects are remarka-bly free of other minerals, suggesting that the precursor from which the phyllosilicates were derived was a homogeneous mate-rial. We suggest that these round phyllosilicates aggregates in CI1 chondrites were cryptocrystalline to glassy microchondrules. If so then CI chondrites cannot be considered chondrule-free. Small though they are, the abundance of these putative microchondrules is the same as that of chondrules in the Tagish Lake meteorite.

Zolensky, M.↗
NASA NTRS2015

Enhanced Cleaning of Genesis Solar Wind Sample 61348 for Film Residue Removal

The Genesis mission returned to Earth on September 8, 2004, experiencing a nonnominal reentry. During the recovery of the collector materials from the capsule, many of the collector fragments were placed on the adhesive protion of post-it notes to prevent the fragments from moving during transport back to Johnson Space Center. This unknowingly provided an additional contaminate that would prove difficult to remove with the limited chemistries allowed in the Genesis Curation Laboratory. Generally when collector material samples are prepared for allocation to PIs, the samples are cleaned front side only with Ultra-Pure Water (UPW) via megasonic dispersion to the collector surface to remove crash debris and contamination. While this cleaning method works well on samples that were not placed on post-its during recovery, it has caused movement of the residue on the back of the sample to be deposited on the front in at least two examples. Therefore, samples placed on the adhesive portion on post-it note, require enhanced cleaning methods since post-it residue has proved resistant to UPW cleaning.

Allums, K. K.↗
NASA NTRS2015

Multiple Absorption Components in the Post-Periastron He I P Cygni Absorption Troughs of Eta Carinae

We have obtained more than 100 high spectral resolution (R approx. 90,000) spectra of the massive binary star eta Carinae since 2012 in an effort to continue our orbital and long-term echelle monitoring of this extreme binary (Richardson et al. 2010, AJ, 139, 1534) with the CHIRON spectrograph on the CTIO 1.5 m telescope (Tokovinin et al. 2013, PASP, 125, 1336) in the 4550-7500A region. We increased our monitoring efforts and observation frequency as the periastron event of 2014 has approached, and resumed observations in October. We note that since mid-October, we have observed unusual multiple absorption components in the P Cygni troughs of the He I lines (4714, 5876, 6678, and 7065; 4921 and 5015 are blended with Fe II). In particular, we note that these components extend to -700 km/s, well beyond the terminal wind speed of the primary. These absorptions are likely related to clumps and turbulence in the wind-wind collision region and bow shock, as suggested by the high-velocity absorption observed by Groh et al. (2010, A&A, 519, 9) in the He I 10830A transition and our pre-periastron observations (Richardson et al. 2014, ATel #6336). In these cases, we suspect that we look along an arm of the shock cone and that we see a fast absorption change from the other collision region shortly after periastron. Further, high spectral resolution data are highly encouraged, especially for resolving powers greater than 50,000. These observations were obtained with the CTIO 1.5 m telescope, operated by the SMARTS Consortium, and were obtained through both SMARTS and NOAO programs 2012A-0216, 2012B-0194, and 2013b-0328. We thank Emily MacPherson (Yale) for her efforts in scheduling the observations that we have and will obtain in the coming weeks and months.

multiple absorption components↗
NASA NTRS2008

Delay-Tolerant Networking for Space Flight Operations: Design and Development

Interplanetary Overlay Network (ION) is an implementation of the Delay-Tolerant Networking (DTN) architecture that is specifically intended to be usable for interplanetary communications. As such, its design differs in several ways from that of other implementations including DTN2, the reference implementation of the DTN Bundle Protocol. This paper briefly reviews the constraints on interplanetary communication that argue against the suitability not only of most off-the-shelf Internet technology but also of many DTN implementations. It then describes the operational components of ION, including its implementations of both the Bundle Protocol and the Licklider Transmission Protocol, noting the ways in which they address those constraints. Features of the system are explained with reference to their counterparts in the Internet architecture. The paper concludes with some notes on ION testing experience to date and plans for additional development in the future.

Interplanetary Overlay Network (ION)↗
NASA NTRS2008

Web Based Tool for Mission Operations Scenarios

A conventional practice for spaceflight projects is to document scenarios in a monolithic Operations Concept document. Such documents can be hundreds of pages long and may require laborious updates. Software development practice utilizes scenarios in the form of smaller, individual use cases, which are often structured and managed using UML. We have developed a process and a web-based scenario tool that utilizes a similar philosophy of smaller, more compact scenarios (but avoids the formality of UML). The need for a scenario process and tool became apparent during the authors' work on a large astrophysics mission. It was noted that every phase of the Mission (e.g., formulation, design, verification and validation, and operations) looked back to scenarios to assess completeness of requirements and design. It was also noted that terminology needed to be clarified and structured to assure communication across all levels of the project. Attempts to manage, communicate, and evolve scenarios at all levels of a project using conventional tools (e.g., Excel) and methods (Scenario Working Group meetings) were not effective given limitations on budget and staffing. The objective of this paper is to document the scenario process and tool created to offer projects a low-cost capability to create, communicate, manage, and evolve scenarios throughout project development. The process and tool have the further benefit of allowing the association of requirements with particular scenarios, establishing and viewing relationships between higher- and lower-level scenarios, and the ability to place all scenarios in a shared context. The resulting structured set of scenarios is widely visible (using a web browser), easily updated, and can be searched according to various criteria including the level (e.g., Project, System, and Team) and Mission Phase. Scenarios are maintained in a web-accessible environment that provides a structured set of scenario fields and allows for maximum visibility across the project. One key aspect is that the tool was built for a scenario process that accounts for stakeholder input, review, comment, and concurrence. By creating well-designed opportunities for stakeholder input and concurrence and by making the scenario content easily accessible to all project personnel, we maximize the opportunities for stakeholders to both understand and agree on the concepts for how their mission is to be carried out.

Boyles, Carole A.↗
NASA NTRS2016

CO2 on the International Space Station: An Operations Update

PROBLEM STATEMENT: We describe CO2 symptoms that have been reported recently by crewmembers on the International Space Station and our continuing efforts to control CO2 to lower levels than historically accepted. BACKGROUND: Throughout the International Space Station (ISS) program, anecdotal reports have suggested that crewmembers develop CO2-related symptoms at lower CO2 levels than would be expected terrestrially. Since 2010, operational limits have controlled the 24-hour average CO2 to 4.0 mm Hg, or below as driven by crew symptomatology. In recent years, largely due to increasing awareness by crew and ground team, there have been increased reports of crew symptoms. The aim of this presentation is to discuss recent observations and operational impacts to lower CO2 levels on the ISS. CASE PRESENTATION: Crewmembers are routinely asked about CO2 symptoms in their weekly private medical conferences with their crew surgeons. In recent ISS expeditions, crewmembers have noted symptoms attributable to CO2 starting at 2.3 mmHg. Between 2.3 - 2.7 mm Hg, fatigue and full-headedness have been reported. Between 2.7 - 3.0 mm Hg, there have been self-reports of procedure missed steps or procedures going long. Above 3.0 - 3.4 mm Hg, headaches have been reported. A wide range of inter- and intra-individual variability in sensitivity to CO2 have been noted. OPERATIONAL / CLINICAL RELEVANCE: These preliminary data provide semi-quantitative ranges that have been used to inform a new operational limit of 3.0 mmHg as a compromise between systems capabilities and the recognition that there are human health and performance impacts at recent ISS CO2 levels. Current evidence would suggest that an operational limit between 0.5 and 2.0 mm Hg may maintain health and performance. Future work is needed to establish long-term ISS and future vehicle operational limits.

Law, Jennifer↗
NASA NTRS2015

[Fall 2015 Abstract by Stephanie Scharf]

This Fall I worked on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the Branch. The purpose of this document is to create a standard process and ensure that the data is collected in the same way, no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own, all while taking notes on the procedure. These notes were used to write the final work instruction, which will become the Branch standard. My second project continued the work of the Summer co-op before me. I tested aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks had been designed by the previous Summer co-op, but there was not much time for testing before he left. We thus ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (Energy Systems Test Area) and are providing very promising results, indicating that safe, high performing (>180 Wh/kg) designs are possible. My main project was a redesign of the LLB (Lightweight Lithium Battery). Another summer intern had done some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the existing design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density, and the rest of the design was up to me. First, I created new heat sink banks in CREO, using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place, and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve > 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options for cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan was to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Cutting open a cell for DPA After photo from oven heat-to-vent test

Scharf, Stephanie↗
NASA NTRS2015

[Redesign of the Spacesuit Long Life Battery and the Personal Life Support System Battery]

This fall I was working on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the department. The purpose of this document is to create a standard process and ensure that the data in the same way no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own all while taking notes on the procedure. These notes were used to write the final work instruction that will become is the department standard. My second project continued the work of the summer co-op before me. I was testing aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks were designed by the summer intern but there was not much time for testing before he left. We ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (energy systems test area) and are providing very promising results that safe, high performing (greater than 180 Wh/kg) designs are possible. My main project was a redesign of the LLB battery. Another summer intern did some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the current design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density and the rest of the design was up to me. First, I created new heat sink banks in Creo using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve greater than 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options of cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan is to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Some of my side projects included working on the CAD data for the PLSS with EC and attending the NASA Aerospace Battery Workshop in Huntsville. I was also a member of the Tours and Lectures Committee for the USRA and Pathways interns. I coordinated Apollo Evening and was on the committee for touring KSC and seeing an Atlas 5 launch. I really enjoyed my time at JSC and I would like to continue working for NASA or another aerospace company in the future. I have worked other internships prior to this, but I think the heavy research and development focus is the best fit for me. I originally thought I would need to go to grad school to work in an environment like this, but I now see it is possible with a bachelor’s degree and hard work. I would like to go into the workforce and maybe continue my education with night classes.

Scharf, Stephanie↗
NASA NTRS2016

Forward Skirt Structural Testing on the Space Launch System (SLS) Program

Structural testing was performed to evaluate heritage forward skirts from the Space Shuttle program for use on the Space Launch System (SLS) program. One forward skirt is located in each solid rocket booster. Heritage forward skirts are aluminum 2219 welded structures. Loads are applied at the forward skirt thrust post and ball assembly. Testing was needed because SLS ascent loads are roughly 40% higher than Space Shuttle loads. Testing objectives were to determine margins of safety, demonstrate reliability, and validate analytical models. Two forward skirts were structurally tested using the test configuration. The test stand applied loads to the thrust post. Four hydraulic actuators were used to apply axial load and two hydraulic actuators were used to apply radial and tangential loads. The first test was referred to as FSTA-1 (Forward Skirt Structural Test Article) and was performed in April/May 2014. The purpose of FSTA-1 was to verify the ultimate capability of the forward skirt subjected to ascent ultimate loads. Testing consisted of two liftoff load cases taken to 100% limit load followed by an ascent load case taken to 110% limit load. The forward skirt was unloaded to no load after each test case. Lastly, the forward skirt was tested to 140% limit and then to failure using the ascent loads. The second test was referred to as FSTA-2 and performed in July/August of 2014. The purpose of FSTA-2 was to verify the ultimate capability of the forward skirt subjected to liftoff ultimate loads. Testing consisted of six liftoff load cases taken to 100% limit load followed by the six liftoff cases taken to 140% limit load. Two ascent load cases were then tested to 100% limit load. The forward skirt was unloaded to no load after each test case. Lastly, the forward skirt was tested to 140% limit and then to failure using the ascent loads. The forward skirts on FSTA-1 and FSTA-2 successfully carried all applied liftoff and ascent load cases. Both FSTA-1 and FSTA-2 were tested to failure by increasing the ascent loads. Failure occurred in the forward skirt thrust post radius. The forward skirts on FSTA-1 and FSTA-2 had nearly identical failure modes. FSTA-1 failed at 1.72 times limit load and FSTA-2 failed at 1.62 times limit load. This difference is primarily attributed to variation in material properties in the thrust post region. Test data were obtained from strain gages, deflection gages, ARAMIS digital strain measurement, acoustic emissions, and high-speed video. Strain gage data and ARAMIS strain were compared to finite element (FE) analysis predictions. Both the forward skirt and tooling were modeled. This allows the analysis to simulate the loading as close as possible to actual test configuration. FSTA-1 and FSTA-2 were instrumented with over 200 strain gages to ensure all possible failure modes could be captured. However, it turned out that three gages provided critical strain data. One was located in the post bore and two on the post radius. More gages were not specified due to space limitations and the desire to not interfere with the use of the ARAMIS system on the post radius. Measured strains were compared to analysis results for the load cycle to failure. Note that FSTA-1 gages were lost before failure was reached. FSTA-2 gages made it to the failure load but one of the radius gages was lost before testing began. This gage was not replaced because of the time and cost associated with disassembly of the test structure. Correlation to analysis was excellent for FSTA-1. FSTA-2 was not quite as good because there was more residual strain from previous load cycles. FSTA-2 was loaded and unloaded with 12 liftoff cases and two ascent cases before taking the skirt to failure. FSTA-1 only had two liftoff cases and one ascent case before taking the skirt to failure. The ARAMIS system was used to determine strain at the post radius by processing digital images of a speckled paint pattern. Digital cameras recorded images of the speckled paint pattern. ARAMIS strain results for FSTA-2 just prior to failure. Note a high strain location develops near the left side. This high strain compares well to analysis prediction for both FSTA-1 and FSTA-2. The strain at this location was also plotted versus limit load. Both FSTA-1 and FSTA-2 had excellent correlation between ARAMIS and analysis strains. Acoustic emission (AE) sensors were used to monitor for damage formation that may occur during testing (e.g., crack formation and growth or propagation). AE was very important because after disassembly of FSTA-1, a crack was observed in the ball fitting radius. The ball fitting did not crack on FSTA-2. AE data was used to reconstruct when the crack occurred. The AE energy versus time plot for FSTA. The energy increased considerably at 850 seconds (152% limit load), indicating a crack could have formed at this point. The only visual evidence found that could have corresponded to this was the crack that initiated in the ball fitting. The cracks in the forward skirt aluminum structures would likely have been lower energy due to a lower modulus and all that were found after failure correlated to occurring after the initial crack in the post radius. This was verified by high-speed cameras used to record the failure.

Lohrer, J. D.↗
NASA NTRS2016

Spacecraft Risk Posed by the 2016 Perseid Outburst

The Perseids are one of the more prolific annual showers, known for high rates and for producing bright meteors. Outbursts of this shower have been noted in the 1860s, the early 1990s, 2004, and 2009, with the 1993 outburst being especially active (peak ZHR above 300). The 1993 Perseids also affected the space-faring nations, as the launch of the STS-51 mission was delayed by NASA until after the shower maximum due to an inability to predict the shower intensity, and the ESA telecommunications satellite Olympus suffered a mission-ending anomaly attributed to a static discharge caused by a Perseid impact [1]. Rates were again high (peak ZHR around 200) in 2009, when the NASA/USGS imaging satellite Landsat-5 experienced a gyro anomaly just before the shower peak; however in this case, the satellite was recovered and normal operations resumed one week later [2]. It is interesting to note that both spacecraft anomalies were not what is typically expected from meteoroid strikes, i.e., physical damage or an attitude displacement due to transfer of momentum. It would appear that the very fast Perseids (59 km s(sup -1) have a marked ability to produce plasma upon impact, which can then serve as a conductive path for discharge currents. The shower is expected to outburst again in 2016, and we present the results from the MSFC Meteoroid Stream Model [4], which predicts enhanced activity on a level similar to that of 2009 as the Earth passes through several debris trails on the night of August 11-12 (UT). We then compare our results to those of other modelers.

Cooke, W. J.↗
NASA NTRS2016

Martian Environment Electrostatic Precipitator

As part of the planned manned mission to Mars, NASA has noticed that shipping oxygen as a part of life support to keep the astronauts alive continuously is overly expensive, and impractical. As such, noting that the Martian atmosphere is 95.37% CO2, NASA chemists noted that one could obtain oxygen from the Martian atmosphere. The plan, as part of a larger ISRU (in-situ resource utilization) initiative, would extract water from the regolith, or the Martian soil which can be electrolyzed by solar panel produced voltage into hydrogen and oxygen. The hydrogen can then be used in the Sabatier reaction with carbon dioxide to produce methane and water producing a net reaction that does not lose water and outputs methane and oxygen for use as rocket fuel and breathing.

Dust↗
NASA NTRS2015

[Determine and Implement Updates to Be Made to MODEAR (Mission Operations Data Enterprise Architecture Repository)]

My main project was to determine and implement updates to be made to MODEAR (Mission Operations Data Enterprise Architecture Repository) process definitions to be used for CST-100 (Crew Space Transportation-100) related missions. Emphasis was placed on the scheduling aspect of the processes. In addition, I was to complete other tasks as given. Some of the additional tasks were: to create pass-through command look-up tables for the flight controllers, finish one of the MDT (Mission Operations Directorate Display Tool) displays, gather data on what is included in the CST-100 public data, develop a VBA (Visual Basic for Applications) script to create a csv (Comma-Separated Values) file with specific information from spreadsheets containing command data, create a command script for the November MCC-ASIL (Mission Control Center-Avionics System Integration Laboratory) testing, and take notes for one of the TCVB (Terminal Configured Vehicle B-737) meetings. In order to make progress in my main project I scheduled meetings with the appropriate subject matter experts, prepared material for the meetings, and assisted in the discussions in order to understand the process or processes at hand. After such discussions I made updates to various MODEAR processes and process graphics. These meetings have resulted in significant updates to the processes that were discussed. In addition, the discussions have helped the departments responsible for these processes better understand the work ahead and provided material to help document how their products are created. I completed my other tasks utilizing resources available to me and, when necessary, consulting with the subject matter experts. Outputs resulting from my other tasks were: two completed and one partially completed pass through command look-up tables for the fight controllers, significant updates to one of the MDT displays, a spreadsheet containing data on what is included in the CST-100 public data, a tool to create a csv file with specific information from spreadsheets containing command data, a command script for the November MCC-ASIL testing which resulted in a successful test day identifying several potential issues, and notes from one of the TCVB meetings that was used to keep the teams up to date on what was discussed and decided. I have learned a great deal working at NASA these last four months. I was able to meet and work with amazing individuals, further develop my technical knowledge, expand my knowledge base regarding human spaceflight, and contribute to the CST-100 missions. My work at NASA has strengthened my desire to continue my education in order to make further contributions to the field, and has given me the opportunity to see the advantages of a career at NASA.

Fanourakis, Sofia↗
NASA NTRS2016

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↗
NASA NTRS2016

Kepler: A Search for Terrestrial Planets - Kepler Data Characterization Handbook

The Kepler Data Characteristics Handbook (KDCH) provides a description of all phenomena identified in the Kepler data throughout the mission, and an explanation for how these characteristics are handled by the final version of the Kepler Data Processing Pipeline (SOC 9.3).The KDCH complements the Kepler Data Release Notes (KDRNs), which document phenomena and processing unique to a data release. The original motivation for this separation into static, explanatory text and a more journalistic set of figures and tables in the KDRN was for the user to become familiar with the Data Characteristics Handbook, then peruse the short Notes for a new quarter, referring back to the Handbook when necessary. With the completion of the Kepler mission and the final Data Release 25, both the KDCH and the DRN encompass the entire Kepler mission, so the distinction between them is in the level of exposition, not the extent of the time interval discussed.

Kepler↗
NASA NTRS2016

Kepler Archive Manual

A description of Kepler, its design, performance and operational constraints may be found in the Kepler Instrument Handbook (KIH, Van Cleve Caldwell 2016). A description of Kepler calibration and data processing is described in the Kepler Data Processing Handbook (KDPH, Jenkins et al. 2016; Fanelli et al. 2011). Science users should also consult the special ApJ Letters devoted to early Kepler results and mission design (April 2010, ApJL, Vol. 713 L79-L207). Additional technical details regarding the data processing and data qualities can be found in the Kepler Data Characteristics Handbook (KDCH, Christiansen et al. 2013) and the Data Release Notes (DRN). This archive manual specifically documents the file formats, as they exist for the last data release of Kepler, Data Release 25(KSCI-19065-002). The earlier versions of the archive manual and data release notes act as documentation for the earlier versions of the data files.

Kepler↗
NASA NTRS2017

Verification Testing: Meet User Needs Figure of Merit

Verification is the process through which Modeling and Simulation(M&S) software goes to ensure that it has been rigorously tested and debugged for its intended use. Validation confirms that said software accurately models and represents the real world system. Credibility gives an assessment of the development and testing effort that the software has gone through as well as how accurate and reliable test results are. Together, these three components form Verification, Validation, and Credibility(VV&C), the process by which all NASA modeling software is to be tested to ensure that it is ready for implementation. NASA created this process following the CAIB (Columbia Accident Investigation Board) report seeking to understand the reasons the Columbia space shuttle failed during reentry. The reports conclusion was that the accident was fully avoidable, however, among other issues, the necessary data to make an informed decision was not there and the result was complete loss of the shuttle and crew. In an effort to mitigate this problem, NASA put out their Standard for Models and Simulations, currently in version NASA-STD-7009A, in which they detailed their recommendations, requirements and rationale for the different components of VV&C. They did this with the intention that it would allow for people receiving MS software to clearly understand and have data from the past development effort. This in turn would allow the people who had not worked with the MS software before to move forward with greater confidence and efficiency in their work. This particular project looks to perform Verification on several MATLAB (Registered Trademark)(The MathWorks, Inc.) scripts that will be later implemented in a website interface. It seeks to take note and define the limits of operation, the units and significance, and the expected datatype and format of the inputs and outputs of each of the scripts. This is intended to prevent the code from attempting to make incorrect or impossible calculations. Additionally, this project will look at the coding generally and note inconsistencies, redundancies, and other aspects that may become problematic or slow down the codes run time. Certain scripts lacking in documentation also will be commented and cataloged.

validation↗
NASA NTRS2018

Challenges Beyond the Standard Model: An Examination and Evaluation of Alternatives with Respect to Unsolved Problems in Energetics and Signaling

The standard model of particle physics is regarded as one of the greatest achievements of modern physics. It has successfully predicted the existence of numerous hadrons; e.g. the Higgs Boson, the W and Z Bosons, B mesons, etc. Moreover it accurately models many phenomena such as Beta and Radioactive decay, pair production, hadron mass splitting, and others. In spite of this, the standard model has many shortfalls. For example it fails to account for or explain the presence of dark matter and dark energy. Many alternative models of the substructure of matter etc. have been proposed. Some of these are examined. In addition the strongly related standard model of cosmology, that is the big bang theory, accounts for all observed celestial phenomena. What it cannot do is satisfactorily justify all astrophysical events. As noted, dark matter and dark energy are not well understood yet they are core elements of the big bang model. Many elements of this standard model of cosmology are challenged regularly, yet somehow the community always fits the problems with the model into another mysterious element. This model and others are examined for consistency and reconciliation. Evidence of particles that move faster than the speed of light has long been sought, but remains elusive. Some of the known space-like observations of physics are examined. Potential consequences of such particles are likewise investigated. Some conclusions are drawn with respect to the framework of tachyons in a rational but non-rigorous sense. Finally, some of my ideas are presented, concerning all of the above material. The framework of theories of everything is examined, considering what such a theory requires for validity. Sociological notes on the structure of research in physics are given.

Coxe, Alexander M.↗
NASA NTRS2018

Optical Coronagraphic Spectroscopy of AU Mic: Evidence of Time Variable Colors?

We present coronagraphic long slit spectra of AU Mic's debris disk taken with the STIS instrument aboard the Hubble Space Telescope. Our spectra are the first spatially-resolved, scattered light spectra of the system's disk, which we detect at projected distances between approximately 10 and 45 au. Our spectra cover a wavelength range between 5200 and 10200 Angstrom. We find that the color of AU Mic's debris disk is bluest at small (12-17 au) projected separations. These results both confirm and quantify the findings qualitatively noted by Krist et al. and are different than IR observations that suggested a uniform blue or gray color as a function of projected separation in this region of the disk. Unlike previous literature, which reported that the color of AU Mic's disk became increasingly more blue as a function of projected separation beyond approx. 30 au, we find the disk's optical color between 35 and 45 au to be uniformly blue on the southeast side of the disk and decreasingly blue on the northwest side. We note that this apparent change in disk color at larger projected separations coincides with several fast, outward moving ''features'' that are passing through this region of the southeast side of the disk. We speculate that these phenomenon might be related and that the fast moving features could be changing the localized distribution of sub-micron-sized grains as they pass by, thereby reducing the blue color of the disk in the process. We encourage follow-up optical spectroscopic observations of AU Mic to both confirm this result and search for further modifications of the disk color caused by additional fast moving features propagating through the disk.

Lomax, Jamie R.↗