queenBee multithreading, number of tasks

[pmcmm]

Hi guys,

I just wrote the following post in another topic:

Annual daylight 1.3 example error

Hi Chris, I see that now radiance appears to be dividing the total number of points by the selected number of workers again, instead of creating multiple smaller calculation grids with a default of sensor count of 200, which was the standard new approach since ladybug tools were revamped. I loved that approach, as it greatly increased the simulation speed, so I’m sad to see it gone. Any reason why the sensor count optional parameter has been removed in 1.3.1?

but I find this discussion important and very related.

@Mathiassn I think your conclusion above is holds true when you are running low accuracy calculations (ab 2). If you were to increase the ab’s to 6, I think your results would be very different, as your simulation would be dominated by the most complex piece of the calculation, which would take way more time.

I’ve done the exact same test as you, and ended up with very different results. For my example, the sensor_count of 200 reduced the speed by 50%. See here for more info:

HB[+] & Accelerad vs Honeybee[+] vs Honeybee

It turns out you were right Nathaniel. HB1.1 is dividing the simulation per grid. I rerun the simulation as a whole and here is the final result, with a total run time of 2 min! With that out of the way, the question now is: how we can group all the grids for the simulations and ungroup them at the end for data processing of individual rooms? [image]

Unfortunately, I’m unable to reproduce those tests as the sensor_count is gone, and that leads me to my question: why is that?