Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “STEP file”

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 145 records · Page 8

Converting from CVF to AAF

A computer program called dsn config converter automates what had been a manual process for updating the multimission adaptation file (multi.aaf) used by a multiple-mission-command-sequence-generating process comprised of a combination of the AUTOGEN and APGEN programs mentioned in the immediately preceding article. The program converts the dsn_config.cvf file that provides DSN (Deep Space Network) antenna configuration code mappings from a context variable file (CVF) format used in another part of the command generation process to an APGEN activity file (AAF) format used by AUTOGEN and APGEN. Whereas previously, the information in the dsn_config.cvf file was manually encoded into the multi.aaf file, now the program automatically generates a dsn_config.aaf file from the dsn_config.cvf file. As part of this development effort the multi.aaf file was adapted to use the new dsn_config.aaf representations. Through this automation a tedious error-prone step has now been replaced by a quick and robust step.

Gladden, Roy E.↗

Maximizing the Volume of Collocated Data from Two Coordinated Suborbital Platforms

Suborbital (e.g., airborne) campaigns that carry advanced remote sensing and in situ payloads provide detailed observations of atmospheric processes, but can be challenging to use when it is necessary to geographically collocate data from multiple platforms that make repeated observations of a given geographic location at different altitudes. This study reports on a data collocation algorithm that maximizes the volume of collocated data from two coordinated suborbital platforms and demonstrates its value using data from the NASA Aerosol Cloud Meteorology Interactions Over the western Atlantic Experiment (ACTIVATE) suborbital mission. A robust data collocation algorithm is critical for the success of the ACTIVATE mission goal to develop new and improved remote sensing algorithms, and quantify their performance. We demonstrate the value of these collocated data to quantify the performance of a recently developed vertically resolved lidar + polarimeter–derived aerosol particle number concentration (Na ) product, resulting in a range-normalized mean absolute deviation (NMAD) of 9% compared to in situ measurements. We also show that this collocation algorithm increases the volume of collocated ACTIVATE data by 21% compared to using only nearest-neighbor finding algorithms alone. Additional to the benefits demonstrated within this study, the data files and routines produced by this algorithm have solved both the critical collocation and the collocation application steps for researchers who require collocated data for their own studies. This freely available and open-source collocation algorithm can be applied to future suborbital campaigns that, like ACTIVATE, use multiple platforms to conduct coordinated observations, e.g., a remote sensing aircraft together with in situ data collected from suborbital platforms.

Atmosphere↗

Development and validation of an advanced low-order panel method

A low-order potential-flow panel code, PMARC, for modeling complex three-dimensional geometries, is currently being developed at NASA Ames Research Center. The PMARC code was derived from a code named VSAERO that was developed for Ames Research Center by Analytical Methods, Inc. In addition to modeling potential flow over three-dimensional geometries, the present version of PMARC includes several advanced features such as an internal flow model, a simple jet wake model, and a time-stepping wake model. Data management within the code was optimized by the use of adjustable size arrays for rapidly changing the size capability of the code, reorganization of the output file and adopting a new plot file format. Preliminary versions of a geometry preprocessor and a geometry/aerodynamic data postprocessor are also available for use with PMARC. Several test cases are discussed to highlight the capabilities of the internal flow model, the jet wake model, and the time-stepping wake model.

Ashby, Dale L.↗

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence K - Raw Data

Sequence K: Step AOA, Probes (P) This sequence was designed to quantify the 3-D blade static angle-of-attack response in the presence of rotational influences by varying the blade pitch angle. Sequence K used an upwind, rigid turbine with a 0° cone angle. The wind speeds ranged from 6 m/s to 20 m/s, and data were collected at yaw angles of 0° and 30°. The rotor rotated at 72 RPM. Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to -99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. The blade pitch angle ramped continuously at 0.18°/s over a wide range of increasing and decreasing pitch angles. A step sequence was also performed. The blade pitch was stepped 5°, the flow was allowed to stabilize, and the pitch angle was held for 8 seconds. Then the pitch angle step was repeated. Again, a wide range of pitch angles was obtained, both increasing and decreasing. The file lengths for this sequence varied from 96 seconds to 6 minutes, depending on the pitch angle range. Some short points were collected at 0° yaw and 3° pitch to verify the functionality of the instrumentation. The file name convention used the initial letter K, followed by two digits specifying wind speed, followed by two digits for yaw angle, followed by RU, RD, or ST, followed by the repetition digit. The angle-of-attack motion was differentiated by RU (ramp up), RD (ramp down), and ST (step down then step up). This sequence is related to sequences L and R.

