I am trying to apply Autoshutoff and daylighting controls to applicable spaces from PRM navigator. It shows me the options in tabular edit. But when I apply the controls and close the tabular edit window and go back to it, all the controls are reset to None.
Its VE version 2024 and PRM navigator is ...
Search found 8 matches
- Fri Dec 27, 2024 9:06 am
- Forum: ASHRAE 90.1 App. G - PRM
- Topic: Autoshutoff and daylight controls getting reset to none
- Replies: 0
- Views: 11496
- Mon Dec 09, 2024 9:22 pm
- Forum: VE Python API
- Topic: VE API returning incorrect values for 'Daily running mean temp.' and 'Max. adaptive temp.'
- Replies: 0
- Views: 6364
VE API returning incorrect values for 'Daily running mean temp.' and 'Max. adaptive temp.'
Hi All,
I reckon that this is related to the issue of incorrect TM52 Operative temperature and delta T variable being returned by VE API.
I noticed that weather for variables 'Daily running mean temp.' and 'Max, adaptive temp.' (which are supposed to be supported and indexed at 15,16 as per enum ...
I reckon that this is related to the issue of incorrect TM52 Operative temperature and delta T variable being returned by VE API.
I noticed that weather for variables 'Daily running mean temp.' and 'Max, adaptive temp.' (which are supposed to be supported and indexed at 15,16 as per enum ...
- Tue Dec 03, 2024 7:17 am
- Forum: VE Python API
- Topic: IES operative temperature (TM 52/CIBSE) different from calculated operative temperature
- Replies: 8
- Views: 3726
Re: IES operative temperature (TM 52/CIBSE) different from calculated operative temperature
Hi Olly,
Are you getting correct Criterion 1 result using delta T variable from vistapro or calculating it using mean outdoor and operative temperatures ? I have observed that VE API throws value of delta T at 0.8m/s not 0.1m/s.
Are you getting correct Criterion 1 result using delta T variable from vistapro or calculating it using mean outdoor and operative temperatures ? I have observed that VE API throws value of delta T at 0.8m/s not 0.1m/s.
- Mon Nov 25, 2024 9:47 am
- Forum: VE Python API
- Topic: Relate coil name with respective room
- Replies: 2
- Views: 5120
Re: Relate coil name with respective room
Hi,
VE API has "get_space_id(layer number)" method which can be used to extract space IDs of each multiplex layer. This can be easily used to extract room names using Body ID and name attributes or using body "get_general()" method. Layer number and coil IDs are already tied togeter.
VE API has "get_space_id(layer number)" method which can be used to extract space IDs of each multiplex layer. This can be easily used to extract room names using Body ID and name attributes or using body "get_general()" method. Layer number and coil IDs are already tied togeter.
- Mon Nov 25, 2024 9:05 am
- Forum: VE Python API
- Topic: External Libraries
- Replies: 2
- Views: 3867
Re: External Libraries
Hi Josef,
This feature would be super helpful. Unfortunately, currently there is no way to access external libraries. I have tried different ways like pasting installed library folders in VE folder or current script folder but it throws a lot of errors. Importing and exporting data in different ...
This feature would be super helpful. Unfortunately, currently there is no way to access external libraries. I have tried different ways like pasting installed library folders in VE folder or current script folder but it throws a lot of errors. Importing and exporting data in different ...
- Fri Nov 22, 2024 4:12 pm
- Forum: VE Python API
- Topic: Filtering out void spaces when extracting room data using VEScript
- Replies: 1
- Views: 2367
Re: Filtering out void spaces when extracting room data using VEScript
If void spaces are included as Void body subtype, you can use if statement to exclude such spaces from analysis -
Example:
if body.type != iesve.VEBody_type.room:
continue
If void spaces are Room body subtype, you can either exlude them using their names like voids/risers etc. Another way is to ...
Example:
if body.type != iesve.VEBody_type.room:
continue
If void spaces are Room body subtype, you can either exlude them using their names like voids/risers etc. Another way is to ...
- Fri Nov 22, 2024 11:38 am
- Forum: VE Python API
- Topic: VE API returning different values 'Degrees > Max. adaptive temp. (TM 52 criterion 1)' variable than vistapro
- Replies: 1
- Views: 2328
VE API returning different values 'Degrees > Max. adaptive temp. (TM 52 criterion 1)' variable than vistapro
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 ...
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 ...
- Fri Feb 23, 2024 3:16 pm
- Forum: VE Python API
- Topic: Set internal gains using python
- Replies: 1
- Views: 2406
Set internal gains using python
Hi All,
VE python API has get_internal_gains() method to read all the internal gains data from the model.
However I could not find anything similar to set the internal gains.
Basically I want to override the lighting, power and people gain using script at room level.
Anyone aware of such method ...
VE python API has get_internal_gains() method to read all the internal gains data from the model.
However I could not find anything similar to set the internal gains.
Basically I want to override the lighting, power and people gain using script at room level.
Anyone aware of such method ...