Construction set not inherited [closed]

asked 2 years ago

IanVG
281 ●4 ●8

updated 2 years ago

Aaron Boranian

14315 ●89 ●25 http://bigladdersoftware.com/

I know that similar questions have been posted, but I will attach some pictures to this post to clarify. I have set 90.1-2013 - PriSchool - ASHRAE-169-2013-5B as the Construction Set for each Space except one which I have left as none in the FloorspaceJS editor as shown.

image description

I have also set the default construction set for the building as 90.1-2013 - PriSchool - ASHRAE-169-2013-5B as shown:

image description

When I go to the Spaces tab and view the Default Construction Set column, I see that the space I assigned to none in FloorspaceJS is empty as shown:

image description

Shouldn't the space have inherited the default construction set from the building? Can someone explain what I did wrong?

Closed for the following reason the question is answered, right answer was accepted by IanVG
close date 2022-10-06 08:11:38.106057

answered 2 years ago

David Goldwasser

20460 ●94 ●14 http://www.openstudio.net/

You will not see anything in space field for default construction set unless you have set one specifically for the space. However if you do to the construction field under a surfaces construction, you should see a green inherited construction even for the space that doesn't directly have a construction set assigned.

Some elements in the OpenStudio Application interface show inherited connections, others areas do not.

link

Comments

Thank you for the answer! I ended up going to the surfaces tab, but I guess I was expecting similar behavior in different parts of the program. Are there reasons that some elements in the OS app show inherited connection and others do not?

IanVG ( 2 years ago )

Enhancements were added as needed prioritized what was most important. Surfaces are the end of the line, so I think that was a way to see what was going to be in the IDF at run time. You can add this as a feature request to the OpenStudio Coalition's GithHub page for the application by creating an issue.

David Goldwasser ( 2 years ago )

Issue submitted! Link here.

Edit: I closed the ticket I submitted, as it turned out there's already an outstanding ticket on this issue that you had already engaged with. The original ticket on this issue is here.

IanVG ( 2 years ago )

Sorry I forgot thee already was one. Thanks for linking them together.

David Goldwasser ( 2 years ago )

add a comment