17 WIND ENERGY↗

UAE6 - Wind Tunnel Tests Data - UAE6 - Sequence L - Raw Data

Sequence L: Step AOA, Parked (P) This sequence was designed to quantify the 3-D blade static angle-of-attack response in the absence of rotational influences by varying the blade pitch angle. This test sequence used an upwind, rigid turbine with a 0° cone angle. Wind speeds of 20 m/s and 30 m/s were used, and all data were collected at a yaw angle of 0°. The rotor was parked with the instrumented blade fixed at 0° azimuth, and the rotor lock was installed (see Appendix A). Blade and probe pressure measurements were collected. The teeter dampers were replaced with rigid links, and these two channels were flagged as not applicable by setting the measured values in the data file to -99999.99 Nm. The teeter link load cell was pre-tensioned to 40,000 N. The blade pitch angle ramped continuously at 0.18°/s over a wide range of increasing and decreasing pitch angles. A step sequence was also performed. The blade pitch was stepped 5°, the flow was allowed to stabilize, and the pitch angle was held for 8 seconds. Then the pitch angle step was repeated. Again, a wide range of pitch angles was obtained, both increasing and decreasing. The file lengths for this sequence varied from 5 to 10 minutes, depending on the pitch angle range. The file name convention used the initial letter L followed by two digits specifying wind speed, followed by 00 for yaw angle, followed by RU, RD, or ST, followed by the repetition digit. The angle-of-attack motion was differentiated by RU (ramp up), RD (ramp down), and ST (step down, then step up). This sequence is related to sequences K and R.

17 WIND ENERGY↗

TURBOMAT-FR: Turbomachinery Aeroelastic Forced Response Analysis Automation Using MATLAB®: PART 1

The primary aim of this effort is to develop a software tool named “Turbomachinery Aeroelastic Analysis Tool for Forced Response (TURBOMAT-FR)” using MATLAB® (The MathWorks, Inc.) scripts. The tool will aid in performing routine forced response analysis of turbomachinery fan blades with the aid of the modal summation method (MSUM). The MSUM approach requires a modal solution consisting of modal displacements, modal frequencies, and modal stresses. The MATLAB® scripts facilitate easy extraction of the required quantities from the computational fluid dynamics (CFD) and MSC Nastran (Hexagon AB) solution files. These quantities are subsequently utilized by the MSUM approach to perform a complete forced response analysis.The MATLAB® scripts in TURBOMAT-FR are utilized in postprocessing of the MSC Nastran finite element analysis outputs in three types of solutions or steps, namely (1) stresses and displacements from static and steady response solution, (2) unsteady stresses and displacements from direct forced response solution, and (3) modal solution containing modal displacements and modal stresses. In step (4), separate MATLAB® scripts are also developed to read the processed outputs in step (3) and perform forced response analysis using MSUM. The TURBOMAT-FR MATLAB® scripts mentioned previously are presented in two reports designated “Part 1” and “Part 2”. The current report, Part 1, presents the scripts needed to accomplish steps (1) and (2), noted previously. This will be exclusively useful for performing only the static and steady response analysis and the forced response analysis using the direct forced response solution approach. Part 2 contains the TURBOMAT-FR MATLAB® scripts needed to accomplish steps (3) and (4). The MATLAB® scripts given in Part 2 facilitate the calculation of unsteady stresses using MSUM and provide an automated procedure associated with aeroelastic forced response analysis with different pressure files for the same structural model. The unsteady stresses calculated using MSUM in Part 2 can be compared with those presented in Part 1. A cantilevered blade-alone model subjected to a realistic pressure loading to a boundary was used for static and unsteady direct forced response analysis to demonstrate the effectiveness of the TURBOMATFR MATLAB® scripts.

