Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “START Program”

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,549 records · Page 86

A Parallel Genetic Algorithm for Automated Electronic Circuit Design

Parallelized versions of genetic algorithms (GAs) are popular primarily for three reasons: the GA is an inherently parallel algorithm, typical GA applications are very compute intensive, and powerful computing platforms, especially Beowulf-style computing clusters, are becoming more affordable and easier to implement. In addition, the low communication bandwidth required allows the use of inexpensive networking hardware such as standard office ethernet. In this paper we describe a parallel GA and its use in automated high-level circuit design. Genetic algorithms are a type of trial-and-error search technique that are guided by principles of Darwinian evolution. Just as the genetic material of two living organisms can intermix to produce offspring that are better adapted to their environment, GAs expose genetic material, frequently strings of 1s and Os, to the forces of artificial evolution: selection, mutation, recombination, etc. GAs start with a pool of randomly-generated candidate solutions which are then tested and scored with respect to their utility. Solutions are then bred by probabilistically selecting high quality parents and recombining their genetic representations to produce offspring solutions. Offspring are typically subjected to a small amount of random mutation. After a pool of offspring is produced, this process iterates until a satisfactory solution is found or an iteration limit is reached. Genetic algorithms have been applied to a wide variety of problems in many fields, including chemistry, biology, and many engineering disciplines. There are many styles of parallelism used in implementing parallel GAs. One such method is called the master-slave or processor farm approach. In this technique, slave nodes are used solely to compute fitness evaluations (the most time consuming part). The master processor collects fitness scores from the nodes and performs the genetic operators (selection, reproduction, variation, etc.). Because of dependency issues in the GA, it is possible to have idle processors. However, as long as the load at each processing node is similar, the processors are kept busy nearly all of the time. In applying GAs to circuit design, a suitable genetic representation 'is that of a circuit-construction program. We discuss one such circuit-construction programming language and show how evolution can generate useful analog circuit designs. This language has the desirable property that virtually all sets of combinations of primitives result in valid circuit graphs. Our system allows circuit size (number of devices), circuit topology, and device values to be evolved. Using a parallel genetic algorithm and circuit simulation software, we present experimental results as applied to three analog filter and two amplifier design tasks. For example, a figure shows an 85 dB amplifier design evolved by our system, and another figure shows the performance of that circuit (gain and frequency response). In all tasks, our system is able to generate circuits that achieve the target specifications.

Long, Jason D.↗

New Data on the Topside Electron Density Distribution

The existing uncertainties about the electron density profiles in the topside ionosphere, i.e., in the height region from hmF2 to approx. 2000 km, require the search for new data sources. The ISIS and Alouette topside sounder satellites from the sixties to the eighties recorded millions of ionograms and most were not analyzed in terms of electron density profiles. In recent years an effort started to digitize the analog recordings to prepare the ionograms for computerized analysis. As of November 2001 about 350,000 ionograms have been digitized from the original 7-track analog tapes. These data are available in binary and CDF format from the anonymous ftp site of the National Space Science Data Center. A search site and browse capabilities on CDAWeb assist the scientific usage of these data. All information and access links can be found at http://nssdc.gsfc.nasa.gov/space/isis/isis-status.html. This paper describes the ISIS data restoration effort and shows how the digital ionograms are automatically processed into electron density profiles from satellite orbit altitude (1400 km for ISIS-2) down to the F peak. Because of the large volume of data an automated processing algorithm is imperative. The automatic topside ionogram scaler with true height algorithm TOPIST software developed for this task is successfully scaling approx.70 % of the ionograms. An 'editing process' is available to manually scale the more difficult ionograms. The automated processing of the digitized ISIS ionograms is now underway, producing a much-needed database of topside electron density profiles for ionospheric modeling covering more than one solar cycle. The ISIS data restoration efforts are supported through NASA's Applied Systems and Information Research Program.

Huang, Xue-Qin↗

CERES Single Scanner Satellite Footprint, TOA, Surface Fluxes and Clouds (SSF) data in HDF (CER_SSF_TRMM-SIM-VIRS_Edition2-VIRSonly)

