-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App crashes when cloning air loop containing AirLoopHVAC:UnitarySystem #351
Labels
Triage
Issue needs to be assessed and labeled, further information on reported might be needed
Comments
eringold
added
the
Triage
Issue needs to be assessed and labeled, further information on reported might be needed
label
May 27, 2021
Ok, this seems like an App problem, can't reproduce in the CLI [1] OSApp-build(main)> m = Model.new
=> #<OpenStudio::Model::Model:0x000056515b4af850 @__swigtype__="_p_openstudio__model__Model">
[2] OSApp-build(main)> a = AirLoopHVAC.new(m)
=> #<OpenStudio::Model::AirLoopHVAC:0x000056515b2f2058 @__swigtype__="_p_openstudio__model__AirLoopHVAC">
[3] OSApp-build(main)> unitary = AirLoopHVACUnitarySystem.new(m)
=> #<OpenStudio::Model::AirLoopHVACUnitarySystem:0x000056515b0969a8 @__swigtype__="_p_openstudio__model__AirLoopHVACUnitarySystem">
[4] OSApp-build(main)> unitary.addToNode(a.supplyOutletNode)
=> true
[5] OSApp-build(main)> a.clone(m)
[utilities.idf.Workspace] <-1> Renamed Object of type 'OS:AirLoopHVAC' and named 'Air Loop HVAC 1' to 'Air Loop HVAC 2' to avoid a name conflict upon WorkspaceObject addition.
[utilities.idf.Workspace] <-1> Renamed Object of type 'OS:Schedule:Constant' and named 'Always On Discrete' to 'Always On Discrete 1' to avoid a name conflict upon WorkspaceObject addition.
[utilities.idf.Workspace] <-1> Renamed Object of type 'OS:AirLoopHVAC:UnitarySystem' and named 'Air Loop HVAC Unitary System 1' to 'Air Loop HVAC Unitary System 2' to avoid a name conflict upon WorkspaceObject addition.
=> #<OpenStudio::Model::ModelObject:0x000056515a3d4f58 @__swigtype__="_p_openstudio__model__ModelObject"> |
It looks like an orphaned node... I've definitely seen something similar in the past:
|
Yeah, actually it is a SDK issue. I can crash the app only by using the CLI to prepare the model [1] OSApp-build(main)> m = Model.new; a = AirLoopHVAC.new(m); unitary = AirLoopHVACUnitarySystem.new(m); unitary.addToNode(a.supplyOutletNode)
=> true
[2] OSApp-build(main)> a2 = a.clone(m).to_AirLoopHVAC.get
[utilities.idf.Workspace] <-1> Renamed Object of type 'OS:AirLoopHVAC' and named 'Air Loop HVAC 1' to 'Air Loop HVAC 2' to avoid a name conflict upon WorkspaceObject addition.
[utilities.idf.Workspace] <-1> Renamed Object of type 'OS:Schedule:Constant' and named 'Always On Discrete' to 'Always On Discrete 1' to avoid a name conflict upon WorkspaceObject addition.
[utilities.idf.Workspace] <-1> Renamed Object of type 'OS:AirLoopHVAC:UnitarySystem' and named 'Air Loop HVAC Unitary System 1' to 'Air Loop HVAC Unitary System 2' to avoid a name conflict upon WorkspaceObject addition.
=> #<OpenStudio::Model::AirLoopHVAC:0x00005623c414db68 @__swigtype__="_p_openstudio__model__AirLoopHVAC">
[4] OSApp-build(main)> m.save('2cli.osm') |
Moved to NREL/OpenStudio#4335 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Triage
Issue needs to be assessed and labeled, further information on reported might be needed
Issue overview
Maybe related to #217
Current Behavior
App crashes (closes with no message) when cloning an AirLoopHVAC with AirLoopHVAC:UnitarySystem on supply side.
Steps to Reproduce
Possible Solution
Details
Environment
Some additional details about your environment for this issue (if relevant):
The text was updated successfully, but these errors were encountered: