-
Notifications
You must be signed in to change notification settings - Fork 25
Description
Problem: Right now the libraries such as the HVAC one are .osm files. It would be great to have the library being openstudio measures instead.
Rationale: This would allow much greater flexibility, including adding your own components (right now the “safe way” to modify the hvac_library.osm is to do it through a measure anyways…), and would allow for a large base of easily reusable code (or snippets) in measures.
Solution: Replace the libraries (especially hvac_library.osm) with a set of measures.
Context: I’m going to use simple PV as an example because it’s a very simple case where you only need to define a surface to receive the PV, you don’t have to find the adequate node to drop a component or anything. Let’s also assume that the simple PV object is actually available in the GUI.
An example of why this is annoying is that I may just want to add simple PV to my model in a parametric run. In which case I’ll have to write an entire measure for that, asking for the same user arguments I’d see in the GUI, picking them up in the run methods, and in turn just calling everything single “setXXX” method to set the values. It’s tedious and boring.
Pros and Cons of Solution:
- Flexibility
- Customization
- Reusable snippets/code encouraging new users to write measures (and share them on BCL for everyone to enjoy)
- Requires some work to switch
Migrated from UserVoice