The Single Scanner Footprint TOA/Surface Fluxes and Clouds (SSF) product contains one hour of instantaneous Clouds and the Earth's Radiant Energy System (CERES) data for a single scanner instrument. The SSF combines instantaneous CERES data with scene information from a higher-resolution imager such as Visible/Infrared Scanner (VIRS) on TRMM or Moderate-Resolution Imaging Spectroradiometer (MODIS) on Terra and Aqua. Scene identification and cloud properties are defined at the higher imager resolution and these data are averaged over the larger CERES footprint. For each CERES footprint, the SSF contains the number of cloud layers and for each layer the cloud amount, height, temperature, pressure, optical depth, emissivity, ice and liquid water path, and water particle size. The SSF also contains the CERES filtered radiances for the total, shortwave (SW), and window (WN) channels and the unfiltered SW, longwave (LW), and WN radiances. The SW, LW, and WN radiances at spacecraft altitude are converted to Top-of-the-Atmosphere (TOA) fluxes based on the imager defined scene. These TOA fluxes are used to estimate surface fluxes. Only footprints with adequate imager coverage are included on CER_SSF_TRMM-PFM-VIRS_Subset_Edition1the SSF which is much less than the full set of footprints on the CERES ES-8 product. The following CERES SSF data sets are currently available: CER_SSF_TRMM-PFM-VIRS_Edition1 CER_SSF_TRMM-PFM-VIRS_Subset_Edition1 CER_SSF_TRMM-PFM-VIRS_Edition2A CER_SSF_TRMM-SIM-VIRS_Edition2_VIRSonly CER_SSF_TRMM-PFM-VIRS_Edition2A-TransOps CER_SSF_TRMM-PFM-VIRS_Edition2B-TransOps CER_SSF_TRMM-PFM-VIRS_Edition2B CER_SSF_Terra-FM1-MODIS_Edition1A CER_SSF_Terra-FM1-MODIS_Edition1A CER_SSF_Terra-FM1-MODIS_Edition2A CER_SSF_Terra-FM2-MODIS_Edition2A CER_SSF_Terra-FM1-MODIS_Edition2B CER_SSF_Terra-FM2-MODIS_Edition2B CER_SSF_Aqua-FM4-MODIS_Beta1 CER_SSF_Aqua-FM3-MODIS_Beta2 CER_SSF_Aqua-FM4-MODIS_Beta2. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1998-01-01; Stop_Date=2001-07-01] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 hour; Temporal_Resolution_Range=Hourly - < Daily].

CLOUD INFRARED EMISSIVITY↗

CERES ERBE-like Monthly Regional Averages (ES-9) in HDF ( CER_ES9_Terra-FM2_Edition1-CV)

The ERBE-like Monthly Regional Averages (ES-9) product contains a month of space and time averaged Clouds and the Earth's Radiant Energy System (CERES) data for a single scanner instrument. The ES-9 is also produced for combinations of scanner instruments. All instantaneous shortwave and longwave fluxes at the Top-of-the-Atmosphere (TOA) from the CERES ES-8 product for a month are sorted by 2.5-degree spatial regions, by day number, and by the local hour of observation. The mean of the instantaneous fluxes for a given region-day-hour bin is determined and recorded on the ES-9 along with other flux statistics and scene information. For each region, the daily average flux is estimated from an algorithm that uses the available hourly data, scene identification data, and diurnal models. This algorithm is 'like' the algorithm used for the Earth Radiation Budget Experiment (ERBE). The ES-9 also contains hourly average fluxes for the month and an overall monthly average for each region. These average fluxes are given for both clear-sky and total-sky scenes. The following CERES ES9 data sets are currently available: CER_ES9_FM1+FM2_Edition1 CER_ES9_PFM+FM1+FM2_Edition1 CER_ES9_PFM+FM1+FM2_Edition2 CER_ES9_PFM+FM1_Edition1 CER_ES9_PFM+FM2_Edition1 CER_ES9_PFM+FM1_Edition2 CER_ES9_PFM+FM2_Edition2 CER_ES9_TRMM-PFM_Edition1 CER_ES9_TRMM-PFM_Edition2 CER_ES9_Terra-FM1_Edition1 CER_ES9_Terra-FM2_Edition1 CER_ES9_FM1+FM2_Edition2 CER_ES9_Terra-FM1_Edition2 CER_ES9_Terra-FM2_Edition2 CER_ES9_Aqua-FM3_Edition1 CER_ES9_Aqua-FM4_Edition1 CER_ES9_FM1+FM2+FM3+FM4_Edition1 CER_ES9_Aqua-FM3_Edition2 CER_ES9_Aqua-FM4_Edition2 CER_ES9_FM1+FM3_Edition2 CER_ES9_FM1+FM4_Edition2 CER_ES9_Aqua-FM3_Edition1-CV CER_ES9_Aqua-FM4_Edition1-CV CER_ES9_Terra-FM1_Edition1-CV CER_ES9_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1998-01-01; Stop_Date=2006-10-31] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=2.5 degree; Longitude_Resolution=2.5 degree; Horizontal_Resolution_Range=250 km - < 500 km or approximately 2.5 degrees - < 5.0 degrees; Temporal_Resolution=hourly, daily, monthly; Temporal_Resolution_Range=Hourly - < Daily, Daily - < Weekly, Monthly - < Annual].

CLEAR-SKY SHORTWAVE FLUX↗

International Satellite Cloud Climatology Project (ISCCP) Stage D1 3-Hourly Cloud Product - Revised Algorithm in Hierarchical Data Format (ISCCP_D1)

