Hotspots

Video: Create hotspots of critical areas of results

You can create hotspots of critical areas of results on which you want to focus. Using hotspots, you can:

• Find the most critical areas (for example, the highest or lowest values) in a result.

• Save the hotspots to groups for display purposes or for further pre-processing.

The following shows a hotspot of Specialist Durability results. The hotspot contains elemental results between a range of values.

Each hotspot contains a central entity, the seed, that has the highest or lowest value that meets the search criteria.

Defining hotspot recipes

You find the hotspots using hotspot recipes that define the search criteria, which includes:

• The result type, location, and component to be included in the hotspot.You can use the result types that are displayed in the current post view or specify the type of results.

• The search method to be used to find the results. Four search methods are available for finding critical areas: specifying a threshold, defining a range of values, or setting minimum and maximum values. For more information about the different hotspot search methods, see Search methods for finding hotspots.

You can apply the hotspot recipe to the entire model or selected entities. To specify the entities, you can:

• Select the entities in the post view in the graphics window. You can only select pre-processing entities (related FE entities for polygon bodies, faces, or edges). You cannot select post-processing entities when creating a recipe.

• Select entities by node or element ID.

Generating hotspots

After you create a post view, the hotspot recipes that match the results displayed in the post view appear in the Post Processing Navigator under the Hotspot Recipes node of the post view.

To generate the hotspots, use the Resolve right-click command. Hotspots appear in the Post Processing Navigator under the hotspot recipe. The hotspot name includes the ID of the most critical entity, often referred to as the seed.

The hotspots are sorted in decreasing order of the value of their most critical entity. The first hotspot listed is the most critical to review.

If you change the results in the post view or edit the hotspot recipe, the software updates the hotspots to list only those that match the results in the post view and deletes any hotspots previously generated. To keep the generated hotspots, save them to groups. For more information about saving hotspots to groups, see Save hotspots to groups.

Managing hotspot recipes

The Hotspot Recipe Manager lets you create, edit, copy, and delete all hotspot recipes. You can edit the search criteria and the result components of a hotspot recipe. You cannot edit the search method or the results type. You can also display information about a hotspot recipe or a hotspot.

• The information displayed for a hotspot recipe includes the name of the hotspot recipe. If you resolved hotspots from the recipe, the information includes the number of hotspots resolved and a list of the hotspots. The list includes the name of the hotspot, the number of entities in it, and the critical entity and its value.

• The information displayed for a hotspot includes the name of the hotspot, the number of entities, its units, and the critical entity and its value. It also displays each of the entities in the hotspot.

Hotspot recipes are saved in the Simulation file.

Where do I find it?

Application	Pre/Post
Prerequisites	A Simulation file as the work part and displayed partPost view loaded (imported results are not supported)
Command Finder	Hotspot Recipe Manager

How do I

Create a hotspot recipe for a threshold

Create a hotspot recipe for a range of values

Create a hotspot recipe for minimum or maximum results

Generate hotspots from hotspot recipes

Manage hotspot recipes

Learn more

Search methods for finding hotspots

Quick links

Command reference

Pre/Post video examples

Bulk Entry Descriptions

Simcenter 3D tutorials

Browse Simcenter 3D help by product area

Hotspots, Simcenter 3D 2021.1 Series

© 2020 Siemens

window.mainLanguage="en_US"

window.delivId=""

window.projectId=""

MathJax.Hub.Config({ TeX: { extensions: ["autoload-all.js"] }, tex2jax: { displayMath: [ ] }, "SVG": { scale: 125 } });