ALBERT

Description: The emissions of NOx (defined as NO (nitric oxide) + NO2 (nitrogen dioxide)) and hydrogen cyanide (HCN), per unit amount of fuel burned, from fires in the pine forests that dominate the mountains surrounding Mexico City (MC) are about 2 times higher than normally observed for forest burning. The ammonia (NH3) emissions are about average for forest burning. The upper limit for the mass ratio of NOX to volatile organic compounds (VOC) for these MC-area mountain fires was approximately 0.38, which is similar to the NOx/VOC ratio in the MC urban area emissions inventory of 0.34, but much larger than the NOx/VOC ratio for tropical forest fires in Brazil (approximately 0.068). The nitrogen enrichment in the fire emissions may be due to deposition of nitrogen-containing pollutants in the outflow from the MC urban area. This effect may occur worldwide wherever biomass burning coexists with large urban areas (e.g. the tropics, southeastern US, Los Angeles Basin). The molar emission ratio of HCN to carbon monoxide (CO) for the mountain fires was 0.012 +/- 0.007, which is 2-9 times higher than widely used literature values for biomass burning. The ambient molar ratio HCN/CO in the MC-area outflow is about 0.003 +/- 0.0003. Thus, if only mountain fires emit significant amounts of HCN, these fires may be contributing about 25% of the CO production in the MCarea (approximately 98-100 W and 19-20 N). Comparing the PM10/CO and PM2.5/CO mass ratios in the MC Metropolitan Area emission inventory (0.01 15 and 0.0037) to the PM1/CO mass ratio for the mountain fires (0.133) then suggests that these fires could produce as much as approximately 79-92% of the primary fine particle mass generated in the MC-area. Considering both the uncertainty in the HCN/CO ratios and secondary aerosol formation in the urban and fire emissions implies that about 50 +/- 30% of the "aged" fine particle mass in the March 2006 MC-area outflow could be from these fires.

Description: The MRO Sequence Checking Tool program, mro_check, automates significant portions of the MRO (Mars Reconnaissance Orbiter) sequence checking procedure. Though MRO has similar checks to the ODY s (Mars Odyssey) Mega Check tool, the checks needed for MRO are unique to the MRO spacecraft. The MRO sequence checking tool automates the majority of the sequence validation procedure and check lists that are used to validate the sequences generated by MRO MPST (mission planning and sequencing team). The tool performs more than 50 different checks on the sequence. The automation varies from summarizing data about the sequence needed for visual verification of the sequence, to performing automated checks on the sequence and providing a report for each step. To allow for the addition of new checks as needed, this tool is built in a modular fashion.

Description: One of the major problems associated with solid waste processing technologies is effluent contaminants that are released in gaseous forms from the processes. This is a concern in both biological as well as physicochemical solid waste processing. Carbon dioxide (CO2), the major gas released, does not present a serious problem and there are currently in place a number of flight-qualified technologies for CO2 removal. However, a number of other gases, in particular NOx, SO2, NH3, and various hydrocarbons (e.g. CH4) do present health hazards to the crew members in space habitats. In the present configuration of solid waste processing in the International Space Station (ISS), some of these gases are removed by the Trace Contaminant Control System (TCCS), demands a major resupply. Reduction of the resupply can be effective by using catalyst impregnated carbon nanotubes. For example, NO decomposition to N2 and O2 is thermodynamically favored. Data showing decomposition of NO on metal impregnated carbon nanotubes is presented. Comparisons are made of the existing TCCS systems with the carbon nanotube based technology for removing NOx based on mass/energy penalties.

Description: Mixed liquid/solid wastes, including feces, water processor effluents, and food waste, can be lyophilized (freeze-dried) to recover the water they contain and stabilize the solids that remain. Our previous research has demonstrated the potential benefits of using thermoelectric heat pumps to build a lyophilizer for processing waste in microgravity. These results were used to build a working prototype suitable for ground- based human testing. This paper describes the prototype design and presents results of functional and performance tests.

Description: dragREPORT software was developed in parallel with abmREPORT, which is described in the preceding article. Both programs were built on the capabilities created during that process. This tool generates a drag_pass report that summarizes vital information from the MRO aerobreaking drag_pass build process to facilitate both sequence reviews and provide a high-level summarization of the sequence for mission management. The script extracts information from the ENV, SSF, FRF, SCMFmax, and OPTG files, presenting them in a single, easy-to-check report providing the majority of parameters needed for cross check and verification as part of the sequence review process. Prior to dragReport, all the needed information was spread across a number of different files, each in a different format. This software is a Perl script that extracts vital summarization information and build-process details from a number of source files into a single, concise report format used to aid the MPST sequence review process and to provide a high-level summarization of the sequence for mission management reference. This software could be adapted for future aerobraking missions to provide similar reports, review and summarization information.

