Possible Bug - New Honeybee Run Daylight Simulation Module - 03.16.15

old forum
1

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.

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

Thank you,

Reinhardt

2

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

3

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

4

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

5

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.

6

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

7

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.

8

Thanks for the heads up!

Reinhardt