Exploratory Analytic Cases and Coronagraph Exploratory Cases
Explore the source record for details and available documents.
HWO↗
SEARCH · Search NASA
Results for “START TAG”
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.
The Habitable Worlds Observatory Engineering View: Status, Plans and Opportunities
Explore the source record for details and available documents.
HWO↗
HWO TMPO Status
Habitable Worlds Observatory (HWO) Technology Maturation Project Office (TMPO) Status
HAB↗
The Habitable Worlds Observatory Engineering View: Status, Plans and Opportunities
The NASA has begun the Great Observatory Maturation Program (GOMAP) with the goal of studying and advancing the Habitable Worlds Observatory (HWO), a large ultraviolet, optical, infrared space telescope recommended by the Astro 2020 Decadal Survey. Among its many goals, HWO will obtain spectra of at least 25 exo-Earth candidates to search for signs of life and conduct transformative astrophysics at ultraviolet, optical, and near-infrared wavelengths. The observatory, like HST and JWST, will be a powerful general class observatory. This past Fall the GOMAP program stood up two study groups, the Science Technology Architecture Review Team (START) and the Technical Assessment Group (TAG) aimed at helping to study the science, technology and architecture options for this new flagship mission. This talk will discuss the engineering activities associated with these studies including the team and organization, the study plan and the use of the Concept Maturity Level (CML) approach. In addition, the talk will discuss the key initial engineering efforts, the key technology gaps, and overall engineering plans.
HWO↗
Fox Trails
1. This software utilizes python pandas to pull data from P6 databases or XER files. The software transforms the datasets into multiple main tables by joining, filtering, iteratively flattening hierarchical structured data, and pivoting datasets to give simple flat output tables. The activity table includes all of the information related to an activity including activity codes, global, EPS, and project codes, UDFs, and WBS information as separate columns. This includes the code id, code value and sequence number for all levels in hierarchical codes. The resource table is similar to the activity table and includes all of the information related to resources on activities including UPFs and resource codes. The resource time phased table takes the resource information and time phases it for the budget, forecast, late, and actual dates/units/costs that closely matches P6's user interface's values as it implements the resource curve and calendars. The wbs table contains the WBS structure broken out by levels and includes UDFs, codes, and notebook topics. The final P6 data table is the relationships table which simply contains the relationships. 2. When a user updates the tool with data (via giving it P6 project names with database username/password information or XER files) the system creates the data in #1, then creates a networkx graph with the activity data imbedded in the node data and the relationships added as edges. Each edge also has it's float calculated (working time distance between the predecessor and successor) and attached to the edge. Activities are also tagged as a potential start of a path based on their constraints, constraint dates, remaining start date, and activity status. When a user enters an activity ID into the UI, it runs a shortest path calculation on the network graph between each node tagged as potential start to the entered activity id based on the float tagged on the edge. Each path returned by the algorithm contains all of the nodes on the path in order, as well as the total float of the edges that make the path. This data is then collected and returned to the user in the form of a gantt chart with groupings for each path that includes the total float for each group. 3. Similar to 2, if the user passes through a reference dataset each activity set in the path is checked to see if it had a path in the reference dataset, if that path was the primary path between the start and end activities, and what has changed regarding logic and durations. These changes are color coded and summarized before sent to the user to be displayed by the UI for simple discovery. 4. Utilizing the data from #1, the user can submit desired grouping code(s) and filters to the system. The system will then pull the activities, resources, and relationships and create a gantt chart based on the groupings sent and filtered based on the filters sent. 5. The system will produce a gantt chart in a similar method to #4, but allows interactivity with the data. As the user interacts with the gantt chart, the software captures the changes and stores it with the user making the change so that project controls and implement those changes in P6.
Fox, Ben↗
Performance Evaluation of 40 cm Ion Optics for the NEXT Ion Engine
The results of performance tests with two 40 cm ion optics sets are presented and compared to those of 30 cm ion optics with similar aperture geometries. The 40 cm ion optics utilized both NSTAR and TAG (Thick-Accelerator-Grid) aperture geometries. All 40 cm ion optics tests were conducted on a NEXT (NASA's Evolutionary Xenon Thruster) laboratory model ion engine. Ion optics performance tests were conducted over a beam current range of 1.20 to 3.52 A and an engine input power range of 1.1 to 6.9 kW. Measured ion optics' performance parameters included near-field radial beam current density profiles, impingement-limited total voltages, electron backstreaming limits, screen grid ion transparencies, beam divergence angles, and start-up transients. Impingement-limited total voltages for 40 cm ion optics with the NSTAR aperture geometry were 60 to 90 V lower than those with the TAG aperture geometry. This difference was speculated to be due to an incomplete burn-in of the TAG ion optics. Electron backstreaming limits for the 40 cm ion optics with the TAG aperture geometry were 8 to 19 V higher than those with the NSTAR aperture geometry due to the thicker accelerator grid of the TAG geometry. Because the NEXT ion engine provided beam flatness parameters that were 40 to 63 percent higher than those of the NSTAR ion engine, the 40 cm ion optics outperformed the 30 cm ion optics.
Soulas, George C.↗
Johnson Space Center's Free Range Bicycle Program.- Fall 2015 Intern Report
NASA's Johnson Space Center is a big place, encompassing 1,620 acres and more than a hundred buildings. Furthermore, there are reportedly 15 thousand employees, all of which have somewhere to be. To facilitate the movement of all these people JSC has historically relied on human power. Pedaling their way towards deep space, bicycles have been the go to method. Currently there are about 200 Free Range Bicycles at JSC. Free Range Bicycles belong to nobody, except NASA, and are available for anybody to use. They are not to be locked or hidden (although frequently are) and the intention is that there will always be a bike to hop on to get where you're going (although it may not be the bike you rode in on). Although not without its own shortcomings, the Free Range Bicycle Program has continued to provide low cost, simple transportation for NASA's JSC. In addition to the approximately 200 Free Range Bicycles, various larger divisions (like engineering) will often buy a few dozen bikes for their team members to use or individuals will bring their own personal bike to either commute or use on site. When these bicycles fall into disrepair or are abandoned (from retirees etc) they become a problem at JSC. They are an eye sore, create a safety hazard and make it harder to find a working bike in a time of need. The Free Range Program hopes to address this first problem by "tagging out" abandoned or out of service bicycles. A bright orange "DO NOT OPERATE" tag is placed on the bike and given a serial number for tracking purposes. See picture to the right. If the bike has an active owner with intentions to repair the bike the bottom of the tag has instructions for how to claim the abandoned bicycle. After being tagged the owner of the bicycle has 30 days to claim the bicycle and either haul it off site or get it repaired (and labeled) in accordance with Johnson's Bicycle Policy. If the abandoned bicycle is not claimed within 30 days it becomes the property of the Government. The bicycle is then (in short) repaired, labeled, documented and converted to a free range bicycle. Bikes beyond repair are cannibalized of useable parts and then scrapped. That was nearly the first thing I did when arriving at work. After getting settled in and coordinating the purchase of 50 new bicycles (elaboration below); I started combing the Center. Bikes are hidden and tucked away in the oddest of places and it was my priority to root all of them out. I tagged 70 bikes on the center, setting a record. I tagged so many bikes I ran out tags and had to make more. Long ago it was discovered that the same harsh elements that wreak havoc on the bikes, destroy the tags before the 30 day timeframe. The tags are labeled with instructions on how to claim the bike and numbered, then these paper labels are laminated with packing tape. It sounds like a simple process but nothing fits right, everything has to be trimmed, put on straight and is generally a pain in the neck. So I made an assembly process and knocked out a few hundred to save having to do it again for a while. I walked the center and tagged bikes at every building hiding in nearly every nook and cranny. Thus, in conclusion, I've done many things here at JSC on my first term and had a blast doing it. I've learned a lot from my multi-faceted roles and continual challenges. In short I've done my best to get folks at JSC on bikes and keep folks at JSC on bikes and tended a flock of free range bicycles. Everything from turning the rusty bolts and oiling chains to coordinating a $20,000 deal on 50 new free range bicycles. I am proud of the bicycle shop I have built and am infinitely grateful to the people who lead, help, guide and support me. I have fixed a great number of bicycles and cleaned the center of unsightly and unsafe piles of bicycles. I am immensely thankful for this opportunity to learn and serve and appreciate the privilege of coming back for a second term. A second term, in which I will continue to develop this awesome program.
Lee-Stockton, Willem↗
Rapid Model Import Tool (RMIT)
Our project is about developing a tool to implement conversion of 3D Computer Aided Design (CAD) models produced with software such as Delmia, 3DS Max, or Maya, into a size and format compatible with the Unity 3D environment. RMIT will be used to aid KSC engineering personnel in the design, development, testing, operations, and training on spacecraft, launch vehicles, facilities, and ground support equipment. For our project, we are using Blender, a free/open-source 3D graphics software, with the goal of developing, testing, and deploying a 3D CAD model converter tool. I worked on using Blender to import 3D CAD models exported from CATIA software into Collada file format. The Collada file format has file extension DAE. Importing the Collada DAE file as is into Blender, generates dots and dashes. In 3DS Max, there is an existing OpenCollada plugin and with that plugin, 3DS Max can import the DAE file successfully. But, Blender does not seem to have an OpenCollada plugin, so I worked on writing a new OpenCollada plugin for Blender. Since 3DS Max was able to display the image, I looked into comparing differences between the original DAE file and the DAE file exported from 3DS Max using the OpenCollada plugin. As Collada documents describing digital assets are XML files with file extension DAE, Collada files contains XML tags, making them easily modifiable. After some research, it appears that Blender does not like primitive 2D tags like tristrips and trifans. Changing those tags to polygons slightly improved the image, but the pieces were exploded. I found after further research comparing differences between the original file and the file exported from 3DS Max that the values inside the translate tags in the original file are scaled down by a factor of 25.4 in the exported file from 3DS Max, representing the millimeters to inches conversion (1 inch = 25.4 millimeters). After scaling down values inside all of the translate tags by 25.4, the exploded pieces stuck back in, but the image needed further improvement. I have been able to create a new plugin in Blender that takes the original DAE file, replaces the primitive 2D tags tristrips and trifans with polygons, scales down the values inside the translate tags by a factor of 25.4, and saves the changes into a temporary DAE file. After the temporary DAE file is imported into Blender, the temp file is then deleted, keeping the original DAE file intact. Starting with a DAE file that is exported using the NASA Enterprise Visualization Application (NEVA), a Collada exporter, from CATIA gives better results. NEVA is a Design Visualization product that is used for exporting 3D models from CATIA. With NEVA, the up axis is defined in the top-level node if navigation gravity is enabled. With that file, just replacing the primitive tags tristrips and trifans with polygons in yields a much improved image in Blender. As we identify more differences between the original DAE file and the DAE file exported from 3DS Max, this plugin can be improved further. Our goal is to have a model that is formatted and sized for import into Unity, and we are trying out different 3D programs to see which will work best.
Ayyangar, Arjun↗
An object-oriented, technology-adaptive information model
The primary objective was to develop a computer information system for effectively presenting NASA's technologies to American industries, for appropriate commercialization. To this end a comprehensive information management model, applicable to a wide variety of situations, and immune to computer software/hardware technological gyrations, was developed. The model consists of four main elements: a DATA_STORE, a data PRODUCER/UPDATER_CLIENT and a data PRESENTATION_CLIENT, anchored to a central object-oriented SERVER engine. This server engine facilitates exchanges among the other model elements and safeguards the integrity of the DATA_STORE element. It is designed to support new technologies, as they become available, such as Object Linking and Embedding (OLE), on-demand audio-video data streaming with compression (such as is required for video conferencing), Worldwide Web (WWW) and other information services and browsing, fax-back data requests, presentation of information on CD-ROM, and regular in-house database management, regardless of the data model in place. The four components of this information model interact through a system of intelligent message agents which are customized to specific information exchange needs. This model is at the leading edge of modern information management models. It is independent of technological changes and can be implemented in a variety of ways to meet the specific needs of any communications situation. This summer a partial implementation of the model has been achieved. The structure of the DATA_STORE has been fully specified and successfully tested using Microsoft's FoxPro 2.6 database management system. Data PRODUCER/UPDATER and PRESENTATION architectures have been developed and also successfully implemented in FoxPro; and work has started on a full implementation of the SERVER engine. The model has also been successfully applied to a CD-ROM presentation of NASA's technologies in support of Langley Research Center's TAG efforts.
Anyiwo, Joshua C.↗
Recovery of stable isotope taggants along a wet production pathway of uranium dioxide
Stable isotope taggants added to nuclear materials could be utilized as diagnostic nuclear forensics signatures; however, intentionally adding taggants is a relatively new and untested concept with respect to the nuclear fuel cycle. Here, in this study, we added trace amounts of stable Mo and W isotope taggants to starting materials used to synthesize UO 2 along a wet synthesis pathway. Successful incorporation and recovery of the Mo and W taggants was achieved in the UO 2 product and all its precursors. This study demonstrates the efficacy of stable isotope tagging along a wet UO 2 production pathway.
Nuclear forensics↗
The Joint Confidence Level Paradox: A History of Denial
This paper is intended to provide a reliable methodology for those tasked with generating price tags on construction (C0F) and research and development (R&D) activities in the NASA performance world. This document consists of a collection of cost-related engineering detail and project fulfillment information from early agency days to the present. Accurate historical detail is the first place to start when determining improved methodologies for future cost and schedule estimating. This paper contains a beneficial proposed cost estimating method for arriving at more reliable numbers for future submits. When comparing current cost and schedule methods with earlier cost and schedule approaches, it became apparent that NASA's organizational performance paradigm has morphed. Mission fulfillment speed has slowed and cost calculating factors have increased in 21st Century space exploration.
Butts, Glenn↗
What Can We Learn from One Billion Ground System Log Messages?
Shortage of log-based data in a ground system they have traditionally been the under achievers in a satellite ground system. This is due to several factors: Once log messages scroll out of view on the TTC event console window they are soon forgotten. Application and system log files are scattered across directories within a system, across a multitude of servers, and across one or more databases making access cumbersome. Typical tools to perform log file content searching are generally crude and typically only employed as part of trouble-shooting exercises.As we move towards satellite constellations and fleets and add even more status information, the number of messages keeps growing. One mission now estimates that they could generate 3,000,000 messages per day 1 billion per year - for the life of their mission. What to do with those 1 billion messages? That is the challenge. With the recent technological advances in the management of large data sets, text-based processing, and data analytics, there are now capabilities that we can provide to the ground system engineers and satellite operators to address what we postulate are missed opportunities. Advanced real-time log analysis can allow us to be less reactionary in favor of being more proactive. Analytics goals include the ability to: Identify root cause of unexpected events, failures or error conditions enabled by correlating disparate data. Detect security breaches attempts before they are successful. Help admins ensure IT resources continue running optimally. Identify trends and patterns that may indicate impending failures or error conditions for valuable assets before they happen. Compare satellites in a fleet or constellation in terms of number of alarms, number of command sent to them, etc.. Answer questions like "Are the operations support needs increasing over the past year?" or "Have we seen this combination of alarm conditions before?" But really, once the tools are readily available the users will start realizing what can be done with their new powers. In this presentation we will show the results of analyzing millions of actual mission operations log messages, how the results can be displayed to the user, and how new products now available as open source can be applied to the challenges of large scale time-tagged text-based mission operations messages. Flight operations team members believe that this is a powerful new option for how they assess overall system and space asset health. Technical descriptions of the design, tools, and storage will be provided. One billion messages? Bring'em on!
Orsborne, Sharon↗
MSL-RAD Cruise Operations Concept
The Mars Science Laboratory (MSL) payload includes the Radiation Assessment Detector (RAD) instrument, intended to fully characterize the radiation environment for the MSL mission. The RAD instrument operations concept is intended to reduce impact to spacecraft resources and effort for the MSL operations team. By design, RAD autonomously performs regular science observations without the need for frequent commanding from the Rover Compute Element (RCE). RAD operates with pre-defined "sleep" and "observe" periods, with an adjustable duty cycle for meeting power and data volume constraints during the mission. At the start of a new science observation, RAD performs a pre-observation activity to assess count rates for selected RAD detector elements. Based on this assessment, RAD can enter "solar event" mode, in which instrument parameters (including observation duration) are selected to more effectively characterize the environment. At the end of each observation period, RAD stores a time-tagged, fixed length science data packet in its non-volatile mass memory storage. The operating cadence is defined by adjustable parameters, also stored in non-volatile memory within the instrument. Periodically, the RCE executes an on-board sequence to transfer RAD science data packets from the instrument mass storage to the MSL downlink buffer. Infrequently, the RAD instrument operating configuration is modified by updating internal parameter tables and configuration entries.
Mars Science Laboratory (MSL)↗
Label-based Virtual Directories In dCache
Traditional filesystems organize data in directories. These directories are typically a collection of files whose grouping is based on a single criterion, e.g., the starting date of an experiment, experiment name, beamline ID, measurement device, or instrument. However, each file in a directory can belong to several logical groups, such as a special event type, experiment condition, or a part of a selected dataset. dCache is a storage system developed to store large amounts of scientific data, used by many HEP and Photon Science experiments. With recent developments in dCache, we have introduced a concept of file tagging, which dynamically groups files with the same label into virtual directories. The file labels can be added, removed, renamed, and deleted through the admin interface or via REST API. The files in virtual directories are exposed through all protocols supported by dCache. This contribution will describe the details of the implementation for file tagging in dCache and present our future development plans on automatic metadata extractions, a feature that will significantly simplify data management. Additionally, we are exploring the future use of virtual directories as a way to translate scientific data catalogs into filesystem views for direct data analysis.
Sahakyan, Marina [DESY]↗
First-Generation Jet Propulsion Laboratory "Hockey-Puck" Free-Flying Magnetometers for Distributed In-Situ Multiprobe Measurement of Current Density Filamentation in the Northern Auroral Zone: Enstrophy Mission
The sub-orbital rocket mission was a collaborative project between the University of New Hampshire, Cornell University, and the Jet Propulsion Laboratory (JPL) to study filamentation phenomena in the northern Auroral zone. The Enstrophy mission test flies the JPL Free-Flying Magnetometer (FFM) concept. The FFM technology development task has been funded by NASA develop miniaturized, low-power, integrated "sensorcrafts". JPL's role was to design, integrate, test, and deliver four FFMs for deployment from the sounding rocket, allowing a unique determination of curl-B. This provides a direct measurement of magnetic-field-aligned current density along the rocket trajectory. A miniaturized three-axis fluxgate magnetometer was integrated with a 4-channel 22-bit sigma-delta Analog to Digital Converter (ADC), four temperature sensors, digital control electronics, seven (Li-SOCl2) batteries, two (4 deg x 170 deg field of view) sun-sensors, a fan-shaped-beam laser diode beacon, a (16 MHz) stable Temperature Compensated Crystal Oscillator (TCXO) clock, Radio Frequency (RF) communication subsystem, and an antenna for approximately 15 minutes of operation where data was collected continuously and transmitted in three (3) bursts (approximately 26 seconds each) to ground station antennas at Poker Flat, Alaska. FFMs were stowed within two trays onboard the rocket during the rocket launch and were released simultaneously using the spinning action of the rocket at approximately 300 km altitude (approximately 100 sec. into the flight). FFMs were deployed with spin rate of approximately 17 Hz and approximately 3 m/sec linear velocity with respect to the rocket. For testing purposes while the rocket was in the launch pad and during flight prior to release of FFMs from the rocket, commands (such as "power on", "test", "flight", "power off', and clock "Reset" signal) were transmitted via a infrared Light Emitting Diode to an infrared detector in the FFM. Special attention was paid to low magnetic signature electronic design and choice of materials in packaging. The miniaturized fluxgate magnetometers had a range of 1-60000 nT with 0.1% full-scale linearity. The frequency range of interest for magnetic measurement was 10 mHz - 50 Hz. Digital data from the magnetometer's three axes were placed in a 4MB Static Random Access Memory (SRAM) in data packages (frames) formatted together with time tags and frame ID. After a specified time was elapsed, the data were Viterbi encoded and transmitted at a rate of 100 kbps (BPSK). Each of the four FFMs transmitted at different frequency. These carrier frequencies were in the range of 2200-2300 MHz. The antenna was a single patch on a high dielectric constant substrate covering one end-plate of the hockey-puck-sized unit. The local clocks aboard the FFMs were reset at the start of the mission and stayed synchronized within 3 msec during the mission. Position of each FFM with respect to the rocket is calculated by the knowledge of its release velocity (measured at exit point of the FFM launcher tract) providing an accuracy of 1 m over the maximum range of 3 km. Spatial and temporal nature of observants can be separated to within 3 m in space or 3 msec time interval.
Javadi, H.↗
The ATLAS experiment at the CERN Large Hadron Collider: a description of the detector configuration for Run 3
The ATLAS detector is installed in its experimental cavern at Point 1 of the CERN Large Hadron Collider. During Run 2 of the LHC, a luminosity of ℒ = 2 × 10 34 cm -2 s -1 was routinely achieved at the start of fills, twice the design luminosity. For Run 3, accelerator improvements, notably luminosity levelling, allow sustained running at an instantaneous luminosity of ℒ = 2 × 10 34 cm -2 s -1 , with an average of up to 60 interactions per bunch crossing. The ATLAS detector has been upgraded to recover Run 1 single-lepton trigger thresholds while operating comfortably under Run 3 sustained pileup conditions. A fourth pixel layer 3.3 cm from the beam axis was added before Run 2 to improve vertex reconstruction and b-tagging performance. New Liquid Argon Calorimeter digital trigger electronics, with corresponding upgrades to the Trigger and Data Acquisition system, take advantage of a factor of 10 finer granularity to improve triggering on electrons, photons, taus, and hadronic signatures through increased pileup rejection. The inner muon endcap wheels were replaced by New Small Wheels with Micromegas and small-strip Thin Gap Chamber detectors, providing both precision tracking and Level-1 Muon trigger functionality. Trigger coverage of the inner barrel muon layer near one endcap region was augmented with modules integrating new thin-gap resistive plate chambers and smaller-diameter drift-tube chambers. Tile Calorimeter scintillation counters were added to improve electron energy resolution and background rejection. Upgrades to Minimum Bias Trigger Scintillators and Forward Detectors improve luminosity monitoring and enable total proton-proton cross section, diffractive physics, and heavy ion measurements. These upgrades are all compatible with operation in the much harsher environment anticipated after the High-Luminosity upgrade of the LHC and are the first steps towards preparing ATLAS for the High-Luminosity upgrade of the LHC. This paper describes the Run 3 configuration of the ATLAS detector.
72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
Time-Tag Generation Script
Time-Tag Generation Script (TTaGS) is an application program, written in the AWK scripting language, for generating commands for aiming one Ku-band antenna and two S-band antennas for communicating with spacecraft. TTaGS saves between 2 and 4 person-hours per every 24 hours by automating the repetitious process of building between 150 and 180 antenna-control commands. TTaGS reads a text database of communication satellite schedules and a text database of satellite rise and set times and cross-references items in the two databases. It then compares the scheduled start and stop with the geometric rise and set to compute the times to execute antenna control commands. While so doing, TTaGS determines whether to generate commands for guidance, navigation, and control computers to tell them which satellites to track. To help prevent Ku-band irradiation of the Earth, TTaGS accepts input from the user about horizon tolerance and accordingly restricts activation and effects deactivation of the transmitter. TTaGS can be modified easily to enable tracking of additional satellites and for such other tasks as reading Sun-rise/set tables to generate commands to point the solar photovoltaic arrays of the International Space Station at the Sun.
Jackson, Dan E.↗
Trip-Induced Transition Measurements in a Hypersonic Boundary Layer Using Molecular Tagging Velocimetry
Measurements of mean streamwise velocity, fluctuating streamwise velocity, and instantaneous streamwise velocity profiles in a hypersonic boundary layer were obtained over a 10-degree half-angle wedge model. A laser-induced fluorescence-based molecular tagging velocimetry technique was used to make the measurements. The nominal edge Mach number was 4.2. Velocity profiles were measured both in an untripped boundary layer and in the wake of a 4-mm diameter cylindrical tripping element centered 75.4 mm downstream of the sharp leading edge. Three different trip heights were investigated: k = 0.53 mm, k = 1.0 mm and k = 2.0 mm. The laminar boundary layer thickness at the position of the measurements was approximately 1 mm, though the exact thickness was dependent on Reynolds number and wall temperature. All of the measurements were made starting from a streamwise location approximately 18 mm downstream of the tripping element. This measurement region continued approximately 30 mm in the streamwise direction. Additionally, measurements were made at several spanwise locations. An analysis of flow features show how the magnitude, spatial location, and spatial growth of streamwise velocity instabilities are affected by parameters such as the ratio of trip height to boundary layer thickness and roughness Reynolds number. The fluctuating component of streamwise velocity measured along the centerline of the model increased from approximately 75 m/s with no trip to +/-225 m/s with a 0.53-mm trip, and to +/-240 m/s with a 1-mm trip, while holding the freestream Reynolds number constant. These measurements were performed in the 31-inch Mach 10 Air Tunnel at the NASA Langley Research Center.
Bathel, Brett F.↗