OpenStudio

Welcome! Please add your suggestion below or vote on other ideas for improving OpenStudio following the posted guidelines.

This website is exclusively for ideas and suggestions for OpenStudio.

This site is NOT intended for:

To link a suggestion to an existing Unmet Hours question or GitHub issue, simply copy and paste the URL into the suggestion.

How can we improve OpenStudio?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Create Measures for 90.1 Appendix G System Types

    Problem: TBD

    Solution: Create measures for 90.1 appendix G system types

    Context: ported from GitHub: https://github.com/NREL/OpenStudio/issues/1432

    11 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  0 comments  ·  Measures  ·  Admin →
  2. Graphical representation of node/equipment variables on a schematic of the plant loop

    Problem:
    ---------
    Checking the behavior of a plant or air loop is currently limited to plotting graphs of the chosen Node variables (temperature, flow rate, setpoints, etc). This mode of representation, while useful, makes it hard to analyze considering you have to mentally replace it physically in the plant loop (which node is where, etc).
    Having a way of representing it on a schematic of the plant loop would help a lot. To my knowledge this has never been implemented in another GUI yet, and yet I feel it'd be an amazing feature to have.

    Rationale:
    -----------
    For troubleshooting or…

    9 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Measures  ·  Admin →
  3. Openstudio measure: dynamically change an argument field

    Problem: The GUI window asking for arguments is static. It would be nice to have the capacity to change it as users select a given response to a previous question.

    Rationale: I've touched on one example here, which is to set the default of some fields based on the systems they picked: https://unmethours.com/question/10831/openstudio-measure-dynamically-change-an-argument-field/
    Another one would be to be able to gray out, or to add/remove fields, depending on another question

    Potential solution: add an event watcher (OnChange) that reloads the GUI window (keeping the variable values in storage) so that you could change the apparence of the GUI window.…

    9 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Measures  ·  Admin →
  4. Make airLoopHVAC.clone work

    AirLoopHVAC has a `clone` method, but it does not clone components, and can also cause segmentation fault errors when you try to, e.g. addBranchForZone to a "cloned" air loop. T

    A fully-featured system clone would be really helpful for system libraries.

    https://github.com/NREL/OpenStudio/blob/develop/openstudiocore/src/model/AirLoopHVAC.cpp#L575

    8 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Measures  ·  Admin →
  5. Run Reporting Measures in Apply Measure Now

    Problem: Users currently have to re-run a model to apply reporting measures.

    Solution: Allow running of reporting measures after a simulation via "Apply Measures Now"

    Context: ported from GitHub: https://github.com/NREL/OpenStudio/issues/1480

    7 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  0 comments  ·  Measures  ·  Admin →
  6. Allow gem use in CLI

    Allow use of gems in CLI and OS Server. Should be able to specify a gemfile or something to control which gems are used for a given workflow, maybe allow measures to specify their own gems and then bundle at the OSW level.

    5 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Measures  ·  Admin →
  7. Sort measures alphabetically in GUI

    Problem: Users cannot find measures quickly/easily

    Solution: Sort measures alphabetically in "Find Measures" dialog as well as in the Library itself

    Context: ported from GitHub: https://github.com/NREL/OpenStudio/issues/1613

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  0 comments  ·  Measures  ·  Admin →
  8. Add method for creating non-ribbon windows

    Problem: Users cannot (auto) create windows in the manner they would like; especially considering shading structures.

    Solution: Add method with more capabilities during automated window creation

    Context: ported from GitHub: https://github.com/NREL/OpenStudio/issues/1729

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  0 comments  ·  Measures  ·  Admin →
  9. Implement measure testing framework

    Problem: Some measures submitted contain bugs.

    Solution: Something built into the BCL that runs when users submit measures.

    ported from GitHub: https://github.com/NREL/OpenStudio/issues/1391

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    in discussion  ·  0 comments  ·  Measures  ·  Admin →
  • Don't see your idea?

Sign in to suggest ideas, vote, or participate in polls for your favorite feature request!

Feedback and Knowledge Base