MATLAB-Scripts↗

Procedure Parsing: A Method for Parsing Handwritten Documents into Computer-Based Procedures

The nuclear industry is heavily procedure driven, where almost everything has a step-by-step instruction that is expected to be followed in detail. Historically, these procedures were printed on paper copies. Recently, the industry transitioned towards electronic copies (i.e., PDFs on tablets). One major drive for this transition is the introduction of human error and loss of situation awareness when using paper copies. However, electronic copies of documents inherently have the same error traps as their paper cousins. Therefore, there is an increased interest in a way to utilize the information in the step-by-step guidance, but to present it in a dynamic manner that guides the user and adapts to any encountered conditions. Researchers at Idaho National Laboratory propose a flexible, automated method based on document parsing and augmented by natural language processing (NLP) techniques, to address these shortcomings and capitalize on these recent advancements in machine learning. The proposed method provides a cost-effective solution for computer-assisted procedure parsing of hand-written control room procedures, originally authored in Word or PDF formats, into instructions that can be displayed as computer-based procedures (CBP) in a modern graphical user interface. The researchers devised, implemented and demonstrated the Operating Procedure Extender for Novel Systems (OPENS) method in 2020. The key to OPENS is to map the original procedure text into a context-free grammar, tying content to equipment, locations, and other steps, actions, etc. This formal grammar is then used to isolate and define keywords and actions verbs, such as “measure” or “evaluate” and tie them to specific equipment referenced within that step or located in other steps, substeps, actions, subactions and tables throughout the procedure. OPENS generates an abstract syntax tree from the document which it uses to store a copy of this information in the open-standard, machine-readable and human-readable file formats XML and JSON. The XML is useful to preserve the relational aspects of the procedure for referencing tables and branching information so the user can be directed to the next appropriate active step based on the values entered for that step and previous steps. The JSON is useful for storing and exchanging data objects used to track responses to previous steps and state changes in simulated environments. In future iterations, these formats can also be used for storing more detailed information about input during plant operation or simulation. The techniques the researcher developed could further be improved by integration of recent advancements in machine learning. NLP methods could standardize documents, correct for grammatical error, and provide automated semantic validation. The researcher expects that self-supervised techniques applied to collections of natural language instructions could strengthen the model with broader context. All these methods together give us a practical way to automatically extract protocols from documents and user interactions, empowering researchers, procedure writers and nuclear operators while moving the industry forward.

99 GENERAL AND MISCELLANEOUS↗

Synthetic Biology PacBio/JAWS QC Analysis (PBJ) v3.0

This software was designed as a sequence validation tool for the assembly of synthetic constructs. It analyzes FASTQ files against a list of reference sequences, combining the results from eight sequencing libraries to generate a summary, and the files needed to view the results in the Integrative Genomics Viewer (IGV) application for manual verification. This was developed for FASTQ files generated by PacBio sequencing, but could be used on any FASTQ files that do not have paired end reads. It can be used to analyze one - eight libraries at a time, and assumes that each construct sequence in the reference will be in each pool, however, this is not a requirement. This is used to identify which libraries of pooled sequences contains a perfect match, or fixable match to the reference file. This pipeline uses many freely available open source libraries, the value added is that in our application the steps of the pipeline are defined in Workflow Description Language (WDL) and run through the Cromwell workflow engine in Docker containers, for easy distribution and set up, as well as the user friendly html summary that is generated.

Simirenko, Lisa↗

SynBio QC Dual Barcode QC (DBC) v1.0

This software was designed as a sequence validation tool for the assembly of synthetic constructs, where the constructs have a high degree of similarity and thus are barcoded prior to the sequencing library prep. It demultiplexes each FASTQ file for each barcode, then analyzes the resulting FASTQ files against a list of reference sequences for that barcode/library, combining the results from eight sequencing libraries to generate a summary, and the files needed to view the results in the Integrative Genomics Viewer (IGV) application for manual verification. This was developed for FASTQ files generated by PacBio sequencing, but could be used on any FASTQ files that do not have paired end reads. It can be used to analyze one - eight libraries at a time. Each construct is independently analyzed with only the sequences with the same barcode, in the same pooled library. Then the results are combined into a user friendly summary. This is used to identify which libraries of pooled sequences contains a perfect match, or fixable match to the reference file. This pipeline uses many freely available open source libraries, the value added is that in our application the steps of the pipeline are defined in Workflow Description Language (WDL) and run through the Cromwell workflow engine in Docker containers, for easy distribution and set up, as well as the user friendly html summary that is generated.

