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

adjacent surfaces mismatch vertices.

asked 2019-11-27 06:07:39 -0600

RabindraKumar gravatar image

updated 2019-11-27 08:02:15 -0600

Hi,

Could anyone help regarding the mismatch the number of vertices in adjacent surfaces after matching surfaces. So can you suggest I would fix this problem quickly through OSM edit file. For example:

Surface 482,                            !- Name
Floor,                                  !- Surface Type
,                                       !- Construction Name
{fedb58fb-85f6-42fb-9224-d914de3f2009}, !- Space Name
Surface,                                !- Outside Boundary Condition
{0a73280c-71e0-4c04-86b2-ae866a7dfca8}, !- Outside Boundary Condition Object
NoSun,                                  !- Sun Exposure
NoWind,                                 !- Wind Exposure
,                                       !- View Factor to Ground
,                                       !- Number of Vertices
-1.95658023762474, 21.2500001941292, 0, !- X,Y,Z Vertex 1 {m}
-1.59287521774265, 20.489064658754, 0,  !- X,Y,Z Vertex 2 {m}
-0.976562649273255, 19.0041590180099, 0, !- X,Y,Z Vertex 3 {m}
-0.524470438300814, 17.7300001941292, 0, !- X,Y,Z Vertex 4 {m}
-4.63326495613921, 17.7300001941292, 0, !- X,Y,Z Vertex 5 {m}
-4.63326495613921, 13.8900004067006, 0, !- X,Y,Z Vertex 6 {m}
-9.01326495613926, 13.8900004067006, 0, !- X,Y,Z Vertex 7 {m}
-9.01326495613926, 20.970062273176, 0,  !- X,Y,Z Vertex 8 {m}
-5.33326495613917, 20.9700395084942, 0, !- X,Y,Z Vertex 9 {m}
-5.33326495613917, 21.2500001941292, 0; !- X,Y,Z Vertex 10 {m}

& other surface having 14 no. vertices.

OS:Surface,
{0a73280c-71e0-4c04-86b2-ae866a7dfca8}, !- Handle
Surface 946,                            !- Name
RoofCeiling,                            !- Surface Type
,                                       !- Construction Name
{dc962ea0-fced-43c7-b680-a227141c424c}, !- Space Name
Surface,                                !- Outside Boundary Condition
{568a12a8-3424-44b3-96ec-dfb4cf5a5898}, !- Outside Boundary Condition Object
NoSun,                                  !- Sun Exposure
NoWind,                                 !- Wind Exposure
,                                       !- View Factor to Ground
,                                       !- Number of Vertices
-1.15505827125162e-014, -1.9799997874285, 2.025, !- X,Y,Z Vertex 1 {m}
0, 1.86000000000002, 2.025,             !- X,Y,Z Vertex 2 {m}
4.10879451783821, 1.86000000000002, 2.025, !- X,Y,Z Vertex 3 {m}
3.65670230686596, 3.13415882388072, 2.025, !- X,Y,Z Vertex 4 {m}
3.04038973839656, 4.61906446462481, 2.025, !- X,Y,Z Vertex 5 {m}
2.67668471851429, 5.38000000000014, 2.025, !- X,Y,Z Vertex 6 {m}
-0.699999999999979, 5.3800000000001, 2.025, !- X,Y,Z Vertex 7 {m}
-0.699999999999979, 5.10003931436511, 2.025, !- X,Y,Z Vertex 8 {m}
-4.38000000000006, 5.10006207904691, 2.025, !- X,Y,Z Vertex 9 {m}
-4.38000000000004, 1.629999723366, 2.025, !- X,Y,Z Vertex 10 {m}
-1.95000000000017, 1.629999723366, 2.025, !- X,Y,Z Vertex 11 {m}
-1.95000000000017, -0.865000276633828, 2.025, !- X,Y,Z Vertex 12 {m}
-4.38000000000004, -0.865000276633828, 2.025, !- X,Y,Z Vertex 13 {m}
-4.38000000000006, -1.9799997874285, 2.025; !- X,Y,Z Vertex 14 {m}
edit retag flag offensive close merge delete

Comments

Please try to add a tag for the specific software you're using if appropriate (eg: openstudio here). Developers tend to watch for specific tags only.

Julien Marrec gravatar imageJulien Marrec ( 2019-11-27 08:02:53 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-11-27 12:34:42 -0600

updated 2019-11-27 12:35:19 -0600

@RabindraKumar the second surface looks like it has four pair of collinear vertices. So they could still be matched even though they vertex count doesn't match. If that is the case you don't have to change anything

For reference on the UnmetHours GitHub.com repository there is a diagnostic version of SurfaceMatching Measure that can remove duplicate and collinear vertices. This runs much slower because it intersects each space against only one other space at a time to help identify failure point on complex models.

edit flag offensive delete link more

Your Answer

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

Add Answer

 



Question Tools

1 follower

Stats

Asked: 2019-11-27 06:07:39 -0600

Seen: 34 times

Last updated: Nov 27