FYI -
https://www.eevblog.com/forum/metrology/lm399-heat-loss-within-a-vacuum/msg4392685/#msg4392685PS:
one of the great issues with Spice (LTspice, etc.) since ever is there is none "on-the fly" feedback of the actual Temperature (the temperature of a particular part) into its intrinsic models.
Having that would be a fundamental breakthrough.
You may easily model a schematics where, for example, a power loss of a 2N2222 transistor will be 100W (and its temperature say 700C) and it still will show nice results. Today LTspice assumes everything in your schematics is "kept" at the set global Temperature, like the default 27degC. You may "step" through temperature, but each individual step means that you change the global temperature to a certain value, and again, all in your schematics is kept at that temperature during the entire simulation run within the set step.. Also you may assign an individual temperature to a certain part, but again, it will stay constant during the entire simulation run.
That is a real world nonsense, of course..
To create an actual temperature of something is easy in the Spice as you may derive it from the power loss which is accessible anytime, but there is none mechanism to feed it back into the intrinsic models (diodes, transistors, resistors, etc.).. Also modeling of the temperature gradients and flows in the Spice is easy even today (provided you have on the actual temperature based behavior of the parts handy, what is not the case today).
I asked on this problem at the ADI's EZone forum (where LTspice developers sit), after a short discussion the guys there indicated
"..it would require almost complete rewrite.." of the LTspice.
Btw., there is everything you need in the Spice to do it,
as all its intrinsic models ARE ALREADY a function of Temperature (the temperature is an internal variable in the models, like any currents/voltages)..
Thus all what needs to be done is to SIMPLY expose the internal intrinsic model's temperature variable such we may wire it somewhere (where we created the actual temperature value).
So instead of a single global CONSTANT Temperature (as is today) we will have N_x temperature VARIABLES (where N is the number of the LTspice's intrinsic models, perhaps 15-20), applicable to each specific part in the schematics individually (as the part's parameter into which we will wire our temperature_value generating node).
Like Q1_Q_BIP3_temp, Q23_Q_MOS2_temp, D3_D_temp, D6_D_temp, R7_R_temp..
When not wired/set by the user in the schematics the default global Temperature will be used.
I encouraged them to go for it..