openstudiocoalition / openstudioapplication Goto Github PK

When you have more than 12 rules in a schedule rules "Priority 13" and higher take on the color of the default profile. Ok, so this is a corner case, but maybe we can loop through the same colors we just used for first 12 rules. If not, then I'd prefer to stop one color earlier, so at least I could see if a day used the default profile or not. I hit this in the past, but couldn't find issue for it.

My use case here was creating a kiln schedule that fires 10 times a year from Friday afternoon into Saturday morning (about once a month except over the summer).

For another model where it ran once a week except for summer I was able to just use two rules.

Possibly related to NREL/OpenStudio#1749, NREL/OpenStudio#1747

Setting a SetpointManager:Scheduled control variable to 'HumidityRatio' (or 'MassFlowRate', or any controlVariable other than temperature) and leaving the default Schedule Name (referencing a schedule of type: Temperature) is allowed and the model will save. Attempting to run this model will cause an error at ModelToIdf, but with no error or output message (/resources/run/1-ModelToIdf-0 is empty).

The only notification that this is wrong will occur upon re-opening the model, which will fail due to draft strictness with the following error:

The collection is INVALID at strictness level 'Draft', because of the errors:
Object     level data error of type DataType          .
Error pertains to an object of type 'OS:Schedule:Ruleset', named 'Deck Temperature'.
Additional information about the error type: field-level data is of an incorrect type.
Field      level data error of type DataType          .
Error is in an object of type 'OS:SetpointManager:Scheduled', named 'Scheduled Deck Temp', in         field 3.
Additional information about the error type: field-level data is of an incorrect type.

Recommended solution: only allow schedule name choice for correct schedule type, e.g. 'Dimensionless' for humidity-related control, 'Mass Flow Rate' for mass flow control. Alternatively, provide error message at ModelToIdf failure.

Note: control variable set to 'HumidityRatio' will not allow changing the Schedule Name to another schedule of type: Temperature, but does allows the choice to remain a Temperature schedule if previously set when controlVariable = Temperature.
Found in OpenStudio v.1.8.0, Windows 64bit

1.9.0 Space tab: do not see inherited properties NREL/OpenStudio#1893
NREL/OpenStudio#1893

Inherited Default Construction and Schedule Sets Not Displayed in Facility Tab NREL/OpenStudio#1460
NREL/OpenStudio#1460

You can see all schedule but it will only accept as a selection schedules of the correct type. It should only show you schedules that you can apply.

Filed by @jmarrec

I hit this in 2.2.0 (but went back and confirmed same behavior with 2.1.2) on mac OS 10.11.6. At first it looks like it is very quick, but then when you try to scroll a beach ball comes up. At first may refresh in 0.5 seconds, but didn't take too many cycles to get to 5 to 20 seconds for beach ball to go away. Then for some reason one time might be really quick again, then gets slower. Maybe render of previous views of a report are being saved in memory somewhere?

In y test I was going back and forth between OpenStudio Results and EnergyPlus results, cross referencing data.

I talked with @evanweaver about this. We know this will just be known issue for now, it is a complicated fix, the preferred solution maybe keeping the header row always visible so scrolling isn't necessary. We should note this in release notes so people know how to get around it.

