Link

Before describing design optimization, it is best to first define optimization and present a brief mathematical example.

Optimization is the process of finding a minimum or maximum to a given objective function and constraints.

Consider this objective function.

The objective function's surface plot is shown in Figure 1. The problem posed is to find the minimum of the objective function given that the starting or initial point is  (x₁, x₂) = (3, 4) . This example can easily be done by hand. Alternatively, an optimizer, such as the one available in MSC Nastran SOL 200, can be used to automatically search for the minimum. Figure 1 shows the search path the SOL 200 optimizer took to find the minimum.

Design optimization is essentially regular optimization, i.e. the goal is to find a minimum or maximum of an objective function, but is different in the sense that now a structural model is being optimized.  Objectives are expressed as minimizing the weight, maximizing the stiffness of a structure, or finding the optimum of some other response or quantity. If performing size optimization, variables such as x1, x2 are now corresponding to structural parameters such as plate thickness or dimensions of beam cross sections. Constraints are limits imposed on stress, displacement, or many other types of structural responses.

Consider the following design optimization example, Figure 2, from the MSC Nastran Design Sensitivity and Optimization User's Guide. Like regular optimization, an objective, constraints and design variables are specified, but are directly associated with a structural model.

Figure 2

This example has two design variables, and the result of the MSC Nastran Optimization can be plotted three dimensionally. See Figure 3.

Figure 3

Table 1 compares optimization and design optimization. As can be seen, both are very similar, except that with design optimization the objective, variables and constraints are associated with a structural model.

Table 1

The optimization capability available in MSC Nastran SOL 200 is quite extensive and offers engineers multiple methods to improve structural designs.

For example, design sensitivity analysis is the process of computing partial derivatives or sensitivities of structural responses with respect to design variables. These sensitivities can be used to determine which design variables will have the most impact on achieving a desired objective. Design optimization is the actual process of determining an optimum configuration of a finite element model to achieve a minimum or maximum objective. During the optimization process, optimizers are constantly computing sensitivities to determine the best search paths to take in order to find minimums or maximums.

For a brief introduction to MSC Nastran SOL 200, please refer to the Introduction to Nastran SOL 200 Design Sensitivity and Optimization eBook.

A comprehensive list of each optimization feature is available in the MSC Nastran Design Sensitivity and Optimization User's Guide.

To use MSC Nastran SOL 200, an existing SOL 1xx BDF file must be converted to SOL 200. The conversion process involves the selection of design variables, objective, and constraints. The SOL 200 Web App, web app for short, facilitates the conversion process. The Supported Capabilities section of this guide details what the web app supports in MSC Nastran SOL 200.

Converter

Supported Entries

• BEADVAR
• DCONADD
• DCONSTR
• DDVAL
• DEQATN
• DESVAR
• DLINK
• DRESP1
• DRESP2
• DVPREL1, DVMREL1, DVCREL1
• DVPREL2, DVMREL2, DVCREL2
• TOMVAR
• TOPVAR

Modified Fields

$   1  ||   2  ||   3  ||   4  ||   5  ||   6  ||   7  ||   8  |
DESVAR  1       A1      .8365   .1      100.    1.
                    

$   1  ||   2  ||   3  ||   4  ||   5  ||   6  ||   7  ||   8  |
DESVAR  1       A1      .8365   .1      100.    1.
                    

Converting to Equivalent Entries

DVPREL1 1       PSHELL  1       T                       .5
        10      1.0     20      1.000   30      1.0


                    

DVPREL2 2000001 PSHELL  1       T                       5001
DESVAR  200010  200020  200030
DEQATN  5001
        g(y10,y20,y30) =
        y10 * 1.0 + y20 * 1.000 + y30 * 1.0 + .5

DVPREL1     402 PBRSECT 11994   T
              2 1.000
DVPREL1     403 PBRSECT 11994   T(1)
              2 1.000
DESVAR        2 T11994  1.000   0.600   8.000

DVPREL1 1000402 PBRSECT 11994   T
         100402 1.000
DVPREL1 1000403 PBRSECT 11994   T(1)
         100403 1.000
DESVAR   100402 x402    1.000   0.600   8.000
DESVAR   100403 x403    1.000   0.600   8.000
DLINK   1       100403                  100403  1.0

DRESP2  30005   RTSUMSQ MAX
DRESP1  10001   10002   10003   10004   10005   10006   10007

DRESP2  9030005 R30005  170005
DRESP1  7010001 7010002 7010003 7010004 7010005 7010006 7010007
DEQATN  170005
        g(b10001,b10002,b10003,b10004,b10005,b10006,b10007) =
        MAX(b10001,b10002,b10003,b10004,b10005,b10006,b10007)

Solution Discrepancies

• For file dsoug3.dat, the DVPREL1 entries are converted to DVPREL2 entries. This change has implications when the sensitivity coefficients are computed.
• For file dsoug7.dat, the DVPREL1 entry is using PMIN. The web app does not support the PMIN or PMAX fields and will remove the PMIN or PMAX fields. The limits are already specified on the DESVAR entry and renders the use of PMIN or PMAX unnecessary.
• For file dsoug8.dat, the DEQATN entry uses PI(1) to signify the value of 3.14. The Converter App replaces PI(1) with 3.1416. PI(1) is not supported by the web app.
• For file dsoug14.dat, the original DESVAR entry is in the large field format. The initial value of the original DESVAR entry is 8.36519659E-01, but after conversion, the entry uses the small field format. As a result, the new initial value is .8365. The web app creates entries only in the small field format.

Over 25 step-by-step tutorials are available regarding fundamentals of optimization and how to properly use the SOL 200 Web App. Click on any of the following links to jump to the section.

• Optimization Basics
• Size Optimization Tutorials
• Topology, Topometry and Topography Tutorials
• Advanced Tutorials
• Miscellaneous Tutorials
• Machine Learning Tutorials
• Beams Tutorials
• Composite Laminate Optimization Tutorials
• Shape Optimization Tutorials
• Post-processor Tutorials
• Uncertainty Quantification Tutorials
• Optimization Under Uncertainty Tutorials

Optimization Basics

	Title and Description	YouTube Tutorial
	Unconstrained Optimization with MSC Nastran SOL 200 Part of Calculus involves finding maximums or minimums of functions. The process of finding maximums or minimums is the essence of optimization. In this video, MSC Nastran Optimization is used to find the optimum point or minimum of a two-variable function, f(y1, y2) = y1^2 + y2^2.	Link
	Constrained Optimization with MSC Nastran SOL 200 This video demonstrates the use of MSC Nastran Optimization to find the minimum of f(y1, y2) subject to a constraint g(y1, y2).	Link
	Side Constraints on Design Variables - MSC Nastran Optimization This video demonstrates the use of MSC Nastran Optimization to find the minimum of f(y1, y2) subject to limits on the design variables y1 and y2.	Link
	Best Compromise Infeasible Design - MSC Nastran Optimization In constrained optimization, an optimum solution may not exist that satisfies all the constraints. This video demonstrates such a scenario and walks through a fix.	Link
	What is Global Optimization? MSC Nastran SOL 200 / Optimization Tutorial  This video discusses the meaning of Global Optimization and walks you through the process of setting up a Global Optimization with MSC Nastran SOL 200.	Link
	What is size optimization? What is shape, topology, topography and topometry optimization? In this short video, the following MSC Nastran optimization types are described. Size Optimization Shape Optimization Topology Optimization Topography Optimization Topometry Optimization	Link

