Apologizes if I missed this in the documentation or on discourse, I’m curious how OS measures are run within a pollination recipe.
Are measures being run with OpenStudio server or is it just an environment which executes a OpenStudio workflow (OSW), is there any information or Github repo which you can point me to about this environment? I’m looking to learn as much as possible about it.
Also how many workflows can this environment run simultaneously?
It is the latter. We don’t use OpenStudio server. Is it something that is required for your workflows?
The best place for you to learn about how measures are executed is to check the annual-energy-use recipe and in particular the simulate model step which uses this function. You can see the command there which is a honeybee-energy command which you should be able to find on GitHub.
Back to how we execute the commands. They are being executed inside a docker image. In this case honeybee-energy:
We have to make some adjustments to support this since currently the image that runs OpenStudio doesn’t have Radiance as a dependency. Is it the default OpenStudio measure? I personally think there are better ways than using the Radiance measure on Pollination to run your daylight studies in scale.
I’ll share our current pricing with you via a message.
You can run those 300 runs on Pollination right now with no issues.
That will be a very long answer but here are the most important ones:
OpenStudio sever has been implemented for a very particular purpose. Pollination is designed to support OpenStudio among other simulation engines.
The older version was not using the most recent technologies. It’s good to see that they are moving to K8s.
In the Pollination world, Radiance is a first class citizen which is not the case in the OpenStudio world. We have several specific Radiance workflows which would have been really hard to implement with the OpenStudio server.
You may want to watch this presentation about the big picture decisions behind building Pollination and why it is built this way:
We are also introducing Pollination apps which will make building UIs on top of the Pollination API easy and straightforward. Are you still using floorspace.js for building the input model? We might be able to integrate this directly into Pollination Apps by building a Streamlit component for floorspace.js.