Hi !
I try to use .set(room conditions, system data) on my Thermal template, the method does not recognize the following dictionary keys
- "heating_capacity_unlimited"
- "cooling_capacity_unlimited"
- "HVAC_methodology"
- "conditioned"
An other problem is that this method don't set properly the heating and cooling profiles.
That would be great and very useful to correct it !
Best regards,
Kevin
Probleme : class VEThermalTemplate and set(room_conditions, system_data)
Re: Probleme : class VEThermalTemplate and set(room_conditions, system_data)
Hi,
"heating_capacity_unlimited" and "cooling_capacity_unlimited" are not supported keys for VEThermalTemplate.set(). I just tried the 'set_templates.py' sample which sets 'HVAC_methodology', 'conditioned' and heating and cooling profiles, which worked fine for me on a simple model.
Are you able to run this sample script?
"heating_capacity_unlimited" and "cooling_capacity_unlimited" are not supported keys for VEThermalTemplate.set(). I just tried the 'set_templates.py' sample which sets 'HVAC_methodology', 'conditioned' and heating and cooling profiles, which worked fine for me on a simple model.
Are you able to run this sample script?
Re: Probleme : class VEThermalTemplate and set(room_conditions, system_data)
Hi
After a long time I came back to it and solved all my problems. I post here my solutions and bug reports
The goal of my script is to save the details of my thermaltemplate (heating condition, internal gain ...), and to be able to reload them later.
Here are the differences I found between the dictionary keys of get_apache_systems () and set ():
- the cooling and heating_capacity_unlimited key exists in the get () but not in the set (). We must therefore delete this key (which is useless)
- the cooling or heating_capacity_units key gives all the information you need for this subject. But it gives an integer with the get () and the set () needs an IESVE Object. We must therefore transform the integer into a corresponding object.
And now the differences between the dictionary keys of get_room_conditions () and set ()
- If you are in VE2019, you cannot set the setpoint two value, the entry does not exist in the set ().
- there is a bug with the cooling and heating_setpoint_constant key. The get () is correct, on the other hand if you enter "True" in the set (), it will put "False", and vice versa. If you are with VE2019, you should use it, you just need to save the opposite value.
- If you are with VE2021, you can delete the cooling and heating_setpoint_constant key. All the info is contained in the cooling and heating_setpoint_type key.
After some hack, I have a scipt that works well.
Regards,
Kevin
After a long time I came back to it and solved all my problems. I post here my solutions and bug reports
The goal of my script is to save the details of my thermaltemplate (heating condition, internal gain ...), and to be able to reload them later.
Here are the differences I found between the dictionary keys of get_apache_systems () and set ():
- the cooling and heating_capacity_unlimited key exists in the get () but not in the set (). We must therefore delete this key (which is useless)
- the cooling or heating_capacity_units key gives all the information you need for this subject. But it gives an integer with the get () and the set () needs an IESVE Object. We must therefore transform the integer into a corresponding object.
And now the differences between the dictionary keys of get_room_conditions () and set ()
- If you are in VE2019, you cannot set the setpoint two value, the entry does not exist in the set ().
- there is a bug with the cooling and heating_setpoint_constant key. The get () is correct, on the other hand if you enter "True" in the set (), it will put "False", and vice versa. If you are with VE2019, you should use it, you just need to save the opposite value.
- If you are with VE2021, you can delete the cooling and heating_setpoint_constant key. All the info is contained in the cooling and heating_setpoint_type key.
After some hack, I have a scipt that works well.
Regards,
Kevin