Description: abmREPORT Version 3.1 is a Perl script that extracts vital summarization information from the Mars Reconnaissance Orbiter (MRO) aerobraking ABM build process. This information facilitates sequence reviews, and provides a high-level summarization of the sequence for mission management. The script extracts information from the ENV, SSF, FRF, SCMFmax, and OPTG files and burn magnitude configuration files and presents them in a single, easy-to-check report that provides the majority of the parameters necessary for cross check and verification during the sequence review process. This means that needed information, formerly spread across a number of different files and each in a different format, is all available in this one application. This program is built on the capabilities developed in dragReport and then the scripts evolved as the two tools continued to be developed in parallel.

Description: This software analyzes Mars Reconnaissance Orbiter (MRO) orbital geometry with respect to Mars Exploration Rover (MER) contact windows, and is the first tool of its kind designed specifically to support MRO-MER interface coordination. Prior to this automated tool, this analysis was done manually with Excel and the UNIX command line. In total, the process would take approximately 30 minutes for each analysis. The current automated analysis takes less than 30 seconds. This tool resides on the flight machine and uses a PHP interface that does the entire analysis of the input files and takes into account one-way light time from another input file. Input flies are copied over to the proper directories and are dynamically read into the tool s interface. The user can then choose the corresponding input files based on the time frame desired for analysis. After submission of the Web form, the tool merges the two files into a single, time-ordered listing of events for both spacecraft. The times are converted to the same reference time (Earth Transmit Time) by reading in a light time file and performing the calculations necessary to shift the time formats. The program also has the ability to vary the size of the keep-out window on the main page of the analysis tool by inputting a custom time for padding each MRO event time. The parameters on the form are read in and passed to the second page for analysis. Everything is fully coded in PHP and can be accessed by anyone with access to the machine via Web page. This uplink tool will continue to be used for the duration of the MER mission's needs for X-band uplinks. Future missions also can use the tools to check overflight times as well as potential site observation times. Adaptation of the input files to the proper format, and the window keep-out times, would allow for other analyses. Any operations task that uses the idea of keep-out windows will have a use for this program.

Description: The soeWINDOW program automates the generation of an ITAR (International Traffic in Arms Regulations)-compliant sub-RSOE (Replacement Sequence of Events) by extracting a specified temporal window from an RSOE while maintaining page header information. RSOEs contain a significant amount of information that is not ITAR-compliant, yet that foreign partners need to see for command details to their instrument, as well as the surrounding commands that provide context for validation. soeWINDOW can serve as an example of how command support products can be made ITAR-compliant for future missions. This software is a Perl script intended for use in the mission operations UNIX environment. It is designed for use to support the MRO (Mars Reconnaissance Orbiter) instrument team. The tool also provides automated DOM (Distributed Object Manager) storage into the special ITAR-okay DOM collection, and can be used for creating focused RSOEs for product review by any of the MRO teams.

Description: The MRO OLVM wrapper script software allows Mars Reconnaissance Orbiter (MRO) sequence and spacecraft engineers to rapidly simulate a spacecraft command product through a tool that simulates the onboard sequence management software (OLVM). This script parses sequence files to determine the appropriate time boundaries for the sequence, and constructs the script file to be executed by OLVM to span the entirety of the designated sequence. It then constructs script files to be executed by OLVM, constructs the appropriate file directories, populates these directories with needed input files, initiates OLVM to simulate the actual command product that will be sent to the spacecraft, and captures the results of the simulation run to an external file for later review. Additionally, the tool allows a user to manually construct the script, if desired, and then execute the script with a simple command line.

Description: A computer program called "autogen hypertext map generator" satisfies a need for documenting and assisting in visualization of, and navigation through, model files used in the AUTOGEN and APGEN software mentioned in the two immediately preceding articles. This program parses autogen script files, autogen model files, PERL scripts, and apgen activity-definition files and produces a hypertext map of the files to aid in the navigation of the model. This program also provides a facility for adding notes and descriptions, beyond what is in the source model represented by the hypertext map. Further, this program provides access to a summary of the model through variable, function, sub routine, activity and resource declarations as well as providing full access to the source model and source code. The use of the tool enables easy access to the declarations and the ability to traverse routines and calls while analyzing the model.