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

Revision history [back]

The reason this failsafe was put in is that it's very easy to fill an entire building with calculation points, and in many cases, the Radiance Measure as written will generate too much data to be reasonably handled, even on a "more powerful computer". Stress testing this measure way back when we found we could easily blow up even the most robust VMs available on Amazon's EC2 service. Coupled with the energy modeling industry expectation of running thousands of models or more, we chose to hamstring the measure in this way.

If you want to disable this, you could make a copy of the measure, and modify the block starting at line 770. Either increase the allowable number of points (and be ready to wait!), or remove all the conditionals and let L776 stand alone.

Also, consider filing a concern about this on the OpenStudio UserVoice forum...

The reason this failsafe was put in is that it's very easy to fill an entire building with calculation points, and in many cases, the Radiance Measure as written will generate too much data to be reasonably handled, even on a "more powerful computer". Stress testing this measure way back when we found we could easily blow up even the most robust VMs available on Amazon's EC2 service. Coupled with the energy modeling industry expectation of running thousands of models or more, we chose to hamstring the measure in this way.

If you want to disable this, you could make a copy of the measure, and modify the block starting with this line:

if 1000 < rfluxmtxDim.to_i && rfluxmtxDim.to_i < 2999

In the current version of the measure on the bcl, this block begins at line 770. Either increase the allowable number of points for the warning and the fail (and be ready to wait!), or remove all the conditionals and let L776 stand alone.

Also, consider filing a concern about this on the OpenStudio UserVoice forum...