Size Optimization Tutorials

	Title and Description	Lecture Notes	PDF Tutorial	YouTube Tutorial
	Structural Optimization of a 3 Bar Truss - MSC Nastran Optimization A truss structure is optimized with MSC Nastran. The design variables are the cross-sectional areas of the rod elements. The objective is to minimize the weight of the structure while ensuring the stress and displacements are within specified constraints. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Sensitivity Analysis of a 3 Bar Truss - MSC Nastran Optimization A structural optimization was previously performed on a 3 bar truss. In this tutorial, the process to perform a sensitivity analysis is detailed. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Automated Structural Optimization of a Stiffened Plate with MSC Nastran SOL 200/Design Optimization This example demonstrates the use of MSC Nastran to optimize the thickness of the plate and the thickness of a beam section to minimize weight. Constraints are imposed on the stresses in the shell and beam elements. Additional constraints are imposed on deflections. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Vibration of a Cantilevered Beam (Turner's Problem), MSC Nastran Optimization This example demonstrates the use of MSC Nastran to optimize the rod areas and shell thicknesses such that the structure's weight is minimized and the first natural frequency is above 20 Hz. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Dynamic Response Optimization with MSC Nastran Optimization This example is from the MSC Nastran Design Sensitivity and Optimization User's Guide. "This example demonstrates structural optimization when the structural loads are frequency dependent. The system considered is a flat rectangular plate clamped on three edges and free along the fourth, as shown in Figure 8-21 . The problem investigates minimization of the mean square response of the transverse displacement at the midpoint of the free edge, while constraining the volume of the structure (and hence, weight) to be equal to that of the initial design. A pressure loading with an amplitude of 1.0 lbf ⁄ in^2 is applied across a frequency range of 20.0 to 200.0 Hz. A small amount of frequency- dependent modal damping has also been included." Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Model Matching, Frequency Response Analysis A frequency response analysis has been performed, but the results do not match experimental results. This tutorial discusses the model matching procedure in order to correlate Finite Element Analysis and test results. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Using MSC Nastran Optimization for Model Matching / System Identification In this example, the cross section of a rod is designed such that the analysis modes match experimentally measured data. MSC Nastran Optimization is used to minimize the root sum of squares for Mode 1. This example is an adaptation of the example found in the UAI/Nastran User's Guide for Version 20.1 - 252.6.6 System Identification. The following is an excerpt from the guide describing this example. Keep in mind this video is an adaptation and will not match all the values in the following description: "An important area of research is the tuning of finite element models to experimental test results. This is often called system identification. This example problem illustrates how optimization may be used to address these requirements. It features: Normal modes optimization Constraints on RMS error in mode shapes Frequency constraints Using an analytical response as the objective Example Problem 25-6 Consider the model shown in Figure 25-13. It is a simple cantilever beam which is composed of 10BAR elements with circular cross sections having a constant diameter of 4.0 in. The cross-sectional area of the three BAR elements at the root of the beam may be varied. You wish to design this area such that it matches known test results. The finite element model, which is found in file MDO6, is shown in Figure 25-13. Table 25-19 presents the test results and a definition of the design constraints for the problem. These data reflect that two natural modes, mode 1 (first bending) and mode 3 (first extensional) have been measured experimentally at three locations which correspond to GRID points 3, 6 and 9 in the finite element model. The frequency of the first mode, 61.912, has also been measured. The design model is simple having a single design variable which represents the root cross-sectional area." Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Ply Number Optimization of a Composite Laminate with MSC Nastran Optimization (SOL 200) This tutorial details the process to configure a ply number optimization for MSC Nastran. The optimization problem statement is to reduce the mass of a composite cylinder, ensure ply failure index constraints are satisfied, and vary the number of plies for 0, 90 and +/-45-degree layers. This example considers ply number optimization for multiple PCOMP entries and multiple load cases. Additional comments are made regarding displaying fringe plots of the failure indices after optimization, updating the final BDF files with new PCOMP entries, and stacking sequence optimization. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Automated Optimization of a Composite Laminate with MSC Nastran Optimization (SOL 200) This example details the use of MSC Nastran Design Optimization (SOL 200) to optimize the weight of a tube composed of a composite laminate. The ply thicknesses and orientations are allowed to vary during the optimization process. The orientation angles are limited to 5 degree increments. Constraints on the failure indices are applied. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Optimizing for Buckling - Twenty-Five Bar Truss with MSC Nastran Optimization This example is from the MSC Nastran Design Sensitivity and Optimization User's Guide. "This problem, often seen in the early design optimization literature, calls for a minimum weight structure subject to member stress, Euler buckling, and joint displacement constraints. The structure is shown in Figure 8-25 . The formulation of the buckling constraints is a good example of constructing normalized constraints based on user-defined structural responses." Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Acoustic Optimization, Beta Method A fluid is enclosed in a structural box and subjected to an acoustic source. The goal is to minimize the peak acoustic pressure while letting the structural thicknesses vary and preventing the weight from significantly changing. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	Acoustic Optimization, Nastran BETA Function This tutorial is a repeat of the previous Acoustic Optimization example, but highlights an alternative method to setting up the optimization for Nastran SOL 200. The BETA method is used and reduces the work that was previously required. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Optimization for Multiple Load Cases or SUBCASEs The web app makes simple configuring design constraints for dozens or hundreds of load cases. This tutorial guides you through the process. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Buckling Optimization of a Cantilever Beam This example demonstrates the procedure to configure Nastran SOL 200 for buckling optimization. This example also covers how to optimize for multiple buckling scenarios. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Global Optimization This example demonstrates the procedure of performing a Global Optimization with MSC Nastran SOL 200. Often, optimization problems have multiple local minimums, or maximums, when starting from different initial design variables. To find the global optimum, multiple local optimizations must be performed, then the best of the local optimizations is taken to be global optimum. This process can be performed with the Global Optimization capability available in MSC Nastran SOL 200. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Parameter Study This tutorial details the use of MSC Nastran SOL 200 to perform a "parameter study." What is a parameter study? A common engineering technique is to try different structural configurations, for example, changing structural dimensions, and review the impact on structural responses such as displacements and stresses. Dozens, possibly hundreds of structural configurations would ideally be evaluated. This is termed "parameter study." MSC Nastran SOL 200 includes a capability to automatically generate multiple structural configurations and perform static or dynamic analyses. The outcome are results from multiple structural configurations that can be compared. Starting BDF Files: Link Solution BDF Files: Link		Link	Link
	Multi Model Optimization Multi Model Optimization (MMO) is the process of optimizing multiple design models concurrently. Design variables across multiple models can be linked and simultaneously optimized. A merged or combined objective can optimize the objective of each design model. The design constraints of each design model are also included in a multi model optimization. This tutorial details the procedure to configure a multi model optimization. Starting BDF Files: Link Solution BDF Files: Link		Link	Link

Topology, Topometry and Topography Tutorials

	Title and Description	Lecture Notes	PDF Tutorial	YouTube Tutorial
	MSC Nastran Topology Optimization - Minimizing mass with stress and displacement constraints A solid block of material composed of 3D or Hexahedral elements is subjected to two load cases. Topology Optimization is used to minimize the mass of the structure, while satisfying both stress and displacement design constraints. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	MSC Nastran Topology Optimization Manufacturing Constraints A cantilever beam is composed of 3D or Hexahedral elements and a load is applied at the free end. Topology Optimization is used to identify regions of material to remove. This example discusses options to produce a symmetric design and a design that can be manufactured via casting. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	MSC Nastran Topology Optimization Mirror Symmetry Constraints A plate composed of 2D finite elements, is simply supported and has a load applied at the midpoint. Topology Optimization is used to identify material to remove. This example focuses on satisfying weight, stiffness and symmetry targets. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	MSC Nastran Topology Optimization - Multidiscipline - Static Loading and Natural Frequency A simply supported plate is composed of 2D finite elements and a load is applied at the midspan. The MSC Nastran Topology Optimization capability is used to determine which portions of the plate should be kept while satisfying weight, stiffness and first natural frequency constraints. This example also showcases the ability to optimize for multiple analysis types, e.g. static and normal modes analysis. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	MSC Nastran Topometry Optimization of a Cantilever Plate This tutorial is an introduction to Topometry Optimization. A simple cantilever plate is used to demonstrate element-by-element optimization of thickness. Starting BDF Files: Link Solution BDF Files: Link	Link	Link	Link
	MSC Nastran Topometry Optimization with Symmetry Constraints This tutorial details the configuration of symmetry constraints in a topometry optimization. Starting BDF Files: Link Solution BDF Files: Link		Link
	MSC Nastran Topography Optimization - Bead or Stamp Optimization This tutorial covers the use of Topography Optimization to determine optimal bead or stamp patterns. The Post-processor web app is used afterwards to review the results of the optimization. Starting BDF Files: Link Solution BDF Files: Link		Link

Advanced Tutorials

Miscellaneous Tutorials

	Title and Description	PDF Tutorial	YouTube Tutorial
	Use the HDF5 Explorer to Create Plots Starting with MSC Nastran 2016, results can be outputted to the HDF5 file type. This tutorial introduces the HDF5 Explorer and the following concepts: Acquiring datasets from the HDF5 file (.h5) Creating plots Applied Loading vs. Frequency Displacement vs. Frequency Mode Participation Factors vs. Frequency Natural Frequency vs. Mode Number Exporting data to CSV Starting Files: Link	Link
	Remote execution of MSC Nastran on a remote operating system available on the local network This tutorial discusses the use of the Remote Execution web app and how to run MSC Nastran jobs on remote operating systems available on the local network. Traditionally, FTP and SSH programs are required to run MSC Nastran on remote operating systems, but this tutorial discusses how to run MSC Nastran through the web browser alone. FTP and SSH programs are not required for this tutorial.	Link
	Creation of Dynamic Loads via RLOAD1 or RLOAD2 Entries A critical part of dynamic analysis is defining the dynamic load. For frequency response analysis, the dynamic load is defined via the RLOAD1 or RLOAD2 bulk data entries. For the simplest dynamic loads, only RLOAD1 or RLOAD2 entries are sufficient. For more complex dynamic loads, the following entries might be required: RLOAD1, RLOAD2, TABLED1, TABLED2, TABLED3, TABLED4, DELAY or DPHASE. This exercise details the use of the Dynamic Loads web app to define dynamic loads and the following entries: RLOAD1, RLOAD2, TABLED1, TABLED2, TABLED3, TABLED4, DELAY or DPHASE. Starting Files: Link Solution BDF Files: Link	Link
	Configure a 0 Hz Frequency Response and Statics Analysis One recommended strategy when configuring a frequency response analysis is the following: Perform a frequency response analysis at 0 Hz and a statics analysis. If the results of both analyses are significantly different, there may be an issue that needs to be addressed. This exercise details the use of the Model Validation web app to configure a 0 Hz frequency response and statics analysis. A comparison of the results is also done. Ultimately, the results are identical and confirms there are no unintended issues in the model. Starting BDF Files: Link Solution BDF Files: Link	Link

Machine Learning Tutorials

	Title and Description	PDF Tutorial	YouTube Tutorial
	Introduction - MSC Nastran Machine Learning Web App There are many machine learning methods available, such as neural networks, decision trees, genetic algorithms, supervised learning, etc. Watch this presentation to gain an understanding of the machine learning methods implemented in the MSC Nastran Machine Learning web app. The MSC Nastran Machine Learning web app makes use of the following methods: Gaussian Process Regression - Used to predict the output of MSC Nastran Bayesian Optimization - Used to select candidate designs	Link	Link
	Machine Learning, Structural Optimization of a 10 Bar Truss with MSC Nastran SOL 400 Machine learning methods are used to optimize a truss structure. This example features the optimization of nonlinear responses from MSC Nastran SOL 400. MSC Nastran is used to evaluate the FE model. The design variables are the cross-sectional areas of the rod elements. The objective is to minimize the weight of the structure while constraining the axial stresses and displacements. Most machine learning examples are lower dimension problems with 1 to 5 parameters. This tutorial demonstrates a higher dimension scenario with 10 parameters. Starting Files: Link Solution BDF Files: Link	Link	Link
	Machine Learning, Structural Optimization of a 3 Bar Truss Machine learning methods are used to optimize a truss structure. MSC Nastran is used to evaluate the FE model. The design variables are the cross-sectional areas of the rod elements. The objective is to minimize the weight of the structure while constraining the axial stresses. Starting Files: Link Solution BDF Files: Link	Link	Link
	Machine Learning, Nonlinear Buckling (Post-Buckling) Optimization of a Reinforced Cylinder with MSC Nastran SOL 400 A reinforced cylinder is fixed at the base and a load is applied laterally at its top. Machine learning is performed to determine the optimal thicknesses of the reinforcements to achieve a minimum eigenvalue of 30 while minimizing the weight. This example features the optimization of nonlinear responses from MSC Nastran SOL 400 and involves nonlinear buckling (post-buckling) analysis. Starting Files: Link Solution BDF Files: Link	Link	Link
	Parameter Study, Global Optimization with a Latin Hypercube Design Consider the optimization of a generic engine model that represents a V6 engine and automatic transmission as well as other components such as engine mount, transmission mount, crankshaft, drive axles, and flywheel. The Parameter Study web app is used to configure multiple local optimizations, each with different initial values for the variables, and MSC Nastran is used to perform each optimization. Frequency response plots are created afterward. The process of performing multiple local optimizations, then taking the best, or optimal, design is known as Global Optimization. Starting Files: Link Solution BDF Files: Link	Link	Link
	Parameter Study, Varying the Location of Concentrated Masses A frequency response analysis is performed on a bracket. The goal in this tutorial is to vary the position of 5 concentrated masses on the bracket and determine the displacement vs. frequency plots for each different configuration of concentrated masses. In total, six MSC Nastran runs are configured, each with a different configuration of the concentrated masses. Starting Files: Link Solution BDF Files: Link	Link
	Parameter Study, Varying the Position of Extra Supports The location of supports on a structural or mechanical system greatly influences its stiffness. This tutorial discusses one method to vary the location of supports and view displacement vs. frequency plots. Starting Files: Link Solution BDF Files: Link	Link
	Prediction Analysis, Gaussian Process Regression This tutorial demonstrates the use of Gaussian process regression.	Link	Link
	Prediction Analysis, Dynamic Impact of a Rigid Sphere on a Woven Fabric Consider a transient analysis of a rigid sphere impacting a woven fabric. The parameters allowed to vary include the friction coefficients. The response of interest are the displacements. This tutorial describes how to configure multiple MSC Nastran runs to generate training data. Gaussian process regression is used to train a surrogate model and make predictions. The prediction performance of the surrogate model is also evaluated. Also discussed are instructions to create displacement vs. time plots. Starting Files: Link Solution BDF Files: Link	Link
	Prediction Analysis, Frequency Response Analysis (SOL 111) Consider a frequency response analysis of a ground vehicle. For different configurations of the ground vehicle, there is a desire to rapidly determine the frequency responses, including accelerations and pressures, while keeping the number of Finite Element (FE) solver runs to a minimum. This tutorial describes the procedure to use Gaussian progress regression as a surrogate model for computationally expensive Finite Element (FE) based simulations. This tutorial walks users through the process of acquiring training data, fitting the surrogate model, making predictions and quantifying uncertainty. In addition, the process to screen variables/parameters via Automatic relevance determination (ARD) is discussed. Starting Files: Link Solution BDF Files: Link	Link
	Prediction Analysis, Buckling Consider a linear buckling analysis. The parameter allowed to vary is a spring constant. The response of interest is the buckling load factor. This tutorial describes how to configure multiple MSC Nastran runs to generate training data. Gaussian process regression is used to train a surrogate model and make predictions. The prediction performance of the surrogate model is also evaluated. Starting Files: Link Solution BDF Files: Link	Link
	Prediction Analysis, Post-Buckling Consider a post-buckling analysis. The parameter allowed to vary is a spring constant. The responses of interest include the applied load and displacements. This tutorial is similar to the previous tutorial named Prediction Analysis, Buckling. Like the previous tutorial, this tutorial discusses the use of Gaussian process (GP) regression to train a surrogate model. To expand your experience with GP regression, this tutorial purposely demonstrates a scenario where a poorly fitted model is obtained and what the procedure is to remedy this issue. Also discussed are instructions to create load vs. displacement plots . Starting Files: Link Solution BDF Files: Link	Link

Beams Tutorials

	Title and Description	PDF Tutorial	YouTube Tutorial
	Introduction to the PBMSECT Web App This introductory tutorial details the use of the PBMSECT web app to generate arbitrary beam cross sections. The PBMSECT web app is used to automatically generate and manage the following bulk data entries: PBMSECT, PBRSECT, POINT and SET1.	Link	Link
	Examples of arbitrary beam cross sections with PBMSECT and PBRSECT This tutorial describes the procedure to generate different types of arbitrary beam cross sections, including open or closed profiles. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Composite Arbitrary Beam Cross Section Composite arbitrary beam cross section (ABCS) may be defined through the use of the PBMSECT and CBEAM3 entries. This tutorial details the use of the PBMSECT web app to construct a composite ABCS and generate the necessary PBMSECT, POINT and SET1 entries. Important considerations, such as ply coordinate systems and validating the FEM of the beam cross section, are discussed. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Arbitrary Beam Cross Section Optimization MSC Nastran SOL 200 supports varying the width, height and wall thickness of arbitrary beam cross sections (ABCS) defined by the PBRSECT or PBMSECT entries. This tutorial walks you through the process of generating an ABCS via the PBMSECT entry, configuring an optimization for MSC Nastran SOL 200, and reviewing the optimization results. Starting BDF Files: Link Solution BDF Files: Link	Link	Link

Composite Laminate Optimization Tutorials

	Title and Description	PDF Tutorial	YouTube Tutorial
	Composite Coupon – Phase A – Determination of the optimal 0° direction of a composite The goal of this 5-phase tutorial series is to optimize a composite coupon, with a core, and produce a lightweight composite that satisfies failure index constraints. The optimal ply shapes (ply drop-offs) and ply numbers are determined for 0°, ±45°, and 90° plies. A stacking sequence optimization is performed to satisfy manufacturing requirements. One important part of optimizing composites is visualizing the composite plies. This tutorial series also demonstrates the visualization of ply drop-offs, tapered plies and core layers. This first phase involves determining the optimal 0° direction of a composite. It is best practice to align the 0° plies in the direction of the load. Not doing so will more than likely produce a suboptimal composite that is heavier than necessary. This tutorial demonstrates the use of MSC Nastran's optimizer to determine the optimal 0° direction of a composite. An optimization is performed to maximize the stiffness of the composite for multiple load cases and while varying the angle of the 0° plies. Ultimately, the best 0° direction is determined. This is the first phase in a 5-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Composite Coupon – Phase B – Baseline Ply Number Optimization This tutorial demonstrates how to configure a basic ply number optimization of continuous plies that span the entire model. The goal of this tutorial is to demonstrate basic actions such as creating variables, a weight objective and constraints on failure index. The results of this ply number optimization serve as a baseline for future comparisons. In a subsequent tutorial, the ply shapes will be optimized to minimize weight. This is the second phase in a 5-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Composite Coupon – Phase C – Data Preparation for Ply Shape Optimization This tutorial is a guide to preparing data for ply shape optimization in a subsequent tutorial. The maximum failure index values of the outer plies of the composite are determined and saved to specially formatted PLY000i files. The PLY000i files will be used to construct optimal ply shapes in a subsequent tutorial. This is the third phase in a 5-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Composite Coupon – Phase D – Ply Shape and Ply Number Optimization This tutorial details the process to build optimal ply shapes and perform a ply number optimization. The optimal ply shapes are constructed to follow the contours of the failure indices. The ply number optimization involves minimizing weight and constraining the failure indices of plies. The PLY000i files and BDF files from the previous tutorial, phase C, are used in this tutorial. This is the fourth phase in a 5-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Composite Coupon – Phase E – Stacking Sequence Optimization This tutorial involves performing a stacking sequence optimization and is a continuation of the previous tutorial, phase D. A final statics analysis is performed to confirm the optimized composite satisfies failure index constraints. This is the fifth phase in a 5-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link

	Title and Description	PDF Tutorial	YouTube Tutorial
	Sandwich Composite Panel – Phase B – Baseline Core Thickness Optimization The goal of this 3-phase tutorial series is to optimize a curved composite panel, with a core, and produce a lightweight composite that satisfies constraints on the buckling load factor. This tutorial series focuses exclusively on optimizing the thickness of the core. The methods detailed in the tutorial series are applicable to both foam and honeycomb cores. This tutorial demonstrates how to configure a basic core thickness optimization where the core has a constant thickness throughout the entire model. The goal of this tutorial is to demonstrate basic actions such as creating variables, a weight objective and constraints on the buckling load factor. The results of this core thickness optimization serve as a baseline for future comparisons. In a subsequent tutorial, the core will be allowed to have a variable thickness throughout the model and will be optimized to minimize weight. This is the first phase in a 3-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Sandwich Composite Panel – Phase C – Topometry Optimization to Determine Optimal Core Shape This tutorial is a guide to preparing data for core shape and core thickness optimization in a subsequent tutorial. A topometry optimization is performed in this tutorial to determine the ideal thickness distribution of the core throughout the entire composite panel while satisfying constraints on the buckling load factor and minimizing weight. The results of a topometry optimization are contained in the PLY000i files and will be used to construct optimal core shapes in a subsequent tutorial. This is the second phase in a 3-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Sandwich Composite Panel – Phase D – Core Shape and Core Thickness Optimization This tutorial details the process to build optimal core shapes and perform a core thickness optimization. The optimal core shapes are constructed to follow the contours of thickness results generated by a topometry optimization. The core thickness optimization involves minimizing weight and constraining the buckling load factor. The PLY000i files and BDF files from the previous tutorial, phase C, are used in this tutorial. Comparisons are made between this optimization in phase D and the baseline optimization performed in phase B. This is the third phase in a 3-phase tutorial series. Starting BDF Files: Link Solution BDF Files: Link	Link	Link

Shape Optimization Tutorials

	Title and Description	PDF Tutorial	YouTube Tutorial
	Shape Optimization of a Cantilever Beam This tutorial is an introduction to MSC Nastran's Shape Optimization capability. A cantilever beam is configured for a shape optimization. The goal is to minimize the mass while satisfying stress constraints. Specified regions of the beam are allowed to expand or contract and define the shapes that will vary during the optimization. This tutorial discusses the following concepts: auxiliary models, shape basis vectors, scaling shape basis vectors, configuring variable bounds, strategies to prevent mesh distortions, results interpretation, updating the model, and more. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Shape Optimization of a Steering Knuckle A steering knuckle is configured for a shape optimization. The goal is to minimize the mass while satisfying stress constraints. Twelve load cases are considered. Four regions of the model are allowed to expand or contract and define the shapes that will vary during the optimization. This tutorial is an advanced shape optimization tutorial and utilizes MSC Nastran's shape optimization capability. Starting BDF Files: Link Solution BDF Files: Link	Link	Link

Post-processor Tutorials

	Title and Description	PDF Tutorial	YouTube Tutorial
	MSC Nastran Results - Introduction to Nastran Results - Displacements, forces, stresses and composite ply stresses for entries CQUAD4, CTRIA3, CQUAD8, CBEAM, CBUSH, CFAST, PSHELL, PCOMP, PBMSECT, PBUSH and PFAST This tutorial is an introduction to Nastran results. The Post-processor web app is used to inspect the following types of results. Deformations/Displacements Stresses of CQUAD4, CTRIA3 and PSHELL entries Composite ply stresses of CQUAD8 and PCOMP entries Beam forces, moments and stresses of CBEAM and PBMSECT entries Element forces of CBUSH and PBUSH entries Element forces of CFAST and PFAST entries This tutorial also details how to export element forces for CBUSH elements to a CSV file. The analysis results are for 3 load cases after an optimization. This tutorial discusses how to distinguish results across different load cases and optimization design cycles. The Post-processor web app is free to MSC Nastran users. The Post-processor web app is only compatible with MSC Nastran. Starting BDF Files: Link	Link	Link
	MSC Nastran Results - CBAR - Element forces, stresses and displacements The goal of this exercise is to review the results from a statics analysis. The element forces, bending stresses, displacements and twist of CBAR elements is displayed. Source of Exercise Problem 1: Linear Statics, Rigid Frame Analysis Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - PCOMP - Ply stresses The goal of this exercise is to view the ply stresses of a 3 layer composite laminate. Source of Exercise Problem 2: Linear Statics, Cross-Ply Composite Plate Analysis Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - CQUAD4 - Stresses and deformations in spherical coordinates The goal of this exercise is to inspect the deformation and stresses of an FE model configured in the spherical coordinate system. Source of Exercise Problem 5: Linear Statics, 2D Shells in Spherical Coordinates Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - CROD - Axial forces and stresses The goal of this exercise is to plot the deformations, axial forces and stresses of CROD elements. Source of Exercise Problem 8: Linear Statics, Pinned Truss Analysis Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - CGAP - Element force and stresses in CGAP elements The goal of this exercise is to inspect the element forces and displacements in CGAP elements. Source of Exercise Problem 13: Nonlinear Statics, Beams with Gap Elements Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - CONM2 and CELAS1 - Natural Frequencies, Mode Shapes, Spring Mass The goal of this exercise is to inspect the natural frequencies and mode shapes of a spring mass system. Source of Exercise Problem 14: Normal Modes, Point Masses and Linear Springs Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - CTRIA - Natural Frequencies, Mode Shapes, Cylindrical Coordinates The goal of this exercise is to inspect the natural frequencies and mode shapes of an FE model composed of CTRIA elements. Source of Exercise Problem 16: Normal Modes, Pshells and Cylindrical Coordinates Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - Buckling Load Factor of a Thin Walled Cylinder The goal of this exercise is to determine the eigenvalue from a buckling analysis and determine the buckling load. Source of Exercise Problem 17: Buckling, shells and Cylindrical Coordinates Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran Results - CHEXA - Transient Analysis in Cylindrical Coordinates The goal of this exercise is to view the displacements of a static and transient analysis. The process to create displacement vs. time plots is also demonstrated. Source of Exercise Problem 19: Direct Transient Response, Solids and Cylindrical Coordinates Patran Reference Manual, Part 6: Results Postprocessing, Chapter 15 - Verification and Validation Starting BDF Files: Link		Link
	MSC Nastran SOL 400 Results - Displacements, forces of a steel roller moving on rubber The displacements are displayed for a steel roller moving on a rubber base. Special consideration is given to the steel roller. A load vs. displacement plot is created for the steel roller. Source of Exercise Chapter 5: Steel Roller on Rubber MSC Nastran 2023.3 Demonstration Problems Manual - Implicit Nonlinear Starting BDF Files: Link		Link
	MSC Nastran SOL 400 Results - CBUSH,CFAST,CWELD - Shear Forces in Fasteners of a Lap Joint The shear forces in fasteners of a lap joint are displayed. The fasteners are modeled with CBUSH, CFAST and CWELD elements. Source of Exercise Chapter 33: Large Rotation Analysis of a Riveted Lap Joint MSC Nastran 2023.3 Demonstration Problems Manual - Implicit Nonlinear Starting BDF Files: Link		Link
	MSC Nastran SOL 400 Results - Load vs. Deflection Graph (Load Stroke Plot) This exercise the procedure to create load vs. deflection graphs, also known as load stroke plots. Source of Exercise Chapter 36: Shallow Cylindrical Shell Snap-through MSC Nastran 2023.3 Demonstration Problems Manual - Implicit Nonlinear Starting BDF Files: Link		Link

Uncertainty Quantification

	Title and Description	PDF Tutorial	YouTube Tutorial
	Uncertainty Quantification - Installing Sandia Dakota on Windows and Red Hat Linux 7 This tutorial details the process to download and configure Sandia Dakota on Windows and Red Hat Linux 7.	Link
	Uncertainty Quantification - 10 Bar Truss with MSC Nastran This example details the use of uncertainty quantification to reduce the variability of responses when uncertain parameters are present. Forward propagation of uncertainty is the focus of this exercise and the sampling method is used for uncertainty quantification. A 10 bar truss with 4 uncertain parameters is considered and a Latin Hypercube sampling is used. The quantities of interest include the mean and standard deviation values of the responses and correlation coefficients between the inputs (parameters) and outputs (responses). Starting BDF Files: Link Solution BDF Files: Link	Link

Optimization Under Uncertainty

	Title and Description	PDF Tutorial	YouTube Tutorial
	Optimization Under Uncertainty - 3 Bar Truss, Part 1 of 2 There are many methods available for uncertainty quantification to approximate statistics such as mean, standard deviation and tail probabilities of stochastic responses. Each method has its own computational cost. During an optimization under uncertainty (OUU), an uncertainty quantification (UQ) is performed frequently. If the cost of each UQ is high, the OUU’s computational costs will also be prohibitively high. The mean value first-order second-moment (MVFOSM) method is the one of the least expensive UQ methods and involves one black box function evaluation to acquire the response values and gradients. From a single evaluation, the required statistics are approximated, and is a contrast to other UQ methods that may require dozens or hundreds of black box function runs. The MVFOSM is limited to responses that are linear and normally (Gaussian) distributed and is not universally appropriate. This exercise details a procedure to determine if the MVFOSM method is appropriate to approximate the statistics of stress responses of a 3-bar truss. If the MVFOSM is suitable, this will significantly reduce the number of black box function runs necessary to perform the UQ and OUU. The black box function is the FEA solver MSC Nastran. MSC Nastran is used to perform the finite element analysis and acquire responses and gradients. Sandia Dakota is used to perform the UQ. The SOL 200 Web App is used to configure the UQ. This is part 1 of a 2-part tutorial. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Optimization Under Uncertainty - 3 Bar Truss, Part 2 of 2 This example details the process to configure and perform an optimization under uncertainty (OUU) for a 3-bar truss. Also, details are included regarding how to interpret the OUU results and final probabilities of failure. The uncertainty quantification (UQ) is performed via the mean value first-order second-moment (MVFOSM) method. This is part 2 of a 2-part tutorial. The optimization problem statement is to minimize the mean mass while ensuring the stress constraints have a probability of failure no greater than 5%. MSC Nastran is used to perform the finite element analysis and acquire responses and gradients. Sandia Dakota is used to perform the UQ and OUU. The SOL 200 Web App is used to configure the OUU and will automatically exchange responses and gradients between MSC Nastran and Sandia Dakota. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Optimization Under Uncertainty - 53 Bar Truss Both uncertainty quantification (UQ) and optimization under uncertainty (OUU) may require hundreds or thousands of black box function evaluations when considering a large number of uncertain variables. Certain black box functions will require hours or days for a single run, so thousands of black box function evaluations are impractical. Finite element solvers are such black box functions where at most a few hundred runs are practical. This tutorial details how to configure an OUU when a large number of uncertain variables are considered, and strategies are discussed to minimize the number of black box function runs. The OUU involves minimizing the mass of a 53-bar truss, varying the mean cross section area of 53 truss members (53 variables), and constraining the probability of failure to 5%, where failure occurs if the axial stress exceeds the material yield strength. This OUU may require 200 to 2000 black box function runs, so the strategies discussed are critical to reducing the number of runs necessary to converge to a solution. The black box function is the FEA solver MSC Nastran. MSC Nastran is used to perform the finite element analysis and acquire responses and gradients. Sandia Dakota is used to perform the UQ and OUU. The SOL 200 Web App is used to configure the OUU. Starting BDF Files: Link Solution BDF Files: Link	Link	Link
	Robust Design Optimization - Acoustic Box Small deviations to structural or mechanical systems during manufacturing can result in significantly varying performance. Examples of varying performance include variations in hole diameters that can lead to variations in peak stress, and variations in gauge thicknesses that can lead to variations in acoustic peak pressures. This tutorial details the use of robust design optimization to reduce the variability of performance when input uncertainties are considered. Specifically, a robust design optimization is configured and performed to minimize the variability of responses. A finite element model is considered of an acoustic box subjected to a dynamic load. The uncertain variables correspond to the gauge thicknesses of the acoustic box. The robust design objective is to minimize the sum of mean and 3-standard deviations of peak acoustic pressures at 2 locations of the FE model. A constraint on mean mass is imposed. The FE solver MSC Nastran is used to perform the acoustic analysis and acquire the necessary responses. Sandia Dakota is used to perform the uncertainty quantification and robust design optimization. The SOL 200 Web App is used to configure both the uncertainty quantification and robust design optimization. Starting BDF Files: Link Solution BDF Files: Link	Link	Link

 *** USER FATAL MESSAGE 7147 (DPR3H1)
     THE DESOBJ COMMAND WITH ID =  9000000 REFERENCES A DRESP2   ENTRY WHICH IN
     TURN REFERENCES DRESP1 ID =  8000003 WHICH INVOKES MULTIPLE RESPONSES.
     USER INFORMATION: THE DRESP1 ENTRIES INVOLVED IN DEFINING THE OBJECTIVE MUST BE SCALAR QUANTITIES.
     USER ACTION     : IF YOUR DRESP2 REFERENCES A DRESP1 THAT DEFINES A RESPONSE LIKE MAX OR RSS,
     MAKE SURE TO USE FLAG 'DRESP2' INSTEAD OF 'DRESP1' ON THE CONTINUATION LINE.

Examples of Acceptable and Unacceptable Objectives

Configuration	Explanation
Objective, r0 Let r0 be defined as shown below. The label r0 is described as "The x displacement of GRID 1."	Since r0 is associated with 1 value (1 components x 1 GRID), the DRESP1 entry yields 1 value. This is an acceptable objective.
Objective, r0 Let r0 be defined as shown below. The label r0 is described as "The x and y displacements of GRIDs 1, 2 and 3."	Since r0 is associated with 6 values (2 components x 3 GRIDs), the DRESP1 entry yields 6 values. This is an unacceptable objective.
Objective, r0 Let r0 be defined as shown below. The label r0 is described as "The z frequency displacement for all forcing frequencies at GRID 1101."	Assume there are 100 forcing frequencies. The label r0 will yield 100 z-displacement values for GRID 1101. This is an unacceptable objective.
Objective, S0 Let S0 be defined as shown below. The label S0 is described as "Take the AVG or average z frequency displacements for all forcing frequencies at GRID 1101."	Since the ATTB is set to AVG or average, S0 will be the average displacement across the forcing frequency range. The label S0 ultimately yields one value. This is an acceptable objective.

Examples of Acceptable and Unacceptable Equation Objectives

Configuration	Explanation
Equation Objective, R0: g(a1) = a1 a1: Let a1 be defined as shown below. The label a1 is described as "The vonMisses stress of element 1."	Since a1 is associated with only one value, the equation R0 evaluates to one value. This is an acceptable objective equation.
Equation Objective, R0: g(a1) = a1 a1: Let a1 be defined as shown below. The label a1 is described as "The vonMisses stress of any element associated with PSHELL 101."	Suppose PSHELL 101 is associated with 100 elements. The label a1 is associated with 100 values (1 stress value x 100 elements). Ultimately, the equation R0 evaluates to 100 values. This is an unacceptable objective equation.

Response Types and Ideal Configurations for a Single Scalar Response

1. Q: Can the design variable labels be customized?
   A: A limited level of label customization is supported. All labels are strictly in the form: qi. For example, x101 and r3400.
   • q - The letter q is dependent on the section, e.g. x for design variables, y for custom design variables, r for constraints, etc.
   • i - This is a positive integer.
   The labels can only be changed via the CSV Export/Import capability and must honor the strict form of qi, e.g. a label such as x1 can be changed to x101, but a label such as y1 cannot be changed to T_PANEL1.
2. Q: For user supplied IDs such as GRID IDs, ELEM IDs and PIDs, does the web app check to make sure the ID exists?
   A: Only PIDs are checked. When specifying the ATTi input for responses or constraints, the web app only checks if the IDs exist for MSC Nastran property entries, e.g. PSHELL, PCOMP, etc. All other IDs are not checked, e.g. GRID IDs, ELEM IDs, etc.

Uploading files to the web app is best described in one sentence:

Every file MSC Nastran needs to run should also be uploaded to the web app.

Consider an example model that consists of the following file set:

car_model.bdf (Currently not set to SOL 200)
door_left.bdf
door_right.bdf
hood.dat
frame.bdf

When running an analysis with MSC Nastran, only one file, car_model.bdf, must be specified and MSC Nastran, upon execution, will search for the other files. For this example, MSC Nastran needs 5 files to run.

When uploading BDF files to the web app, EACH file must be manually selected.

As shown in the image below, 5 files have been manually selected and uploaded.

Generally, upon download from the web app, two BDF files will be downloaded from the web app.

model.bdf (Formerly car_model.bdf, but has been set for SOL 200)
design_model.bdf (Contains entries for the design model)

model.bdf (Formerly car_model.bdf)
design_model.bdf
door_left.bdf
door_right.bdf
hood.dat
frame.bdf

A previous design model downloaded from the SOL 200 Web App can be re-uploaded in the future. Upon re-upload, changes to the design model, such as design variable, objective or constraint changes may be performed.

Like before each file MSC Nastran needs to run should also be provided to the web app.

One exception to this procedure is the Multi Model Optimization web app. For each design model uploaded to the app, only the following and respective files are needed: model.bdf and design_model.bdf.

There are two options for downloading .bdf files from the SOL 200 Web App. Both options are summarized below. Option 1 is the preferred method.

Option 1 - Auto Execute MSC Nastran

This option will download the following files:

• nastran_working_directory.zip

1. This option will download a new file named "nastran_working_directory.zip"
2. Right click on the new .zip file and select "Extract All." A new folder is created.
3. Within this new folder is a shortcut named Start MSC Nastran. Double click this shortcut.
4. If there are any additional windows, click Open, Run or Allow Access in each window.
5. MSC Nastran will now be executed and after MSC Nastran is finished, results will be automatically uploaded to the SOL 200 Web App.

This option will perform 3 actions:

1. MSC Nastran will be automatically started. This step will be skipped if there is an existing .f06 file in the folder.
2. A Status page will be opened and tracks the progress of MSC Nastran.
3. If MSC Nastran finishes successfully, a Results page will be opened. If there is a FATAL MESSAGE in the .f06, the Results page will not be opened.

This executable has been tested ONLY on Windows 10 and Red Hat Linux 7.x. In order for this executable to work successfully, the following conditions must be met. Failure to meet any of these requirements will cause the executable to terminate early before starting MSC Nastran.

• MSC Nastran is installed in the default location (Windows - C:\MSC.Software\MSC_Nastran, Linux - /msc/MSC_Nastran) OR the PATH environment variable has been configured with the installation location.
• Any INCLUDE files must be in the same directory.
• The machine running MSC Nastran must have network access to the SOL 200 Web App.
• A compatible must be installed in the default location.

If performing any of the following, the MSC Nastran utility MultiOpt is to be used:

• Global Optimization
• Global Optimization Type 2
• Parameter Study
• Multi Model Optimization

If using MultiOpt,

• the MSC_LICENSE_FILE environment variable is configured with the location to the license.
• the folder name does not contain any spaces or special characters such as ( ! @ # $ %.

Option 2 - Download BDF Files

This option will download the following files:

• model.bdf
• design_model.bdf
• GO.xml or MMO.xml

If performing Local Optimization or Sensitivity Analysis

1. Find and double click the MSC Nastran desktop shortcut.
2. Select the model.bdf file.
3. Click Run.

If performing any of the following, the MSC Nastran utility MultiOpt is to be used:

• Global Optimization
• Global Optimization Type 2
• Parameter Study
• Multi Model Optimization

If using MultiOpt, do the following:

1. Open the command prompt.
2. Navigate to the folder containing the model.bdf, design_model, GO.xml or MMO.xml files.

   cd Downloads\nastran_working_directory

3. Use this command to start MSC Nastran (If MMO.xml is present, use MMO.xml instead of GO.xml)

   msc20180 MultiOpt GO.xml

   .
4. The msc20180 word will depend on the version of MSC Nastran being used. This will only work if:
   1. The PATH environment variable is properly configured with the location of the MSC Nastran installation.
   2. The MSC_LICENSE_FILE environment variable has been configured.
   Refer to the MSC Nastran Installation and Operation Guide for additional information.

A majority of MSC Nastran's SOL 200 capabilities are supported by the SOL 200 Web App. This section discusses which specific capabilities are supported.

Capabilities

• Optimization Types
  • Size
  • Topometry
  • Topology
  • Topography
• Optimization Options
  • Local Optimization
  • Sensitivity Analysis
  • Global Optimization
  • Parameter Study
  • Multi Model Optimization
  • Machine Learning
• Analysis Types
  • SOL 101 - Statics
  • SOL 103 - Normal Modes
  • SOL 105 - Buckling
  • SOL 107 - Direct Complex Eigenvalues
  • SOL 108 - Direct Frequency Response
  • SOL 110 - Modal Complex Eigenvalues
  • SOL 111 - Modal Frequency Response
  • SOL 112 - Modal Transient Response
  • SOL 144 - Static Aeroelastic Response
  • SOL 145 - Aerodynamic Flutter
  • SOL 400 - Implicit Nonlinear (Machine Learning only)
• Multidisciplinary Optimization
  • Specify different ANALYSIS types per SUBCASE
• INCLUDE file support
• Equation driven objective and constraints (DRESP2 and DEQATN)
• Objective and constraints dependent on multiple load cases or SUBCASEs (DRSPAN)
• CSV Import/Export - Generate hundreds of Variables, DLINK entries and Constraints
• Semi-automatic Nastran execution and live status updates
• Auto Plotting of Results - Line plots and bar charts
• Model Matching

Supported MSC Nastran Entries

The following lists the MSC Nastran entries supported by the web app. For example, if using the Size web app, DESVAR, DVPREL1, ... entries are generated.

Supported Designable Parameters

* Not documented in Table 2-1 of the MSC Nastran Design Sensitivity and Optimization User’s Guide but is supported by the DVPREL1 entry

Supported Responses for Objective and Constraints

Supported Bulk Data Entries and Fields

The following depicts bulk data entries and their specific fields that are supported by the web app.

* The field is imported and exported but is not configurable within the web app. A text editor is recommended to edit the indicated field.

** The special DEQATN functions, e.g. AVG, SUM, ..., are supported.

Installation Configurations

The "Installation Procedure" section details the installation instructions for the Node JS web server and the SOL 200 Web App on Windows and Linux platforms.

Web Browser Requirements

At least one of the web browsers listed below should be installed to access the SOL 200 Web App.

* Microsoft Edge Legacy is not supported. Use the new Microsoft Edge . Refer to your company’s IT support team for assistance.

Web Server Requirements

Node JS is a free open-source application that will run a web server and host the SOL 200 Web App to other machines.

Installation Procedure - Windows

Video Instructions

Instructions

Prerequisites

• Ensure Google Chrome, Mozilla Firefox or Microsoft Edge is installed.

The commands listed in this section are to be executed in the Command Prompt.

1. Download the web app ZIP file, e.g. sol_200_web_app.zip
2. Extract the contents of the zip file to a folder named: sol_200_web_app
3. Licensing - To configure the licensing, following these instructions.
   
   

   Method A - License File
   Prerequisites You have been provided a license file, for example 1100101101.dat. Instructions A.1 Ensure the license file name includes only the numbers 1 or 0 and the file extension '.dat' (Correct: 1100101101.dat Incorrect: for_chris_1100101101.dat) A.2 Take the license file (example: 10111010.dat) and put it in this directory ./sol_200_web_app/license

4. Download and install the latest version of Node JS
   • Windows Installer (.msi), 64-bit: https://nodejs.org/dist/v18.20.5/node-v18.20.5-x64.msi
5. Open the windows command prompt.
   
   If the location of the web app is in restricted directory such as C:\Program Files\sol_200_web_app, the command prompt should be opened with the option "Run as administrator."
6. Navigate to the directory that contains this file: app.min.js .
   

   cd sol_200_web_app

7. Confirm Node JS has been installed by verifying a version number is available. If a version number is shown, this confirms Node JS has been installed successfully.
   

   node --version

   The output of this command will be similar to below but will vary depending on your Node JS version.

   v16.13.0

   If the output is similar to below, the Microsoft HPC Pack is installed on the desktop. This Node application is not the correct version to use. A workaround is provided below.

   Node Commands
   
   Syntax:
       node {operator} [options] [arguments]
   
   Parameters:
           /? or /help   - Display this help message.
           [...]
           resume        - Resume node [deprecated]
   
   For more information about HPC command-line tools,
   see http://go.microsoft.com/fwlink/?LinkId=120724.
                           

   As a workaround, try acquiring the Node JS version by using the full path of the Node JS executable.

   "C:\Program Files\nodejs\node.exe" --version
   v16.13.0

8. To start the web app, type this and run. The first start will ask you to accept the end user license agreement (EULA).
   

   node app.min.js

   Important! If the command above does not work, this command may also be used.

   "C:\Program Files\nodejs\node.exe" app.min.js

   
9. The Windows Firewall will prompt to select an access option.
   • 1) Mark the checkbox for "Public networks, such as those in airports and coffee shops."
   • 2) Click "Allow Access." This will open port 8080 on your machine. If this window did not pop up, port 8080 will have to be opened manually using these instructions: Open and Verify Port 8080 of the Server is Open.
   
   
   
