Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Problem with ShopWithSimplePVT idf

The ShopWithSimplePVT idf file shows invalid fields for Collector # Branch with # replaced with 1,2,3,4,5. This shouldn't be the case as the fields Collect # objects all exist, but they aren't present in the drop down list to pick from. The simulation doesn't complain though.


I encountered this problem while writing a measure to automatically add PVT to a building. Everything was going smoothly until I tried adding a Branch with a SolarCollector:FlatPlate:PhotovoltaicThermal object in the Component 1 Name field using

idfObject = OpenStudio::IdfObject::load(idf_string)
object = idfObject.get
wsObject = workspace.addObject(object)

but the string for the Component 1 Name field is not successfully added because it's not in the drop down list in the IDF editor. My current workaround is to name the Shading object for the PVT panel and the PVT object the exact same string. The Shading object name is then in the drop down list of objects to add in the Component 1 Name field, the measure can successfully add the name of the PVT panel (even though the IDF editor thinks it's adding the name of a shading object), and the simulation runs without complaining about the Branch object.

Problem with ShopWithSimplePVT idf

The ShopWithSimplePVT idf file shows invalid fields for Collector # Branch with # replaced with 1,2,3,4,5. This shouldn't be the case as the fields Collect # objects all exist, but they aren't present in the drop down list to pick from. The simulation doesn't complain though.


I encountered this problem while writing a measure to automatically add PVT to a building. Everything was going smoothly until I tried adding a Branch with a SolarCollector:FlatPlate:PhotovoltaicThermal object in the Component 1 Name field using

idfObject = OpenStudio::IdfObject::load(idf_string)
object = idfObject.get
wsObject = workspace.addObject(object)

but the string for the Component 1 Name field is not successfully added because it's not in the drop down list in the IDF editor. My current workaround is to name the Shading object for the PVT panel and the PVT object the exact same string. The Shading object name is then in the drop down list of objects to add in the Component 1 Name field, the measure can successfully add the name of the PVT panel (even though the IDF editor thinks it's adding the name of a shading object), and the simulation runs without complaining about the Branch object.

Here is a link for the ShopWithSimplePVT idf file and a png showing the highlighted orange Component 1 Name fields in my google drive
https://drive.google.com/open?id=1q4Shq3BZmNIK__LK7ffEPtlE1SM7X6DL

Problem with ShopWithSimplePVT idf

The ShopWithSimplePVT idf file shows invalid fields for Collector # Branch with # replaced with 1,2,3,4,5. This shouldn't be the case as the fields Collect # objects all exist, but they aren't present in the drop down list to pick from. The simulation doesn't complain though.


I encountered this problem while writing a measure to automatically add PVT to a building. Everything was going smoothly until I tried adding a Branch with a SolarCollector:FlatPlate:PhotovoltaicThermal object in the Component 1 Name field using

idfObject = OpenStudio::IdfObject::load(idf_string)
object = idfObject.get
wsObject = workspace.addObject(object)

but the string for the Component 1 Name field is not successfully added because it's not in the drop down list in the IDF editor. My current workaround is to name the Shading object for the PVT panel and the PVT object the exact same string. The Shading object name is then in the drop down list of objects to add in the Component 1 Name field, the measure can successfully add the name of the PVT panel (even though the IDF editor thinks it's adding the name of a shading object), and the simulation runs without complaining about the Branch object.

Here is a link for the ShopWithSimplePVT idf file and a png showing the highlighted orange Component 1 Name fields in my google drive
https://drive.google.com/open?id=1q4Shq3BZmNIK__LK7ffEPtlE1SM7X6DL

Using EnergyPlus 8.8.0

Problem with ShopWithSimplePVT idf

The ShopWithSimplePVT idf file shows invalid fields for Collector # Branch with # replaced with 1,2,3,4,5. This shouldn't be the case as the fields Collect # objects all exist, but they aren't present in the drop down list to pick from. The simulation doesn't complain though.


I encountered this problem while writing a measure to automatically add PVT to a building. Everything was going smoothly until I tried adding a Branch with a SolarCollector:FlatPlate:PhotovoltaicThermal object in the Component 1 Name field using

idfObject = OpenStudio::IdfObject::load(idf_string)
object = idfObject.get
wsObject = workspace.addObject(object)

but the string for the Component 1 Name field is not successfully added because it's not in the drop down list in the IDF editor. My current workaround is to name the Shading object for the PVT panel and the PVT object the exact same string. The Shading object name is then in the drop down list of objects to add in the Component 1 Name field, the measure can successfully add the name of the PVT panel (even though the IDF editor thinks it's adding the name of a shading object), and the simulation runs without complaining about the Branch object.

Here is a link for the ShopWithSimplePVT idf file and a png showing the highlighted orange Component 1 Name fields in my google drive
https://drive.google.com/open?id=1q4Shq3BZmNIK__LK7ffEPtlE1SM7X6DL

Edit: Using EnergyPlus 8.8.0

