IES-VE User Forum

Please ignore this above comment ^

The issue was on our end.

Hi Terence,

Thanks for getting back to us on this problem. Just want to follow up with another question...

Will this operative temperature bug affect the Comfort Analysis TM52 report?

We have a calculation for the CIBSE TM52 criteria and we're confident that our calculation is correct but it is ...

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?t=78979&sid=fa75f817dfddb1e3b50e11797c3ed774

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

I think the issue may be with the API obtaining different results to VistaPro for Operative Temperature (TM52/CIBSE).



I am not sure why these results differ but it would be good to figure out why this is the case.

Issue

IES VE Version: 2023.5.2.0

Hi, I have calculated the operative temperature following CIBSE's TM52 guidance and my output is different to what the IES API returns for the "Operative temperature (TM 52/CIBSE)" variable from VistaPro.

I've run this in two different models and the absolute ...

Great - thanks for your help.
The following function did the conversion and we validated that the results from VistaPro and the API are now an exact match.


def utc_to_bst(arr):
"""convert annual hourly from utc time to bst time

Args:
arr (np.array): array in UTC

Returns:
np.array: array ...

Hello Rhind, thank you for getting back to me.

Is there a way for the API to return the dry-bulb temperature where the day-light savings time is accounted for?

I've noticed a discrepancy between the dry-bulb temperature obtained from VistaPro and the dry-bulb temperature obtained through the Python API.

From vista, the first few values are (in list format):


[16. , -1.6, -2. , -3.2, -3.2, -2.6, -2. , -1.9, -1.8, -2. , -1.4, -0.5, 0.1, 0.4, 0.6, ...] (1 ...