10. Open Google Chrome, Mozilla Firefox or Microsoft Edge and go to localhost:8080/optimization
11. If you can access the web app, the web app has been successfully installed
12. Other machines on the local network can also access the web app. Determine the IP address of the machine that has the web app installed. Use the IP address to access the web app.
    
    For this example, the IP address 192.168.56.1 has the web app running. Open a web browser and go to this URL to access the web app: 192.168.56.1:8080/optimization
    
    If other machines cannot access the web app, it is likely that the IP address is not accessible or the firewall is not configured properly to open port 8080. See this section for additional instructions Enabling Web App Access to Other Devices.
    
    
13. You can close the command prompt to stop running the web app. To restart the web app again, repeat steps 6 and 7.
14. If during the use of the SOL 200 Web App, you encounter messages indicating 0 available licenses, this indicates the licensing is not correctly configured. Consider the following.
    1. Ensure you have followed the instructions to configure the license
    2. Contact technical support for assistance
    
    

How to automatically start the web app

Video Instructions

Instructions

1. Open any folder on your desktop. Press the following key combination: ALT + V + Y + O . This will open the Folder Options. Go to the View tab and uncheck 'Hide extensions for known file types.' Click OK to close the Folder Options.
   
   
   
2. Create a text file on your desktop and name it startup_app.bat. This batch (BAT) file will be use in the following steps.
3. Add this text to the BAT file that was created. Make sure to update the directory for your own web app folder.
   
   startup_app.bat

   if not "%minimized%"=="" goto :minimized
       set minimized=true
       @echo off
   
       cd /D "C:\Users\caparici\Desktop\sol_200_web_app"
   
       start /min cmd /C "node app.min.js"
       goto :EOF
       :minimized
       

