Possible Bug - New Honeybee Run Daylight Simulation Module - 03.16.15

Hello,

I recently updated the Honeybee and Ladybug modules for Github. In running the 'Honeybee_Run DaylightSimulation' module I encountered a problem. It runs fine when using grid-based analysis recipes. When using an annual based recipe (DAYSIM) run, I receive an error:

This module had worked previously before the most recent update.

I tried using a simple plane as the geometry, as well as a simple name to ensure it wasn't anything to do with the naming of the file or objects. Again, I tried the grid-based run, and it worked.
The annual did not - this leads me to believe I can isolate the issue to that input (the analysis recipe, rad parameters, DS parameters, module itself, etc.).
I have update all modules from Github as of 06.22.15
The same RAD parameters module feeds into the grid-based or annual-based analysis recipes.

Perhaps there is a bug with one of the updated modules? Please let me know your thoughts.

Thank you,

Reinhardt

Replies are closed for this discussion.

Replies to This Discussion

Permalink Reply by Chris Mackey on June 30, 2015 at 6:39pm

Reinhardt,

It seems that the error is probably linked to the number of CPUs that you are inputting into the run daylight simulation component as this seems to be the line where things are failing:

I fixed a bug in the cpu count a while ago:

(https://github.com/mostaphaRoudsari/Honeybee/commit/32582b2d2686d29...)

This may have triggered another bug that you have discovered here. Could you upload your GH file complete with the number of cpus that you are using? Could you also let us know the number of logical processors on your machine.

Thanks for finding this,

-Chris

Permalink Reply by Reinhardt Swart on July 1, 2015 at 7:14am

Chris,

Thanks for the prompt reply. I looked into the the CPU count. I am running 8 CPUs which hasn't been a problem in the past. However, I am also testing only 1 test point (for a quick turnaround). When this happens, the annual simulation does not work. When I changed the grid count to be greater than 8, the annual simulation ran.

It appears it does have something to do with exactly what you stated above. Let me know if that helps.

Thank you,

Reinhardt

Permalink Reply by Chris Mackey on July 1, 2015 at 2:06pm

Reinhardt,

All of this definitely helps. If you could upload your GH file so that I don't have to re-create the case of failure myself, I can fix the issue more quickly.

-Chris

Permalink Reply by Mostapha Sadeghipour Roudsari on July 6, 2015 at 6:25pm

Hi Reinhardt, I could replicate the error and Chris is right about the cause. I just got it fixed (https://github.com/mostaphaRoudsari/Honeybee/commit/422bcba96fe3ac1...). Thanks for reporting.

Permalink Reply by Reinhardt Swart on July 7, 2015 at 2:29pm

No problem, I am glad I could help. Thank you, Mostapha.

Chris, my apologies for such a delayed response. It seems all is well. Thanks again for your help!

Reinhardt

Permalink Reply by Mostapha Sadeghipour Roudsari on July 7, 2015 at 4:45pm

You may need to update the component once again. While fixing the component for your case I made a small mistake that will make the component crash for image-based analysis. It should be all fine right now.

Permalink Reply by Reinhardt Swart on July 8, 2015 at 6:50am

Thanks for the heads up!

Reinhardt

RSS