Issue: If select an object (hilighted in yellow as copy object for "Apply to Selected" and then use the scroll bar to go up to the top (if header row is off the screen) you lose the selection. I also had the same issue using the mouse scroll wheel. The work around for me on windows was to use the "up/down" arrow keys. That allowed me to get back to the top without losing my selection.

Currently it accepts any kind of surface or sub-surface.

The "toolbar" at the top of the HVAC tab has some obnoxious and downright confusion behavior as you switch between VRF, Refrigeration, Service Hot Water, and HVAC systems. Review and fix as appropriate.

System info:

• Sketchup 2016
• macOS Sierra 10.12.2
• OpenStudio 2.0.0 (47ba3cbe19)

There seem to be a small bug that you might have noticed too with Measures on mac (aside from not telling you it’s broken and not giving you any message that can help), where you delete a measure and re-add it from library

1. It doesn’t ask anything (no "Update all previous reference to measure?" or something)
2. You end up with a new folder named “Measure blablabla 1", as you redo that it can get quite huge

In model/measures:

Allow selection of VRF Condenser node, by choosing from available zone nodes / zones.

https://openstudio.uservoice.com/forums/308629-openstudio/suggestions/9099592-allow-rearranging-material-layers-in-construction

Problem: Currently there's not a quick way to rearrange ZoneHVAC equipment in the Thermal Zones tab without a measure. In order to switch the order of equipment the user must delete ZoneHVAC objects losing any user-specified inputs.

Rationale: Heating and cooling priority is set by the order of the ZoneHVAC objects assigned to a zone in the GUI. Not all users are aware of this and it can significantly affect model results.

Solution: Explicitly show the user heating and cooling priority. Add a Grid View feature to increase or decrease selected equipment priority.

Context: ZoneHVAC:EquipmentList

Right now, the forward translator gets the Minimum Outside Air Schedule from OS:Controller:OutdoorAir. When the Controller:OutdoorAir is setting the outside air flow rate the Minimum Outside Air Schedule can be used to scale the minimum outside air with a decimal multiplier. This is incredibly useful for changing unoccupied/occupied OA operation. In an ideal would there would be 0% OA during unoccupied hours, but due to leaky dampers, it's not unrealistic to see maybe ~3% OA when the dampers are commanded to 0%. To model this I would create a Minimum Outside Air Schedule that would have some fractional value during unoccupied hours and 1 during occupied hours.

Now the Availability Schedule for Controller:MechanicalVentilation determines its' operation from values that are 0, disabling it, or values that are > 0, enabling it. When the controller is enabled the Minimum Outside Air Schedule assigned to the Controller:OutsideAir will not be taken into account, as was commented. The fact that the same schedule is used in both places, means that you can't scale the minimum outside air with the schedule assigned to Minimum Outside Air Schedule. This schedule can only be used to either allow the Controller:MechanicalVentilation to control the outside air flow rate (when the schedule value is 1) or set the outside air flow rate to 0 (when the schedule value is 0).

I see a couple of different solutions...

1. Create an additional dialog to allow the user to specify the availability schedule for Controller:MechanicalVentilation
2. Create a new schedule to use for the Availability Schedule of Controller:MechanicalVentilation that has 0 for all times when the Minimum Outside Air Schedule is >0 and 1 when the Minimum Outside Air Schedule is 1.
3. Only create Controller:MechanicalVentilation when DCV is used or something other than ZoneSum is desired. The only consequence here is that the outside air schedule attached to the DesignSpecification:OutdoorAir won't be factored in.

There is an OS object field for Controller:MechanicalVentilation Availability Schedule and there is a setter in the API for it. The broader issue here is that unless you know the above, the user won't have their Minimum Outside Air Schedule realized if they are using something other than 0s or 1s in the assigned schedule.

Hopefully that all makes sense...

If user has already run their model, allowing them to run reporting measures in apply measures now without having to re-run the model would be helpful. This would be especially useful for the 3D viewer reporting measures.

From Andrew's testing:

Selection:

1. When you scroll up or down in the grid view, you lose the yellow selected cell. This makes it impossible to click "Apply to Selected" from a row you have to scroll down to get to.
2. When you click an object in the grid, the cell turns yellow and that object opens in the inspector. Then when you then click inside the inspector to edit that object, you lose the yellow selected cell in the grid. This matters when you are trying to go through the grid and edit each object one at a time, because you can lose your place.

Button activation:
3. "Apply to Selected" button activates even when no rows are selected. (Talk with Marj about whether this should be changed or not, I’m not convinced myself.)

Backend support has been added, but we need to add columns in the case table view for per door properties.

Possibly related to NREL/OpenStudio#1587

In OpenStudio v1.8.4 (Windows 64-bit) the Space tab grid view exhibits a strange column size shift after 100 spaces:

This occurs (to varying degree) on all sub-tabs:

@evanweaver, @macumber

In the OS app you see this when you go first select the measure. It doesn't show anything is happening while the search is going on. You still see "Select Measure to Apply" after choosing one, until search is done.

When adding measure to workflow, the delay occurs when you first take the measure and drop it on the dropzone. It doesn't look like it took. Then when it does show up the arguments are immediately available.

I can demo this at next iteration meeting.

cc: @macumber @evanweaver @asparke2

Would work when file was on mapped drive, did not work when saved to //nrel.gov/shared/5500/5500 HPBldg/DansFiles/Untitled.osm

https://docs.google.com/document/d/1QmcpED4BGvdzA2TD_yszF2XbxV8DuMypOf7ISrfgOTQ/

Given a model with ventilation and infiltration assigned at the space type level.

On the Space Types Tab

• Under "General" view you can see both types of loads.
• Infiltration can be seen and edited, and deleted from the "Loads" view, but you can't add new ones from this view.

On the Space type

• Under "Properties/Airflow" you can see inherited ventilation but not inherited infiltration
• Under "Loads" you can see inherited infiltration but not inherited ventilation.

When scrolling grid view if headers do not stay fixed it is very difficult to tell what each column is

You have to go to the tree, right click the job and do show errors and warnings. Seems like these should get printed to the screen as well

https://openstudio.uservoice.com/forums/308629-openstudio/suggestions/9313437-curve-editing-in-openstudio

Problem: There's no easy or user friendly way to edit or add new curves

Rationale: It would be nice to be able to edit the curve coefficients/add new curves for say a chiller directly in OpenStudio. I've found that creating them manually in notepad++ is unstable at best and not user friendly.

Solution: Implement a new pane where one can add a curve or edit one when you click on a given curve attached to a specific HAVC equipment

Allow users to choose which design days (0.4%, 1%, 2%) are imported, as detailed in this unmet hours post:

https://unmethours.com/question/13050/how-to-modifying-design-day-conditions-as-per-ashrae-901-g1221/

Migrated from UserVoice

OS App 1.11, tested in Windows 7 and 10 x64.

Ideally the edit pane size should stay static where the user sets it within each tab. Resizing the pane when cycling through project measures or subtabs is bad for workflow.

Needs mockups

No way to access daylighting objects in app

https://openstudio.uservoice.com/forums/308629-openstudio/suggestions/10473030-organize-hvac-library-by-category

Since 1.9.0, the quantity of available library objects when viewing the "HVAC System" makes it really hard to find an object. It'd be great to categorize the objects, for example following the EnergyPlus "Groups" (in the I/O documentation, or when using IDF editors)

You'd have a group for "Setpoint Managers", with all possible setpoints managers under it. One for "Fans" which all fans under it, one for Pumps, one for Condenser Equipment (Cooling Towers, Fluid Coolers, etc)

Tried to make a run period from 3/1/2012-2/28/13 and could not do it

The Prototype Models save the climate zone as 7A and 8A. The climate zone is saved in the OSM, but not displayed in the GUI.

Showing non-standard strings could be an option, but maybe not a good idea. Could also either update standards to drop the A from 7 and 8 (maybe a can of worms) or in OpenStudio we could update 7 and 8 to 7A and 8A. If we do this some measure like AEDG would need to be updated.

The DOE Prototype measure and the updated SpaceType and Const. set wizard use 7A and 8A.

@macumber and @asparke2 any thoughts

Using Openstudio 2.3.0 with Build Number: cf58ee1e38 on a Macbook Pro 2017 running macOS Sierra 10.12.6

Can be recreated by opening the OS app, navigating to Components & Measures > Find Measures, selecting a measure and pressing download. The BCL pop up remains working and more measures can be downloaded, however after closing the BCL pop up all OpenStudio buttons become inactive.

Going to Apple > Force Quit doesn't show OpenStudio as 'Not Responding'.

Currently the user has to know something has been updated on BCL, to decide to update it, or stumble across it when searching for something else. A number of times I had updated measures but users didn't know there was a newer one with new features and or bug fixes. It would be great for a way in the GUI to update all BCL content for the latest version that works on my OS version.

From what I learned in writing measures to download components, I think this could be prototyped in a measure. So yes, while it is odd, a measure can be written that's sole job is to download measures. Another use of this would be to get measure collections like AEDG.

On 2012-09-18 08:38:14, @DavidGoldwasser wrote:

Since every type you click it it acts as hyper-link to another view, you can't ever see data in edit tab to rename it. Are there other fields that the user might also want to set for this object?

In the Edit section for PTAC zone equipment, the units for "Rated Evaporator Fan Power Per Volume Flow Rate" is labeled as "Pa". It should not be pressure, looks like it should be something like W/m^3/s, but should be verified.
-Erik Kolderup

Within the "Grid" view of refrigeration systems; the drop-down lists showing schedules don't present the schedules in an alphabetized manner.
@kbenne

Ctrl-f for find, Ctrl-c, Ctrl-v

Requested at https://unmethours.com/question/4422/determining-the-heating-and-cooling-loads-for-each-zone/?comment=4442#comment-4442

Have to keep opening this to drag in more space types

Understanding that they might not be editable users are concerned if they cannot see their schedules in the model. Kristin was concerned that all of her schedule compacts had been removed after importing model from idf.

Alternatives are to show schedules in read only or convert all schedules to schedule ruleset

On 2012-06-07 13:14:35, @DavidGoldwasser wrote:

Tested this with schedule set, schedule ruleset, space type, and lights def. I don't know that this is in scope for 0.8.0, but I just wanted to document it.

I also tried to reload the file to make sure that didn't update the graphic.

On 2012-09-13 16:00:45, @DavidGoldwasser wrote:

Per Elaine's request I tested this by deleting an attached object (like a removing people instance from a space type). Results were the same.

If this isn't an easy fix, then I think it can wait until post 0.9.0, just wanted to consider if it was low hanging fruit.

Would translate to OSM and use as the library model

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

https://openstudio.uservoice.com/forums/308629-openstudio/suggestions/10771254-graphical-representation-of-node-equipment-variabl

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 QA/QC or investigation, looking at the detailed output of a plant or air loop is extremely important.

Solution:

What I propose is to implement a graphical representation similar to what you would see on a BMS, with the same type of time controls you have in the "View Data" measure.
My initial thoughts are as follows:

1. Export OpenStudio plant/air loop view (or another way of graphically representing the plant loop with the equipments and branches etc)
2. Add some fields on each node of said loop to receive temperature, mass flow, setpoints (etc)
3. Add time controls to be able to display/navigate hourly or timestep values (similar to the View Model, you could pick a day and then cycle on each timestep during that day, etc)

Additional Features:

Additionally, I could see the following features being useful too:

• Being able to click on a few data fields and have them be plotted in "real time" (for your chosen day when you cycle through the timesteps) in a graphing window (that you could move around)
• Adding some equipment/zone values: such as current chiller kW, PLR and efficiency, zone cooling load, pump kW and PLR
• Adding another section for additional site variables such as outside air DB/WB

Pros and Cons of Solution:

• Easy understanding of plant loops

• Difficulty of implementation?

I loaded the "DEER_2017.osm" that ships with OpenStudio 2.4.3 into OS app and then went to Apply Measures Now. My measure directory is "nrel_published" from develop branch of measure repo.

The dialog came up in about 10 seconds and listed all of the measure, but when I select a measure (even if it is a measure without any arguments) it took 130 seconds before I could click run. My guess is this is measure manager working through all the measures. Once I have waited for this if I leave the dialog and come back it is very quick. None of the measure.XML files were updated during this time.

If I quit the app and the launch and re-load the model, it takes 120 seconds again when I first use apply measures now.

@macumber @axelstudios maybe this is related to API improvements mentioned in issue NREL/OpenStudio#1609.

The comment on YouTube about not finding measures is more common of an issue now that we have enough measures that results often span multiple pages. Ideally If I have enough screen space I'd like to see more than 10 at a time, but if I see 10 at a time, they should be alphabetical. Currently they are reverse of order last edited.
https://www.youtube.com/watch?v=umQR8XoORZc

I think this is just because I have so many measures in my measure directory (168). It seems that this dialog may parse the XML data each time it is opened. I think the "measures" tab just does this when the app is launched. I wonder if this dialog should do the same. All the dialog should need at first is the taxonomy information.

@macumber @asparke2 and @evanweaver any thoughts?.

https://openstudio.uservoice.com/forums/308629-openstudio/suggestions/15300522-improve-drag-and-drop-response-time-in-openstudio

When dragging and dropping model or library elements into an OpenStudio section (e.g. dropping a thermal zone into an air loop), the app takes several seconds to register before it allows further input. It makes the App annoying to use at times. Faster response (<0.25s) would improve usability.

Matt Brown sent a 1.3.0 file. When double clicking this on a Mac (using 1.4.0) the OpenStudio application launches and initially shows the model. However, after dismissing the "Model Updated from 1.3.0 to 1.4.0" dialog the app refreshes and an empty model is displayed. This appears to happen if the model is already up to date as well.

This does not happen on Windows, it also does not happen on Mac if you go to File->Open.

https://openstudio.uservoice.com/forums/308629-openstudio/suggestions/14802282-improve-grid-views-performance-for-big-models

Working with real models with 400+ spaces and 4000+ surfaces would be really helpful from grid views. Surprisingly, they are very slow with such size. More filters could be useful as well