4. Right click on the BAT file and click Create shortcut. A new shortcut is created and named startup_app.bat - Shortcut.
   
   
   
5. Right click on the shortcut file startup_app.bat - Shortcut and click Properties. A new Shortcut Properties window appears.
   
   
   
6. Make the modifications as listed below.
   1. In the Shortcut Properties window, click Advanced.
   2. A new Advanced Properties window appears.
   3. Mark the checkbox for Run as administrator.
   4. Click OK on any open windows.
   
   
   
7. The shortcut may now be used to start the web app. You can double click the shortcut and the SOL 200 Web App server will be started automatically.
   
   Optionally, you can place the shortcut file in the 'Startup' folder so the server starts automatically when the machine is started. The location of the 'Startup' folder will vary for different versions of Windows. For some Windows operating systems, the ‘Startup’ folder is at this location, where USERNAME is replaced with your actual username: C:\Users\USERNAME\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

Enabling Web App Access to Other Devices

For demonstration purposes, it is assumed Computer A and B exist. It is very important to note that the IP addresses you work with will be different. Computer A (Server - The machine that hosts the web app) IP Address: 192.168.56.108 OS: Windows 10 Installed Software: SOL 200 Web App Computer B (Client - A remote machine that accesses the web app) IP Address: 192.168.56.111 OS: Windows 10 Installed Software: Google Chrome, Mozilla Firefox or Microsoft Edge

