Error: Undefined data: left side of '<=' evaluating rule: Set DEFAULT Spc:RetailArea
DR - This is due to the default for Bldg:AboveGrdStoryCnt no resolving to a value, which is in turn due to the value for Story:Z not resolving to a value. For DetailedGeometry projects, Story:Z is set by the program. I thought it might be related to the bad Spc:PolyLp error described below, but I’m not sure. Entering a user value for Bldg:AboveGrdStoryCnt resolves this error. I can fix the rule to resolve the Undefined data error, but since this is the first time we’ve encountered this error that I would have expected in earlier releases, and there is a valid work around, I don’t necessarily think this requires a re-release.
DR - This is due to at least one bad Spc:PolyLp, here is what it looks like when plotted in 2D. This suggests may be other geometry issues that are causing problems with calculating Story:Z.
User model from CEC run in 2019.1.3
Error: Undefined data: left side of '<=' evaluating rule: Set DEFAULT Spc:RetailArea
DR - This is due to the default for Bldg:AboveGrdStoryCnt no resolving to a value, which is in turn due to the value for Story:Z not resolving to a value. For DetailedGeometry projects, Story:Z is set by the program. I thought it might be related to the bad Spc:PolyLp error described below, but I’m not sure. Entering a user value for Bldg:AboveGrdStoryCnt resolves this error. I can fix the rule to resolve the Undefined data error, but since this is the first time we’ve encountered this error that I would have expected in earlier releases, and there is a valid work around, I don’t necessarily think this requires a re-release.
InitSideDaylitAreas() error processing space 'L2-W units': Boost.Geometry Overlay invalid input exception
DR - This is due to at least one bad Spc:PolyLp, here is what it looks like when plotted in 2D. This suggests may be other geometry issues that are causing problems with calculating Story:Z.
Reported by: joesinger12
Original Ticket: cbecc-com/tickets/3229