mattkoch's profile - activity

... not enough space in comment, see sort-of-answer below ...

FWIW, I have had good success with the following, after "import openstudio" and creating or loading a model. # Make su

I just upgraded from openstudio-3.6.0 SDK to opnstudio-3.7.0 SDK in Python. The following simple test used to work in 3.6.0:

import openstudio
model = openstudio.model.Model()
path = openstudio.path("./ModelTest.osm")
model.save(path)

However, in 3.7.0, I receive the following error:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "D:\Python-3.10.11\lib\site-packages\openstudio\openstudioutilitiesidf.py", line 1997, in save
    return _openstudioutilitiesidf.Workspace_save(self, p, overwrite)
TypeError: Wrong number or type of arguments for overloaded function 'Workspace_save'.
  Possible C/C++ prototypes are:
    openstudio::Workspace::save(openstudio::path const &,bool)
    openstudio::Workspace::save(openstudio::path const &)

Interestingly, the following does seem to work instead, namely using a simple Python String instead of an OpenStudio Path:

import openstudio
model = openstudio.model.Model()
path = "./ModelTest.osm"
model.save(path)

Is there some type incompatibility going on? A "pip freeze" does confirm that I am using openstudio-3.7.0 in my Python-3.10.11.

No problem, Julien Marrec. If you are the driving force behind the Python port of openstudio, then the world owes you a

Why does model.save(path) fail with path an openstudio.path()? I just upgraded from openstudio-3.6.0 SDK to opnstudio-3.

Why does model.save(path) fail with path an openstudio.path()? I just upgraded from openstudio-3.6.0 SDK to opnstudio-3.

I was hoping to implement MeasureStep in a Python script. Much like "model = openstudio.model.Model()" or "space = openstudio.model.Space(model)", or "vector = openstudio.Vector3d(1.0,2.0,3.0)," I expected MeasureStep to be accessible as "measure_step = openstudio.MeasureStep(measure_directory)" after an "import openstudio" in my "test.py" file. Alas, I am being told by the Python interpreter there is none such. And "measure_step = openstudio.utilities.MeasureStep()" or "measure_step = openstudio.workflowJSON.MeasureStep()" or similar variations do not lead to success either. Has MeasureStep not been implemented yet in the openstudio SDK Python module? Or if it was, where can it be found? On a side note, is there an openstudio-standards for Python yet? Thanks.