Determine the IP Address of the Server

C:\Users\User>ipconfig

Windows IP Configuration


Ethernet adapter Ethernet 2:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Ethernet adapter Ethernet 3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::a14d:b145:f240:50df%7
   IPv4 Address. . . . . . . . . . . : 192.168.56.108
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ethernet adapter Ethernet 4:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::4495:1e84:f3c3:35e7%23
   IPv4 Address. . . . . . . . . . . : 192.168.57.3
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

Ping the Server

Do the following on the server. Open the Control Panel Search for "firewall" Click Windows Defender Firewall
Click Advanced settings
Click Inbound Rules Right Click on Fire and Printer Sharing (Echo Request ICMPv4-In) Click Enable Rule Right Click on Fire and Printer Sharing (Echo Request ICMPv4-In) Click Enable Rule After the installation is fully complete, these rules can be disabled.
Do the following on the client. Execute this command, note your IP address will be different ping 192.168.56.108 The output indicates address 192.168.56.108 is accessible. This address 192.168.56.108 is accessible and should be used going forward.	Output C:\Windows\system32>ping 192.168.56.108 Pinging 192.168.56.108 with 32 bytes of data: Reply from 192.168.56.108: bytes=32 time=2ms TTL=128 Reply from 192.168.56.108: bytes=32 time<1ms TTL=128 Reply from 192.168.56.108: bytes=32 time=8ms TTL=128 Reply from 192.168.56.108: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.56.108: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 8ms, Average = 2ms
Execute this command, note your IP address will be different ping 192.168.57.3 The output indicates address 192.168.57.3 is not an accessible IP address and should not be used.	Output C:\Windows\system32>ping 192.168.57.3 Pinging 192.168.57.3 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.57.3: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Open and Verify Port 8080 of the Server is Open

