How do I resolve surface construction matching conflicts between Surface X and Surface Y in the Openstudio APP - FloorspaceJS? How do I resolve the following error "Polyhedron is not enclosed in original testing. Trying to add missing colinear points. Polyhedron is not enclosed." ?

asked 2024-04-08 02:22:30 -0500

Mike117's avatar

updated 2024-04-08 10:39:03 -0500

I tried manually resolving the surface construction mismatch by matching the construction materials. The errors return after I rerun the simulation. I obtain errors like below:

Could not resolve matched surface construction conflicts between surfaces 'Face 1250', and 'Face 1267'
Could not resolve matched surface construction conflicts between surfaces 'Face 1304', and 'Face 1264'
Could not resolve matched surface construction conflicts between surfaces 'Face 1230', and 'Face 1296'

I have redone the spaces in FloorspaceJS that are called out with the following error message, but the error persists. Error message below.

Polyhedron is not enclosed in original testing. Trying to add missing colinear points.
Polyhedron is not enclosed.
Object of type 'OS:Space' and named 'Wet Lab 1' is not enclosed, there are 1 edges that aren't used exactly twice. Falling back to ceilingHeight * floorArea. Volume calculation will be potentially inaccurate.
Object of type 'Schedule:Constant' and named 'Always Off Discrete', points to an object named OnOff 2 from field 1, but that object cannot be located.
Object of type 'Schedule:Constant' and named 'Always On Continuous', points to an object named Fractional 1 from field 1, but that object cannot be located.

I posted two questions which are in the same failed simulation. Please let me know if this against posting rules.

Let me know if providing my model will help with troubleshooting.

Edit: This is a link a to the google drive where my model is stored. Link : https://drive.google.com/drive/folders/1tL6ghJ2tHihvcGWL37C-wHx-aNN9_Bnb?usp=sharing

edit retag flag offensive close merge delete

Comments

@Mike117 are you using the OpenStudio Application or a different tool that uses floorspace.js? Please mention it in the title or body of your post, as well as add a tag so that others can provide better help.

Aslo, if you can you upload your model to Google Drive, Dropbox, etc. and then share a URL for others to download, that would help others provide better solutions.

Aaron Boranian's avatar Aaron Boranian  ( 2024-04-08 09:27:22 -0500 )edit

Hi Aaron. I have added a link to the original post. I will add one here as well. Link : https://drive.google.com/drive/folders/1tL6ghJ2tHihvcGWL37C-wHx-aNN9_Bnb?usp=sharing

Mike117's avatar Mike117  ( 2024-04-08 10:37:08 -0500 )edit

@Mike117, yes: providing the model .osm file helps. Look up surfaces (with conflicting constructions) in the run/in.idf file. They are not referencing the same (inverted) constructions. For instance, "Face 1250" references a 2x layer "Typical Interior Wall", while its adjacent "Face 1267" references a 1x layer "Uninsulated Steel Stud Wall". Most obvious culprit would be some mismanagement of FloorspaceJS/OpenStudio SpaceTypes and DefaultConstructionSets. Hope this helps.

Denis Bourgeois's avatar Denis Bourgeois  ( 2024-04-08 11:22:54 -0500 )edit

So I went back to the model and reapplied the correct constructions, but the error persists. I think the constructions reverted to the "faulty" constructions during/at simulation run time. Is there a method for hardcoding the constructions without the constructions reverting?

Mike117's avatar Mike117  ( 2024-04-08 11:34:22 -0500 )edit

Yes, you can hard-assign a construction to a surface (or rather both interzone surfaces) with the OpenStudio Application, thus overriding default construction set assignments:

  • Spaces tab
  • ... Surfaces sub-tab
  • ... ... drag-and-drop a predefined construction into a surface's Construction column cell
  • ... ... (the construction name will switch from green to black, i.e. it's now hard-assigned)
Denis Bourgeois's avatar Denis Bourgeois  ( 2024-04-08 12:35:54 -0500 )edit