Simirenko, Lisa↗

LIM1TR: Lithium-Ion Modeling with 1-D Thermal Runaway (V.1.0)

LIM1TR (Lithium-Ion Modeling with 1-D Thermal Runaway) is an open-source code that uses the finite volume method to simulate heat transfer and chemical kinetics on a quasi 1-D domain. The target application of this software is to simulate thermal runaway in systems of lithium-ion batteries. The source code for LIM1TR can be found at https://github.com/ajkur/lim1tr. This user guide details the steps required to create and run simulations with LIM1TR starting with setting up the Python environment, generating an input file, and running a simulation. Additional details are provided on the output of LIM1TR as well as extending the code with custom reaction models. This user guide concludes with simple example analyses of common battery thermal runaway scenarios. The corresponding input files and processing scripts can be found in the “Examples” folder in the on-line repository, with select input files included in the appendix of this document.

25 ENERGY STORAGE↗

Enhancement of the Earth Science and Remote Sensing Group's Website and Related Projects

The major problem addressed throughout the term was the need to update the group's current website, as it was outdated and required streamlining and modernization. The old Gateway to Astronaut Photography of the Earth website had multiple components, many of which involved searches through expansive databases. The amount of work required to update the website was large and due to a desired release date, assistance was needed to help build new pages and to transfer old information. Additionally, one of the tools listed on the website called Image Detective had been underutilized in the past. It was important to address why the public was not using the tool and how it could potentially become more of a resource for the team. In order to help with updating the website, it was necessary to first learn HTML. After assisting with small edits, I began creating new pages. I utilized the "view page source" and "developer" tools in the internet browser to observe how other websites created their features and to test changes without editing the code. I then edited the code to create an interactive feature on the new page. For the Image Detective Page I began an evaluation of the current page. I also asked my fellow interns and friends at my University to offer their input. I took all of the opinions into account and wrote up a document regarding my recommendations. The recommendations will be considered as I help to improve the Image Detective page for the updated website. In addition to the website, other projects included the need for additional, and updated image collections, along with various project requests. The image collections have been used by educators in the classroom and the impact crater collection was highly requested. The glaciers collection focused mostly on South American glaciers and needed to include more of the earth's many glaciers. The collections had not been updated or created due to the fact that related imagery had not been catalogued. The process of cataloging involves identifying the center point location of the image and feature identification. Other project needs included collecting night images of India in for publishing. Again, many of the images were not catalogued and the database was lacking in night time imagery for that region. The last project was to calculate the size of mega fans in South Africa. Calculating the fan sizes involved several steps. To expedite the study, calculations needed to be made after the base maps had been created. Using data files that included an outline of the mega fans on a topographic map, I opened the file in Photoshop, determined the number of pixels within the outlined area, created a one degree squared box, determined the pixels within the box, converted the pixels within the box to kilometers, and then calculated the fan size using this information. Overall, the internship has been a learning experience for me. I have learned how to use new programs and I developed new skills. These These skills can help me as I enter into the next phase of my career. Learning Photoshop and HTML in addition to coding in Dreamweaver are highly sought after skills that are used in a variety of fields. Additionally, the exposure to different aspects of the team and working with different people helped me to gain a broader set of skills and allowed me to work with people with different experiences. The various projects I have worked on this summer have directly benefitted the team whether it was completing projects they did not have the time to do, or by helping the team reach deadlines sooner. The new website will be the best place to see all of my work as it will include the newly designed pages and will feature my updates to collections.

Coffin, Ashley↗

