Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
In OpenStudio 1.4 we added an "Apply Measures Now" feature. You could use it to run a measure that reports information about surfaces much like the surface search does in the SketchUp plugin. You could create info or warning messages or you could export to text or csv file.
An alternate approach is to keep a copy of your model open in the SketchUp plugin just for reference. When you get an error in the app you can quickly check it in the plugin. Of course don't try to edit and save from the plugin if you are working in the app.
| | 2 | No.2 Revision |
In OpenStudio 1.4 we added an "Apply Measures Now" feature. You could use it to run a measure that reports information about surfaces much like the surface search does in the SketchUp plugin. You could create info or warning messages or you could export to text or csv file.
An alternate approach is to keep a copy of your model open in the SketchUp plugin just for reference. When you get an error in the app you can quickly check it in the plugin. Of course don't try to edit and save from the plugin if you are working in the app.
Updated - Just for anyone interested, here is an example section of code that would look for sub surfaces without constructions. This would go in the run section of a measure. As is, it just reports, and doesn't change the model, but you could extend this to assign constructions. You can also ask if a construction is hard assigned to a surface, or inherits it from its parent space, or from the building, etc.
sub_surfaces = model.getSubSurfaces
sub_surfaces.sort.each do |sub_surface|
if not sub_surface.construction.is_initialized
runner.registerWarning("#{sub_surface.name} doesn't have a construction.")
else
const_name = sub_surface.construction.get.name
runner.registerInfo("Everything is fine with #{sub_surface.name}. It uses #{const_name}.")
end
end
| | 3 | No.3 Revision |
In OpenStudio 1.4 we added an "Apply Measures Now" feature. You could use it to run a measure that reports information about surfaces much like the surface search does in the SketchUp plugin. You could create info or warning messages or you could export to text or csv file.
An alternate approach is to keep a copy of your model open in the SketchUp plugin just for reference. When you get an error in the app you can quickly check it in the plugin. Of course don't try to edit and save from the plugin if you are working in the app.
Updated - Just for anyone interested, here is an example section of code that would look for sub surfaces without constructions. This would go in the run section of a measure. As is, it just reports, and doesn't change the model, but you could extend this to assign constructions. You can also ask if a construction is hard assigned to a surface, or inherits it the construction from its parent space, or from the building, etc.
sub_surfaces = model.getSubSurfaces
sub_surfaces.sort.each do |sub_surface|
if not sub_surface.construction.is_initialized
runner.registerWarning("#{sub_surface.name} doesn't have a construction.")
else
const_name = sub_surface.construction.get.name
runner.registerInfo("Everything is fine with #{sub_surface.name}. It uses #{const_name}.")
end
end
