Ansys Employee


If you place python script commands in an indented block like this, it will delay graphical update until the end of this code block:

with Transaction():
    for element in element_list:
        hf = analysis.AddHeatFlux()

However, the GUI is still not really meant to handle 20k load objects in the Outline well. It would be better to do this in an APDL command object if you choose to do this by script. See SF command:



The _table_variable will be a table of variables over time for each element. Create a heat flux load object and write the Ansys input file to see the format.

Better yet, why not use “External Data” to import all the heat flux:

It must be difficult to know the heat flux at each element number. It’s more typical to know XYZ locations of each heat flux. For each time point, you can use another data file in the same “External Data” system and click in the “master” for one. Or just append another column of heat flux data to all one file. Each column would be the heat flux values for another time point.

Also it seems your dome is stagnant air, which is too much of an insulator. This does not model heat transfer well since even in dead air there are natural convection current that carries the heat much faster than modeling the air as a solid body. This would need a CFD solver, or I know some people have done some fudging with the convections or stagnant air properties. I don’t remember the specifics. We usually don’t model the stagnant air in FEA heat transfer analysis. The convection BCs handle natural convection to the environment.