HarDWR - Cumulative Water Rights Curves

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. This product is the dataset used as input to the WBM model (Grogan et al., in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (submission pending). This database contains 1,744 individual .csv files, two for each Water Management Area (WMA; see here) in the 11-state region. File naming convention: WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either S for surface water rights, or G for groundwater rights. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the ### unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al., in review)

Economics↗

HarDWR - Cumulative Water Rights Curves

For a detailed description of the database of which this record is only one part, please see the HarDWR meta-record. This product is the dataset used as input to the WBM model (Grogan et al., in review; Grogan et al. 2022), and is the result of the step creating cumulative water rights curves described in Lisk et al. (submission pending). This database contains 1,744 individual .csv files, two for each Water Management Area (WMA; see here) in the 11-state region. File naming convention: WMA_[###]_[X]W.csv, where [###] is the unique identifier for each WMA, and [X] is either S for surface water rights, or G for groundwater rights. Column headers in each file: Year: the priority date year CUML: the total cumulative water rights allocated up to this priority date year (ft3s-1) Irrigation: The percent of cumulative water rights allocated to the Irrigation category up to this priority date year (%) Domestic: The percent of cumulative water rights allocated to the Domestic category up to this priority date year (%) Livestock: The percent of cumulative water rights allocated to the Livestock category up to this priority date year (%) Fish: The percent of cumulative water rights allocated to the Fish category up to this priority date year (%) Industrial: The percent of cumulative water rights allocated to the Industrial category up to this priority date year (%) Environmental: The percent of cumulative water rights allocated to the Environmental category up to this priority date year (%) Other: The percent of cumulative water rights allocated to the Other category up to this priority date year (%) In addition to the database files, there is a companion .csv file, called stateWMAs_ID.csv. The main purpose of this file is to provide the means of translating between the ### unique identifier and the various other id of the WMA the file is attached to. This translation file has five columns, which are: basinNum: The official state given alpha-numeric identifier of the WMA basinName: the state provided English name of the area, where applicable state: the state name uniID: a unique identifier we created by concatenating the state name, and underscore, and the state numerical ID ID: a unique numeric identifier we created as a requirement for the files to be used within WBM (Grogan et al., in review) The code related to the creation of this dataset can be viewed within HarDWR GitHub Repository/dataCumulationCurves.

Economics↗

User's guide to resin infusion simulation program in the FORTRAN language

RTMCL is a user friendly computer code which simulates the manufacture of fabric composites by the resin infusion process. The computer code is based on the process simulation model described in reference 1. Included in the user's guide is a detailed step by step description of how to run the program and enter and modify the input data set. Sample input and output files are included along with an explanation of the results. Finally, a complete listing of the program is provided.

Weideman, Mark H.↗

Science Opportunity Analyzer (SOA): Science Planning Made Simple

.For the first time at JPL, the Cassini mission to Saturn is using distributed science operations for developing their experiments. Remote scientists needed the ability to: a) Identify observation opportunities; b) Create accurate, detailed designs for their observations; c) Verify that their designs meet their objectives; d) Check their observations against project flight rules and constraints; e) Communicate their observations to other scientists. Many existing tools provide one or more of these functions, but Science Opportunity Analyzer (SOA) has been built to unify these tasks into a single application. Accurate: Utilizes JPL Navigation and Ancillary Information Facility (NAIF) SPICE* software tool kit - Provides high fidelity modeling. - Facilitates rapid adaptation to other flight projects. Portable: Available in Unix, Windows and Linux. Adaptable: Designed to be a multi-mission tool so it can be readily adapted to other flight projects. Implemented in Java, Java 3D and other innovative technologies. Conclusion: SOA is easy to use. It only requires 6 simple steps. SOA's ability to show the same accurate information in multiple ways (multiple visualization formats, data plots, listings and file output) is essential to meet the needs of a diverse, distributed science operations environment.

observation planning operations↗

Designing Scenarios for Controller-in-the-Loop Air Traffic Simulations

