Some Limitations of ATTACHED - Mainly Due to Using *SET_xxx
Some Limitations of ATTACHED - Mainly Due to Using *SET_xxx
Because the definition of "attached" is wider than the purely structural one of connected nodes and elements (see What Does "Attached to" Actually Mean?), some problems can arise when definitions which use sets are diagnosed as being "attached".
Consider the following case:
- Initial velocities for the whole model are defined by * INITIAL_VELOCITY using a *SET_NODE that contains all nodes in the model.
- Once a single node in that set is detected as being "visible" then the set itself is also made visible. This has the consequence of drawing all nodes (with their initial velocities) in the model ....
- .... and the next thing you see, after a single operation, is the whole model being drawn.
This presents a dilemma: should track through *SET definitions or not?
If it does then the problem defined above occurs.
If it does not then, for example, extra nodes on a rigid part (defined by * CONSTRAINED_EXTRA_NODES_SET ) will not be drawn properly when the part is visible.
At present does track through *SET definitions, leading to the problem outlined above. (Although the case of set zero, where it means "all nodes in the model", is detected and trapped.)
You can stop specific cases happening by turning off their switch (for example to stop the initial velocity display turn off INITIAL switch). You can also specific items (although they will probably unblank themselves again after the next operation).