Since 1983 an international group of institutions has collected and analyzed satellite radiance measurements from up to five geostationary and two polar orbiting satellites to infer the global distribution of cloud properties and their diurnal, seasonal and interannual variations. The primary focus of the first phase of the project (1983-1995) was the elucidation of the role of clouds in the radiation budget (top of the atmosphere and surface). In the second phase of the project (1995 onwards) the analysis also concerns improving understanding of clouds in the global hydrological cycle. [Location=TROPOSPHERE] [Temporal_Coverage: Start_Date=1983-07-01; Stop_Date=] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=280 Km; Longitude_Resolution=280 Km; Temporal_Resolution=3 Hourly].

CLOUD LIQUID WATER PATH↗

Investigating the Simulink Auto-Coding Process

Model based program design is the most clear and direct way to develop algorithms and programs for interfacing with hardware. While coding "by hand" results in a more tailored product, the ever-growing size and complexity of modern-day applications can cause the project work load to quickly become unreasonable for one programmer. This has generally been addressed by splitting the product into separate modules to allow multiple developers to work in parallel on the same project, however this introduces new potentials for errors in the process. The fluidity, reliability and robustness of the code relies on the abilities of the programmers to communicate their methods to one another; furthermore, multiple programmers invites multiple potentially differing coding styles into the same product, which can cause a loss of readability or even module incompatibility. Fortunately, Mathworks has implemented an auto-coding feature that allows programmers to design their algorithms through the use of models and diagrams in the graphical programming environment Simulink, allowing the designer to visually determine what the hardware is to do. From here, the auto-coding feature handles converting the project into another programming language. This type of approach allows the designer to clearly see how the software will be directing the hardware without the need to try and interpret large amounts of code. In addition, it speeds up the programming process, minimizing the amount of man-hours spent on a single project, thus reducing the chance of human error as well as project turnover time. One such project that has benefited from the auto-coding procedure is Ramses, a portion of the GNC flight software on-board Orion that has been implemented primarily in Simulink. Currently, however, auto-coding Ramses into C++ requires 5 hours of code generation time. This causes issues if the tool ever needs to be debugged, as this code generation will need to occur with each edit to any part of the program; additionally, this is lost time that could be spent testing and analyzing the code. This is one of the more prominent issues with the auto-coding process, and while much information is available with regard to optimizing Simulink designs to produce efficient and reliable C++ code, not much research has been made public on how to reduce the code generation time. It is of interest to develop some insight as to what causes code generation times to be so significant, and determine if there are architecture guidelines or a desirable auto-coding configuration set to assist in streamlining this step of the design process for particular applications. To address the issue at hand, the Simulink coder was studied at a foundational level. For each different component type made available by the software, the features, auto-code generation time, and the format of the generated code were analyzed and documented. Tools were developed and documented to expedite these studies, particularly in the area of automating sequential builds to ensure accurate data was obtained. Next, the Ramses model was examined in an attempt to determine the composition and the types of technologies used in the model. This enabled the development of a model that uses similar technologies, but takes a fraction of the time to auto-code to reduce the turnaround time for experimentation. Lastly, the model was used to run a wide array of experiments and collect data to obtain knowledge about where to search for bottlenecks in the Ramses model. The resulting contributions of the overall effort consist of an experimental model for further investigation into the subject, as well as several automation tools to assist in analyzing the model, and a reference document offering insight to the auto-coding process, including documentation of the tools used in the model analysis, data illustrating some potential problem areas in the auto-coding process, and recommendations on areas or practices in the current Ramses model that should be further investigated. Several skills were required to be built up over the course of the internship project. First and foremost, my Simulink skills have improved drastically, as much of my experience had been modeling electronic circuits as opposed to software models. Furthermore, I am now comfortable working with the Simulink Auto-coder, a tool I had never used until this summer; this tool also tested my critical thinking and C++ knowledge as I had to interpret the C++ code it was generating and attempt to understand how the Simulink model affected the generated code. I had come into the internship with a solid understanding of Matlab code, but had done very little in using it to automate tasks, particularly Simulink tasks; along the same lines, I had rarely used shell script to automate and interface with programs, which I gained a fair amount of experience with this summer, including how to use regular expression. Lastly, soft-skills are an area everyone can continuously improve on; having never worked with NASA engineers, which to me seem to be a completely different breed than what I am used to (commercial electronic engineers), I learned to utilize the wealth of knowledge present at JSC. I wish I had come into the internship knowing exactly how helpful everyone in my branch would be, as I would have picked up on this sooner. I hope that having gained such a strong foundation in Simulink over this summer will open the opportunity to return to work on this project, or potentially other opportunities within the division. The idea of leaving a project I devoted ten weeks to is a hard one to cope with, so having the chance to pick up where I left off sounds appealing; alternatively, I am interested to see if there are any opening in the future that would allow me to work on a project that is more in-line with my research in estimation algorithms. Regardless, this summer has been a milestone in my professional career, and I hope this has started a long-term relationship between JSC and myself. I really enjoy the thought of building on my experience here over future summers while I work to complete my PhD at Missouri University of Science and Technology.