Well prepared traffic scenarios contribute greatly to the success of controller-in-the-loop simulations. This paper describes each stage in the design process of realistic scenarios based on real-world traffic, to be used in the Airspace Operations Laboratory for simulations within the Air Traffic Management Technology Demonstration 1 effort. The steps from the initial analysis of real-world traffic, to the editing of individual aircraft records in the scenario file, until the final testing of the scenarios before the simulation conduct, are all described. The iterative nature of the design process and the various efforts necessary to reach the required fidelity, as well as the applied design strategies, challenges, and tools used during this process are also discussed.

ATD1↗

Validation of CFD/Heat Transfer Software for Turbine Blade Analysis

I am an intern in the Turbine Branch of the Turbomachinery and Propulsion Systems Division. The division is primarily concerned with experimental and computational methods of calculating heat transfer effects of turbine blades during operation in jet engines and land-based power systems. These include modeling flow in internal cooling passages and film cooling, as well as calculating heat flux and peak temperatures to ensure safe and efficient operation. The branch is research-oriented, emphasizing the development of tools that may be used by gas turbine designers in industry. The branch has been developing a computational fluid dynamics (CFD) and heat transfer code called GlennHT to achieve the computational end of this analysis. The code was originally written in FORTRAN 77 and run on Silicon Graphics machines. However the code has been rewritten and compiled in FORTRAN 90 to take advantage of more modem computer memory systems. In addition the branch has made a switch in system architectures from SGI's to Linux PC's. The newly modified code therefore needs to be tested and validated. This is the primary goal of my internship. To validate the GlennHT code, it must be run using benchmark fluid mechanics and heat transfer test cases, for which there are either analytical solutions or widely accepted experimental data. From the solutions generated by the code, comparisons can be made to the correct solutions to establish the accuracy of the code. To design and create these test cases, there are many steps and programs that must be used. Before a test case can be run, pre-processing steps must be accomplished. These include generating a grid to describe the geometry, using a software package called GridPro. Also various files required by the GlennHT code must be created including a boundary condition file, a file for multi-processor computing, and a file to describe problem and algorithm parameters. A good deal of this internship will be to become familiar with these programs and the structure of the GlennHT code. Additional information is included in the original extended abstract.

Kiefer, Walter D.↗

TURBOMAT-FR: Turbomachinery Aeroelastic Forced Response Analysis Automation Using MATLAB® Part 2

The primary aim of this effort is to develop a software tool named “Turbomachinery Aeroelastic Analysis Tool for Forced Response (TURBOMAT-FR)” using MATLAB® (The MathWorks, Inc.) scripts. The tool will aid in performing routine forced response analysis of turbomachinery fan blades with the aid of the modal summation method (MSUM). The MSUM approach requires a modal solution consisting of modal displacements, frequencies, and stresses. The MATLAB® scripts facilitate easy extraction of the required quantities from the computational fluid dynamics (CFD) and MSC Nastran (Hexagon AB) solution files. These quantities are subsequently utilized by the MSUM approach to perform a complete forced response analysis using the MATLAB® scripts. The MATLAB® scripts in TURBOMAT-FR are utilized in postprocessing of the MSC Nastran finite element analysis outputs in three types of solutions or steps, namely (1) stresses and displacements from static or steady response solution, (2) unsteady stresses and displacements from direct forced response solution, and (3) modal solution containing modal displacements and modal stresses. In step (4), separate MATLAB® scripts are also developed to read the processed outputs in step (3) and perform forced response analysis using MSUM. It should be noted that the direct forced response solution from step (2) will provide for a comparison with those obtained from the MSUM approach in steps (3) and (4). The TURBOMAT-FR MATLAB® scripts mentioned previously are presented in two reports designated Parts 1 and 2. Part 1 presents the scripts needed to accomplish steps (1) and (2). The current report, Part 2, presents the scripts needed to accomplish steps (3) and (4), noted previously. The TURBOMAT-FR MATLAB® scripts provided here in Part 2 facilitate the calculation of unsteady stresses using MSUM and provide an automated procedure associated with aeroelastic forced response analysis with different pressure files. The unsteady stresses calculated using MSUM can be compared with those presented in Part 1. A cantilevered blade-alone model subjected to a realistic pressure loading to a boundary was used for static and unsteady direct forced response analysis to demonstrate the effectiveness of the TURBOMATFR MATLAB® scripts.

T S R Reddy↗