When using the act convection extension, how can we workaround a possible issue?

Question

When using the act convection extension, how can we workaround a possible issue with the Pilot Node Temperature result?

Erik Kostson · Accepted Answer

The extension (Convection 21.1 created by Ansys Inc) might block/freeze the UI when using the

Pilot Node Temperature result in newer releases (say 2025R2). Workaround is, do not use this extension pilot node result.

Instead:

We can retrieve the last node number which would correspond to the single Pilot Node Temperature in the model. We can do that with the below MAPDL script. Instead of *get we can use also the internal extension name for the pilot node: my_iNodeMax=nodeEnclosure_1 (_2, etc for other enclosure.

Then in a python post code object retrieve this node (ndm=comd.PropertyByName("my_iNodeMax").InternalValue), and generate a temperature result on it.

As shown below (after solve python code - make sure to RMB on the python code and → Connect for it to work):

def after_solve(this, analysis):# Do not edit this line

    solution=analysis.Solution

    comd = DataModel.GetObjectsByName("CommandsAPDL")[0]

    ndm=comd.PropertyByName("my_iNodeMax").InternalValue

    temperature_result=solution.AddTemperature()

    temperature_result.ScopingMethod = GeometryDefineByType.ResultFileItem

    temperature_result.ItemType = ResultFileItemType.NodeIDs

    temperature_result.SolverComponentIDs = str(int(ndm))

    solution.EvaluateAllResults()