Gualdoni, Matthew J.↗

Ontolology Negotiation Between Scientific Archives

This paper describes an approach to ontology negotiation between information agents. Ontologies are declarative (data driven) expressions of an agent's "world": the objects, operations, facts, and rules that constitute the logical space within which an agent performs. Ontology negotiation enables agents to cooperate in performing a task, even if they are based on different ontologies. 'Me process allows agents to discover ontology conflicts and then, though incremental interpretation, clarification, and explanation, establish a common basis for communicating with each other. The need for ontology negotiation stems from the proliferation of information sources and of agents with widely varying specialty expertise. The unmanageability of massive amounts of web-based information is already becoming apparent. It is starting to have an impact on professions that rely on distributed archived information. If the expansion continues at its present rate without an ontology negotiation process being introduced, there will soon be no way to ensure the accuracy and completeness of information that scientists obtain from sources other than their own experiments. Ontology negotiation is becoming increasingly recognized as a crucial element of scalable agent technology. This is because agents, by their very nature, are supposed to operate with a fair amount of autonomy and independence from their end-users. Part of this independence is the ability to enlist other agents for help in performing a task (such as locating information on the web). The agents enlisted for help may be "owned" by a different end-user or organization (such as a document archive), and there is no guarantee that they will use the same terminology or understand the same concepts (objects, operators, theorems, rules) as the recruiting agent. For NASA, the need for ontology negotiation arises at the boundaries between scientific disciplines. For example: modeling the effects of global warming might involve knowledge about imaging, climate analysis, ecology, demographics, industrial economics, and biology. The need for ontology negotiation also arises at the boundaries between scientific programs. For example, a Principal Investigator may want to use information from a previous mission to complement downloads from the instruments currently deployed.

Bailin, Sidney C.↗

XML: James Webb Space Telescope Database Issues, Lessons, and Status

This paper will present the current concept using extensible Markup Language (XML) as the underlying structure for the James Webb Space Telescope (JWST) database. The purpose of using XML is to provide a JWST database, independent of any portion of the ground system, yet still compatible with the various systems using a variety of different structures. The testing of the JWST Flight Software (FSW) started in 2002, yet the launch is scheduled for 2011 with a planned 5-year mission and a 5-year follow on option. The initial database and ground system elements, including the commands, telemetry, and ground system tools will be used for 19 years, plus post mission activities. During the Integration and Test (I&T) phases of the JWST development, 24 distinct laboratories, each geographically dispersed, will have local database tools with an XML database. Each of these laboratories database tools will be used for the exporting and importing of data both locally and to a central database system, inputting data to the database certification process, and providing various reports. A centralized certified database repository will be maintained by the Space Telescope Science Institute (STScI), in Baltimore, Maryland, USA. One of the challenges for the database is to be flexible enough to allow for the upgrade, addition or changing of individual items without effecting the entire ground system. Also, using XML should allow for the altering of the import and export formats needed by the various elements, tracking the verification/validation of each database item, allow many organizations to provide database inputs, and the merging of the many existing database processes into one central database structure throughout the JWST program. Many National Aeronautics and Space Administration (NASA) projects have attempted to take advantage of open source and commercial technology. Often this causes a greater reliance on the use of Commercial-Off-The-Shelf (COTS), which is often limiting. In our review of the database requirements and the COTS software available, only very expensive COTS software will meet 90% of requirements. Even with the high projected initial cost of COTS, the development and support for custom code over the 19-year mission period was forecasted to be higher than the total licensing costs. A group did look at reusing existing database tools and formats. If the JWST database was already in a mature state, the reuse made sense, but with the database still needing to handing the addition of different types of command and telemetry structures, defining new spacecraft systems, accept input and export to systems which has not been defined yet, XML provided the flexibility desired. It remains to be determined whether the XML database will reduce the over all cost for the JWST mission.

Detter, Ryan↗

CERES Clouds and Radiative Swath (CRS) data in HDF (CER_CRS_TRMM-PFM-VIRS_Edition2C)

The Clouds and Radiative Swath (CRS) product contains one hour of instantaneous Clouds and the Earth's Radiant Energy System (CERES) data for a single scanner instrument. The CRS contains all of the CERES SSF product data. For each CERES footprint on the SSF the CRS also contains vertical flux profiles evaluated at four levels in the atmosphere: the surface, 500-, 70-, and 1-hPa. The CRS fluxes and cloud parameters are adjusted for consistency with a radiative transfer model and adjusted fluxes are evaluated at the four atmospheric levels for both clear-sky and total-sky. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1998-01-01; Stop_Date=2000-03-31] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 hour; Temporal_Resolution_Range=Hourly - < Daily].

