MV-7008: Co-simulation with AcuSolve

1. From the Start menu, selectAltair <version> MotionView <version>.
2. Open the model Valve_model.mdl from <altair>\<version>\tutorials\mv_hv_hg\mbd_modeling\motionsolve\cosimulation.
   This model is prepared to run in MotionSolve but requires modifications to run in co-simulation with AcuSolve. These steps are outlined below.

   Once the model is loaded into MotionView, the graphical window displays the shutter valve, perforated plate, joint and spring entities, as well as a graphical representation of the spring damper as shown in the figure below.

   
   
   Figure 4. The MotionSolve model of the pressure check valve

   The MotionSolve model consists of the following components:

   Component Name	Component Type	Description
   Ground Body	Rigid Body	Ground Body
   Shutter Body	Rigid Body	30 degree section of the shutter body.
   Shutter Body Graphic	Graphic	The graphic that represents the shutter body. This graphic is used both for the co-simulation and the contact force calculations.
   Perforated Plate Graphic	Graphic	The graphic that represents the perforated plate belonging to Ground Body. This graphic is used both for the co-simulation and for the contact force calculations.
   Contact	3D Rigid-Rigid Contact Force	3D rigid-rigid contact force between the Shutter body and the Ground Body (Perforated Plate).
   Solver Units	Data Set	The units for this model (Newton, Meter, Kilogram and Second).
   Gravity	Data Set	Gravity specified for this model. The gravity is turned on and acts in the negative Y direction.
   Spring	Graphic	The graphic that represents the spring modeled between the shutter body and the perforated plate body. This is only for visualization and does not affect the co-simulation results.
   Translation	Translational Joint	This translational joint allows motion of the shutter body along the X axis.
   Spring	Spring Damper	This is a simple spring damper mounted between the shutter body and the Ground Body.
   ContactOutput	Output	An output signal that measures the contact force.
   Displacement	Output	An output signal that measures the displacement between the shutter body and the ground.
   Velocity	Output	An output signal that measures the velocity of the shutter body with respect to the ground.

1. From the MotionView toolbar, click Run Solver, , to display the Run panel.
2. Provide a name for the XML file: Valve_Model_no_cosim.xml
3. Click Run
4. Review the log in the solver window. Verify that the MotionSolve run is complete and there are no errors. Close the solver window.
   Note: If you load the animation H3D file that is generated from running this model, notice that there is no motion in any of the parts. This is because all of the actuation for this model comes from AcuSolve, which was disabled for this simulation.

   To verify that the MotionView model is set up correctly, run the model in MotionSolve and verify there are no warning/error messages from MotionSolve.