Confirmed, openstudio-3.7.0 works in Windows as well: Python 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:38:17) [MS

I am running openstudio-3.6.0, below is the python output. >>> import openstudio >>> test=openstudio.

Where is MeasureStep in Python version of OpenStudio SDK? I was hoping to implement MeasureStep in a Python script. Much

OK, so I am a bit confused about "create baseline" measures. There is one I can find under Whole Building/Space Types and it is called "Create Baseline Building" I know how to invoke this (Apply Measure Now), but unfortunately it goes no further than ASHRAE 90.1-2013.

Then there seems to be a "Create Performance Rating Method Baseline Building" method in the openstudio-standard GEM, which might (or not?) go to ASHRAE 90.1-2016, but which I do not know how to invoke (do I have to call this from within a custom measure?). Has anyone successfully used any (which?) measure along these lines to create an ASHRAE 90-1-2016 Appendix G Performance Rating Baseline?

I know there is also a "Space Type and Construction Set Wizard" measure, and it does go to ASHRAE 90.1-2016, but as the name says, it ends at Space Types and Constructions, i.e. does not include Lighting or HVAC.

Any enlightenment would be much appreciated!

Eric Ringold hit the nail on the head. Adding a thermal zone did indeed solve this problem. Thank you! And Denis Bourgeo

Eric Ringold hit the nail on the head. Adding a thermal zone did indeed solve this problem. Thank you! And Denis Bourgeo

... see Additional Update in original post above.

Swimming Pool in OpenStudio I tried to implement a swimming pool following this post on Unmet Hours. If I just create th

OK, this is rather curious. I just used a batch file (oneliner.bat) file with following content: D:\OpenStudio-3.4.0\bi

Swimming Pool in OpenStudio I tried to implement a swimming pool following this post on Unmet Hours. If I just create th

Swimming Pool in OpenStudio I tried to implement a swimming pool following this post on Unmet Hours. If I just create th

This is getting to be pretty long so I want to close this off by stating that macumber had suggested intersection does n

This is getting to be pretty long so I want to close this off by stating that macumber had suggested intersection does n

Just to close the loop, I did this with Trace, Info, Debug, Warn, Error and Fatal now - some result in no messages at al

I was also looking for 2.9.X-LTS, following your links above. computeIntersection in Surface.cpp and intersectSurfaces i

OpenStudio 3.4.0 Python subsurface intersect/match I am working on a geometry modeler for OpenStudio. I am doing this in

all three versions are treated identically in my FreeCAD to OpenStudio conversion, and all run to "completion" without e

Thank you Julian Marrec. Last thing first, I agree 100% with your caution, and I am only using the 2.9.1 hack so I can k

Interesting, thanks to your link I was able to convert the Ruby into a Python and get some info out of it, sort of. Now,

Also, one other reason I am hoping to make progress with FreeCAD is to reduce some of the labor, such as having to gener

Thank you macumber. it seems that intersectSurfaces calls computeIntersection, and that has the following parts: if (!t

OpenStudio 3.4.0 Python subsurface intersect/match I am working on a geometry modeler for OpenStudio. I am doing this in

I am dabbling with using the FreeCAD BIM Workbench to generate geometry for the .OSM file. FreeCAD is very powerful and has built-in Python capability. At this point, I can generate some simple spaces. However, I'd like to check adjacent surfaces and am running into a problem transferring the boost::optional approach from Ruby to Python. In Ruby, I would do the following (more or less, I am not in Ruby right now):

model.getSurfaces().each do |surface|
  adjacent_surface = surface.adjacentSurface()
  unless adjacent_surface.empty? then
    puts surface.name
    puts adjacent_surface.get.name
  end
end

With this, I would obtain just the names (simple strings) of surface and adjacent_surface, as desired.

In Python, I am trying the following:

for surface in model.getSurfaces():
  adjacent_surface = surface.adjacentSurface()
  if adjacent_surface is not None:
    print(surface.name)
    print(adjacent_surface.get.name)

But the "get.name" part in the last line results in this error: AttributeError: 'function' object has no attribute 'name'. And if I use just "get", the following is an example output:

<bound method IdfObject.name of <openstudio.openstudiomodelgeometry.Surface; proxy of <Swig Object of type 'std::vector< openstudio::model::Surface >::value_type *' at 0x7fea7ab0f870> >>

<bound method OptionalSurface.get of <openstudio.openstudiomodelgeometry.OptionalSurface; proxy of <Swig Object of type 'openstudio::model::OptionalSurface *' at 0x7fea66d46630> >>

That is to say, not even non-boost::optional surface shows the name. Both it and boost::optional adjacent_surface just show what appears to be a type or class specification. How can I get the simple name strings here?

OK, so it was late last night and I was tired. A little more digging this morning led me to try the following: for surf

Actually, using surface.name() rather than surface.name at least gets me surface name. However, using adjacent_surface.g

openstudio python bindings I am dabbling with using the FreeCAD BIM Workbench to generate geometry for the .OSM file. Fr

Ah, I think I see. As of 90.1-2016, the baseline building will always be the same, and instead the Building Performance

You should be able to locate files "eplusout.rdd" and "eplusout.mdd" somewhere in the run folder for your IDF file. In

OK, so I simply did the following, which does seem to run to completion, albeit with fairly low energy usage. standard

Has anyone had any luck in using the Create Baseline Building measure? I am trying to run it on a random (proposed) building and am receiving hundreds of Warnings about all kinds of things not being found, though the measure does run to completion. Most warnings are of the following type:

Warning: Space type properties lookup failed: {"template"=>"90.1-2013","building_type"=>nil,"space_type"=>nil}

I am (randomly) selecting a SmallOffice in climate zone 2A when the measure first starts up, just to select something. When the measure is done, new AirLoopHVACs have appeared, and some Schedules have been added, but constructions and loads appear to be untouched?

I suspect the proposed building has to be set up in a particular way for this measure to work properly? I was trying to find openstudio-standards documentation to find out what that set-up might need to be, but no luck thus far.

Happy to report that I was able to make it run now, adjusting all those measure tags, not just in Space Types, but also