The IDFeditor isn't really a problem. It's inconvenient to not have the PVT object name in the drop down menu, but easily fixed for one model. I really need to automate the process though. I'm working on a project to automate generation of building models to try and reach a zero net energy building in the most cost effective way. To do that, we're making measures that add skylights, change insulation, add PVT to a building, etc. We are also changing the percent of the roof that is windows, PVT, etc. As a consequence, we expect to have on the order of a million different simulation to run. Unfortunately, an EnergyPlus measure won't add what is considered an invalid object name to an IDF object field. Normally this is a good thing because the program makes sure I'm not using an object name that doesn't exist and makes debugging much easier. In this case though, I'm being prevented from adding an object that does exist, the PVT object name in a Branch object field.

Problem with ShopWithSimplePVT idf

The ShopWithSimplePVT idf file shows invalid fields for Collector # Branch with # replaced with 1,2,3,4,5. This shouldn't be the case as the fields Collect # objects all exist, but they aren't present in the drop down list to pick from. The simulation doesn't complain though.


I encountered this problem while writing a measure to automatically add PVT to a building. Everything was going smoothly until I tried adding a Branch with a SolarCollector:FlatPlate:PhotovoltaicThermal object in the Component 1 Name field using

idfObject = OpenStudio::IdfObject::load(idf_string)
object = idfObject.get
wsObject = workspace.addObject(object)

but the string for the Component 1 Name field is not successfully added because it's not in the drop down list in the IDF editor. My current workaround is to name the Shading object for the PVT panel and the PVT object the exact same string. The Shading object name is then in the drop down list of objects to add in the Component 1 Name field, the measure can successfully add the name of the PVT panel (even though the IDF editor thinks it's adding the name of a shading object), and the simulation runs without complaining about the Branch object.

Here is a link for the ShopWithSimplePVT idf file and a png showing the highlighted orange Component 1 Name fields in my google drive
https://drive.google.com/open?id=1q4Shq3BZmNIK__LK7ffEPtlE1SM7X6DL

Edit: Using EnergyPlus 8.8.0

The IDFeditor isn't really a problem. an insurmountable obstacle as I can forcibly write in the correct PVT name in the Branch object field. It's inconvenient to not have the PVT object name in the drop down menu, but easily fixed for one model. I really need to automate the process though. I'm working on a project to automate generation of building models to try and reach a zero net energy building in the most cost effective way. To do that, we're making measures that add skylights, change insulation, add PVT to a building, etc. We are also changing the percent of the roof that is windows, PVT, etc. As a consequence, we expect to have on the order of a million different simulation to run. Unfortunately, an EnergyPlus measure won't add what is considered an invalid object name to an IDF object field. Normally this is a good thing because the program makes sure I'm not using an object name that doesn't exist and makes debugging much easier. In this case though, I'm being prevented from adding an object that does exist, the PVT object name in a Branch object field.

Problem with ShopWithSimplePVT idf

The ShopWithSimplePVT idf file shows invalid fields for Collector # Branch with # replaced with 1,2,3,4,5. This shouldn't be the case as the fields Collect # objects all exist, but they aren't present in the drop down list to pick from. The simulation doesn't complain though.


I encountered this problem while writing a measure to automatically add PVT to a building. Everything was going smoothly until I tried adding a Branch with a SolarCollector:FlatPlate:PhotovoltaicThermal object in the Component 1 Name field using

idfObject = OpenStudio::IdfObject::load(idf_string)
object = idfObject.get
wsObject = workspace.addObject(object)

but the string for the Component 1 Name field is not successfully added because it's not in the drop down list in the IDF editor. My current workaround is to name the Shading object for the PVT panel and the PVT object the exact same string. The Shading object name is then in the drop down list of objects to add in the Component 1 Name field, the measure can successfully add the name of the PVT panel (even though the IDF editor thinks it's adding the name of a shading object), and the simulation runs without complaining about the Branch object.

Here is a link for the ShopWithSimplePVT idf file and a png showing the highlighted orange Component 1 Name fields in my google drive
https://drive.google.com/open?id=1q4Shq3BZmNIK__LK7ffEPtlE1SM7X6DL

Edit: Using EnergyPlus 8.8.0

The IDFeditor isn't an insurmountable obstacle as I can forcibly write in the correct PVT name in the Branch object field. It's inconvenient to not have the PVT object name in the drop down menu, but easily fixed for one model. I really need to automate the process though. I'm working on a project to automate generation of building models to try and reach a zero net energy building in the most cost effective way. To do that, we're making measures that add skylights, change insulation, add PVT to a building, etc. We are also changing the percent of the roof that is windows, PVT, etc. As a consequence, we expect to have on the order of a million different simulation to run. Unfortunately, an EnergyPlus measure won't add what is considered an invalid object name to an IDF object field. Normally this is a good thing because the program makes sure I'm not using an object name that doesn't exist and makes debugging much easier. In this case though, I'm being prevented from adding an object that does exist, the PVT object name in a Branch object field.