IES-VE User Forum

Hi All,

I have been working on a script to extract TM52 deltaT variable (Criterion 01) to perform overheating analysis. However, VE python API output and vistapro outputs are not matching for almost all the rooms. This causes different number of hours > 1deg numbers reported via python API and vistapro (default ADO reports from VE).
Upon further investigation, I found that VE API results are matching with default ADO reports when air speed in ADO report is set to 0.8m/s.
This means that delta T variable returned by VE API is calculated at air speed of 0.8m/s instead of 0.1m/s (as reported in Vistapro).
Anyone else experienced this problem ? How do you back calculate delta T at 0.1m/s in VE API ?

Thanks!

Hi Tan,

I had a similar problem between the API output and VistaPro output for the operative temperature. See the forum post here: https://forums.iesve.com/viewtopic.php? ... 797c3ed774

Maybe this relates to your problem as the deltaT variable is dependent on the operative temperature.

The development team at IES have said that they will address this in the next release:

An update on this, our developers have confirmed an error in the API obtained Operative Temperature variable and are working to correct this for our next major release (VE 2025) Thanks for bringing this to our attention.

Olly