First time here? Check out the Help page!
1 | initial version |
We have had similar errors in CBECC 2022 due to a floor being made up of multiple polygons and CBECC being unable to properly merge them all together into a single polyloop. This may not be your exact problem, though I suspect it is.
What happens is a building model is created in an xml format with a floor touching multiple other zones. Those floor polyloops are combined during a one-time translation process when importing the xml file into CBECC, where it attempts to create a single polyloop to then use as the reference for the specific space. In a text file, the polyloop directly after a space (SPC) is declared. When we had this same error, the polyloop had a name but did not have any cartesian points.
Our solution was to find all the polyloops which were suppose to be stitched together, because they do exist as interior floor elements, and manually create a polyloop of the correct points, eliminating duplicates, and aligning them in a clockwise list. This a little bit of time though was not impossible and, it helped to keep the entire model running. I can provide more details and examples if this is your error.
We suspect the error must be due to a problem in the translation script though have run across this error in many building models without a clear understanding of why.
2 | No.2 Revision |
We have had similar errors in CBECC 2022 due to a floor being made up of multiple polygons and CBECC being unable to properly merge them all together into a single polyloop. This may not be your exact problem, though I suspect it is.
What happens is a building model is created in an xml format with a floor touching multiple other zones. Those floor polyloops are combined during a one-time translation process when importing the xml file into CBECC, where it attempts to create a single polyloop to then use as the reference for the specific space. In a text file, the polyloop directly after a space (SPC) is declared. When we had this same error, the polyloop had a name but did not have any cartesian points.
Our solution was to find all the polyloops which were suppose to be stitched together, because they do exist as interior floor elements, and manually create a polyloop of the correct points, eliminating duplicates, and aligning them in a clockwise list. This took a little bit of time though however, it was not impossible and, it helped to keep the entire model running. I can provide more details and examples if this is your error.
We suspect the error must be due to a problem in the translation script though have run across this error in many building models without a clear understanding of why.