Mental model ~6 min · ~10 min remaining in this part

Two overlapping models

Selection is state: what is active affects every subsequent command.

Operational mental map

Two overlapping models: topology and selection

Geometry defines what exists; selection defines what the next command will act on.

Complete the diagram from memory

Predict the missing relationships before revealing the model

Write the idea, not the exact wording. The comparison is feedback, not a grade.

3 missing links

1Input

Geometry

Primitives and the KP → LINE → AREA → VOLU hierarchy.

2StateWhat MAPDL state must be established or inspected?3DecisionWhat engineering or programming decision follows?4EvidenceWhat evidence would prove that the decision is defensible?

Mental model: two overlapping models

MAPDL maintains two entity families in the same database. The solid model describes geometry; the finite element model describes its discretization.

Entity hierarchy: volume, areas, lines, and keypoints in the solid model; elements and nodes in the finite element model — A component contains a single entity class. `fixed_nodes` contains nodes; `mid_elems`Elements.

Physical question	Useful entity	Example APDL
Where does the solid end up?	Face area or nodes	`NSEL,...,LOC,X,...`
Which part will be embedded?	Nodal component	`CM,fixed_nodes,NODE`
What elements are in the center?	Elements by centroid	`ESEL,...,CENT,X,...`
Which entities are active now?	Selection Status	`*GET,...,COUNT`

Selecting does not mean deleting

Both NSEL and ESEL internal flags change. Entities do not selected remain in the database. The danger is not to lose them, but to forget that they are temporarily invisible to subsequent commands.

Quick check

What does ALLSEL,ALL restore?

All selectable entities to the complete set. Only the nodes in the active component. The default material.

View complete module Download m02-kit.zip

Checking access…

Save your progress