1.1 Where are the simulation files saved by default?

* The simulation/error log is available in the working directory for each problem. The default simulation directories are located at :C:\Users\{username}\AppData\Roaming\Intact.Simulation For Grasshopper\
* Under each, you can find the simulation working directory labeled by the time and date of the simulation run:{YYYY-MM-DD-TIME} * Within each, there is a log of the simulation run:log.txt

1.2 What happens when two components are extremely close to each other but not bonded?

* Intact.Simulation models assemblies of parts as bonded if the gap between them is small. “Small” depends on the element size used in the simulation and the orientation of the gap.
* To ensure the accuracy of disconnected physics, reduce cell size (increase resolution) to be less than the gap size.

Solver Settings

2.1 When should I use linear elements and when should I use quadratic elements?

* Regardless of the scenario, either will work. Generally, quadratic elements converge to a good answer quicker and with few elements, but it depends on the simulation scenario.
* For geometries that undergo bending, quadratic elements perform better.
* It is important to note that with quadratic elements, many fewer elements are needed to compute an accurate solution. Having more elements increases computation time, so start with a low resolution or high cell size and increase the resolution/decrease cell size to improve accuracy.

📌 See example application Ex-6: Linear Elements vs Quadratic Elements

2.2 When should I use Iterative solvers vs. Direct Solver?

* For linear elements, the Direct Solver is recommended at a lower resolution (100-200K for 32GB RAM), and the Iterative solver at a higher resolution.
* For quadratic elements, we recommend using the Direct Solver.

2.3 How do I know what resolution/cell size to set?

* To accurately capture small features with linear elements, set the cell size to 1/3 the thickness of that feature.
* For quadratic elements, a cell size equal to the thickness of the small feature is sufficient.
* Low resolutions (<100,000) will generally solve problems quickly. Intact can typically support a resolution of 10 million elements (more on powerful computers), so start small, and gradually increase the resolution until consistent results are obtained.

📌 For more information see this post on resolution and convergence.

2.4 Is there a maximum resolution (or minimum cell size)?

* A decent laptop/desktop should be able to support a resolution (number of elements in the grid) in order of millions. The maximum depends on your computer's memory and whether you choose to use the direct (high performance, lots of memory) or iterative (slower performance, smaller memory footprint) solver.

2.5 How do I change where my simulation saves?

* First, place a file path object on the Grasshopper Canvas.
* Right click, and click “Select a directory” and connect it to Solution Directory (SD)

3.1 How can I turn on/off display mesh visualization?

* Intact plots results using a display mesh. The result values are sampled on the mesh vertices and then linearly interpolated within the mesh facets based on the facet nodes.
* To turn on or off this display mesh, see the steps in the video below
* Seeing the display mesh can be useful to ensure if there a visualization artifact due to the display mesh.

++3.2 How to create sections in the visualization using Rhino Clipping Plane?|

• Use Rhino’s `ClippingPlane` command to insert a plane that intersects the geometry you want to section.
  
• On the Grasshopper canvas, insert a `GUID` parameter block.
  
• Right-click the `GUID` block and choose “Set one GUID.” Then select the Clipping Plane object in Rhino.
  
• Once the GUID is linked to the Clipping Plane, the visualization should automatically update.
  
• The simulation geometry will be sectioned and filled accordingly, allowing clearer inspection of internal features.
  
• Note: Moving the Clipping Plane in Rhino will *not* update the sectioned geometry in Grasshopper. This is because the `GUID` block only captures the object’s identity—not its dynamic position or orientation.