Has this limitation been removed in newer versions of Pollination? If not, when will multiple runs be available to run locally? Is there a work around for this in the meantime? Debating if we would be better off using Colibri in the meantime.
This was not under my radar. Technically, it will be possible to support this feature but we have to make a few changes to how the executor runs the simulations locally and how we report the progress. If it is an important feature for you, we can make it a priority.
Meanwhile, the easiest workaround is to use Colibri or fly to feed them to the Pollinate component one at a time. Make sure to change all the downstream components to be blocking. Otherwise, it will start the next run before finishing the previous one.
We were thinking of shifting from Pollinate to Colibri, thank you for the confirmation.
Internally to our firm, we have a few powerful computers with over 40 CPU cores. I was hoping to find a workflow where we could run many studies simultaneously, similar to cloud computing. I’m not sure I would classify it as a high priority but it would be great to have!
Thank you for clarifying that! I was thinking of Colibri with Honeybee-Radiance and Honeybee-Energy. But hadn’t considered the workflow with Colibri + Pollinate.
We’re trying to run a coupled daylight and energy simulation. I’ll have to try if I can the load asset from the daylight recipe Pollination run into an electric lighting schedule for the energy simulation. Unless there is a better workflow?
I don’t think we have an automated workflow for that right now. I know that we have a component that can be used to create the lighting control schedules.
We can automate the workflow to put both of these in a single recipe but in that workflow, we should generate the sensor grids in a certain way to be able to map the lighting schedule per room. Otherwise, it can get tricky.
For what it’s worth, I agree. I would like to be able to run a parametric study on a local machine.
In your example video from a few years ago, the small room model took 1.5 minutes (x6 iterations), so any study of size with hundreds of iterations will easily use up the allotted free cloud hours.
Maybe this is a non-issue for subscribers, but limits free users a bit.