1. The name of the “wet” body/bodies need to match between MotionSolve and AcuSolve. The names of the “wet” body/bodies are specified in the *.inp file on the AcuSolve side.
   Note: The names are case-sensitive and must match exactly (see the text in red below).

   MotionSolve (.xml):

   <!-- MODEL.b_Part1 -->
   <Body_Rigid
   full_label = "Model-Shutter Body"

   AcuSolve (.inp):

   EXTERNAL_CODE_SURFACE( "Valve wall" ) {
   rigid_body_name = "Model-Shutter Body"

2. The print_interval for the MotionSolve model needs to match the step size for the AcuSolve model. For this tutorial, it is set to 0.002s.
3. You must set the MotionSolve step size, h_max, to match the print_interval (0.002s in this case).
4. Also, verify that the end times for both models are set to the same values. For this tutorial, the end times for both the AcuSolve and MotionSolve models are set to 0.35s.
   See the Run Panel in MotionView to set the print_interval, step size (h_max), and end times.

   Note that the units in the MotionSolve and AcuSolve models do not need to match to run the co-simulation; however, the units must match to overlay the results animations in HyperView. The units in MotionView are set via the Units form shown below:

   
   
   Figure 5. Setting the units in MotionView

   All values in the MotionSolve model are set with respect to these units settings.

1. From the Project Browser, select the body Shutter Body.

   Figure 6.

   The body panel is displayed at the bottom.
2. From the Properties tab, select Fluid interaction with Acusolve

   Figure 7.

3. To export the solver deck to your working directory, click Export.
   You may change the default name of the model.

   
   
   Figure 8. Exporting the model to .xml

   At this point, you have set up the model in MotionView to interact with AcuSolve.

1. From the Start menu, select All Programs > Altair <version> > Compute Console and select MotionSolve as the solver.
   Locate the model you just exported by clicking on the file open icon.

   
   
   Figure 9. Select the exported model from disk

2. Click the ellipsis button next to the Options field to open the Available Options dialog.

   
   
   Figure 10. Selecting the co-simulation flag

3. Activate the –as_cosim option. When this flag is enabled, it tells the Run Manager to do the following:
   1. Invoke the MotionSolve executable and run the model that is specified.
   2. Invoke the middleware “acuMSI”, which enables communication between MotionSolve and AcuSolve.

   When you activate this option, the following dialog is displayed and you are prompted for additional options:

   
   
   Figure 11. Specifying options for the co-simulation

   You may specify the following options here:

   acuMSI Options

   -aport <integer>

   Specifies the communication port number for communication between AcuSolve and acuMSI. The default is 48000.

   Note If you need to change the default port for communication between AcuSolve and acuMSI, in addition to changing this argument, you also have to specify the changed port number in the AcuSolve input file.

   -mport <integer>

   Specifies the communication port number for communication between MotionSolve and acuMSI. The default is 94043.

   Note: If you need to change the default port for communication between MotionSolve and acuMSI, in addition to changing this argument, you also have to specify the changed port number in an environment variable MS_AS_PORT. MotionSolve checks for this environment variable at the start of the simulation and changes its listening port accordingly.

   -mi <integer>

   Specifies the maximum number of iterations per time step between the two solvers. The default is 0.

   -v <integer>

   Specifies the verbosity level of the output file from acuMSI. The default is set to 0 (verbosity OFF).

4. If you retain the default options, click None.
5. Click Apply Options and click Close.

   
   
   Figure 12. Specifying the co-simulation flag

6. You are now setup to start the co-simulation on the MotionSolve side. Click Run.

   
   
   Figure 13. Run the MotionSolve model

   This launches MotionSolve as well as the acuMSI executable. The MotionSolve run is paused at the first time step – it is now in waiting mode and the co-simulation will start as soon as AcuSolve is run.

   
   
   Figure 14. The MotionSolve simulation is waiting for a connection to AcuSolve

1. To run the co-simulation model in AcuSolve, first copy the model file Check_Valve_Coupled.acs from <installation_directory>\tutorials\mv_hv_hg\mbd_modeling\motionsolve\cosimulation to your working directory.
2. From the Start menu, select All Programs > Altair <version> > AcuSolve Job Launcher. In the window that is displayed, change the field Problem name as specified by the AcuSolve .inp file. Make sure your Problem directory is set to your current working directory.

   
   
   Figure 15. Launching AcuSolve for the co-simulation

   For this model, the default values are used. AcuSolve runs using a single processor, and AcuConsole generates the input files and launches AcuSolve.

3. Press Launch to launch the solution process.
   As the solution starts, an AcuTail window opens. After executing AcuPrep, AcuSolve stops at the acuRun path step. It’s waiting for the execution of the process.MotionSolve

   Soon, AcuSolve and MotionSolve should begin to communicate with one another. You should be able to see relevant time stepping information in both solver windows. For example, you should see something like the following in the MotionSolve window at the beginning of the co-simulation:

   INFO: [AS-COSIM] Connected to AcuMsi on port 94043
   
   INFO: [AS-COSIM] License checked out.
   
   …
   
   Time=2.000E-06; Order=1; H=2.000E-06 [Max Phi=1.314E-16]
   Time=3.600E-02; Order=2; H=2.000E-03 [Max Phi=1.653E-08]
   …

   The co-simulation should take roughly 15 minutes to complete on a laptop (Intel i7. 2.8GHz).

   Note that there is no order dependency on launching the co-simulation – either MotionSolve or v can be launched first.

The animation H3D generated by the MotionSolve part of the co-simulation contains only the results from MotionSolve. Similarly, the result files from AcuSolve only contain the results for the AcuSolve model. To animate the results from the co-simulation, follow these steps:

1. Load the animation H3D generated by MotionSolve in HyperView.
   1. Go to the Load Model panel.
   2. Click the file open button, , next to Load model and navigate to the results directory (the same directory where the .xml file is located).
   3. Select the .h3d file and click Open.
   4. Click Apply.

      
      
      Figure 16. Loading MotionSolve H3D in HyperView

2. HyperView loads the MotionSolve results file into the graphical window at the first time step. From this point, you can animate the transient results using Start/Stop on the Animation Slider.
3. To load the AcuSolve results, they must first be converted to the .h3d format. This can be accomplished by using the AcuSolve utility, AcuTrans. AcuTrans is available from the Start menu. Select Altair <version> AcuSolve > AcuSolve Cmd Prompt.
4. Navigate to the results directory and execute the following command to convert the AcuSolve database into the .h3d format:

   acuTrans -out -to h3d -h3dopt single -ts A

   This creates a single .h3d file containing all of the time steps available for the simulation.

5. Using AcuTrans, overlay the newly-created H3D over the MotionSolve result H3D in HyperView. This is accomplished by repeating Step 1 described above and activating Overlay when selecting the AcuSolve result H3D.

   
   
   Figure 17. Overlaying AcuSolve H3D over the MotionSolve H3D in HyperView

   Once loaded, the graphical window contains both results and can be animated as before. To visualize the information contained within the AcuSolve results, a Contour plot may be used. Click on the Contour button to display the panel.

6. Set the options as shown in the figure below and click Apply.

   
   
   Figure 18. Overlaying AcuSolve H3D over the MotionSolve H3D in HyperView

   This creates a contour plot of the velocity magnitude overlaid with the results from MotionSolve in one window.

   
   
   Figure 19. Velocity magnitude plot overlaid with the MotionSolve results in HyperView

Plotting the MotionSolve Results in HyperGraph

You can also interpret the results with a two dimensional plot using HyperGraph. HyperWorks Desktop can be used in a multi-window layout, allowing both HyperView and HyperGraph to be open at the same time.

7. First, open HyperView following the steps described in the previous section.
8. From the toolbar, click the Page Window Layout button and split the page into two vertical pages.

   
   
   Figure 20. Splitting the page into two vertical pages

   This automatically adjusts the graphical window to accommodate two pages, defaulting to two instances of HyperView.

9. Click anywhere in the page on the right and switch to HyperGraph by clicking the Page Selector button and selecting HyperGraph 2D from the drop-down list.
10. Click the Build Plots button to load the .plt file from the same results directory.
    Once the .plt file is loaded into HyperGraph, the two outputs are available for plotting.
11. Perform the following selections:
    1. Under Y Type, select Displacement.
    2. Under Y Request, select Displacement (on Shutter Body).
    3. Under Y Component, select X.
    4. Click Apply.
    HyperGraph can be used to create additional traces on the same plot to generate the following plots.

    
    
    Figure 21. Select the signals for plotting

    
    
    Figure 22.