search

joesinger12 / TestTicketTransfer

0 stars 0 forks source link

CBECC-Com Issue - Daylight Sensor location errors #45

Open joesinger12 opened 6 years ago

joesinger12 commented 6 years ago

I am getting this error in my EnergyPlus simulation: CalcDaylightCoeffRefPoints: Daylighting calculation cannot be done for zone ZN 1ST FLOOR OTA 1- OO because reference point #1 is less than 0.15m (6") from window plane 1S000000_W3-W0

~~~ Distance=[3.96558E-002]. This is too close; check position of reference point.

This particular zone has a complicated shape but also has skylights. The skylights provide enough daylight to meet the Title 24 requirement. Is it possible to turn off the daylight calculation for sidelight in this zone and only do skylights?

Reported by: joesinger12

Original Ticket: cbecc-com/tickets/2567

joesinger12 commented 6 years ago

Original comment by: joesinger12

joesinger12 commented 6 years ago

12/7/17 NK - Which version of CBECC-Com are you using? And can you send us the project file and the error file

12/7/17 User - I am using CBECC-COM 2016.2.1. The file is attached. I actually solved the problem by deleting a few skylights from the geometry. It seems the skylights were moving the reference points too close to the windows. If I removed skylights that were close to the exterior walls, it solved the issue. This model is an SD model so it is not yet serving any compliance purposes. I am fairly confident that if I were to model the skylights true to the architectural model, the reference points would be problematic in quite a few zones. Any guidance for future compliance models would be helpful.

12/7/17 NK - The sensor location error is a bug for which we don’t have predefined resolution for. You would just need to test options such as breaking the window up/changing the VT and changing the location of the window(s)/skylights in that space or deleting a few, like what you have done below.

You can see the location of the sensor by right clicking on the space and select “View Building Story Footprint” to look at the sensor locations real time when you make changes to the model. That way you don’t have to rerun the model and you can start by deleting one window/skylight or changing their coordinates.

You may want to try the model which gave you an error in 2016.2.1 in the latest version CBECC-Com 2016.3.0, where we have attempted to resolve this issue. Let us know if it occurs in 2016.3.0.

Original comment by: joesinger12

joesinger12 commented 6 years ago

12/7/17 User - I did notice that footprint option and it was very helpful in identifying problematic skylights. There was an occasional case when the footprint did not render the zone completely.

I just ran the model in the new version and the reference point issue is still there. Luckily I have figured out how to solve the problem for now.

Original comment by: joesinger12

joesinger12 commented 6 years ago

12/7/17 NK - If you do not have daylighting /windows the footprint does not show up.

This sensor issue is a bit more complex since we get different geometries and configurations of spaces. We did a fix and tested on the models that originally came to us but it may not be working on all models - so it is good to know by you running this test.

I will flag this for the development team for inclusion in development issues. We will still require a model so if you can send us the 3.0 version that will be help the development team to test it out.

Original comment by: joesinger12

joesinger12 commented 6 years ago

12/11/17 User - Here is the 2.1 version that runs through the EnergyPlus simulation and ends on a fatal error concerning the reference point for the daylight zone.

This particular version of the model when imported in to 3.0, also triggers an issue with the shape of the skylights. I had seen the shape issue previously because EnergyPlus cannot do window calculations on non-rectangular shapes but somehow those windows that are now the problem in my CBECC-Com simulation had never triggered that fatal issue in EnergyPlus.

I went in a deleted the skylights that were problematic and solved the error already!

Original comment by: joesinger12

joesinger12 commented 6 years ago

Original comment by: joesinger12

joesinger12 commented 6 years ago

Original comment by: joesinger12

joesinger12 commented 5 years ago

Original comment by: joesinger12

joesinger12 commented 1 year ago

Original comment by: joesinger12