Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
If you're not interested in using any of the other elements of OpenStudio ("I can do the image generation by myself on Radiance"), I suggest you use a different tool altogether to export the geometry to Radiance format. The OpenStudio plugin does not "do" complex geometry too well and if you have the ability to work with the raw Radiance files, either use the OpenStudio "Radiance Forward Translator" directly (it's accessible through the API) or use something like Thomas Bleicher's SU2Rad (note: a quick search for SU2Rad came up with some old links, not sure the status of that project).
If you wanted to just export the OSM (it seems you have at least gotten the geometry to import to the plugin) to Radiance, you could make a little script to call the OS-Radiance forward translator, and then work with the output from there. This is straight from the Radiance daylighting measure that is used in OpenStudio most often, this is the bit that takes the osm in memory and dumps it all out to Radiance format:
ft = OpenStudio::Radiance::RadianceForwardTranslator.new
radPath = OpenStudio::Path.new('radiance')
radPath = OpenStudio::system_complete(radPath)
ft.translateModel(radPath, model)
If you wrapped this code with the usual stuff to load OpenStudio and load a model, this would (very quickly) dump out a bunch of geometry (and stuff you may or may not want, like materials and points files). The OSM does need to have zones defined, but nothing else daylighting related needs to be there if all you are going to do us use the geometry with your own workflow and scripts.