To open port 8080, the following conditions must be fulfilled: First, the SOL 200 Web App must be running; Second, the firewall must be configured to open port 8080. Two methods are available to open port 8080.

Method 1

Do the following on the server. Open the command prompt Start the web app with this command node app.min.js	Output C:\Users\User\Desktop\nastran_sol_200_web_app_20210202_0944_v_5_0_0_beta>node app.min.js Success! The SOL 200 Web App has started. Desktop Version: Use Google Chrome and go to: http://localhost:8080/optimization Network Version: Use Google Chrome and go to: http://IPADDRESS:8080/optimization IPADDRESS is the IP address of this machine Example: 192.168.56.102:8080/optimization
Open Windows PowerShell Execute this command, note your IP address will be different Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 The output (TcpTestSucceeded: False) shows that port 8080 is not open.	Output PS C:\Users\User> Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 WARNING: TCP connect to (192.168.56.108 : 8080) failed ComputerName : 192.168.56.108 RemoteAddress : 192.168.56.108 RemotePort : 8080 InterfaceAlias : Ethernet 3 SourceAddress : 192.168.56.108 PingSucceeded : True PingReplyDetails (RTT) : 0 ms TcpTestSucceeded : False
Open the Control Panel Search for "firewall" Click Allow an app through Windows Firewall
Click Change settings Mark the checkboxes next to the rows named Node.js: Server-side JavaScript Mark the Private and Public checkboxes for each row named Node.js: Server-side JavaScript Click OK
Click Allow an app through Windows Firewall
Verify the checkboxes have been marked
Do the following on the client. Open Windows PowerShell Execute this command, note your IP address will be different Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 The output (TcpTestSucceeded: True) shows that port 8080 is successfully open.	Output PS C:\Users\User> Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 ComputerName : 192.168.56.108 RemoteAddress : 192.168.56.108 RemotePort : 8080 InterfaceAlias : Ethernet 3 SourceAddress : 192.168.56.108 TcpTestSucceeded : True

Open Google Chrome, Mozilla Firefox or Microsoft Edge Navigate to the address (note your IP address will be different) 192.168.56.108:8080/optimization The web app is now accessible

Method 2

Do the following on the server. Open the command prompt Start the web app with this command node app.min.js	Output C:\Users\User\Desktop\nastran_sol_200_web_app_20210202_0944_v_5_0_0_beta>node app.min.js Success! The SOL 200 Web App has started. Desktop Version: Use Google Chrome and go to: http://localhost:8080/optimization Network Version: Use Google Chrome and go to: http://IPADDRESS:8080/optimization IPADDRESS is the IP address of this machine Example: 192.168.56.102:8080/optimization
Open Windows PowerShell Execute this command, note your IP address will be different Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 The output (TcpTestSucceeded: False) shows that port 8080 is not open.	Output PS C:\Users\User> Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 WARNING: TCP connect to (192.168.56.108 : 8080) failed ComputerName : 192.168.56.108 RemoteAddress : 192.168.56.108 RemotePort : 8080 InterfaceAlias : Ethernet 3 SourceAddress : 192.168.56.108 PingSucceeded : True PingReplyDetails (RTT) : 0 ms TcpTestSucceeded : False
Open the Control Panel Search for "firewall" Click Allow an app through Windows Firewall
Click Advanced settings
Click Inbound Rules Click New Rule...
Select Port Click Next
Select TCP Set Specific local ports to 8080 Click Next
Select Allow the Connection Click Next
Mark the checkboxes for Domain, Private and Public Click Next
Set the Name as 0_port_8080 Click Finnish
A new Inbound Rule has been created
Do the following on the client. Open Windows PowerShell Execute this command, note your IP address will be different Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 The output (TcpTestSucceeded: True) shows that port 8080 is successfully open.	Output PS C:\Users\User> Test-NetConnection -ComputerName 192.168.56.108 -Port 8080 ComputerName : 192.168.56.108 RemoteAddress : 192.168.56.108 RemotePort : 8080 InterfaceAlias : Ethernet 3 SourceAddress : 192.168.56.108 TcpTestSucceeded : True

