Wrong boundary conditions after surface match : user scripts

asked 2018-04-10 14:33:23 -0500

rkbest
1392 ●1 ●4 ●13

updated 2018-04-10 19:29:50 -0500

__AmirRoth__

4436 ●5 ●17 http://bleedinggreenna...

I used Openstudio to model a complex building with different floor plans and then added plenum space at each floor followed by arranging them in the correct order.

>Intersect model
>surface match.

Following these steps generated a non-uniform boundary conditions properties in the model subsurfaces.

image description

The surface at the bottom of each plenum shows outside and default back when I try to change it to the surface.

2nd question: as I created each floor and plenum separately and then sandwiched them into a building prior to matching the entire model. The floor is identified as 'Building Story 1'. What can be a quick way to reorganize the spaces?

Comments

I did see the partial solution on this thread and spend hours to get this right. I guess is not easy for a complex floor plan with objects inside another object that is surrounded by more than 3 boundaries.

rkbest ( 2018-04-11 07:55:04 -0500 )edit

I am trying the Apply measures option for intersect and then surface_matching to see if it does what I need to have proper boundary conditions. I will update here.

rkbest ( 2018-04-11 10:01:02 -0500 )edit

add a comment

answered 2018-04-11 12:09:50 -0500

rkbest
1392 ●1 ●4 ●13

Had to redraw from floor plan level and connected all rectangles that were not touching other surfaces. And then used plugin surface match. I still have some wrong boundary conditions that need to be set manually. OSM measure of surface matching and intersect surfaces failed to help in my model as they took more than 30 minutes with no progress and so I canceled.

Suggestions for the first-timers: - At the floor plan level, all zones or rooms should be touching other surfaces for at least two sides to avoid this error at the later time. -Surface Match does not always do what you expect, so check the boundary conditions and diagnose the colors if they represent the correct situation. Change manually using Inspector from the plugin.

And hope you can fix all errors.

edit flag offensive delete link

Comments

@rkbest, you may want to try this diagnostic version of the surface matching measure.. This version loops through one space at a time with info and puts statements to better troubleshot errors seen on some large models. It can identify the specific surfaces that are creating issues.

David Goldwasser ( 2018-04-11 13:57:51 -0500 )edit

@David Goldwasser, I did create a custom measure using the ruby script but it fails with a syntax error. Am I missing any steps.

[19:50:34.129571 ERROR] :/ruby/2.2.0/gems/openstudio- workflow-1.3.1/lib/openstudio/workflow/util/measure.rb failed with message C:/Users/rajeev/OpenStudio/Measures/surface_match_2/measure.rb:7: syntax error, unexpected ' ^ C:/Users/rajeev/OpenStudio/Measures/surface_match_2/measure.rb:9: syntax error, unexpected '

rkbest ( 2018-04-11 19:54:45 -0500 )edit

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Wrong boundary conditions after surface match : user scripts

Comments

1 Answer

Comments

Your Answer

Careers

Question Tools

Stats

Wrong boundary conditions after surface match : user scripts edit

Comments

1 Answer

Comments

Your Answer

Careers

Question Tools

Stats

Wrong boundary conditions after surface match : user scripts