Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
I cannot do Radiance simulation, it starts, takes a lot of time and then says "annual simulation failed" although I asked for one day simulation only :( I have played with rotation all ways. Actually, I mentioned this when I analyzed a script-generated building and it looked correct all the time but illuminance was strange, so I created this primitive model. I know, that the map is oriented along zone's coordinates (btw, why there is a rotation angle parameter in OS?). It is very confusing when we have a curved facade and cannot model daylight just along it. In E+ we can create a map bigger than the zone to cover its shape. The results for points outside the zone are marked by * in the table, so we can filter them and exclude from visualization. Why we see them in Results viewer in OS? How can we edit the sql file to exclude those points?
| | 2 | No.2 Revision |
I cannot do Radiance simulation, it starts, takes a lot of time and then says "annual simulation failed" although I asked for one day simulation only :(
:(
How to run Radiance in OpenStudio see here. I believe, it should be recorded as an issue, because we do scan for tools, but responsible variable in the Ruby file are not substituted.
The second issue is the disk space. SQL from Radiance takes A LOT of space on your C drive in the /users/username/AppData/Local/Temp/Openstudio*/ results folder. Be sure you have apr 5-10 Gb for each map in a real model. The temporal solution could be reassigning the path to the results folder on another drive with enough space. Is it possible?
I have played with rotation all ways. Actually, I mentioned this when I analyzed a script-generated building and it looked correct all the time but illuminance was strange, so I created this primitive model. I know, that the map is oriented along zone's coordinates (btw, why there is a rotation angle parameter in OS?). It is very confusing when we have a curved facade and cannot model daylight just along it. In E+ we can create a map bigger than the zone to cover its shape. The results for points outside the zone are marked by * in the table, so we can filter them and exclude from visualization. Why we see them in Results viewer in OS? How can we edit the sql file to exclude those points?