ICE PARTICLE DIAMETER↗

Cascade Optimization Strategy for Aircraft and Air-Breathing Propulsion System Concepts

Design optimization for subsonic and supersonic aircraft and for air-breathing propulsion engine concepts has been accomplished by soft-coupling the Flight Optimization System (FLOPS) and the NASA Engine Performance Program analyzer (NEPP), to the NASA Lewis multidisciplinary optimization tool COMETBOARDS. Aircraft and engine design problems, with their associated constraints and design variables, were cast as nonlinear optimization problems with aircraft weight and engine thrust as the respective merit functions. Because of the diversity of constraint types and the overall distortion of the design space, the most reliable single optimization algorithm available in COMETBOARDS could not produce a satisfactory feasible optimum solution. Some of COMETBOARDS' unique features, which include a cascade strategy, variable and constraint formulations, and scaling devised especially for difficult multidisciplinary applications, successfully optimized the performance of both aircraft and engines. The cascade method has two principal steps: In the first, the solution initiates from a user-specified design and optimizer, in the second, the optimum design obtained in the first step with some random perturbation is used to begin the next specified optimizer. The second step is repeated for a specified sequence of optimizers or until a successful solution of the problem is achieved. A successful solution should satisfy the specified convergence criteria and have several active constraints but no violated constraints. The cascade strategy available in the combined COMETBOARDS, FLOPS, and NEPP design tool converges to the same global optimum solution even when it starts from different design points. This reliable and robust design tool eliminates manual intervention in the design of aircraft and of air-breathing propulsion engines where it eases the cycle analysis procedures. The combined code is also much easier to use, which is an added benefit. This paper describes COMETBOARDS and its cascade strategy and illustrates the capability of the combined design tool through the optimization of a subsonic aircraft and a high-bypass-turbofan wave-rotor-topped engine.

Patnaik, Surya N.↗

CERES ERBE-like Instantaneous TOA Estimates (ES-8) in HDF (CER_ES8_TRMM-PFM_Transient-Ops2)

The ES-8 archival data product contains a 24-hour, single-satellite, instantaneous view of scanner fluxes at the top-of-atmosphere (TOA) reduced from spacecraft altitude unfiltered radiances using Earth Radiation Budget Experiment (ERBE) scanner Inversion algorithms and the ERBE shortwave (SW) and longwave (LW) Angular Distribution Models (ADMs). The ES-8 also includes the total (TOT), SW, LW, and window (WN) channel radiometric data; SW, LW, and WN unfiltered radiance values; and the ERBE scene identification for each measurement. These data are organized according to the CERES 3.3-second scan into 6.6-second records. As long as there is one valid scanner measurement within a record, the ES-8 record will be generated. The following CERES ES8 data sets are currently available: CER_ES8_TRMM-PFM_Edition1 CER_ES8_TRMM-PFM_Edition2 CER_ES8_TRMM-PFM_Transient-Ops2 CER_ES8_Terra-FM1_Edition1 CER_ES8_Terra-FM2_Edition1 CER_ES8_Terra-FM1_Edition2 CER_ES8_Terra-FM2_Edition2 CER_ES8_Aqua-FM3_Edition1 CER_ES8_Aqua-FM4_Edition1 CER_ES8_Aqua-FM3_Edition2 CER_ES8_Aqua-FM4_Edition2 CER_ES8_Aqua-FM3_Edition1-CV CER_ES8_Aqua-FM4_Edition1-CV CER_ES8_Terra-FM1_Edition1-CV CER_ES8_Terra-FM1_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1997-12-27; Stop_Date=1999-07-17] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Temporal_Resolution=1 day; Temporal_Resolution_Range=Daily - < Weekly].

TOTAL FILTERED RADIANCE↗

CERES ERBE-like Monthly Regional Averages (ES-9) in HDF (CER_ES9_PFM+FM2_Edition1)