Open Google Chrome, Mozilla Firefox or Microsoft Edge Navigate to the address (note your IP address will be different) 192.168.56.108:8080/optimization The web app is now accessible

Installation Procedure - Linux

The following are directions on how to install the SOL 200 Web App on Red Hat Enterprise Linux (RHEL).

Video Instructions

Instructions

Prerequisites

• Ensure Google Chrome, Mozilla Firefox or Microsoft Edge is installed.
• Ensure 'sudo' privileges are available.
• Ensure Red Hat Enterprise Linux (RHEL) is registered and subscribed to access operating system updates.
• Ensure RHEL is connected to the network and has an IP address.
• Ensure the correct Network Device, e.g. enp0s8, enp0s3, is always enabled. In certain cases, the Network Device may be disabled on startup and will render the web app inaccessible.

The commands listed in this section are to be executed in the Terminal.

1. Log in to the operating system using a non-root account.
   • It is highly recommended to use or create a separate user account with sudo privileges when following these installation instructions. Do NOT use the root account for installation.
   • Running any web server via the root account is not best practice. The following instructions configure a web server via Node JS and will make the SOL 200 Web App accessible to users on the local network.
2. Download the web app
   1. Download the web app ZIP file, e.g. sol_200_web_app.zip .
   2. Extract the contents of the zip file to a folder named: sol_200_web_app .
3. Licensing - To configure the licensing, following these instructions.
   
   

   Method A - License File
   Prerequisites You have been provided a license file, for example 1100101101.dat. Instructions A.1 Ensure the license file name includes only the numbers 1 or 0 and the file extension '.dat' (Correct: 1100101101.dat Incorrect: for_chris_1100101101.dat) A.2 Take the license file (example: 10111010.dat) and put it in this directory ./sol_200_web_app/license

4. Install Node JS
   Use Method 1 to install Node JS. If Method 1 does not work, Method 2 is an alternative method of installing Node JS.
   
   

   Method 1

   Method 2

   Enable the Red Hat Software Collections (RHSCL) repository. sudo yum-config-manager --enable rhel-server-rhscl-7-rpms Execute this command to install Node JS. sudo yum install rh-nodejs12 After installation, the Node JS software collection must be enabled. Do the following. Create a new file enablenodejs12.sh in /etc/profile.d/ sudo gedit /etc/profile.d/enablenodejs12.sh Add the following text to file enablenodejs12.sh. #!/bin/bash source scl_source enable rh-nodejs12 Use this to reload the settings. Alternatively, you may restart the system to reload the settings. source /etc/profile.d/enablenodejs12.sh Note: The command below also reloads the settings, but only for the current terminal window. If you open a new terminal window, the software collection will not be enabled. The command scl enable is for short term use, but the file enablenodejs12.sh is for long term use. scl enable rh-nodejs12 bash

   Add and enable NodeSource's Node.js repository curl -sL https://rpm.nodesource.com/setup_12.x | sudo -E bash - Execute this command to install Node JS. sudo yum install -y nodejs If an error regarding yum lock and PackageKit occurs, this command must be executed first. sudo systemctl stop packagekit

   Open a new Terminal window. To confirm Node JS has been installed, confirm that there is a version number that exists.
   

   node --version

   Example output. If a version number is displayed, then Node JS has been installed successfully. Continue to the next step.

   node --version
   v12.22.12
   

   Important! Older versions of Node JS, such as version 6.17.1 are not compatible with the SOL 200 Web App.

   Older versions may be removed with the terminal commands below.

   If Red Hat Software Collections (RHSCL) was used to install Node JS, follow these instructions to remove Node JS.

   # Remove Node JS
   yum list installed | grep nodejs
   sudo systemctl stop packagekit
   sudo yum autoremove rh-nodejs6-runtime
   yum list installed | grep nodejs
   
   # Before
   #     [user1@skynet ~]$ yum list installed | grep nodejs
   #     rh-nodejs6.x86_64                    2.4-6.el7         @rhel-server-rhscl-7-rpms
   #     rh-nodejs6-gyp.noarch                0.1-0.12.1617svn.el7
   #     rh-nodejs6-http-parser.x86_64        2.7.0-4.el7       @rhel-server-rhscl-7-rpms
   #     rh-nodejs6-http-parser-devel.x86_64  2.7.0-4.el7       @rhel-server-rhscl-7-rpms
   #     rh-nodejs6-libuv.x86_64              1:1.9.1-3.el7     @rhel-server-rhscl-7-rpms
   #     [...]
   #     rh-nodejs6-nodejs-xtend.noarch       4.0.0-6.el7       @rhel-server-rhscl-7-rpms
   #     rh-nodejs6-npm.noarch                3.10.9-3.el7      @rhel-server-rhscl-7-rpms
   #     rh-nodejs6-runtime.x86_64            2.4-6.el7         @rhel-server-rhscl-7-rpms
   #
   # After (The rh-nodejs6 package is no longer listed)
   #     [user1@skynet ~]$ yum list installed | grep nodejs
   #
   # Node JS may now be reinstalled
   

   If NodeSource was used to install Node JS, follow these instructions to remove Node JS.

   # First remove all Node JS repositories
   cd /etc/yum.repos.d/
   ls -l
   sudo rm nodesource-el7.repo
   sudo rm nodesource-el.repo
   ls -l
   
   # Before
   #     [user1@skynet ~]$ ls -l
   #     total 44
   #     [...]
   #     -rw-r--r--. 1 root root  616 Oct 23  2020 CentOS-x86_64-kernel.repo
   #     -rw-r--r--. 1 root root  474 Apr 23  2019 nodesource-el7.repo
   #     -rw-r--r--. 1 root root  474 Apr 23  2019 nodesource-el.repo
   #
   # After (Note the nodesource[...].repo lines are now removed)
   #
   #     [user1@skynet ~]$ ls -l
   #     total 44
   #     [...]
   #     -rw-r--r--. 1 root root  616 Oct 23  2020 CentOS-x86_64-kernel.repo
   
   # Remove Node JS
   sudo yum remove nodejs  # Remove current Node JS
   sudo yum clean all      # Purge any cached installation files, this step is important to avoid reinstalling cached and old installers
   # Node JS may now be reinstalled
   

5. Start the Web App

   On the machine, navigate to this directory: ./sol_200_web_app

   cd sol_200_web_app

   Run this command to start the web app. The first start will ask you to accept the end user license agreement (EULA).

   node app.min.js

   If the location of the sol_200_web_app directory is restricted, sudo privileges will be required to start the web app.

   sudo node app.min.js

   
6. Confirm the web app is Accessible

   Open Google Chrome, Mozilla Firefox or Microsoft Edge and go to: http://localhost:8080/optimization.

   If you can access the web app, this indicates the web app is running successfully.

   The web app can be closed by closing the Terminal window or by pressing CTRL+C on the keyboard.

7. Ensure executable files have execution privileges

   The following files require execution privileges.

   ./sol_200_web_app/public/payload/app_design
   ./sol_200_web_app/public/payload/app_gp
   ./sol_200_web_app/public/payload/desktop_app_a

   Use these commands in the terminal to give execution privileges to these files.

   cd sol_200_web_app/public/payload
   chmod ugo+x app_design
   chmod ugo+x app_gp
   chmod ugo+x desktop_app_a
   cd ../../..

   This command may be used to confirm the files have execution privileges.

   ls -l sol_200_web_app/public/payload

   Example Output - Note that the presence of x characters indicates the files have execution privileges.

   [nectarine@vm-rhel-1 Desktop]$ ls -l sol_200_web_app/public/payload
   total 697900
   -rwxr-xr-x. 1 nectarine nectarine  57769440 Jul 27 09:59 app_design
   -rw-rw-r--. 1 nectarine nectarine  54931899 Jul 27 09:59 app_design.exe
   -rwxr-xr-x. 1 nectarine nectarine  89722536 Jul 27 09:59 app_gp
   -rw-rw-r--. 1 nectarine nectarine  79401492 Jul 27 09:59 app_gp.exe
   -rwxrwxr-x. 1 nectarine nectarine  33392072 Jul 27 09:59 desktop_app_a
   -rw-rw-r--. 1 nectarine nectarine  24646867 Jul 27 09:59 desktop_app_a.exe
   [...]
   

8. If during the use of the SOL 200 Web App, you encounter messages indicating 0 available licenses, this indicates the licensing is not correctly configured. Consider the following.
   1. Ensure you have followed the instructions to configure the license
   2. Contact technical support for assistance
   
   

Enabling Web App Access to Other Devices

9. Open Port 8080

   For the remainder of this guide, "machine" will be referred to the workstation or server that has the SOL 200 Web App installed. Any variation of "machine" such as "second machine" is a different workstation or server.

   By default, RHEL will have port 8080 closed. The following commands will open port 8080. Note that the SOL 200 Web App is configured to use only port 8080.
   

   On the machine, uses these commands to open port 8080.

   $ sudo firewall-cmd --list-ports
   
   $ sudo firewall-cmd --zone=public --add-port=8080/tcp --permanent
   success
   $ sudo firewall-cmd --reload
   success

   After these commands are executed, listing the ports now shows port 8080 is opened for TCP.

   Note: If 8080/tcp is not listed, the machine must be restarted for the changes to take effect.

   $ sudo firewall-cmd --list-ports
   8080/tcp
   

