On 10/30/11 12:09 PM, "Lars O. Grobe" <[email protected]> wrote:
> >... However, in Radiance, we have no database concept. Maybe >this would be something to think about - a database interface. Than we >could access unique objetc and modifier id's, could connect to e.g. >library databases, prevent some locking problems... but - do we really >need it, and does it match the requirements of what is basically a >raytracing code??? While not necessary for the raytracing work, it becomes very important in the context of a broader simulation workflow where you're trying to integrate Radiance in/output with other tools, such as EnergyPlus or whatever. And, in a massively parallel simulation stream, for optimizations and the like, accountability is critical. You need to be able to go back and have a reliable account of what was simulated. OpenStudio has a RunManager application that manages packing up models into "jobs", that can be parceled out to a cluster and all the results are merged back to the OpenStudio project. We're just now integrating Radiance with the RunManager application, but we hope that it will be very useful for large parameter spaces. - Rob _______________________________________________ Radiance-dev mailing list [email protected] http://www.radiance-online.org/mailman/listinfo/radiance-dev