The ERBE-like Monthly Regional Averages (ES-9) product contains a month of space and time averaged Clouds and the Earth's Radiant Energy System (CERES) data for a single scanner instrument. The ES-9 is also produced for combinations of scanner instruments. All instantaneous shortwave and longwave fluxes at the Top-of-the-Atmosphere (TOA) from the CERES ES-8 product for a month are sorted by 2.5-degree spatial regions, by day number, and by the local hour of observation. The mean of the instantaneous fluxes for a given region-day-hour bin is determined and recorded on the ES-9 along with other flux statistics and scene information. For each region, the daily average flux is estimated from an algorithm that uses the available hourly data, scene identification data, and diurnal models. This algorithm is 'like' the algorithm used for the Earth Radiation Budget Experiment (ERBE). The ES-9 also contains hourly average fluxes for the month and an overall monthly average for each region. These average fluxes are given for both clear-sky and total-sky scenes. The following CERES ES9 data sets are currently available: CER_ES9_FM1+FM2_Edition1 CER_ES9_PFM+FM1+FM2_Edition1 CER_ES9_PFM+FM1+FM2_Edition2 CER_ES9_PFM+FM1_Edition1 CER_ES9_PFM+FM2_Edition1 CER_ES9_PFM+FM1_Edition2 CER_ES9_PFM+FM2_Edition2 CER_ES9_TRMM-PFM_Edition1 CER_ES9_TRMM-PFM_Edition2 CER_ES9_Terra-FM1_Edition1 CER_ES9_Terra-FM2_Edition1 CER_ES9_FM1+FM2_Edition2 CER_ES9_Terra-FM1_Edition2 CER_ES9_Terra-FM2_Edition2 CER_ES9_Aqua-FM3_Edition1 CER_ES9_Aqua-FM4_Edition1 CER_ES9_FM1+FM2+FM3+FM4_Edition1 CER_ES9_Aqua-FM3_Edition2 CER_ES9_Aqua-FM4_Edition2 CER_ES9_FM1+FM3_Edition2 CER_ES9_FM1+FM4_Edition2 CER_ES9_Aqua-FM3_Edition1-CV CER_ES9_Aqua-FM4_Edition1-CV CER_ES9_Terra-FM1_Edition1-CV CER_ES9_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1998-01-01; Stop_Date=2000-03-31] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=2.5 degree; Longitude_Resolution=2.5 degree; Horizontal_Resolution_Range=250 km - < 500 km or approximately 2.5 degrees - < 5.0 degrees; Temporal_Resolution=hourly, daily, monthly; Temporal_Resolution_Range=Hourly - < Daily, Daily - < Weekly, Monthly - < Annual].

NET FLUX↗

Computational Modeling of Magnetically Actuated Propellant Orientation