10. Confirm the web app is Accessible

    On a different machine, open Google Chrome, Mozilla Firefox or Microsoft Edge and go to: http://IPADDRESS:8080/optimization. Note that the IPADDRESS should be the IP of the machine that has the sol_200_web_app directory. Examples:

    • http://172.31.99.137:8080/optimization
    • http://192.168.1.234:8080/optimization

    If you can access the web app, the web is now accessible by other machines on the network.

How to automatically start the web app

11. Set the web app to run in the background
    
    

    Process Manager 2 (PM2) will be used to automatically run the SOL 200 Web App in the background. PM2 also automatically starts the SOL 200 Web App after the operating system is restarted.

    Important! Before continuing, please keep consider the following.

    • Be sure that the SOL 200 Web App is working successfully when using node app.min.js to start the web app. To verify the SOL 200 Web App is functioning properly, perform at least one tutorial listed in the Tutorials section.
    • If the SOL 200 Web App is currently running via node app.min.js in a terminal, please stop this process by pressing CTRL+C or by closing the terminal window.

    
    

    The following are instructions to configure the SOL 200 Web App to run in the background.

    Install PM2 using this command.

    sudo npm install pm2 -g

    Use this command to generate output. The output is used in the next step.

    pm2 startup

    The output will give you a new command to use. Execute this command. Note, your command may be slightly different. This command will add PM2 to the list of startup process on the system.

    sudo env PATH=$PATH:/usr/bin /usr/lib/node_modules/pm2/bin/pm2 startup systemd -u apricot --hp /home/apricot

    Navigate to the location of the ecosystem.config.json file and use PM2 to start the web app.

    cd /home/apricot/Downloads/sol_200_web_app
    pm2 start ecosystem.config.json

    Use this command to save the web app to the list of startup applications in PM2.

    pm2 save

    Open Google Chrome, Mozilla Firefox or Microsoft Edge and go to: http://IPADDRESS:8080/optimization. Note that the IPADDRESS should be the IP of your RHEL server. Examples:

    • http://172.31.99.137:8080/optimization
    • http://192.168.1.234:8080/optimization

    If you can access the web app, PM2 has been properly configured to automatically run the SOL 200 Web App in the background when the system is restarted.

    To confirm the SOL 200 Web App is automatically running after the operating system is restarted, do the following. Restart the operating system at your convenience. Open a web browser and confirm you can access the SOL 200 Web App. If successful, this confirms the SOL 200 Web App is running in the background after the system is restarted.

    PM2 Examples

    Below are more explicit PM2 examples. These examples start off assuming the SOL 200 Web App has not yet been configured with PM2.

    Inspect the current list of processes being managed by PM2.

    $ pm2 list all
    [PM2] Spawning PM2 daemon with pm2_home=/home/apricot/.pm2
    [PM2] PM2 Successfully daemonized
    ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
    │ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
    └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
    

    The output indicates there are no processes being managed by PM2.

    Navigate to the SOL 200 Web App directory.

    $ cd ./sol_200_web_app/
    

    Now use PM2 to start the SOL 200 Web App by using the configuration file ecosystem.config.json. This JSON file contains information to start the SOL 200 Web App.

    $ pm2 start ecosystem.config.json
    [PM2][WARN] Applications sol_200_web_app not running, starting...
    [PM2] App [sol_200_web_app] launched (1 instances)
    ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
    │ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
    ├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
    │ 0  │ sol_200_web_app    │ fork     │ 0    │ online    │ 0%       │ 20.6mb   │
    └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
    

    The outputted table shows the process named sol_200_web_app has started and its status is online.

    Save the edits made. Any time a start, stop or delete command is performed, a save must be done afterwards.

    $ pm2 save
    [PM2] Saving current process list...
    [PM2] Successfully saved in /home/apricot/.pm2/dump.pm2
    

    The terminal window may now be closed and PM2 will keep the SOL 200 Web App running in the background. If the system is restarted, PM2 will automatically restart the SOL 200 Web App on the next system startup.

    At any time, the log files of the sol_200_web_app process may be inspected.

    $ pm2 logs sol_200_web_app
    [TAILING] Tailing last 15 lines for [sol_200_web_app] process (change the value with --lines option)
    /home/apricot/.pm2/logs/sol-200-web-app-error.log last 15 lines:
    /home/apricot/.pm2/logs/sol-200-web-app-out.log last 15 lines:
    0|sol_200_ | Success! The SOL 200 Web App has started.
    0|sol_200_ | Local Access:  Use a web browser and go to: http://localhost:8080/optimization
    0|sol_200_ | Remote Access: Use a web browser and go to: http://IPADDRESS:8080/optimization
    0|sol_200_ |                  IPADDRESS is the IP address of this machine
    0|sol_200_ |                  Example: 192.168.56.102:8080/optimization
    0|sol_200_ | Compatible Web Browsers: Google Chrome, Mozilla Firefox, or Microsoft Edge
    0|sol_200_ | License Method: DAT File
    

    This output is updated automatically. To exit the view of the logs, press CTRL+C or close the terminal window. Recall that PM2 will keep the sol_200_web_app process running in the background.

    To clear the log files, use this command.

    $ pm2 flush
    [PM2] Flushing /home/apricot/.pm2/pm2.log
    [PM2] Flushing:
    [PM2] /home/apricot/.pm2/logs/sol-200-web-app-out.log
    [PM2] /home/apricot/.pm2/logs/sol-200-web-app-error.log
    [PM2] Logs flushed
    

    This command is used to list all the existing processes managed by PM2.

    $ pm2 list all
    ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
    │ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
    ├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
    │ 0  │ sol_200_web_app    │ fork     │ 0    │ online    │ 0%       │ 63.2mb   │
    └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
    

    The output indicates one process named sol_200_web_app is currently online and running.

    This command is used to stop the SOL 200 Web App.

    $ pm2 stop sol_200_web_app
    [PM2] Applying action stopProcessId on app [sol_200_web_app](ids: [ 0 ])
    [PM2] [sol_200_web_app](0) ✓
    ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
    │ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
    ├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
    │ 0  │ sol_200_web_app    │ fork     │ 0    │ stopped   │ 0%       │ 0b       │
    └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
    

    After performing a start, stop or delete, the current configuration must be saved. If you do not perform a save, the next time the operating system is restarted, PM2 will restart the sol_200_web_app process even though you performed a stop before. Be sure to save.

    $ pm2 save
    [PM2] Saving current process list...
    [PM2] Successfully saved in /home/apricot/.pm2/dump.pm2
    

    To permanently remove the SOL 200 Web App from being managed by PM2, execute a delete command.

    $ pm2 delete sol_200_web_app
    [PM2] Applying action deleteProcessId on app [sol_200_web_app](ids: [ 0 ])
    [PM2] [sol_200_web_app](0) ✓
    ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
    │ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
    └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
    [PM2][WARN] Current process list is not synchronized with saved list. App sol_200_web_app differs. Type 'pm2 save' to synchronize.
    

    Remember to save after a start, stop or delete command. If a delete command is performed, the force option must be used.

    $ pm2 save --force
    [PM2] Saving current process list...
    [PM2] Successfully saved in /home/apricot/.pm2/dump.pm2
    

    Confirm the sol_200_web_app process has been removed.

    $ pm2 list all
    ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
    │ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
    └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
    

    Updating PM2 to Use a Newer Version of the SOL 200 Web App

    PM2 may run only one version of the SOL 200 Web App (web app). If there is a need to use a different version of the web app, the previous web app version must be stopped and removed. The stop and removal process is detailed in this section.

    Before starting, ensure the newest version of the web app functions properly via the command below. Consider going through at least one exercise in the Tutorials section to confirm the web app is functioning properly.

    node app.min.js

    After the web app is confirmed to be working with the above command, you may stop the web app by closing the terminal window or pressing CTRL+C to stop the web app.

    The following describes how PM2 is used to replace older versions of the web app.

    First, stop and delete the sol_200_web_app process. Save the changes afterwards.

    pm2 stop sol_200_web_app
    pm2 delete sol_200_web_app
    pm2 save --force

    Navigate to the newest location of the web app. Your location will differ. Start the web app like normal and save the newest process.

    cd ./sol_200_web_app_newer_version
    pm2 start ecosystem.config.json
    pm2 save

    The newest web app should now be running. Open a web browser to access the web app.

    If at anytime, you would like to switch back to starting the web app with node app.min.js, you must stop and delete the sol_200_web_app process.

    pm2 stop sol_200_web_app
    pm2 delete sol_200_web_app
    pm2 save --force

    Removing PM2

    The following instructions describes how to completely remove PM2 from the system.

    First inspect the global packages currently installed.

    $ npm -g ls

    Consider the output of the command above. Before removal, one of the listed installed packages is pm2.

    /usr/lib
    ├── corepack@0.10.0
    ├─┬ npm@6.14.17
    │ ├── abbrev@1.1.1
    │ ├── ansicolors@0.3.2
    │ [...]
    └─┬ pm2@5.2.0
      ├─┬ @pm2/agent@2.0.1
      │ ├── async@3.2.4 deduped
    

    To begin the removal of PM2, the PM2 process must first be removed from the operating system's list of startup processes. Execute this command in a terminal.

    pm2 unstartup

    The command above yields an output similar to below, your output will be different. Execute the outputted command in the terminal.

    sudo env PATH=$PATH:/usr/bin /usr/lib/node_modules/pm2/bin/pm2 unstartup systemd -u apricot --hp /home/apricot

    To finish removal of PM2, remove the PM2 package with this command.

    sudo npm -g rm pm2

    Verify pm2 has been removed with this command.

    $ npm -g ls

    The output of the command should look similar to this. Note that pm2 is no longer listed, indicating pm2 has been successfully removed.

    /usr/lib
    ├── corepack@0.10.0
    └─┬ npm@6.14.17
      ├── abbrev@1.1.1
      ├── ansicolors@0.3.2
      [...]
    

    PM2 Commands

    Below is a short list of PM2 commands used in this documenation.

    pm2 delete|del [id|name|all]          stop and delete a process from pm2 process list
    pm2 flush [name]                      flush logs
    pm2 list|ls                           list all processes
    pm2 logs [id|name]                    stream logs file. Default stream all logs
    pm2 restart [id|name|all]             restart a process
    pm2 save|dump [options]               dump all processes for resurrecting them later
    pm2 stop [options] [id|name|all]      stop a process
    

• {{obj.path}}