Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
The OS:ThermalZone objects (3x) in your OSM file have missing zone air port lists (i.e. Inlet, Exhaust and Return), e.g.:
OS:ThermalZone,
{40fec67b-206e-4fb3-a3fc-687b921adfb0}, !- Handle
Thermal Zone: LivingArea, !- Name
, !- Multiplier
, !- Ceiling Height {m}
, !- Volume {m3}
, !- Floor Area {m2}
, !- Zone Inside Convection Algorithm
, !- Zone Outside Convection Algorithm
, !- Zone Conditioning Equipment List Name
, !- Zone Air Inlet Port List
, !- Zone Air Exhaust Port List
{a90b38cb-18e2-4057-bbb9-ada1a5857136}, !- Zone Air Node Name
, !- Zone Return Air Port List
, !- Primary Daylighting Control Name
, !- Fraction of Zone Controlled by Primary Daylig...
, !- Secondary Daylighting Control Name
, !- Fraction of Zone Controlled by Secondary Daylig...
, !- Illuminance Map Name
{e8ffdf51-9252-4f2e-8cbe-b07e379b82f3}, !- Group Rendering Name
{95aa2a88-908d-46ed-a196-8a29cddd3f0b}, !- Thermostat Name
Yes; !- Use Ideal Air Loads
It is indeed crashing at line 1992 here, as there is no Zone Inlet Port List object to assert (the existence of). Could the OpenStudio API feedback be more informative? Sure. Regardless, something went wrong when initializing those thermal zone objects. By default, when an OS:ThermalZone object is initialized, all 3 port list objects are automatically generated, along with the other required thermal zone objects:
These objects are indeed required, even if they're initially circular (i.e. they initially refer back to each thermal zone without valid HVAC components to connect). Any chance you've saved a preliminary version of the model before adding thermal zones?
If not, the safest for you would be to purge the model of all 3 thermal zone objects (and their aforementioned zone-related objects), then re-add thermal zones (the other objects should be auto-generated). Yet after several tries I can't edit/correct your model without crashing the OpenStudioApplication, and therefore can't help in guiding you towards a quick fix. This would fairly straightforward using an API script (e.g. Ruby, Python). Somewhat more hazardous to do by hand, yet this may be your only option (if you're not comfortable interacting with the API). Fortunately, your model holds exactly 3 instances of each object (i.e. 3 nodes, 3 connections, 3 sizing objects, 3 equipment lists), one for each thermal zone. So maybe make a copy of your model, delete all of these objects and restart from there.
There may be something else wrong with your model (which may be crashing the App), yet hard to say before fixing this stuff first.
| | 2 | No.2 Revision |
The OS:ThermalZone objects (3x) in your OSM file have missing zone air port lists (i.e. Inlet, Exhaust and Return), e.g.:
OS:ThermalZone,
{40fec67b-206e-4fb3-a3fc-687b921adfb0}, !- Handle
Thermal Zone: LivingArea, !- Name
, !- Multiplier
, !- Ceiling Height {m}
, !- Volume {m3}
, !- Floor Area {m2}
, !- Zone Inside Convection Algorithm
, !- Zone Outside Convection Algorithm
, !- Zone Conditioning Equipment List Name
, !- Zone Air Inlet Port List
, !- Zone Air Exhaust Port List
{a90b38cb-18e2-4057-bbb9-ada1a5857136}, !- Zone Air Node Name
, !- Zone Return Air Port List
, !- Primary Daylighting Control Name
, !- Fraction of Zone Controlled by Primary Daylig...
D...
, !- Secondary Daylighting Control Name
, !- Fraction of Zone Controlled by Secondary Daylig...
D...
, !- Illuminance Map Name
{e8ffdf51-9252-4f2e-8cbe-b07e379b82f3}, !- Group Rendering Name
{95aa2a88-908d-46ed-a196-8a29cddd3f0b}, !- Thermostat Name
Yes; !- Use Ideal Air Loads
It is indeed crashing at line 1992 here, as there is no Zone Inlet Port List object to assert (the existence of). Could the OpenStudio API feedback be more informative? Sure. Regardless, something went wrong when initializing those thermal zone objects. By default, when an OS:ThermalZone object is initialized, all 3 port list objects are automatically generated, along with the other required thermal zone objects:
These objects are indeed required, even if they're initially circular (i.e. they initially refer back to each thermal zone without valid HVAC components to connect). Any chance you've saved a preliminary version of the model before adding thermal zones?
If not, the safest for you would be to purge the model of all 3 thermal zone objects (and their aforementioned zone-related objects), then re-add thermal zones (the other objects should be auto-generated). Yet after several tries I can't edit/correct your model without crashing the OpenStudioApplication, and therefore can't help in guiding you towards a quick fix. This would fairly straightforward using an API script (e.g. Ruby, Python). Somewhat more hazardous to do by hand, yet this may be your only option (if you're not comfortable interacting with the API). Fortunately, your model holds exactly 3 instances of each object (i.e. 3 nodes, 3 connections, 3 sizing objects, 3 equipment lists), one for each thermal zone. So maybe make a copy of your model, delete all of these objects and restart from there.
There may be something else wrong with your model (which may be crashing the App), yet hard to say before fixing this stuff first.
| | 3 | No.3 Revision |
The OS:ThermalZone objects (3x) in your OSM file have missing zone air port lists (i.e. Inlet, Exhaust and Return), e.g.:
OS:ThermalZone,
{40fec67b-206e-4fb3-a3fc-687b921adfb0}, !- Handle
Thermal Zone: LivingArea, !- Name
, !- Multiplier
, !- Ceiling Height {m}
, !- Volume {m3}
, !- Floor Area {m2}
, !- Zone Inside Convection Algorithm
, !- Zone Outside Convection Algorithm
, !- Zone Conditioning Equipment List Name
, !- Zone Air Inlet Port List
, !- Zone Air Exhaust Port List
{a90b38cb-18e2-4057-bbb9-ada1a5857136}, !- Zone Air Node Name
, !- Zone Return Air Port List
, !- Primary Daylighting Control Name
, !- Fraction of Zone Controlled by Primary D...
, !- Secondary Daylighting Control Name
, !- Fraction of Zone Controlled by Secondary D...
, !- Illuminance Map Name
{e8ffdf51-9252-4f2e-8cbe-b07e379b82f3}, !- Group Rendering Name
{95aa2a88-908d-46ed-a196-8a29cddd3f0b}, !- Thermostat Name
Yes; !- Use Ideal Air Loads
It is indeed crashing at line 1992 here, as there is no Zone Air Inlet Port List object to assert (the existence of). Could the OpenStudio API feedback be more informative? Sure. Regardless, something went wrong when initializing those thermal zone objects. By default, when an OS:ThermalZone object is initialized, all 3 port list objects are automatically generated, along with the other required thermal zone objects:
These objects are indeed required, even if they're initially circular (i.e. they initially refer back to each thermal zone without valid HVAC components to connect). Any chance you've saved a preliminary version of the model before adding thermal zones?
If not, the safest for you would be to purge the model of all 3 thermal zone objects (and their aforementioned zone-related objects), then re-add thermal zones (the other objects should be auto-generated). Yet after several tries I can't edit/correct your model without crashing the OpenStudioApplication, and therefore can't help in guiding you towards a quick fix. This would fairly straightforward using an API script (e.g. Ruby, Python). Somewhat more hazardous to do by hand, yet this may be your only option (if you're not comfortable interacting with the API). Fortunately, your model holds exactly 3 instances of each object (i.e. 3 nodes, 3 connections, 3 sizing objects, 3 equipment lists), one for each thermal zone. So maybe make a copy of your model, delete all of these objects and restart from there.
There may be something else wrong with your model (which may be crashing the App), yet hard to say before fixing this stuff first.
| | 4 | No.4 Revision |
The OS:ThermalZone objects (3x) in your OSM file have missing zone air port lists (i.e. Inlet, Exhaust and Return), e.g.:
OS:ThermalZone,
{40fec67b-206e-4fb3-a3fc-687b921adfb0}, !- Handle
Thermal Zone: LivingArea, !- Name
, !- Multiplier
, !- Ceiling Height {m}
, !- Volume {m3}
, !- Floor Area {m2}
, !- Zone Inside Convection Algorithm
, !- Zone Outside Convection Algorithm
, !- Zone Conditioning Equipment List Name
, !- Zone Air Inlet Port List
, !- Zone Air Exhaust Port List
{a90b38cb-18e2-4057-bbb9-ada1a5857136}, !- Zone Air Node Name
, !- Zone Return Air Port List
, !- Primary Daylighting Control Name
, !- Fraction of Zone Controlled by Primary D...
, !- Secondary Daylighting Control Name
, !- Fraction of Zone Controlled by Secondary D...
, !- Illuminance Map Name
{e8ffdf51-9252-4f2e-8cbe-b07e379b82f3}, !- Group Rendering Name
{95aa2a88-908d-46ed-a196-8a29cddd3f0b}, !- Thermostat Name
Yes; !- Use Ideal Air Loads
It is indeed crashing at line 1992 here, as there is no Zone Air Inlet Port List object to assert (the existence of). Could the OpenStudio API feedback be more informative? Sure. Regardless, something went wrong when initializing those thermal zone objects. By default, when an OS:ThermalZone object is initialized, all 3 port list objects are automatically generated, along with the other required thermal zone objects:
These objects are indeed required, even if they're initially circular (i.e. they initially refer back to each thermal zone without valid HVAC components to connect). Any chance you've saved a preliminary version of the model before adding thermal zones?
If not, the safest for you would be to purge the model of all 3 thermal zone objects (and their aforementioned zone-related objects), then re-add thermal zones (the other objects should be auto-generated). Yet after several tries I can't edit/correct your model without crashing the OpenStudioApplication, and therefore so can't help in guiding you towards a quick fix. This would be fairly straightforward using an API script (e.g. Ruby, Python). Somewhat more hazardous to do by hand, yet this may be your only option (if you're not comfortable interacting with the API). Fortunately, your model holds exactly 3 instances of each object (i.e. 3 nodes, 3 connections, 3 sizing objects, 3 equipment lists), one for each thermal zone. So maybe make a copy of your model, delete all of these objects and restart from there.
There may be something else wrong with your model (which may be crashing the App), yet hard to say before fixing this stuff first.