Unlike terrestrial applications where gravity positions liquid at the "bottom" of the tank, the location of liquid propellant in spacecraft tanks is uncertain unless specific actions are taken or special features are built into the tank. Some mission events require knowledge of liquid position prior to a particular action: liquid must be positioned over the tank outlet prior to starting the main engines and must be moved away from the tank vent before vapor can be released overboard to reduce pressure. It may also be desirable to positively position liquid to improve propulsion system performance: moving liquid away from the tank walls will dramatically decrease the rate of heat transfer to the propellant, suppressing the boil-off rate, thereby reducing overall mission propellant requirements. The process of moving propellant to a desired position is referred to as propellant orientation or reorientation. Propulsive reorientation relies on small auxiliary thrusters to accelerate the tank. The inertia of the liquid causes it to collect in the aft-end of the tank if the acceleration is forward. Liquid Acquisition Devices (LAD's) rely on surface tension to hold the liquid within special geometries, (i.e. vanes, wire-mesh channels, start-baskets), to positively position propellants. Both of these technologies add significant weight and complexity to the spacecraft and can be limiting systems for long duration missions. The subject of the present research is an alternate technique for positively positioning liquid within spacecraft propellant tanks: magnetic fields. LOX is paramagnetic (attracted toward a magnet) and LH2 is diamagnetic (repelled from a magnet). Order-of-magnitude analyses, performed in the 1960's to determine required magnet size, concluded that the magnets would be prohibitively massive and this option has remained dormant during the intervening years. Recent advances in high-temperature superconducting materials hold the promise of electromagnets with sufficient performance to support cryogenic propellant management tasks. In late 1992, NASA MSFC began a new investigation in this technology commencing with the design of the Magnetically-Actuated Propellant Orientation (MAPO) experiment. A mixture of ferrofluid and water is used to simulate the paramagnetic properties of LOX and the experiment is being flown on the KC-135 aircraft to provide a reduced gravity environment. The influence of a 0.4 Tesla ring magnet on flow into and out of a subscale Plexiglas tank is being recorded on video tape. The most efficient approach to evaluating the feasibility of MAPO is to compliment the experimental program with development of a computational tool to model the process of interest. The goal of the present research is to develop such a tool. Once confidence in its fidelity is established by comparison to data from the MAPO experiment, it can be used to assist in the design of future experiments and to study the parameter space of the process. Ultimately, it is hoped that the computational model can serve as a design tool for full-scale spacecraft applications.

Hochstein, John I.↗

CCAAT-binding factor regulates expression of the beta1 subunit of soluble guanylyl cyclase gene in the BE2 human neuroblastoma cell line

Soluble guanylyl cyclase (sGC) is a cytosolic enzyme producing the intracellular messenger cyclic guanosine monophosphate (cGMP) on activation with nitric oxide (NO). sGC is an obligatory heterodimer composed of alpha and beta subunits. We investigated human beta1 sGC transcriptional regulation in BE2 human neuroblastoma cells. The 5' upstream region of the beta1 sGC gene was isolated and analyzed for promoter activity by using luciferase reporter constructs. The transcriptional start site of the beta1 sGC gene in BE2 cells was identified. The functional significance of consensus transcriptional factor binding sites proximal to the transcriptional start site was investigated by site deletions in the 800-bp promoter fragment. The elimination of CCAAT-binding factor (CBF) and growth factor independence 1 (GFI1) binding cores significantly diminished whereas deletion of the NF1 core elevated the transcription. Electrophoretic mobility-shift assay (EMSA) and Western analysis of proteins bound to biotinated EMSA probes confirmed the interaction of GFI1, CBF, and NF1 factors with the beta1 sGC promoter. Treatment of BE2 cells with genistein, known to inhibit the CBF binding to DNA, significantly reduced protein levels of beta1 sGC by inhibiting transcription. In summary, our study represents an analysis of the human beta1 sGC promoter regulation in human neuroblastoma BE2 cells and identifies CBF as a critically important factor in beta1 sGC expression.

Non-NASA Center↗

CERES ERBE-like Monthly Regional Averages (ES-9) in HDF (CER_ES9_TRMM-PFM_Edition1)

The ERBE-like Monthly Regional Averages (ES-9) product contains a month of space and time averaged Clouds and the Earth's Radiant Energy System (CERES) data for a single scanner instrument. The ES-9 is also produced for combinations of scanner instruments. All instantaneous shortwave and longwave fluxes at the Top-of-the-Atmosphere (TOA) from the CERES ES-8 product for a month are sorted by 2.5-degree spatial regions, by day number, and by the local hour of observation. The mean of the instantaneous fluxes for a given region-day-hour bin is determined and recorded on the ES-9 along with other flux statistics and scene information. For each region, the daily average flux is estimated from an algorithm that uses the available hourly data, scene identification data, and diurnal models. This algorithm is 'like' the algorithm used for the Earth Radiation Budget Experiment (ERBE). The ES-9 also contains hourly average fluxes for the month and an overall monthly average for each region. These average fluxes are given for both clear-sky and total-sky scenes. The following CERES ES9 data sets are currently available: CER_ES9_FM1+FM2_Edition1 CER_ES9_PFM+FM1+FM2_Edition1 CER_ES9_PFM+FM1+FM2_Edition2 CER_ES9_PFM+FM1_Edition1 CER_ES9_PFM+FM2_Edition1 CER_ES9_PFM+FM1_Edition2 CER_ES9_PFM+FM2_Edition2 CER_ES9_TRMM-PFM_Edition1 CER_ES9_TRMM-PFM_Edition2 CER_ES9_Terra-FM1_Edition1 CER_ES9_Terra-FM2_Edition1 CER_ES9_FM1+FM2_Edition2 CER_ES9_Terra-FM1_Edition2 CER_ES9_Terra-FM2_Edition2 CER_ES9_Aqua-FM3_Edition1 CER_ES9_Aqua-FM4_Edition1 CER_ES9_FM1+FM2+FM3+FM4_Edition1 CER_ES9_Aqua-FM3_Edition2 CER_ES9_Aqua-FM4_Edition2 CER_ES9_FM1+FM3_Edition2 CER_ES9_FM1+FM4_Edition2 CER_ES9_Aqua-FM3_Edition1-CV CER_ES9_Aqua-FM4_Edition1-CV CER_ES9_Terra-FM1_Edition1-CV CER_ES9_Terra-FM2_Edition1-CV. [Location=GLOBAL] [Temporal_Coverage: Start_Date=1998-01-01; Stop_Date=1998-08-31] [Spatial_Coverage: Southernmost_Latitude=-90; Northernmost_Latitude=90; Westernmost_Longitude=-180; Easternmost_Longitude=180] [Data_Resolution: Latitude_Resolution=2.5 degree; Longitude_Resolution=2.5 degree; Horizontal_Resolution_Range=250 km - < 500 km or approximately 2.5 degrees - < 5.0 degrees; Temporal_Resolution=hourly, daily, monthly; Temporal_Resolution_Range=Hourly - < Daily, Daily - < Weekly, Monthly - < Annual].

CLEAR-SKY ALBEDO↗

Radar Observations from the Haystack Ultrawideband Satellite Imaging Radar in 2019

The NASA Orbital Debris Program Office (ODPO) relies primarily on ground-based radar measurements to characterize the distribution of small debris, down to approximately 3 mm depending upon altitude and the sensor used, in low Earth orbit (LEO). Since the early 1990’s, the Massachusetts Institute of Technology (MIT) Lincoln Laboratory (LL) has been collecting radar measurements for the NASA ODPO under agreements with the U.S. Department of Defense. The Haystack Ultrawideband Satellite Imaging Radar (HUSIR) is the primary ground-based radar sensor used by the ODPO and provides data on orbital debris down to an approximate size of 5.5 mm below 1000km altitude using the NASA size estimation model (SEM). Since orbital debris of this size are a significant risk to both human and robotic missions in LEO, the sensitivity of this radar makes it a high-value sensor. The NASA ODPO radar measurements are conducted on a continual basis for monitoring and enabling modeling of the orbital debris environment over time. HUSIR observations from 2019 are the most recent snapshot of the environment that has been measured and analyzed to date. In recent years, HUSIR measurements indicated relatively stable populations for the orbital debris objects that it is able to detect. In 2019, several interesting events happened on-orbit, including the start of large constellation deployments into LEO, as well as the Indian anti-satellite test with Microsat-R (International Designator 2019-006A, U.S. Strategic Command Space Surveillance Network catalog number 43947). Due to these events, coupled with a general increase in the number of missions and participants launching missions in recent years, continual monitoring is necessary to determine the effects of this increased activity on the orbital debris environment. This paper will explore the results of the 2019 HUSIR radar measurements, including above-average flux measurements at lower LEO altitudes and the evolution of the flux during the time of observations.

James Murray↗

Radar Observations from the Haystack Ultrawideband Satellite Imaging Radar in 2019

The NASA Orbital Debris Program Office (ODPO) relies primarily on ground-based radar measurements to characterize the distribution of small debris, down to approximately 3 mm depending upon altitude and the sensor used, in low Earth orbit (LEO). Since the early 1990’s, the Massachusetts Institute of Technology (MIT) Lincoln Laboratory (LL) has been collecting radar measurements for the NASA ODPO under agreements with the U.S. Department of Defense. The Haystack Ultrawideband Satellite Imaging Radar (HUSIR) is the primary ground-based radar sensor used by the ODPO and provides data on orbital debris down to an approximate size of 5.5 mm below 1000km altitude using the NASA size estimation model (SEM). Since orbital debris of this size are a significant risk to both human and robotic missions in LEO, the sensitivity of this radar makes it a high-value sensor. The NASA ODPO radar measurements are conducted on a continual basis for monitoring and enabling modeling of the orbital debris environment over time. HUSIR observations from 2019 are the most recent snapshot of the environment that has been measured and analyzed to date. In recent years, HUSIR measurements indicated relatively stable populations for the orbital debris objects that it is able to detect. In 2019, several interesting events happened on-orbit, including the start of large constellation deployments into LEO, as well as the Indian anti-satellite test with Microsat-R (International Designator 2019-006A, U.S. Strategic Command Space Surveillance Network catalog number 43947). Due to these events, coupled with a general increase in the number of missions and participants launching missions in recent years, continual monitoring is necessary to determine the effects of this increased activity on the orbital debris environment. This paper will explore the results of the 2019 HUSIR radar measurements, including above-average flux measurements at lower LEO altitudes and the evolution of the flux during the time of observations.

James Murray↗

Validation of Soil Moisture Data Products from the NASA SMAP Mission

The National Aeronautics and Space Administration (NASA)Soil Moisture Active Passive(SMAP) mission has been validatingits soil moisture (SM) products since the start of data production onMarch 31, 2015. Prior to launch, the mission defined a set of criteria for core validation sites (CVS) that enable the testing of the key mission SM accuracy requirement(unbiased root-mean-square error <0.04 m3/m3). Thevalidation approach also includes other (“sparse network”) in situSM measurements, satellite SM products, model-based SM products, and field experiments. Over the past six years, the SMAP SM products have been analyzed with respect to thesereference data,and the analysis approaches themselves have been scrutinizedin an effort to best understand the products’ performance. Validation of themost recent SMAP Level 2 and 3 SMretrievalproducts (R17000) shows that the L-band (1.4 GHz) radiometer-based SM record continues to meet mission requirements. The products aregenerallyconsistentwith SM retrievals from the European Space Agency (ESA)Soil Moisture Ocean Salinity mission, althoughthere aredifferencesin some regions. The high-resolution (3-km) SM retrieval product,generated by combining Copernicus Sentinel-1 data with SMAP observations,performswithin expectations. Currently, however,there is limited availability of3-kmCVSdatato support extensive validation at this spatial scale. The most recent (version 5)SMAP Level4 SMdata assimilation productprovidingsurface and root-zone SM with complete spatio-temporal coverageat 9-km resolution also meets performance requirements. The SMAP SM validation program will continue throughout the mission life; futureplans include expanding ittoforestedand high-latituderegions

SMAP↗