
OpenStudio में ऊर्जा मॉडलिंग का निर्माण - ट्यूटोरियल
फरवरी 18, 2020
इन YouTube वीडियो में हम OpenStudio (और OpenStudio के भीतर स्थित फ़्लोरस्पेसJS) का उपयोग करके भवन ऊर्जा मॉडल बनाने के लिए आवश्यक चरणों पर चर्चा करते हैं। हम एक साधारण, ग्रामीण दमकल केंद्र का ऊर्जा मॉडल तैयार करेंगे। लाइब्रेरी फ़ाइलों को आयात करने, ज्यामिति बनाने, साइट पैरामीटर सेट करने और शेड्यूल बनाने से सबक आगे बढ़ता है।
ऊर्जा उपयोग के निर्माण की गणना ओपनस्टूडियो के माध्यम से यूएस ऊर्जा विभाग, एनर्जीप्लस सिमुलेशन इंजन का उपयोग करके की जाती है।
इन गणनाओं के लिए उपयोग किए जाने वाले सभी सॉफ़्टवेयर (स्केचअप, ओपनस्टूडियो, फ्लोरस्पेसजेएस, और एनर्जीप्लस) ओपन-सोर्स हैं और डाउनलोड करने के लिए स्वतंत्र हैं।
विषयसूची:
1. ओपनस्टूडियो और एनर्जीप्लस का परिचय
2. पुस्तकालय फ़ाइलें आयात करना
5. साइट टैब
14. समस्या निवारण (चेतावनियाँ और गंभीर त्रुटियाँ)
16. घरेलू गर्म पानी की व्यवस्था जोड़ें
17. जोन लेवल एग्जॉस्ट और फोर्स्ड एयर फर्नेस सिस्टम जोड़ें
18. जोन स्तरीय बेसबार्ड और यूनिट हीटर और पैकेज्ड टर्मिनल एयर कंडीशनर जोड़ें
19. समर्पित आउटडोर वायु प्रणाली जोड़ें
20. DView . का उपयोग करके EnergyPlus आउटपुट चरों को प्लॉट करके भवन के प्रदर्शन की समीक्षा करें
21. ज़ोन स्तर के वायु संतुलन को सत्यापित और समायोजित करें
22. एनर्जीप्लस उपायों का उपयोग करके मॉडल में ट्रांसफर एयर जोड़ें
23. स्केचअप का उपयोग करके भवन ज्यामिति को संशोधित करें
1. OpenStudio SketchUp - Orphan Geometry and Boundary Conditions
In this video, we will discuss surface boundary conditions. We will show how to use SketchUp to filter for and edit boundary conditions.
Quality control items for checking your model.
Check the boundary conditions of the surfaces.
Right now, I have this model set to render by surface type. This is pretty standard.
You can see that roofs are a dark red color. Walls are yellow color. Floors, gray.
Switch to render by boundary condition.
You can see that it changes the colors.
The floors are a dark beige. Walls, light blue. Roof, dark blue.
You can see that this one stands out. Inspect this item.
Go to the inspector tool...
Let us use the info tool. You can see that this is surface 47.
Let us click into this space. Click this surface 47.
You can see that the surface is specified as a roof/ceiling.
But, the outside boundary condition is set to ground.
This makes sense. It is a gray color.
You can see that the floors are gray color. Gray is a ground boundary condition.
So, we need to edit this. We will change it to an outdoor boundary condition.
We will change this to outdoors.
You will notice that it has changed to a light blue color.
That is because there are several other boundary conditions that we need to consider.
The Sun Exposed boundary condition...It says that there is no Sun, but this is a sun exposed roof.
It will be sun exposed to the sun.
It will be also wind exposed.
We will edit those conditions.
Do the same thing for the other surfaces that are wrong.
You will notice that this overhang is designated as a ground exposed, outside boundary condition.
This is actually exposed to the outdoors.
It is not sun exposed. It will be wind exposed.
We should change those boundary conditions.
We will do this for the other surfaces that are incorrect. Check those conditions that seem to be wrong.
Thank you. Please like and subscribe!
2. OpenStudio SketchUp - Separating Thermal Zones
In this video, we will show how to use SketchUp to separate large open spaces into thermal zones.
We have a building here that was modeled based on the floor plan.
We will hide the roof and take a look over the top.
We will hide this plenum here too. These are the rooms based on the architectural plans.
What we really have for HVAC zoning looks more like this.
We will work on RTU-2 zone, right here, for now.
You will notice that RTU-2 serves this entire space on this side of the building.
We only have these zones grouped up into rooms right now. Based on the architectural plans.
There is actually no wall here.vv
For our energy model we need to have a wall there to isolate this thermal zone.
We will edit the model to separate this room from this room. This thermal zone from this thermal zone.
First, we will go to camera and turn off perspective view.
Then we will select this space.
Use the Move tool: we will select a corner of it and we will hit the control button to copy.
Copy it up here.
This takes a minute for Sketchup.
Now we need to separate that out. Double click to edit this copied space.
Select everything up to this point to delete.
We can select this to delete and this to delete. This to delete. Delete.
We will just do this here. We will draw a line connecting this edge here.
This edge here. Then we need to draw a line down connecting these two to separate those.
That should split those off. We will go back to overhead view.
Now we should be able to delete this. We have an intact portion of the building.
Back to overhead view. We will select out of the active.
Likewise, we need to sever off this portion of the zone. Same procedure.
We will draw a line severing this portion.
We also need to sever the windows. You need to be very careful where you place your end points.
Make sure that it severs it properly. Now we can delete this.
Double check that we got everything.
Select out. Once you are done, you can just move the new zone into place.
Use the move tool.
Again, you need to make sure that you select the proper place.
You don't want to select this endpoint. We are selecting this endpoint to move.
You need to be very careful what points you are selecting and matching up.
Go back to overhead view. Now this space is severed from this space.
We have two thermal zones. Thank you. Please like and subscribe.
3. OpenStudio SketchUp - Boundary Conditions
Quality control items for checking your model.
Check the boundary conditions of the surfaces.
Right now, I have this model set to render by surface type. This is pretty standard.
You can see that roofs are a dark red color. Walls are yellow color. Floors, gray.
Switch to render by boundary condition.
You can see that it changes the colors.
The floors are a dark beige. Walls, light blue. Roof, dark blue.
You can see that this one stands out. Inspect this item.
Go to the inspector tool...
Let us use the info tool. You can see that this is surface 47.
Let us click into this space. Click this surface 47.
You can see that the surface is specified as a roof/ceiling.
But, the outside boundary condition is set to ground.
This makes sense. It is a gray color.
You can see that the floors are gray color. Gray is a ground boundary condition.
So, we need to edit this. We will change it to an outdoor boundary condition.
We will change this to outdoors.
You will notice that it has changed to a light blue color.
That is because there are several other boundary conditions that we need to consider.
The Sun Exposed boundary condition...It says that there is no Sun, but this is a sun exposed roof.
It will be sun exposed to the sun.
It will be also wind exposed.
We will edit those conditions.
Do the same thing for the other surfaces that are wrong.
You will notice that this overhang is designated as a ground exposed, outside boundary condition.
This is actually exposed to the outdoors.
It is not sun exposed. It will be wind exposed.
We should change those boundary conditions.
We will do this for the other surfaces that are incorrect. Check those conditions that seem to be wrong.
Thank you. Please like and subscribe!
4. OpenStudio Tips - Quickly Edit Multiple Schedules
In this video, we will show how to quickly edit multiple schedules at the same time.
Today we will discuss how to quickly adjust multiple schedules.
Go to the schedules tab.
We have multiple different schedules. Lighting schedules. Occupancy schedules.
There are various different priorities throughout the year for these schedules.
For some of them, we want them to be the same.
We will look at this one here. You will note that it has the year starting on January 3rd.
But there are some schedules that start on January 1st.
If you look at January 1st, it is a a weekend: Sunday.
If we look at this schedule, you will note that this starts on the third.
We actually want to start it on the second. This is a weekend. This starts on the third as well.
We want to start it on the first. We will start all of these on the first of the year.
This issue is found in all of the other other schedules. They are starting on on the third instead of the first.
We want to open up the OSM file with NOTEPAD++.
We will search for this schedule rule. You can see that this schedule starts on the first month of the year. The third day of that month.
We want to change that to the first month of the year and the first day of that month.
Go to replace. We need to type in the new line code "\r\n".
We will select the third day. So, we are trying to find this and we will replace it with this.
You want to make sure to select "wrap around" and "extended search mode".
Click "replace all". It goes through the whole file and replaces all of those occurrences.
It says there were 29 schedules that were changed from January 3rd to January 1st.
Save the file. Go back to OpenStudio. Click "Revert to Saved".
We will go to our schedules. Go to the library light schedule.
Check that it was corrected. You can see that it was changed to January 1st.
That is how you adjust multiple schedules at the same time using a text editor.
Thank you. Please like and subscribe.
5. OpenStudio EnergyPlus - Input Output Objects
In this video, we will discuss EnergyPlus objects and how to find information about how they function. This will help you understand how OpenStudio / EnergyPlus functions to simulate your energy model. It will also help you to know what inputs are important, what inputs can be left default, and how they might affect your energy simulation.
Today we are going to discuss what an EnergyPlus object is.
EnergyPlus objects are programming pieces inside the EnergyPlus program that execute certain calculations.
For example: this fan is an EnergyPlus object. This DX cooling coil is an EnergyPlus object.
This air loop is an EnergyPlus object. All of these are objects.
Objects have certain programming code associated with them that includes inputs.
The inputs are the items that you adjust on the side here, for this object.
There are outputs as well.
We are going to discuss how to figure out what each one of these objects do.
Let us look at this fan here. You can see right here. On the right-hand pane.
It says OS:Fan:ConstantVolume.
If you want to find out what any one of these inputs does for simulating the object, you can go to the EnergyPlus input-output reference.
Go to the EnergyPlus website: EnergyPlus.net/documentation
There is a lot of documentation for EnergyPlus.
In particular, we will look at the input/output reference.
This document here.
We are looking at Fan:ConstantVolume.
Let us type that in the search here. Fan:ConstantVolume
It finds the Fan:ConstantVolume object in the table of contents.
We will just click the link to go directly to it. Here is where it describes this object.
This object models a constant air volume fan that is intended to operate continuously based on a time schedule.
This fan will not cycle on and off based on cooling / heating load or other control signals.
It goes on to tell you what the inputs are. The name of the fan.
The availability schedule name. It describes what that schedule is used for.
The fan total efficiency. Pressure rise. Maximum flow rate.
It keeps going down to the end and use subcategory.
It tells you what each one of these inputs does.
Also, it tells you what the outputs are for the object.
Outputs for this constant volume fan are: electric power, fan rise in air temperature, and fan electric energy.
You can look at any object and you will see the EnergyPlus object name up in the top of the properties pane.
Look at Coil:Heating:Gas.
We can look up Coil:Heating:Gas to find out how this object is used by EnergyPlus.
I am sorry. It is not opening the link.
We will just click here.
It will tell you exactly what all of the inputs are for that particular object.
Same thing with the outdoor air system object.
If you are interested to find out what all of these inputs are in the properties pane on the side.
Just look up this keyword in the EnergyPlus input-output reference.
For the OutdoorAirSystem, it has one input. Name.
For the Controller:OutdoorAir, there is a lot of different inputs and outputs.
If you want to know what any one of these is used for, look at the EnergyPlus input-output reference.
Thank you. Please like and subscribe.
6. OpenStudio EnergyPlus- AirLoopHVAC Autosizing
In this video, we will show discuss how EnergyPlus autosizes air loop fans. We will also discuss how EnergyPlus balances airflows with zone level exhaust systems and use DView to verify the fans and Outdoor Air System are working together.
A user on YouTube asked a question.
Can you do an example of an air handling unit with 6000 CFM supply 5000 CFM return.
1,000 CFM fresh air with zero exhaust, unless it's economizing.
There is a exhaust fan at the zone level at 1,000 CFM.
The exhaust fan is separately ducted from the system. This is how the building stays neutral.
The auto-sizing always makes the supply and exhaust fans the same size, which is wrong. Issue 1.
I am not sure how to tell the fresh air and exhaust air dampers to work with this 1,000 CFM offset.
It doesn't seem to have much for configuration.
Let us do a an example of this.
We will go to apply measure now. We will create a prototype building.
This is just a measure you can download from the building component library.
Click this measure.
We will just stick with small office. All the default stuff. Apply measure.
This has created a prototype office building for our simulation.
Go to the thermal zones tab. We have got five thermal zones and an attic.
None of them have an exhaust fan. We will just put an exhaust fan on zone 4.
We will set this to always on. Pressure. For flow rate: maybe 100 CFM.
Yeah, we can probably do more than that based on the building size. We will use 250 CFM.
You will note that the exhaust fan comes defaulted to Decoupled.
There are different ways to control exhaust fans at the zone level. By default, it come in Decoupled.
Decoupled means it is not reliant on the air loop HVAC system, that serves that zone, to turn it on and off.
Decoupled means that it it runs on its own schedule. But we want to use Coupled.
Coupled (with Always On availability schedule) means it is always available, and the Air Loop System turns it on and off.
Whenever this air loop system is turned on, then it will turn this exhaust fan on. That is what the Coupling does.
Go to the air loops tab. We will just take a look at this real quick.
We have got a unitary heat pump system, but for this we actually need to have a return fan.
We will put in a constant volume fan on the return side of the system.
This serves zone 4 (with the exhaust fan that we just placed).
Let us take a look at these. It looks like the whole system is set to Autosized.
...Flow rate when no cooling or heating is needed...
We will just leave that as AutoSized.
Autosized. OK.
We will run the simulation. It looks like the simulation has completed successfully.
Go to reports and select Air Loops. We will scroll down to zone 4.
OpenStudio results come in sequence of the equipment that is on the air loop.
It starts with the return side of the air loop. This would be the return fan.
It is sizing the return fan for 744 CFM and the unitary heat pump fan was sized for 744 CFM.
Despite us having an exhaust fan that is scheduled always on when the Air Loop is operating.
That is because EnergyPlus does Autosizing based on the loop only.
It does not take into account any external air balancing.
That is an important part to remember about EnergyPlus.
It does some select air balancing, but it doesn't do all air balancing.
So, you need to make sure that your system is balanced.
EnergyPlus does account for Air Loop balancing during the simulation because of that Coupled toggle switch that we selected on the exhaust fan.
See EnergyPlus Input Output Reference- Field: Balanced Exhaust Fraction Schedule Name
Let us take a look at the air flows on some of the system nodes.
Go to output variables. Go to system nodes...to far...system nodes.
We want to look for...here we go. Current density volume flow rate.
We will set the increment to time step. The time step of the simulation. Click Save.
Run the simulation again. Success. Go to results summary.
Scroll back down to zone 4. You will see the supply and return fans are sized the same.
Go to DView to view the output reports on this.
We will go back to the air loop so we can figure out what nodes to look at. Let us see here...
We want to take a look at the return node.
This is actually the supply inlet node and the supply outlet node. This is the supply side of the system.
Select perimeter zone 4 supply outlet node and supply inlet node.
You can see that the return air flow is quite a bit less than the supply side.
This is another important point to make. The way EnergyPlus calculates air flows and system size is based upon the zone level sizing.
EnergyPlus figures out zone level sizing first. Zone level mass flow rates.
Then, everything propagates out from that.
If the zone requires a certain amount of airflow, then you will follow the loop back to the first fan.
That fan will have to supply that amount of airflow at the specified pressure.
Likewise, there is a certain amount of return mass flow rate.
The the next fan in the loop has to flow that amount of flow rate (at the specified pressure).
These are not actually fans. They are not pushing air as in real life.
EnergyPlus calculates fan energy use based on the airflow that the fan theoretically should have been flowing.
So, these fans don't actually push air into the zone and the zone receives it.
EnergyPlus back calculates from the zone and it tells the fan: you have to supply this amount of airflow at this pressure.
Based on the fan power curve, this is how much energy will be used.
You can see that the return air flow is lower than the supply air flow for that zone.
You can also check to see how the economizer dampers are operating.
We will select relief air and outdoor air and mixed air.
We would have to find these on here.
Here is the outdoor air node.
The outdoor air is flowing a little over 250 CFM.
That corresponds to the 250 CFM exhaust fan that we applied to the zone.
If we turn that exhaust fan off, you would probably see this ventilation air flow rate dropping lower than the 250 CFM.
But that exhaust fan is on and it is operating with the air loop.
The outdoor air flow rate in this outdoor air system has to flow a minimum of the 250 CFM. For that exhaust fan.
We can simulate this, if we wanted to. We will rerun the simulation with the exhaust fan turned off.
We can see what that outdoor air flow rate is.
Let us go back to the zone exhaust fan...
...better yet...we can turn the exhaust fan on and off in the middle of the schedule.
We will just create a new schedule. We will turn it off in the middle of the day.
So, we will see the difference. Go back to the exhaust fan. EF schedule. Save. Run.
Success. Let us open up DView again.
Take a look at the zone 4 outdoor air flow rate.
Select inlet node.
Outlet node. OK.
You can see that in the middle of the day the exhaust fan turns off.
The return air flow jumps right back up.
You can see: during the the first part of the day the exhaust fan is on and it is returning less air to the air handler.
Let us look at the outdoor air node.
Same thing.
You can see. During during the first part of the day, when the exhaust fan is on, the outdoor air system supplies extra air flow.
Then, when the exhaust fan turns off, the air flow drops down to minimum outdoor air.
Or, if it is economizing, it might drop down to a different setting.
That is how you know that the outdoor air system is operating correctly.
That is how you ensure that your exhaust fans are balanced with your air loop.
This is this is how you toggle that on and off.
If you want that exhaust fan to operate independently of the air loop, you can put it on decoupled.
Then, it will run on its own schedule, but it will still affect that return air flow to the loop.
So, going back to the original question.
The bottom line is: the auto sizing will size the system for the maximum airflow.
You may have a return fan that is actually sized for less.
Which, could important for energy calculations. You will have to hard size that to the supply air flow minus that exhaust air flow.
For this instance, we would have input Hard Sized maximum flow rate...
I believe the system airflow was...supply air flow is about 750 CFM.
We would size this for 500 CFM.
That is how you ensure that your return fan is sized properly.
Thank you. Please like and subscribe.
7. OpenStudio SketchUp Tips - Project Geometry Tool
We discuss how to use the project geometry tool in the OpenStudio SketchUp Plugin. This tool is helpful for applying sub-surfaces to multiple spaces at one time.
I will show you how to use the project geometry tool. This action will help reduce computing time on the simulation .
We are looking at some windows. There are multiple windows that are very close together.
The divider in-between them really doesn't affect the energy simulation very much.
Draw some rectangles over the windows (external to the spaces).
Now, enter the spaces and delete these windows. Go through and delete all of these windows in the spaces.
Now, go up to the project loose geometry tool. We will project selected loose geometry.
Select these rectangles that we just created. Click the button. Yes.
It was successful. You can see that the windows have been applied to the individual spaces.
Thank you. Please like and subscribe.
8. OpenStudio Tips - Assign Space Type to Multiple Spaces
We discuss how to use the Building Component Library measure "AssignSpaceTypeBySpaceName" to quickly assign space types to spaces with a common string in the name.
Transcript:
If you have a lot of spaces that you want to assign a specific space type, you can use this measure on the building component library.
Go to "whole building", "space types". Search for "assign space type by space name".
You can download the measure. Go to "components and measures", "apply measure now".
Search for the measure under the "whole building" category. It is right here.
Please note: this string search is case specific. We can not search for both upper and lowercase "c" in corridor.
So, you want to make sure that your spaces are named consistently.
This check box does not seem to work, so don't use it.
The measure was successful. It assigned space types to 21 of our spaces.
Thank you. Please like and subscribe.
9. OpenStudio SketchUp Tips - Vertex Size Mismatch
We discuss how to resolve the common error "Vertex size mismatch between base surface".
We are going to discuss a common error, a severe error, that terminates your simulation.
We will go to the error output file. We are looking at this error in particular. Vertex size mismatch between base surface.
It is saying there is a mismatch between this surface 4840 and the surface 149.
You can see that it repeats itself. There is a 4840 here and then further down it shows the same error.
It is just reversed. So, it looks like there is a lot of errors. There is really only half of them.
Once you resolve one, then the other one will be resolved.
We will be looking at this surface 4830 and surface 4897.
It is saying that there are 11 vertices on surface 4830. There are 7 vertices on surface 4897.
We can go to the OSM file and verify that. We will search for surface 4830.
You can see that this surface 4830 has eleven vertices. The other one was surface 4897...This one has seven vertices.
Let us go to the OpenStudio SketchUp plugin. Open up the OpenStudio inspector tool.
We will adjust this a little bit...Select the “Surfaces” category.
It says that our model has 8,576 surfaces.
We want to search for surface 4830. Right here. It says that this surface 4830 is associated with the Space “Hallway 4-3”.
The surface 4897...let us look for that 4897...right here.
This is associated with the Space “Plenum 3-4-N”.
Let us go to our spaces. Search for that “Hallway 4-3”.
It is right there. Let us search for the “Plenum 3-4”. It is right there. It is right below “Hallway 4-3”.
Let us go back to the “Hallway 4-3”. We will use the shift key, and click to add the “Plenum 4-3” to our selection.
Now, let us do a top view. We are going to right-to-left drag while holding the shift key.
This will select everything else. It will also deselect those two spaces that we had selected.
Now, use the Hide function. That hides all the other geometry.
We have now narrowed down our search to these two spaces that have the matching surfaces.
Then, we can double-click into one of the spaces.
Now, search for the surface again. 4830...it is not that one...4830 must be associated with...
Oh, there it is. Right there. So, it is this surface here. 4830.
I am sorry. It must be associated with the other space. This is 4897, which is the matching surface to 4830.
It had selected the 4830 in the other, inactive space.
We can see that it is located on the top of this plenum. We will do a side view...
Maybe like this...
or like this...
We will do a right-to-left drag select. We will hide these surfaces. This will make it easier for us to identify the surfaces.
We can see that this is one of the problem surfaces. 4897.
Click out of this space. Now, double click into this space. We see that it is associated with this surface 4830.
We will click out. You can see that those surfaces are matched.
EnergyPlus thinks that these two surfaces do not have the same number of vertices.
We can select the surface and double click to highlight it. Count the vertices: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11.
This is surface 4897, so it should have 11 vertices.
If we look at our error output...4897...the error output file is saying that it only has seven vertices.
I do not know why. I suspect that it has something to do with SketchUp.
I think SketchUp is simplifying. It is defining this surface based on some of these other surfaces that are attached.
So...there is a vertex that is shared with these other surfaces.
Instead of outputting all of the vertices for this surface, it is just out outputting the the minimum number of vertices to define the surface.
Some of these other surfaces have that vertex in in their definition.
Somehow this confuses OpenStudio. I have discovered. The solution is to divide the surface.
We can draw a line from this vertex to this vertex. That divides the surface in half.
Now we have two surfaces. 4898 and 4897.
Now we have to divide the surface on on the matching surface.
We will just draw a line to connect these vertices. That divides the surface in half.
Oh...looks like I messed up on something here. Let us go back to this one here.
You have to be very careful when you are adding this geometry.
Divide that surface into two. We can see that it is now two surfaces.
So, this is surface 4899 and this is surface 4898.
We need to make sure that it is matched with 4899. Same thing for the other surface that was created. 4897.
It should be matched with 4830. Yes. 4897. That is how you solve vertex mismatch issues.
You may have to further subdivide the surfaces.
Once you get down to about four vertices, there is fewer problems.
You may find that you still have a persistent problem.
A rough workaround: make the surface adiabatic. Select the surface. Go to boundary condition. Click adiabatic.
Sorry. You will have to unmatch the surface first. Unmatch it. Then select “adiabatic”.
It turns it pink. Make the matching surface adiabatic as well.
It got unmatched but it is still looking for a boundary condition.
This says it defaulted to “ground”. We want to make it adiabatic also.
Adiabatic tells EnergyPlus that there will be no heat transfer in between these two surfaces.
If it is a small surface, it may not be a big problem. The energy model results will not be significantly affected.
If the the room temperatures between the two spaces are similar, there is little heat transfer anyway.
But, if there is a large temperature difference, you might consider trying to further subdivide the surfaces.
That is the workaround for solving the vertex mismatch severe error.
If you like these videos, please like and subscribe.
Thank you.
10. OpenStudio Tips - How to lodge issues on GitHub
We discuss OpenStudio and the SketchUp plugin open-source project and how users can contribute by lodging issues on GitHub.
The OpenStudio application is supported by the OpenStudio Coalition.
They are a group of volunteers and paid programmers that keep up and maintain the OpenStudio application.
They rely on feedback from users to help resolve issues with the software.
I will show you how to lodge an issue on GitHub; If you discover issues with the OpenStudio application or the OpenStudio SketchUp plug-in.
You would need to sign up for an account on github.com.
Then, you can follow the the two programs.
We will be lodging an issue on the OpenStudio application today.
We will go to issues. Create a new issue.
This is a categorized as a bug report.
If you have an enhancement request, you can also do that.
Let us do a bug report. Give it a title.
This is basically where you describe what the issue is.
We will just say “The application crashes when the user tries to delete an HVAC Airloop.”
There is not really much more to it.
I did capture a screenshot or actually a gif video of what happens when this problem occurs.
You can see here that the user selects the Airloop and tries to delete it. It crashes the program.
We will upload this gif to the current behavior section.
There is not much more info I have.
If there is additional information you think might be necessary, you can describe the steps to reproduce the issue.
If you have any suggestions for solutions, you can add that information in there. Or, additional details that narrow down the problem.
We are running windows 10.
The version of the application is OpenStudio 110r3.
Yeah. That is pretty much it.
Now, just scroll down to the bottom and submit new issue.
Now, it is submitted as a new issue. If needed, you can always add more info later.
The programmers will eventually see it and hopefully address it.
Thank you. Please like and subscribe.
11. OpenStudio Tips - Create A Combined Plenum
In this video, we will show how to create a shared plenum between multiple spaces and floors. Also see this NREL video for more info on modeling plenums: https://youtu.be/n_u3WT2tX1Y
Transcript:
Today, I am going to show you how to create a shared plenum between two different floors.
We have a large office building. We will be working on the third and fourth floor. For simplicity.
You can see that these floors are comprised of a lot of different spaces.
Right now they are nine foot (2.7m) from floor to ceiling.
We need to put a plenum in between the floors. A four foot (1.2m) plenum.
Put it on side view. Take the camera off of perspective.
Select the fourth floor. Do a move. Move it four feet (1.2m). We have created our separation between the floors.
We want to create a space in between those floors with all of the ceiling and floor characteristics of those spaces.
Save this model. We will save this as the "plenum". We will save it as a separate file.
Re-open the original. We we need to open another instance of SketchUp.
We can just ignore these errors for now. Go to the the new instance of SketchUp.
Delete him. We will open that saved version of the plenum that we just created.
We can ignore these errors. Go side view. Turn the perspective camera off.
Control-A to select all of the geometry. Right click. Explode.
That exploded all of the groupings for the spaces into just a SketchUp file. It is no longer an OpenStudio model.
All of these surfaces do not have any characteristics. Now, they are just simple SketchUp surfaces. Lines and vertices.
You can click on them. You can see that they are no longer associated with any spaces.
Now, select (right-to-left) the top and delete it. That just leaves the floor of the fourth floor.
Likewise, select the bottom of the third floor. Make sure to select all of the windows too. Delete it.
Now, we have the ceiling of the third floor and the floor of the fourth floor.
You can see that those are now isolated. Connect the two on the corners. Now we have our plenum. The geometry of the plenum.
We can save this SketchUp file. Just in case we need it. In case the program crashes.
We will just save it as a SketchUp file. This is basically a dumb file. It does not have any of the OpenStudio information. Just geometry.
If you try to save it as an OpenStudio file, without assigning to a space, all of this information will be lost.
We need to save this as a SketchUp file for now.
Now, create a space. Go to the origin. Create the space. Select the space.
Draw a line for now (as placeholder). Exit out of the space. Select all of this geometry. Cut.
We will enter into the space again. Paste the geometry into the space. It takes a minute.
There we go. You can see that this geometry was pasted into this space.
But, there is a problem. If you recall, we are creating the ceiling of this plenum based on the floor above.
So, all of our plenum ceiling surfaces are labeled as floors. And, all of the plenum floors are labeled as ceilings.
We have to edit that. The quickest way is to use the text editor. I will show you how to do that.
Go to the OpenStudio file that we created for the plenum.
We are going to open this with Notepad++. Search for a surface type. We are looking for an example of a floor.
We have Surface Type "Floor" here. Copy this. We want to replace it with "RoofCeiling".
We will add a "1" as a placeholder to differentiate it from the other roof ceilings. For now.
Click "replace all". Now, we want to look for an example of a RoofCeiling.
We will replace all of these with "Floor". Replace all.
Now, go back to our placeholder "RoofCeiling1". Replacce all of those with "RoofCeiling".
Click save. Yes, reload it.
It corrected some surfaces that were upside down. Click OK.
Now you can see that all of our floor surfaces have been changed to ceilings.
All of our ceiling surfaces on the bottom have been changed to floors.
There are some issues with...sometimes for whatever reason...OpenStudio decides to put in skylights.
That can be kind of a problem. You can just cross over the skylight and delete that. Delete this.
We can delete this here. That is how you get rid of skylights. Sometimes it takes a little extra work.
You can cross over this. Just delete the surface. Redraw the surface. Delete the surface. Redraw the surface.
We can delete this extra line in the middle. We've fixed all of our skylights.
You can see that now the floor is the floor. And, the ceiling is the ceiling. We have created our plenum.
Go ahead and save this OpenStudio model of the plenum.
Next, I will show you how to insert the plenum into your current model.
Create a new space. Double click into it. Go back to our plenum model.
Double click into the space. Control-A to select all. Copy.
Go back to your working model. Control-V to paste the plenum geometry.
It should come in at the proper origin. Just paste it on the origin. It will take a second to calculate.
You can see that it was pasted in with floors and ceilings. Again, we've got some issues with a few of these skylights. We will fix those later.
Click out. You can see that now we have a common plenum that all of these spaces share.
It already has the intersections that are in common with the spaces. Intersect geometry is not needed.
We only have to use surface matching to make the model cohesive.
That is how you create a common plenum between floors. Between multiple spaces.
Thank you. Please like and subscribe.
12. OpenStudio SketchUp - Lights vs Luminares
In this video, we will discuss two different ways to specify lighting power heat loads in a space. Lights Definitions allows for generic lighting power densities. Luminare Definitions (and the SketchUp Plugin Luminare button) are another way to specify lighting power loads.
Transcript:
Today we are going to talk about lighting power loads.
We are just going to focus on this OpenStudio SketchUp extension function here, which is the New Luminaire button.
First, let us take a look at the OpenStudio model.
There are two different ways you can input lighting power loads into your spaces. One is a general lighting power density. eg. watts per square foot (w/m²).
EnergyPlus will calculate the total lighting power for the space based on the square footage of the space.
We can take a look at that by going to the loads tab. Go to Lights Definitions.
We can see here, for break room lights, it is specified as a watts per area. You can also put in a hard value of total wattage for the space or you can put in a watts per person.
For example; if the space had individual task lighting and the people entered the room and turned on their own task lights.
That is one way that you can specify lighting power within a space.
Another way you can specify lighting power is by using luminaires. We don't have any luminaire definitions set up for this project yet.
Let us go back to the OpenStudio SketchUp Plugin. We are going to take a look at this space right here.
The space type for this should actually be Open Office. I do not know why that is not entered. Okay.
We have an Open Office space type here. We can go back to OpenStudio. Take a look at the lights definition.
Look for Open Office space type..I am sorry...Open Office lighting definition. Right here. It is specified as 0.98 watts per square foot (10.5w/m²).
Alternatively, you can add luminaires, lighting fixtures, to the space with this button here.
Double-click the space to edit. Let us turn on the section cuts so we can see inside the space. Overhead view.
Click the New Luminaire button. You can place a new lighting fixture here. So, it placed a new lighting fixture in that space.
We can uh click out of it. We will save the model. Go back to OpenStudio and Revert To Saved. Click yes.
If we go to luminaire definitions you will see that it now inserted a luminaire into the model.
Right now, the luminaire is at a default value of zero. It will do nothing to the room.
But, you can create an OpenStudio project with all of the different types of luminaires that your electrical engineers or the architects will be using within the project.
That is what I did. I just created an OpenStudio model with those definitions. We can open that up.
The only thing in this OpenStudio model is luminaires. I called it a "LuminaireLibrary".
Okay. We will take a look at the loads tab. Go to luminaire definitions. You can see that I have created a bunch of luminaires in here.
We will create another one...we will just select this pendant type here and we will copy it. We will call this a compact fluorescent...60...maybe 14 watts.
We will specify it as 14 watts. Fractions...you have to input these values.
Fraction of radiant, fraction of visible, and if there is any fraction that gets put directly into the return airstream.
This will be just a compact fluorescent light exposed to the room. There will be no plenum heat losses. We will leave these as default values. That is it.
Click save on our LuminaireLibrary.osm. It is just a typical OSM file. Close out of this. Let us go back to our project.
Right now, we only have one luminaire in here. To add more luminaires, go to Change Default Libraries.
We can add that LuminaireLibrary.osm project to our library files for this project.
I already have it added here...so, we will click OK. That will put all of those luminaires in your library tab over here.
Now, we can click down and we can see that all of those luminaires that were in our LuminaireLibrary are located in here.
Drag these in and drop them into your project. We will add few of them there.
Click save. Go back to the SketchUp plugin. It has been updated. Yes, because we saved it. Okay.
It updated our SketchUp file. Let us double-click into the space again.
We can place another luminaire. We will just place it right here. You will notice that it comes up with a drop down menu.
You can select what kind of luminaire you want to place. We will place this pendant light here. Select yes.
It does not matter where these lights are located within the room. It is not going to affect any illuminance calculations.
This is strictly for heat loads to the room. These are really just dummy lights. They only produce heat inside the room.
You will notice that these lights were actually placed in the room 2ft (0.61m) above the floor.
If we unhide the section cut here. We can put it on x-ray view. We will add in another light here.
Click that. You will notice that it was placed two feet from the ceiling. It places two feet from whatever surface you select.
For the purposes of heat calculations, it really does not matter where these are located. As long as they are within the room.
Like I said it does not calculate illuminance within the room. It is just calculating heat energy added to the room.
If we have several of them, shift click all of them and push "m" key for move. Push the control button
to copy it. There. Now we have six light fixtures within the room.
We can click out of it. We will save the model. We can go back to OpenStudio. Revert to saved. Yes
Okay. First thing you will notice. We have those luminaires in there. The ones we had placed.
Let us go to the spaces tab. Go to loads. You will notice on the Space 102, that we were working on,
you can see all of these luminaires that were placed within the room.
Unfortunately, we also still have Open Office lights definition in this space type.
So, in addition to the general lighting power density of the space we are also adding these luminaires.
That is one thing you need to keep account of. You might end up having to delete this lighting power definition if you already have luminares placed.
To do that, you would have to create a separate space type. We can go to Space Types tab.
Go to Open Office. We will copy this. Now we have Open Office 1. We will call this "without lights".
We can go back to our spaces tab...oh...I am sorry. Go back to the Space Types tab.
Let us edit the loads on that new space type...without lights...we will have to delete this light definition here. We will delete it.
There we go. Now this space type without lights has people, plug loads, and infiltration, but it does not have a lighting power density associated with it.
Let us go back to the spaces tab. For this Space 102, you can see that the space type has been assigned "Office - Open Office".
Let us assign "Office - Open Office Without Lights" to this space 102.
If we go to our loads tab, you will see that the only thing in the Space 102 is now those luminaires that we plugged into the space.
So, that is a couple of different ways to get lighting power into your spaces.
Thank you! Please like and subscribe.
13. OpenStudio SketchUp - Daylighting Controls
In this video, we will discuss how to input daylighting controls that reduce space lighting power as sunlight enters the space.
Transcript:
Today we are going to talk about daylighting controls. This button up here; Create New Daylighting Control.
This is used for controlling the lights within your space. If you have exterior windows, throughout the day the sun will shine through the windows and light up the space.
At that point, you might not need as much artificial lighting in the space. The daylighting controls will reduce your artificial lighting based on the amount of sunlight that is coming through the window.
You can click this button to create those controls. Let us edit the space. Click the button New Daylighting Control.
You can just drop it into the space. It automatically places it 3ft (0.91m) above the floor. That can be adjusted as you as need.
You can relocate the object to wherever it is most convenient within the space.
You might want to place it somewhere in the middle of the space, depending on how much daylight harvesting you intend. That is, how aggressive you are with with turning down the lights within the room.
That is how you drop it into the space. We can click the Inspector tool to take a look at the properties for the daylighting control.
You want to make sure that you click that daylighting control object. You can see that it was dropped in here.
It has a name,the space name, that it is associated with.
It is important to note: you can drop these into individual spaces, but EnergyPlus will only allow up to two day lighting controls thermal zone.
So, if these two spaces were part of a thermal zone, this daylighting control would control this space and this space. They are part of one thermal zone.
To get around that, it might be best to assign separate thermal zones to each of these spaces.
These are the position the coordinates of the daylighting control within the space.
These are the rotation axes of the daylighting control sensor. If we wanted to rotate this 180 degrees, you can see that this arrow changes.
We will point this this arrow...I believe this arrow is the glare sensor. It is also used for window shading controls. We will get into that later.
Right now, we are just doing daylighting controls, which is this arrow right here.
It is just a photo sensor that senses lighting levels within the space (in this direction).
You can adjust the glare angle, if you were doing shading controls. Like I said, we will get into that in another video. You can adjust that angle here.
For now, we will just set that at zero for our daylighting controls.
Illuminance Setpoint; this illuminance setpoint is the illuminance of the room in the middle of the night (no sun).
Basically, when there is no sunlight coming through the window. It is the design illuminance of your lighting fixtures.
You will need to know the design illuminance of those lighting fixtures. Or, know what the expected illuminance for this space type is.
You can put that value in there. It is the design illuminance; the daylighting control will dim your interior lights from a maximum of this value all the way down to your specified lower boundaries.
The lower boundaries are these two right here. The lighting control type can be selected here.
Continuous; continuous lighting control starts at your design illuminance and then it it continuously dims the lights until you get to a minimum input power fraction and minimum light output fraction.
The minimums are these values down here.
Stepped; it steps your lighting power down by the specified number of steps.
You can select Stepped, right here, you can specify the number of steps for the lighting power.
We will just leave this at continuous...oh...um
Continuous off; it lowers your lighting power down from design to a minimum input power fraction. Anything below that point it and it shuts the lights off.
Let us go back to continuous...
Probability Lighting Will Be Reset When Needed In A Manual Stepped Control; if you set this up as stepped control and you wanted to simulate this as manual switches (banked lights). No automatic daylighting control sensor.
For example, if you wanted to simulate this as people in the room, no daylighting sensor, but the people regularly flip off a bank of lights during the day to reduce the lighting in the space.
That is how you would simulate the activities of people stepping down the lighting themselves during the day instead of using an automatic sensor.
This probability function here takes into account the probability of people actually turning the lights down.
You might say...oh...if it gets too bright in the room, 30% of the time someone will flip a bank of lights off.
So, that is what the probability function is.
The Number of Daylighting Views; I do not believe this factors into EnergyPlus. If you are going to be using the Radiance Measure in OpenStudio, then this number of daylighting views comes into effect.
I believe it multiplies the number of these arrows here, so it will equally space the arrows pointing throughout the room.
It is used to get a better understanding of how well illuminated the room is.
Maximum Allowable Discomfort Glare Index; that is used if you are doing automatic shading controls on the windows.
If the glare gets too high during the day, the window shades or blinds will go down.
We will get into simulating glare in another video. So, that is how you input a daylighting controls object into a space.
Thank you! Please like and subscribe.
14. OpenStudio Tips - Downloads from BCL or Elsewhere
We discuss OpenStudio and the SketchUp plugin open-source project and how users can contribute by lodging issues on GitHub.
Transcript:
Today, we are going to discuss how to manually install components and measures by downloading them from the Building Component Library (BCL).
Or, if you have a colleague that has created a component or measure that has not been uploaded to the BCL.
You might do this for several reasons.
Perhaps, you go to Apply Measure Now in OpenStudio and you do not have a measure in your measures files.
Perhaps, you go down here to the lower right, Find Measures On BCL. For some reason it is not connecting to the BCL.
You can go to the BCL website and search for measures and components.
Let us go to Browse Measures. Select lighting. We will select one of these recent ones. Maybe...Set Lighting Loads. Okay
This is located under Electric Lighting, Lighting Equipment. Next, download it. Click ok to download it.
It has downloaded into your download folder. Now, go to the My Measures folder, down here in the lower right. Click it.
This will open up all of your custom measures that you have created. All of these are not connected to the BCL.
They are all custom measures. They have been disconnected from syncing with the BCL.
Now, open up your downloads folder. Here is the the measure that we just downloaded.
It is a zip file. Open it. You can see it is called Set Lighting Loads by LPD. We will copy and paste this into our measures folder.
Now it is located in there. Let us go back to OpenStudio. Go to apply measure now. It was located under Electric Lighting, Lighting Equipment. Here it is.
That is the one that we just downloaded and dropped into our folder. It is called Set Lighting Loads by LPD. That is the one we downloaded.
You can see that it is considered a "My" measure. Look at some of the other ones...
If it is a BCL measure, it will have a "BCL" here. That means that it can sync with the Building Component Library. If there are any updates, you can update it.
If you have My measures, it is not going to sync because those are located on your computer and are disconnected from the BCL. They migh also be edited...you can edit the programming in those files.
So, that is how you download directly from the BCL. Or, if you have a colleague that has written a custom measure or a custom component, they can send you that file folder.
It will be a file folder like this. It will have a ruby file, xml file, basically all of these things.
Your colleague can look in their own measures folder, select one of these, and then send you that whole folder. Then, you can take that folder and drop it into your My measures directory.
You can access it directly with this My measures button right here. That buttton opens it up for you. Just drop it right in there.
So, that is how you deal with measures and components that are disconnected from the BCL or have been directly downloaded.
Thank you! Please like and subscribe!
15. OpenStudio SketchUp - Illuminance Controls with Radiance
In this video, we will discuss how to input daylighting controls, glare sensors, illuminance maps, and shading controls in preparation for using the Radiance measure. We will download and install Radiance and Strawberry Perl. We will use the OpenStudio Radiance measure to simulate lighting and shading controls. Finally, we will briefly look at the Radiance outputs using DView.
Transcript:
The last couple of icons at the top are used for the Radiance measure. Radiance is a fairly complicated lighting simulation program.
Instead of using the standard lighting simulation that EnergyPlus uses, you can use Radiance instead. which
Radiance is a lot more detailed and my understanding is the EnergyPlus lighting simulation does not do a very good job. So, you can use Radiance as an alternative.
That is what these two icons, up here, are being used for. In addition to the daylighting control that we had installed previously.
We can edit the space. Go up here to New Illuminance Map...first let us go to camera, turn off perspective. Select an overhead view.
Now, go to the New Illuminance Map button. Click it. Drop this into the space.
We will move this to the corner here. We can stretch it out with the scale button. Stretch it out to encompass the entire room.
This is an illuminance map that Radiance uses to measure the lighting power concentration throughout the entire room.
It is assigned a grid. Each one of these grid spaces measures the the illuminance at that particular area.
You can adjust the number of grid points on the grid to whatever you like. We will keep it at 10 x 10 for now.
You can adjust the size of that...and you can also adjust the coordinates within the room.
Um...that is a little bit high. We probably want to have the grid lower in the room. We will use the move tool...move it down here...maybe a little bit higher. Right there. Probably about desk height.
We do have our daylighting controls. In addition, you can put in a New Glare Sensor. We will drop the glare sensor in here.
For whatever reason, it drops it onto the floor. You can adjust that coordinate. We will adjust this up to three feet.
We will rotate the sensor towards the windows. Now it is facing towards the windows.
You can adjust the number of glare vectors. Right now, we only have one glare vector pointing toward the window.
If you wanted equally spaced glare vectors radiating out from this glare sensor, you can increase those numbers. Maybe we can put in three here.
The object will not show them, but you can see here that we have three vectors for that.
Maximum Allowable Daylight Glare Probability; this is, if I understand correctly, a value that is the probability of number of people in the room that have a problem with the glare.
Right now, in order to activate the the glare controls, 60% of the people in the room have to be bothered by the glare.
We can reduce this down...we will say...30%. So, 30% of the people in the room find the glare bothersome. Then, they will lower down the shades on the windows.
Aside from daylingting controls, shading controls is another thing you can do with Radiance. Shading controls are activated this glare sensor.
To add shading controls to the windows; go up to Extensions, OpenStudio User Scripts, Alter or Add Model Elements, and click Add Shading Controls.
Right now, we do not have any shading materials or switchable constructions. Shading materials would be if you have blinds or shades on the window.
A switchable construction might be if you have a window with two panes of glass and there are blinds located, sandwiched, between the two panes of glass. That would be an example of a switchable construction.
We will create a new blind. Click ok. Go to the OpenStudio Inspector tool. This right here.
Open up the Inspector tool. Go to shading controls over here. This is the shading controls that we just input.
It is attached to these interior blinds. Like I said, if you had a window with blinds that were sandwiched between the window panes, you would use that here instead.
There are a lot of different shading control strategies. You will have to read the Input/Output reference manual to understand what all of these options are.
We will leave it as default for now.
Shading Control Schedules, Glare Control...we will keep glare control turned off. The Radiance measure already has a glare control in this glare sensor we placed.
Angle Slat Control for Blinds; I do not know if that makes a difference for Radiance...we can switch this to Block Beam Solar.
Finally, at the very bottom, you want to assign this shading control to windows that are located on your space.
That will be this window here, Subsurface 4, and this window here, Subsurface 3.
Going back to shading controls, at the very bottom, we will assign the shading controls to subsurface 3. Click + to add one more. Subsurface 4. These are the two windows in the room.
We can save the model...just close this...we can open it OpenStudio.
Go to the Measures tab. The Radiance measure is located under Electric Lighting, Electric Lighting Controls.
I have two of them; one that is connected to the Building Component Library. It is a little bit old and my understanding is that the programmers are editing it right now.
So, I have downloaded the latest one from GitHub and put it into My measures folder.
Drag this into here. Select it. You can customize it a few different ways. We will just leave those as default. Click save.
To run the Radiance measure, you have to have Radiance and Perl installed on your computer.
You need to browse to the Radiance website. Radiance-Online.org. Go to Download/Install, Radiance Installers. Go to the latest version of Radiance on GitHub. Click it.
We are using Windows. We will download the Windows version.
We also need to download the latest version of Perl...P-E-R-L...I believe it is Strawberry Perl. Select this. Select the 32-bit.
Let us go to our downloads folder. Um both of these...let us install Radiance since it is already downloaded.
Okay. Make sure to click this option to add Radiance to the system path. Either for users or for current user. I will select "all users".
This is important because the Radiance measure in OpenStudio relies on the system path to find it.
Click next. Finish. Great! Now they are both installed. We should be good to go. Click save.
Now go to "run"...oh!...I am sorry...the last thing that we have to do, after installing Radiance and Strawberry Perl, is restart the computer.
We will do that now. Okay. We got the computer restarted. Let us re-run the simulation.
Okay. It looks like it is running successfully. Scroll back up here. Radiance runs through the lighting and shading simulation first.
Then it passes that information onto EnergyPlus to do the rest of the building energy model simulation.
You can see, at the very bottom here, it is removing the daylighting controls for the EnergyPlus run.
It has to remove those daylighting controls so that EnergyPlus does not try to overwrite the Radiance information. That is what it is doing there.
Radiance is simulating all of the illuminance and lighting power of the room first. Then, it is passing that information to EnergyPlus.
In order to access that Radiance information, we can go to the project folder where the OpenStudio model file (.OSM) is located. I believe it is this one here.
Open up the OpenStudio file folder. Go to "run" folder. It is right here: "Radiance Daylighting Measure Copy". Open up this folder. Open up the "Radiance" folder.
We are looking for Output..."Output". There are a lot of different files in here that are output from Radiance.
The two that I know about are the ".sql" and the ".csv".
You can use DView to open the SQL file. Right now, I already have it defaulted to open up with DView. You can open up DView first, then you would browse for this SQL file.
Let us open it up.
You can see that this is the output from Radiance. It is simulating the illuminance throughout the entire year.
It shows trends for Direct Normal Illuminance, Global Horizontal Illuminance, Daylight Sensor, and the average of the Illuminance Map.
Let us take a look at the Daylight Sensor and the average Illuminance Map.
You can see that the daylight sensor has quite a bit lower illuminance than the average of the illuminance map.
This likely because the daylight sensor, here, is just measuring a single point in space. The illuminance map is measuring multiple points all along this grid.
It is averaging those out. It might might mean that daylight sensor should be located in a better position. It is dependent on how the occupants are located throughout the room. Where the light is specifically needed.
We can take a look at this...um...the setting is for this daylight sensor. We will have to edit the space, select the sensor.
The illuminance set point is about 46 foot-candles (495 Lux) at that point in the room.
You can see that it is maintaining that approximately 50 foot-candles (538 Lux).
You can see that the the average for the entire room is quite a bit more than the 50 foot-candles at that one point.
We can take a look at some other things...we can go to daily...and heat map. There are different ways to view the data.
You can see that based on the sun's position on the horizon...finally, you can look at the monthly profiles of the lighting.
Let us take a look at the "CSV" file. I am not sure what these others are...
Let us take a look at the csv file. I has a bunch of different statistics...based on how you want to measure the the lighting (illuminance) within the space.
So, that is how you input daylighting controls, Radiance glare sensors, and illuminance maps using the SketchUp Plug-in. And, how to run the Radiance measure in OpenStudio.
Thank you! Please like and subscribe.
16. OpenStudio SketchUp - Merge Spaces from External File
We discuss how to use the SketchUp Plugin user script: Merge Spaces from External File. This can also be applied as a measure downloaded from the Building Component Library. This script/measure is helpful for merging a file with only geometry/spaces to a template file that contains constructions, schedules, loads, and space types.
Transcript:
Today we will talk about a useful user script. If you go to Extensions, OpenStudio User Scripts, Alter or Add Model Elements; it is called Merge Spaces from External File.
This user script is very similar to doing New OpenStudio Model from Wizard. You use it if you want to use your own template files as a library to begin the project.
Right now, we have an empty template file. The template file is empty of geometry.
If we go to the Inspector Tool, we can see that this template file does have space types. It has schedule sets and constructions. It also has loads. It does not have any geometry.
We have another file that contains the geometry. This has just geometry and space types. We can look at Render By
Construction. Look, it has no constructions.
Rendered by Space Type; it has no space types. But, it does have spaces and it does have geometry.
We can look in the the Inspector Tool...we can see that that it does have 48 spaces. We can clearly see that it has geometry.
To merge these two, the one with the geometry and spaces to the library template file, open up the template file. Which we have done.
We can save this template file as our project. We will call it "project". Save.
Now, go to the Extensions menu, OpenStudio User Scripts, Alter or Add Model Elements, Merge Spaces from External File.
We will select our OSM file that contains the geometry and spaces only. Click open.
It says the spaces have been imported and sometimes this takes a while...
Okay. It says it was completed. It has imported the information from the geometry file.
I am not sure why this is here...it must be left over from the previous time I had run the measure.
Let us check it out. We have the geometry imported into the template file. We can look at render by construction. We can see that there has been a construction applied.
That is probably because in the template file, under our default for the facility, there are default constructions, space types, and schedule sets.
If we look at the Rendered by Space Type, it will probably say all of these are the default space type. A lodge bunk room. Yeah.
Now that we have imported the geometry, we can go through and start assigning space types to our model.
For instance, this would be a...I am sorry...let us select Render by Surface Type...
We will select this space here. It is a kitchen. We can apply the Kitchen space type to it.
Go back to Render by Space Type...and see that the space type of Kitchen has been applied to this space.
So, that is how you import geometry into a template file that contains all of your constructions, schedules, loads, and space type templates.
Alternatively, you can use the OpenStudio measure. First let us take a look at the geometry tab on the template again.
Again, this is a template file so it contains all of your schedules, materials, loads, and space types, but it does not contain any geometry.
If you go up to Components and Measures...sorry...um...go up to Components and Measures, Apply Measure Now.
You can download a measure from the Building Component Library...it is located under Whole Building, Space Types. It is called the same thing: Merge Spaces from External File.
You can input the file path to the OpenStudio file that contains your geometry. You can select any number of options for importing that geometry.
That would be how you run the measure in OpenStudio.
Thank you! Please like and subscribe.
17. OpenStudio SketchUp - Assign thermal zones automatically
In today's video, we will be using the OpenStudio User Script: Add New Thermal Zones For Spaces With No Thermal Zone.
Transcript:
Good afternoon.
Today, we are going to teach you a very quick tip.
A very good tip.
A tip on how to assign thermal zones in a few clicks. To all these spaces at once.
Let us start. First, let us select our model. Next, let us go to the Extensions menu, Open Studio User Scripts, Alter or Add Model Elements, Add New Thermal Zone For Spaces With No Thermal Zone
Select it, click, and wait.
All spaces are now assigned with thermal zones.
Realize that some thermal zones have similar colors, but the program understands them as different and unique thermal zones.
OK?
This was the tip for today on how to reduce modeling time by assigning thermal zones to all spaces that are not assigned to a thermal zone.
Thank you! Please like and subscribe.
18.OpenStudio SketchUp - Adding overhang elements in a few clicks
In today's video, we will be adding overhang elements to all or select sub-surfaces of the model in
few clicks. These elements, also known as awnings, brises, or exterior shades aim to minimize the incidence of direct solar radiation to the windows.
This strategy helps to reduce the thermal load, thus minimizing the energy use of active air conditioning systems.
Transcript:
So let us look at another quick and useful tip in a few clicks.
Today, we are going to be inserting window overhangs to the top of the windows.
These are also known as horizontal brises, exterior shades, or awnings.
These elements are essential to minimize the incidence of direct solar radiation on the window surfaces.
It will minimize the thermal load.
To begin, our first step will be to select the model.
Select the spaces to which we want to add the shades. We will select all spaces.
Now go to Extensions, OpenStudio User Scripts, Alter or Add Model Elements, Add Overhangs by Projection Factor.
It gives us these options that are related to the dimensions of the windows.
They will serve to make edits to the overhang elements in our model.
The first dialog box (Projection Factor) refers to how far the overhang projects from the wall. It is a percentage of the window height.
The value of 0.5 means it will project at 50% of the window height. That will be its length.
The Offset corresponds to the vertical distance the overhang will be above the window. It is measured from the top edge of the window.
Again, it is a percentage of window height.
Click "OK".
We will have the following result.
Note the overhang elements.
These elements were created from the characteristics assigned in the dialog box.
The previously mentioned Offset corresponds to the distance from the top edge of that window to where you want to install it.
We will be changing it to see how the shortcut works again.
We will again select our model.
Click on extensions.
Repeat the same steps as before.
However, as we had already added overhangs we will need to replace them.
Let us keep this; the size is 50% of the window or sub-surface height.
For the offset value, we will assign 0.2.
And now we select the True option, because now we want to replace the old overhangs with the new ones.
Click "OK"
Notice a vertical distance.
We now have a greater vertical distance from the top of the window.
Let us do it again as an example.
Select as true.
We will remove this vertical offset.
We will add another 20% to the size of the overhang element.
Realize that the vertical distance no longer exists.
And we obtained an increase of 20% in the length of the overhang element.
This was a quick instruction on how to use the OpenStudio User Script for adding overhangs to your windows.
Thank you! Please like and subscribe.
19. OpenStudio SketchUp - Adding Photovoltaics
Today we will be adding photovoltaic systems to the energy model. We will prepare the model to
receive the system, we will observe some fundamental details in the insertion and investigate the
effects of the fraction of the area occupied by the photovoltaic system and its efficiency.
Transcript:
Good afternoon folks, we are back again, learning about energy modeling.
We are using the SketchUp extension for Open Studio.
Today we are going to be learning how to implement a simple photovoltaic system. We will also run the model, look at the results, and make some comparisons.
A photovoltaic (PV) system is a system capable of converting solar energy into electrical energy, explaining it in a very basic way.
Our aim here is to use this type of system for our model.
To begin, let us first prepare a surface to receive the photovoltaic system.
We cannot use any surface. For this user script, we will be applying the PV to a shading surface.
Our first step is to use the "create shading surface group" tool.
Select in the model a surface to apply the shading element. It will be our PV system.
Validate by pressing the "Enter" key. We will not draw the PV system.
The shading element should have the same shape as the photovoltaic (PV) system.
So when you think about your photovoltaic system, think about its shape when you are drawing it.
To simplify the progress of this video, we will not discuss optimal orientation (the best orientation for capturing the most sunlight).
We have created the shading element. It is important that this dark purple tint is facing outward.
If it is not outward, it is necessary to invert. If necessary: select the face, right click, reverse faces.
We will extrude our surface to a box to give it some depth. (Alternatively, you can use the move tool to position the surface a little higher.)
Okay. Now we will assign the photovoltaic (PV) system. Select the shading group and select the surface.
Go to "Extensions", "OpenStudio User Scripts", "Alter or Add Model Elements" , "Add Photovoltaics".
We have a dialog box with 3 options. The first option is choosing a load distribution center. It is the control center for metering and managing the PV system.
We do not have a distribution center, so it is necessary to create it. Leave this as default.
The second option describes how much of the surface is covered with PV cells.
As shown on the screen, the value is specifying that 100% of the photovoltaic system will occupy the shading element.
If we only assigned 50%, the value to be specified would be 0.5.
The program would understand that only 50% of the system would occupy the shading element. We will leave the default value.
The third option tells us about the conversion efficiency of the PV. The conversion of solar energy into electrical energy is not 100% efficient.
It does not convert all of the sunlight into electricity. The default efficiency is 20%.
Depending on the manufacturer, the percentage of efficiency can be different.
We will leave it as a default. We click ok.
You can see now that the photovoltaic system is assigned to the building.
In the model, this system could be in any position.
But, strategically it is positioned on horizontal surfaces or even with a certain angle. That will capture the most solar radiation.
The next step is to simulate. We open the model in Open Studio and run the simulation.
And we will evaluate in the simulation results.
We are going to add a report measure to be able to evaluate the energy produced by the PV.
How much electric energy is consumed by the building and how much is generated by the PV.
For this model, simple internal loads were used such as lighting and electrical equipment. They are there so we can test the photovoltaic model.
The measurement report is already added.
We are using the International measurement system (Phillipines version). Let us run the simulation.
We were successful in our simulation. We will evaluate the report.
According to the "Building Summary", we see our model has a total demand for electricity. There are internal loads generating this demand.
Let us look at the "Renewable Energy Source Summary". This is electricity produced by the photovoltaic system that we added.
Where the photovoltaic system would occupy 100% of the shading element. It has 20% efficiency.
The system is capable of generating an electricity equivalent to 9,816 kWh.
This results from the characteristics that we previously assigned.
We can also see in the "Site and Source Summary" guide.
Here we have the electric energy demand of the model. Below we have the "Net Site Energy". It is a difference in energy consumed and produced.
The energy being consumed minus the energy generated from the photovoltaic system.
Of course, we will not find exactness in values if we do the calculations.
There are distribution and energy conversion losses. These losses add up from the PV array, to the electrical wires, to the DC to AC conversion, and finally the reactive losses going to the electrical grid.
These factors are used to estimate approximately. They are, in general, reliable esimates.
We are now going to change the characteristics of the photovoltaic system and re-evaluate those numbers in the report.
Let us memorize this amount of electricity produced so that we can compare it later.
This generated value corresponds to a fraction of 100% of the shaded area is solar cells and they operate at 20% efficiency. We will change these values.
Go to "Extensions", "OpenStudio User Scripts", "Alter or Add Model Elements" , "Remove Photovoltaics".
First, let us remove the existing system. Click "Yes" to remove it completely.
We are now going to assign a new photovoltaic system. Let us change the fraction of the photovoltaic plate.
Efficiency will remain at 20%, so that we can compare with the numbers we already have. Click ok.
Save the model and reopen it in the Open Studio application.
Now let us simulate again.
We were successful again. We will evaluate the report again.
The system generated 4,908 kWh of electrical energy.
This value corresponds to exactly half of the energy produced that we had previously.
As we reduce the photovoltaic system by 50%, we will also reduce 50% of the electricity generated.
And that is exactly what was expressed in the report.
We will now work with efficiency. By default, the program uses 20% efficiency.
We are going to increase the efficiencies to obtain new values of electric energy.
Again we are going to edit. Every time you edit, you need to click on the surface and remove the existing system as we did previously. It allows you to deploy a new system.
This time we are not going to touch the fraction of the area, but the efficiency.
We will add an additional 20% efficiency to our system, resulting in an overall efficiency equivalent to 40%.
We click "ok". Save it. Re-open it in Open Studio. (You can search for the file or just use "Revert to Saved")
And we have it opened again.
Recall that we are investigating the influence on the efficiency variable of the photovoltaic system.
We will run the simulation again.
Simulation finished. Let us evaluate the results. Go to the "Renewable Energy Source Summary".
And we observed that the value of electric energy produced is now approximately 19,633 kWh.
In the first simulation, when we had simulations with the characteristics of 100% area fraction and 20% efficiency, we obtained a value of 9,816 kWh.
Realize that the value of power generation has increased and this increase is justified by the 20% increase in efficiency that we used this time.
It is clear that our changes affected the simulation.
So, that is basically it. It is the way to add photovoltaic systems to energy models.
There are many factors to be analyzed when designing a photovoltaic system.
This SketchUp OpenStudio User Script allows you to easily customize the dimensions and simple performance parameters of a PV system.
It will allow you to quickly evaluate performance of a photovoltaic system.
I thank you all, I ask you to subscribe to the channel, enjoy the videos and don't forget to click on the notifications to receive whenever we post new videos.
20. OpenStudio SketchUp - All About Shading Surfaces
We'll cover the three categories of shading elements available in the video and when to use each one. We will assign construction materials to the shading elements as well as transmittance schedules. The model will be simulated and the properties will be evaluated in the HTML report made available by the program after the simulation.
Transcript:
Guys, we have more video.
In this video, we will address the three categories of shading surfaced that the program has for use in simulations.
We will also cover some 'user scripts' tools.
And finally we'll simulate the model.
For a start, let's first assign some shading surfaces using the 'new shading surface group' tool.
Let's implement a shading sruface at this position and let's validate it with the 'ENTER' key.
Using the line tool.
Let's sketch an eave for this roof.
First elaborate a shading surface.
Let's imagine a neighboring building next door.
Let's validate with the 'ENTER' key.
Let's use the rectangle tool.
Let's create this shadow element, representing a neighboring building.
We will also imagine that at the front of our building there is a tree.
Let's use the rectangle tool to shape our tree.
Let's draw the tree.
Drawn tree, now let's cut it.
Let's reposition the tree closest to the building.
We already have three shading surfaces in the model.
Let's select the model
Using the tool we used before.
Let's add horizontal window shades through the 'user scripts' tool.
We are asked to specify the relative projection of the shade.
The relationship is proportional to the size of the window (sub-surface).
For this situation the value is 0.5, it means 50% of the window size.
The 'offset' represents the distance from the shade element to the window. For this situation we will place it at the very beginning of the window, at the top. The value will be '0'.
We validate and wait.
Note the difference in tonality of this shadow element to the others.
This difference is something purposeful in the program, it does not represent any anomaly.
The program is claiming that this shading element differs from the others.
From there, we will start the explanation. Why is there such a thing?
When we click on the shading element that represents the neighboring building, we notice that, through the 'Inpector' tool, we see a dialog box with three options.
Option 'site', 'building', 'space'.
These options each have a purpose.
Suppose we are going to use the 'site' type.
Notice that the hue has changed.
This neighboring building belongs to the site.
However, it belongs to the 'site' type, as this type represents elements that represent the location, that is, they are not linked to the building.
This reasoning is also valid for the tree.
When we look again at the 'Inspector' tool window, it can be seen that the tree was characterized as 'building', but it is of the 'site' type, as it belongs to the site.
Let's change the element name to make it easier to understand when we are going to assign the constructs in the 'Open Studio' app.
Let's also change the name to this one here.
When we click on this element that represents the eave, we notice that it is of the 'building' type. This attribution is true, as the element belongs to our building.
Suppose the building rotates, this element will rotate with the building, because it is an element belonging to the building.
We also look at this other 'space' type.
This type performs the assignment of the shading element to a space.
This simply makes it convenient to edit all shading elements associated with a space.
So the function of type 'space' is association of the shading element to space.
After this information.
Let's export the model to 'OpenStudio', let's load the app.
Tool loaded. The first step is to check the integrity of the geometry.
Let's make sure the placement of the shadow elements is correct.
The eaves, the extension of the roof.
And check the horizontal brises.
Everything is in its place, we only observed this anomaly in the roof color, but it will not interfere with the simulation.
Let's click on the 'facilites' tab.
We click on the 'shading' sub-tab.
Note that we have listed the shading elements we created in the model.
There are these three elements here, but they are empty boxes that we forgot to delete, but it won't influence the simulation.
Let's stick to these other elements.
Here we have the tree, which we named in 'SketchUp'.
The tree can receive a broadcast schedule.
We can also assign a material to the tree. For this situation we would assign wood to the tree.
At this point we have the neighboring building.
This neighboring building can also receive material, for this situation we will imagine it to be concrete.
We also have the eaves, the shading element that is part of the roof.
To this element we can also assign a construction of concrete, metal or something that can serve as a shading element.
To do this, we must add constructions, let's do it.
We click on the 'constructions' tab, 'construction' sub-tab.
Note here that the constructions had already been created.
Let's delete.
And let's do it again.
The first construction will be for the neighboring building, remembering that it is a 'site' type.
Let's name it 'site_building'.
As we think of a concrete building, let's drag a material from the library that looks like concrete.
For the tree, it is also a 'site' type.
For this element, let's generalize just like wood.
We drag from the library and let go.
For the eave, the part of the element that makes up the roof.
For this part we can name the type 'building'.
It will also be made of concrete.
Now let's create one more element for the 'space' type.
These elements are the exterior window shades, which are at the top of the windows.
We can attribute to these elements some material similar to metal, wood. For this situation we will assign them to be metal.
After creating these constructions, it's time to characterize the shading elements.
It is noteworthy that these materials that we are using randomly to only try to approximate their real composition.
However, there is a way to edit the properties of these materials and there is a library available in case you need something more specific.
Now let's go back to the 'facilites' tab.
Beside, let's select 'my model' and look for the buildings.
Let's evaluate the tree first.
We click on the construction made for the tree and drag and drop it to characterize the tree.
Let's now do it for the neighboring building, look at the six sides of the building.
Let's assign each face to the concrete construction made.
The attribution of the name was purposeful to facilitate identification and characterization.
That kind of 'building'.
We attribute 'building'.
The 'space' type is not available here.
However, when we go back to the 'constructions' >'constructions set' tab., note here the option for other constructions to assign the type 'space'.
Let's assign the construct of type 'space' here.
There is the possibility of assigning the other types here too, however in our model we have two similar types of shadow, but with different construction material, we will not make this assignment here due to material standardization.
Due to this condition, we carried out the characterization of the materials in the 'facilites' tab.
All materials have been assigned to the shading elements. Let's look at the transmittance schedule now.
There is the possibility of drawing up a transmittance schedule. This schedule fits in cases where the element may vary depending on the season, environmental variables or some factors.
For our case, we have the tree.
The tree does not have its full foliage every day of the year.
There is a period that the tree has a certain transmittance value and another period that has a different transmittance value.
This variation can be described to the program so that it implements these conditions in the simulation.
Let's now work out this transmittance schedule for the tree.
We click on 'schedules' tab > 'schedules' subtab.
Let's create a fractional schedule.
Let's name it 'tree'.
To facilitate the assignment. By default we will assign 0.9 transmittance.
In other words, if none of the conditions that we will implement are not met, the program will use this default value for the routine.
The program will understand that there are 90% of the passage of sunlight.
Now let's implement the tree condition. A period that it has leaves and a period that has no leaves.
There is a period that starts in the spring where we have the date March 20.
Let's assign this date, so on this date let's consider that the tree has a transmittance of 0.1, that is, it has almost the full volume of the leaves.
And during the period the leaves fall until there are no more leaves until the spring period.
That begins on the September 23.
This period the tree has the leaves.
Outside this period it doesn't have leaves
Let's assign these conditions to the summer design conditions. In the summer, there is a transmittance of 1.
That is, there is no tree, or in the winter the tree was cut.
Anyway, there are these two situations that are the days of 'design'. The worst possible case.
There is this priority, there is this information that during this period which corresponds to March, which corresponds to the period of spring, summer and early autumn that the tree has leaves and later it loses foliage during autumn and winter.
The schedule has now been drawn up, and there is a pattern for the whole year and during design days.
To start the simulation we will need to configure the solar distribution in the simulation control.
We need to consider Solar Distribution with Reflection effects, we have the option to only consider exterior only, interior only or both. Let's assume it's both.
After this configuration, we check the schedule and go to the 'facilites' tab to assign the schedule we created to the tree.
Right here the schedule. Let's go back to check. There is even another schedule, but it is not edited. The valid schedule is this one.
Finally we assign the transmittance schedule to the tree and buildings. Now, let's simulate the model.
We were successful in the simulation, let's show the results through the HTML file.
Through the property we can observe the visible solar reflectance values of the elements that we implemented in the model.
Here the exterior window shades are represented, they received a metal construction, all this information corresponds only to the brises.
Here we have the local elements.
Here we have all the values related to the created elements, these transmittance values directly affect the energy performance of the building.
They also affect the program's energy balance calculation.
So this was another video showing the details of the shadow elements.
Subscribe to the channel, enjoy the videos, activate the notification bell to be informed when new videos are available on the channel.
21. OpenStudio SketchUp - Assigning Stories
In this video we will present a quick and efficient way to characterize the building's floors. For the characterization of the floors, we will use another one of the Users Scripts.
Transcript:
Let's see another quick tip on the channel.
Today we will learn to use one more tool from "Users Scritps".
Today we will quickly assign the floor numbers (stories).
The first step will be to investigate whether the building already has the stories assigned.
We will maximize the "Inpector" window. Let us look at the first floor.
Note that there is a number assigned.
Moving upward...
For that floor too.
And to the top floor too.
Suppose we forgot at the time of modeling to assign stories to these floors.
The simple way to resolve would be.
First step....
But first, I will erase those stories already assigned.
So that we can use the tool.
That will save time for assigning these floors.
Now we don't have the floors anymore.
All assignement of the floors are removed.
Returning to the first step...select the complete model.
Let's minimize the "Inspector" window.
After selecting the model, we will click on extensions.
We click on "Open Studio User Scripts"
We will now click on change or add model to the element.
And finally, we're going to use our next tool.
Assign floors to the building.
Let's wait for the program to perform the assignment.
Of model.
Let's check if the model was assigned stories.
Let's maximize the "Inspector" window and click here.
Notice that the model was assigned.
The assignment can be done manually.
Clicking.
Adding.
Manually.
And selecting the desired space to receive the assignment of the floor, in this case the fifth floor.
And changing it here in the checkbox.
Then these changes can be made manually or automated.
Automatically, the program understood that the building has only four floors.
If any space specification per floor is required, it can be done manually.
Thanks!
Don't forget to subscribe to the channel, like the videos.
And activate notifications, because whenever you have new content you will be notified.
22. OpenStudio SketchUp - Cleanup Origins
In this tutorial, one more functionality of the user scripts extension will be covered. Let's learn how to resize the available space in relation to the space needed. It should be noted that it is a practical tool to use, but you should pay close attention to how you use it.
Transcript:
Let's start another video of the series "User scripts"
We know they are important tools that save time. These are tools that are often effective. However, sometimes you need to be careful when using them.
Today we have our building and we have a problem where the space origins are located way out of the space.
This is really a visual problem, but it can be confusing and difficult to work with.
A quick solution to this kind of problem is through the extension of the "User scripts", "Cleanup Origins".
However, before we start this procedure, let us save the model. We will also check for any errors or warnings.
There are no errors or warnings on our project.
This procedure can be done for a single space, but for our model we will do it for all spaces.
Our model has many spaces that need to be modified.
Let us select the template, click on extensions, Open studio "User Scripts", Alter or Add Model Elements, Cleanup Origins.
The program has completed executing the command. Note the confusion. Most of the time this is not a problem.
Let us save the model and reopen it again.
All origins have been fixed. They have been readjusted to fit within the spaces.
It is very important to pay attention to the errors generated by this procedure.
It is necessary to check whether these errors exist.
For verification, it is good to use the Inspector tool and error information. Let us check if there were these distortions or changes in the model.
Resolving errors is essential to avoid problems in simulations.
Finally, this is another video from the series "User Scripts"
I appreciate everyone's attention and don't forget to SUBSCRIBE to the channel.
Thank you all.
23. OpenStudio SketchUp - Export Selected Spaces to a new External Model
In this episode, we discuss the OpenStudio user script "Export Selected Spaces to a new External Model". It is used to eport geometry and space type information into a completely new, separate, OpenStudio model for further analysis of different thermal zoning patterns and/or HVAC systems.
Transcript:
Today we are going to talk about another useful user script. It is located under extensions, openstudio user Scripts, alter or add model elements.
It is called "export selected spaces to a new external model"
You can see that we have a model with various different spaces in it.
If we take a look at the osm file, you can see that it has a weather file assigned. It has some schedule sets. It has construction materials. It has people, lighting, and gas loads.
It has some specific space types. In the spaces section, you can see that it has spaces assigned.
You can even see that we have assigned some thermal zones and associated with those thermal zones we have assigned some HVAC systems. This is a fully complete model.
If you wanted to export some of these spaces or even all of these spaces to a separate model and create a different thermal zoning pattern or different HVAC systems, you can use this measure.
We can select multiple of these spaces and export them to an external model.
Or, we can we can even select all of them and export this to a an external model for further analysis.
We will select all of the top floor...sorry...all of the top floor spaces.
We will export these to a separate file so that we can analyze it and assign a different type of HVAC system.
It will allow us to see how this first floor operates using different scenarios.
Go to the user scripts, alter or add model elements; "Export Selected Spaces to a new External Model
It says it was successful. It created a new model with 36 spaces in it.
Let us open that up. You can see that it has those 36 spaces exported.
It even has the space types and it has the people and lighting loads associated with those.
If we look at the geometry, you can see that we we exported that Upper Floor.
However, if we look at the thermal zones tab, it did not export any of the thermal zones.
If we look at the HVAC tab, you will note that it did not export any of the HVAC systems.
You can think of this as a a seed model for doing analysis on this Upper Floor.
You can assign these different spaces into different thermal zones and by assigning different HVAC systems to run this separately.
That way, you can see how the system operates with different parameters.
That is how you export geometry to another model. Again, it is extensions, openstudio user Scripts, alter or add model elements, and "Export selected spaces to a new external model"
Thank you! Please like and subscribe.
24. OpenStudio SketchUp - Merge Spaces From External File
In this episode, we discuss the OpenStudio user script "Merge Spaces From External File". It is used to import geometry and space type information into an existing OpenStudio model for further analysis. This measure is useful for combining buildings into a large campus model for analysis of shared HVAC systems such as a central heating or cooling plant.
Transcript:
Today we are going to talk about another useful user script. It is located under extensions, openstudio user Scripts, alter or add model elements.
It is called "export selected spaces to a new external model"
You can see that we have a model with various different spaces in it.
If we take a look at the osm file, you can see that it has a weather file assigned. It has some schedule sets. It has construction materials. It has people, lighting, and gas loads.
It has some specific space types. In the spaces section, you can see that it has spaces assigned.
You can even see that we have assigned some thermal zones and associated with those thermal zones we have assigned some HVAC systems. This is a fully complete model.
If you wanted to export some of these spaces or even all of these spaces to a separate model and create a different thermal zoning pattern or different HVAC systems, you can use this measure.
We can select multiple of these spaces and export them to an external model.
Or, we can we can even select all of them and export this to a an external model for further analysis.
We will select all of the top floor...sorry...all of the top floor spaces.
We will export these to a separate file so that we can analyze it and assign a different type of HVAC system.
It will allow us to see how this first floor operates using different scenarios.
Go to the user scripts, alter or add model elements; "Export Selected Spaces to a new External Model
It says it was successful. It created a new model with 36 spaces in it.
Let us open that up. You can see that it has those 36 spaces exported.
It even has the space types and it has the people and lighting loads associated with those.
If we look at the geometry, you can see that we we exported that Upper Floor.
However, if we look at the thermal zones tab, it did not export any of the thermal zones.
If we look at the HVAC tab, you will note that it did not export any of the HVAC systems.
You can think of this as a a seed model for doing analysis on this Upper Floor.
You can assign these different spaces into different thermal zones and by assigning different HVAC systems to run this separately.
That way, you can see how the system operates with different parameters.
That is how you export geometry to another model. Again, it is extensions, openstudio user Scripts, alter or add model elements, and "Export selected spaces to a new external model"
Thank you! Please like and subscribe.
25. Building Energy Modeling in OpenStudio - Troubleshooting 2
In this series of episodes, we discuss some common simulation warnings and errors found in the EnergyPlus eplusout.err file. We will discuss these errors, and show common strategies to resolve them.
Transcript:
In this series I am going to cover a lot of the most common errors associated with running OpenStudio models for the first time. It is very discouraging to run a model and get this error "simulation failed to run".
A lot of this just stems from improper inputs to the program.
To find this information on YouTube, go to YouTube and type in OpenStudio. Then, type in the error that you are getting.
For example: "requested number of time steps is less than" and then hit enter. I will have the video captions posted in the description.
You can find a lot of these error codes by typing in OpenStudio and then the error wording. If I discuss it, you should be able to find it.
For example, this error we just typed; you can see this in the description. It is also in the closed captions.
If you click on this it will go right to the video and discuss that error: "Requested number of time steps is less than suggested minimum"
Let us begin. Go to the folder where the OpenStudio file is...open up...we have our OpenStudio file here. OSM file. It also creates this folder with a bunch of output information.
We will open this. Go to run. Look for eplusout.err (it is an ".err" file). You can open this with a text editor as discussed in my previous troubleshooting video.
You will see that there are a number of warnings. There are also some severe errors.
Normally, the severe errors are what causes simulation failures. However, there are a few warnings that could significantly affect your model and they should not be neglected.
Normally, EnergyPlus will continue to run the simulation even, if you have just a simple warning.
But certain warnings could significantly affect your model, so some of these warnings should be treated as severe errors, even though it successfully runs your model.
Looking at the first warning; we have here "CheckEnvironmentSpecifications: SimulationControl specified doing design day simulations, but no design environments specified."
We can go back to our model. Look at the site Tab. We will look at our design day information. Here is the design day
information.
You can see that there was no design day specified. These are are the the design days for summer and the design days for winter.
The most extreme temperatures during the summer and during the winter.
You can see that there are none specified, which is why we are getting this design day simulation error.
So, we will have to import a design day file. We will just click any one of these ddy files. Again, these ddy files can be downloaded from the EnergyPlus website.
We can select that...you can also see that there is another error; "CheckEnvironmentSpecifications: SimulationControl specified doing weather simulations; run periods for weather file specified; but no weather file specified.
Looking at the weather file you can see that we did not specify any weather files for this. We need to set the weather file.
And, if we go back to the error file, you will see that there are a couple of severe errors here; "Weather Simulation requested, but no weather file
attached." and "GetNextEnvironment: Errors found in getting a new environment.".
The first one says there was no weather file attached. We solved this already.
As stated in previous videos, down at the very bottom it gives you a summary. It will tell you how many severe errors there were
and how many warnings.
Now that we have added our weather file and design days, let us run the simulation again.
Okay. We successfully completed the simulation. Let us take a look at the error file again.
You can see that we no longer have those errors that we were talking about. We still do have a lot of other errors and warnings.
We will look at the first warning here; "Schedule:Constant="ALWAYS OFF DISCRETE"". Let us take a look at the osm file.
Open this up with the text editor. We will search for the "ALWAYS OFF DISCRETE".
You can see that it did not return any Search terms. That is because this ALWAYS OFF DISCRETE schedule and ALWAYS ON CONTINUOUS schedule are not located inside the osm file.
They are added when the OpenStudio file is translated to EnergyPlus. That means there is nothing you can do about these warnings.
In fact, these warnings are not very important to pay attention to. They are schedules that OpenStudio uses for scheduling equipment always on or always off.
Those schedules get applied once the OpenStudio file gets translated to EnergyPlus.
Let us look at the next warning; "CheckUsedConstructions: There are 11 nominally unused constructions in input." and then it says "For explicit details on each unused construction, use Output:Diagnostics, DisplayExtraWarnings;".
This display extra warnings object used to be toggled using a measure that you installed on the measures tab in OpenStudio. In the latest releases, they have placed this option under the simulation settings menu.
Let us got to simulation settings and scroll down. Click enable display extra warnings. We will re-run the simulation.
The simulation was run successfully. Let us go back to our error file. Reload it. You can see that it now shows the 11 constructions that were unused.
We can take a look at these constructions in our osm file. Go to the constructions tab.
You can see that these constructions are located in our construction set. Why are these constructions not being used? They should be used.
They are in our construction set. We can check to see if this construction set is being used in our space types.
We do not have it applied to our space types. We do have it applied at the facility level.
We do have the construction set applied at this facility level. These construction materials should be used in our model.
Let us go to the thermal zones tab. You will notice that we do not have any thermal zones assigned to the model. This is a problem.
While we do have a lot of spaces in our model, we do not have any thermal zones. Thermal zones are what actually gets passed to EnergyPlus for simulation.
OpenStudio collects all of the spaces into different thermal zones. It combines multiple spaces into a thermal zone.
Those thermal zones are what get passed to EnergyPlus for simulation. So, essentially, we are sending an empty model to EnergyPlus.
We need to have at least one Thermal Zone in our model. Click plus down at the bottom to create a Thermal Zone.
Go back to our spaces tab and assign all of those spaces to that Thermal Zone.
Go to my model tab, thermal zones, and drag in that Thermal Zone that we just created. We will apply this to all of the spaces. Now, all of the spaces are located in this Thermal Zone.
This Thermal Zone will get passed to energy plus for simulation. Let us run the simulation again.
The simulation was run successfully. Let us look at the error file again. Update it. You can see that we no longer have the unused materials and construction sets.
Another error has popped up; "Timestep:Requested number (1) is less than the suggested minimum of 4. Please see entry for Timestep in Input/Output Reference for discussion of considerations.
This Input/Output Reference manual is an important document in EnergyPlus. It describes all of the inputs and the outputs that are contained within the program.
The Input/Output reference manual has been discussed in previous videos on YouTube. Go back to our OpenStudio model.Go to the simulation settings tab.
We can adjust the number of time steps. This is the number of time steps per hour.
This is the number of times the simulation is run in a block of time. We currently have one time step per hour. The simulation is run for each hour of the year.
The error file is recommending that we have at least four time steps per hour. We can change this to four. That equates to a 15 minute time step. The simulation will be run for 15 minutes, then it is run for another 15 minutes and so on for the entire year.
Click the Run simulation tab again. Click run. The simulation was run successfully. Go back to our error file. Reload it.
You can see that it removed that error. Now we have another warning; "ManageSizing: For a Zone sizing run, there must be at least 1 Sizing:Zone input object. SimulationControl Zone Sizing option ignored."
This is a problem. We are looking at Sizing:Zone objects. Let us look at the Input/Output reference manual for EnergyPlus.
Search for this term. This is the object it is called Sizing:Zone.
As discussed in previous videos, you can find this Input/Output reference manual on the EnergyPlus website.
We will search for that term Sizing:Zone. Click on the first search result. It takes us to the table of contents. Use the hyperlink to take us
directly there.
This Sizing:Zone object is needed to perform a Zone design airflow calculation for a single zone.
This error is saying is we do not have any HVAC system assigned to this Thermal Zone that would require a Zone sizing calculation. A system that would require movement.
Let us go back to our osm file. Click on the thermal zones tab again. You can see that we do not have any Air Loops assigned. No Zone Equipment assigned. No Ideal Air Loads assigned.
We can see that there is another error down towards the bottom of the error file. It says that we do not have "District
Heating Peak Demand" meters, we do not have any "District Cooling Peak Demand" meters.
This one; "Output:Meter: invalid Key Name="DISTRICTCOOLING:FACILITY"". So, we do not have any HVAC meters on this facility because there is nothing to meter.
We do not have any HVAC equipment assigned to that Thermal Zone that would use electricity or gas or district cooling or district Heating.
Let us turn on ideal air loads. An ideal air loads uses an ideal District Cooling and District Heating system to heat and cool this Thermal Zone.
Now it should compute the Sizing:Zone object. Re-run the simulation. It has completed successfully. Look back at our error file. Re-load it. Go to the top. You can see the Zone sizing error has disappeared.
As discussed previously, these are inherent schedules in the translation from OpenStudio to EnergyPlus. There is nothing we can do about these warnings.
Let us look at the next warning; "GetHTSurfaceData: Surfaces with interface to Ground found but no "Ground Temperatures" were input." It tells you
which surface this was first found in.
It will default to a constant 18°C annual ground temperature. This is saying is that we did not assign any ground temperatures for the model, so it is just going to use a default ground temperature of 18°C.
This is a pretty general temperature that works good for most models. However, if you are designing for extreme temperatures, for example in the
Arctic or potentially near the equator, those ground temperatures might be different than this value.
To adjust this, you would have to have a special measure used to modify this value. We can leave this as it is or we can modify
this just to get rid of this warning.
Either way, this warning is not a serious warning and it will not significantly affect your simulation.
Thank you! Please like and subscribe!
26. Building Energy Modeling in OpenStudio - Troubleshooting 3
In this series of episodes, we discuss some common simulation warnings and errors found in the EnergyPlus eplusout.err file. We will discuss these errors, and show common strategies to resolve them.
Transcript:
Let us look at the next warning in our eplusout.err file.
It says: Warning CheckConvexivity: Zone="Thermal Zone 1". It tells you what surface is applicable. It is non-convex.
What is convexivity? What is convex and what is non-convex? We will copy this text and search for it in the EnergyPlus input output reference manual.
It takes you to this bit of information. It describes convexivity.
It tells you that convexivity only seriously affects your model if you are running FullInteriorAndExterior or FullInteriorAndExteriorWithReflections.
What do these selections mean in OpenStudio? Go to the simulation settings tab...simulation control...solar distribution.
It gives you an option for how EnergyPlus will simulate the model.
Right now we only have FullExterior selected. It will only be modeling the energy effects of the Sun as it contacts exterior surfaces.
It will not be taking into account Sun Reflections going through windows and bouncing off floors and walls.
If you want to model full solar effects that go through windows and bounce off the inside of the spaces, you need to select FullInteriorAndExterior or FullInteriorAndExteriorWithReflections.
If you are modeling just FullExterior, you don't have to worry about these non-convexivity issues.
Let us go back and take a look at what exactly convexivity is.
In a nutshell, this shows convex zones and non-convex zones.
Definition Convex Zone: a light Ray will only pass through two surfaces as it enters and exits the zone.
Definition Non-Convex Zone: a light Ray would pass through more than two surfaces.
You can see, for example...if this light Ray went through this wall right here and it might pass out through this wall right here. It only passes through two surfaces.
Whereas, this right right Ray might pass through this window right here and it might go out through this wall and it might go in through this window and then it might also pass out through this wall.
It is non-convex because it is actually transiting one, two, three, four surfaces. A convex Zone would only pass through two surfaces.
That is the definition of a convex Thermal Zone. And non-convex Thermal Zone.
If you take a look at our building, you can see that there are a lot of spaces that we have here, but all of these spaces are grouped into only one Thermal Zone.
That one Thermal Zone...all of these spaces get combined into one big Thermal Zone and they get sent to EnergyPlus.
You can see that our building is actually quite non-convex. If you drew a line passing from one side of the zone to the other you can see that it passes through multiple surfaces.
That is what this warning is telling us. If you do have zones that are non-convex; you are going to get a warning.
There are also non-convex surfaces as well...I will talk about those in just a minute.
As mentioned, if you are only modeling full exterior you do not have to worry about these these non-convexivity errors.
Let us now discuss convex and non-convex surfaces. This is saying that we have a surface number 100 which is non-convex.
We can search for the surface 100 in our .osm file. You can see that this surface 100 is composed of one, two, three, four, five vertices.
We can search for the surface 100 in SketchUp. Go to surfaces...and...surface 100.
Usually...you can see it highlighted here...it is surface 100. You can turn on visibility x-ray mode to see it better. Sometimes...
Otherwise, you can go to Edit, Face, Select, All Connected. That gives you a better idea of what it is connected to.
It is connected to this zone. Double click to edit this Zone. Look at surface 100...this roof ceiling right here.
You can see that it has one, two, three, four, five vertices.
This could be a problem if all of the vertices are not quite on the same plane.
According to this, they all have the same Z coordinate. But it is rounded to the third decimal place.
If they are not on the same plane...one of these vertices is not on the same plane...you end up with a surface that is not completely flat.
This confuses EnergyPlus. It is not a serious error. It will not really affect your energy model unless you have a very serious (curved) non-convex surface.
If you want to get rid of this error, you can simply connect some of these vertices.
Preferably, you would connect them into triangles; like this. That way you do not have a surface that is in the shape of a letter U (saddle, hyperbolic geometry).
That is how you get rid of that error. You could do this for every one of these non-convex surfaces.
Surface 159, Surface 175, Surface 172...you could just connect all the vertices...
Okay. We have edited those surfaces that were in the error file. You can see that we added all of the triangles to those surfaces.
Reload the model...we will save the model in SketchUp...reload the model in OpenStudio. Run the simulation again. The simulation was successful.
Let us go back to our error file. Reload it. You can see that those errors got removed.
Let us look at the next error. GetVertices: Distance between two vertices < .01, possibly coincident. It shows the surface number and the associated Thermalzone.
It says that there is a Vertex 5 and vertex 4. You can see that the difference between these is less than 0.01. It says it is going to drop vertex 5.
Let us take a look at this surface 200. Go to the OpenStudio inspector. Go to surfaces. Browse for surface 200. Here. This one. It is a floor.
Double click to edit this. Take a look at this. You can see that it does have multiple vertices...five vertices.
If we zoom in on this see that these two vertices are are very close to each other.
This could have happened when we were tracing the floor plans. Our polygon ended up with this extra fragment here.
That is what this error is saying. It is saying that these two vertices are very close to each other.
They are so close to each other; EnergyPlus is saying it will just delete this vertex five.
I would guess that it is probably doing the same thing for surface 209 on the top.
If we look in the error file...yes...it does say that surface 209 has the same same problem.
Because those vertices are so close to each other, EnergyPlus is saying it will just get rid of these vertices. And it will continue with the simulation.
Clearly this is not a very significant error. It will not destroy the model, so EnergyPlus continues to simulate.
The error is not going to have a big impact on your energy model.
But, if you did want to resolve that error...draw a line between the two vertices...you can see that this axis is swept inward.
To fix it, simply select this line and click the move button. Move it that way. That solves the problem.
It solves the problem for both the floor and the roof surfaces. That is how you solve that problem.
Again, it is not a major error. But, if you want to get rid of those errors, that is how to correct them.
Now that we have solved all those, let us go back and reload and rerun the simulation. It was successful.
If we go back and look at the error output file; you can see that all of those non-convex errors have been resolved.
That is enough for today. We will continue this series of videos troubleshooting errors in future episodes.
Thank you! Please like and subscribe.
27. Building Energy Modeling in OpenStudio - Troubleshooting 4
In this series of episodes, we discuss some common simulation warnings and errors found in the EnergyPlus eplusout.err file. We will discuss these errors, and show common strategies to resolve them. Errors in this episode: 1. CalculateZoneVolume: The Zone="THERMAL ZONE 1" is not fully enclosed. To be fully enclosed, each edge of a surface must also be an edge on one other surface. 2. The surface "SURFACE 10" has an edge that is either not an edge on another surface or is an edge on three or more surfaces:
Transcript:
Okay, we are back here for another episode of troubleshooting the errors. We are looking at the eplusout.err file.
The next warning that we get is CalculateZoneVolume: The Zone="THERMAL ZONE 1" is not fully enclosed. To be fully enclosed, each edge of a surface must also be an edge on one other surface.
Then it says The zone volume was calculated using the opposite wall area times the distance between them method.
So, that is the first error. We are going to look atthis next one in a minute. These are two related.
Let us talk about this calculate Zone volume error. First we will go take a look at the model.
One of the things that we need to note is this model has a single Thermal Zone. Even though I have all of these different spaces, when this gets passed to EnergyPlus it becomes one big blob.
It is a combination of all of the spaces. It is an average of all of these different spaces.
If we take a look at this rendered by Thermal Zone, you can see it is just one Thermal Zone. There are no other colors.
So, this whole thing gets passed to EnergyPlus as a single piece of geometry. A single zone that would be controlled by a single thermostat.
But, it is complicated. There is complicated geometry. With this error "calculate Zone volume" EnergyPlus is saying the geometry is not fully enclosed.
EnergyPlus is saying there is a piece missing somewhere. For example, there is a hole or something in your geometry.
EnergyPlus is saying this is not fully enclosed. There is a hole somewhere, so it can not calculate the volume based on all of the surfaces.
So for example EnergyPlus will calculate the distance between, say, this wall here and this wall here and it multiplies it by the area of this wall.
EnergyPlus is assuming that this is basically just a rectangular Thermal Zone. But it is not. Therefore, EnergyPlus tends to make very big mistakes on this.
There are two ways to solve this problem. You can figure out where the hole is and try to patch it up.
But, sometimes that is not successful because the holes can be very small. Or, there could just be some mismatch in your lines that are connecting the spaces.
The other solution is to hard size the volume and the floor area. Basically, you would manually calculate what the floor area is.
Then, you would enter it in here; in the Thermal Zone in the Open studio inspector.
Then, you would calculate the volume and then hard size that right here.
How would you do that? You can have SketchUp do it for you! We will just open up another instance of SketchUp.
We will copy all of this. Click Control-A to select all. Control-C and copy this. Click Control-V to paste it in here.
Now we have our model pasted into another instance of SketchUp. Click Control-A to select everything and then right click and explode the whole thing.
That destroys all of our spaces that we created. It just makes the model dumb. All of these surfaces are at the very top level. It is all one big mixture of surfaces.
We will do a side view...and change the perspective...then go through here and delete all of the walls.
Delete all of the walls. This gets kind of tricky, especially if you have Windows...
I have most of it deleted...then you can open up the default tray, entity info.
Entity info. If you click on any one of these surfaces, SketchUp will show you what the area is.
You could go through and and add all of these up. Alternatively, you could have SketchUp calculate that for you.
We will just hide this for now. Click hide. Then, do a top-down view of this. Now we can just delete all of these floors.
Now it is one big floor. Then, if you just add one line here, it should connect everything up into a single surface.
Now, if you click on that surface, that will give you the total floor area. Right here.
12,435. Then, you can go into your model and hard size the floor area. Click hard size and then put in 12,435.
You can do the same thing for volume...if we do unhide all...unhide all.
If you unhide everything...you would still need to go through and delete these windows and stuff...
So, assume we deleted all the windows; then you start connecting this together into one piece of geometry.
You may have to delete all of these ceilings too. Once you have the whole thing patched up into one big piece of geometry...
You should be able to click on it and SketchUp will tell you what that volume is.
I will do a sample here....just delete most of this here...just focus on this here...well this is kind of an odd shape...
I will just show you something real quick. I will just draw a rectangle and then push-pull it.
If you click on the surface SketchUp will tell you the area. Now, select the whole thing, right click, and do a "make group".
Now, SketchUp will tell you what the volume is right here.
That is basically what I did with this is. I removed all the walls, the floors, and the ceilings, and I reconnected everything up and so it was one continuous, hollow piece of geometry.
Then I had a SketchUp calculate the volume. So that is one way for solving this calculate Zone volume error.
That is basically the way you solve it if you have complex geometry.
But, we will go into this a little bit farther because this error is actually connected with this other error.
This other error, the next error, says The surface "SURFACE 10" has an edge that is either not an edge on another surface or is an edge on three or more surfaces:.
Then, it tells you what the vertex start and end point is for that edge.
Let us go back to our model...and we can go to the inspector tool...and we can look at surfaces.
In this instance we are looking at surface 10. If we look at surface 10...
Sometimes it is difficult to find these, so we can put it in x-ray mode.
If you still do not see it, you can go to edit face, select all connected. Then it is a lot more apparent where that surface is.
It is going to be on this volume here. Surface 10 is actually this surface right here. You can click on it so that is surface 10.
The error is saying that it has an edge on another surface or is an edge on three or more surfaces.
I would suspect it is probably talking about this Edge right here. It is connected to this space, it is connected to this space, it is connected to this space and it is connected to this space.
So, it is sharing an edge on three or more surfaces. What is the reason for this error?
OpenStudio/EnergyPlus does not recognize this wall as an interior wall. It got exported to EnergyPlus as an exterior wall.
So, EnergyPlus is saying "why is this Edge surrounded by other surfaces, it should be on the outside like this Edge".
So, how do you solve that error and why are we having that problem?
It is because this whole thing is considered a single Thermal Zone. It is getting imported to EnergyPlus is a single Thermal Zone.
We could separate these out into their own individual thermal zones.
You can do that by changing the attributes on these spaces. Go to the set attributes and create a new Thermal Zone.
Another solution would be to try doing surface matching. Surface matching tells OpenStudio/EnergyPlus which surfaces are going to be exterior surfaces and which surfaces are going to be interior surfaces.
To do that, go to the surface matching tool and select intersect in entire model first.
Intersecting will catch any missing surfaces that should be matched.
For example, when you do surface matching, you want to make sure that this surface here is the same geometry and area as the opposing surface (this side here).
Surface matching is going to match those surfaces together and it is going to say this surface here is going to be sharing heat transfer with this surface here.
That way, EnergyPlus will know that it is an interior wall.
Let us do Intersect in Entire Model. It says that it is irreversible. You want to make sure that you are okay with that. Make sure to save your model beforehand.
Click ok. now it has intersected all the surfaces. Then you can click Match in Entire Model. Make sure to save it to have a backup. Just in case something goes wrong.
Click ok. It is done. How do we know that it matched? Go to render by boundary condition. We will go back to x-ray mode.
You can see that all of these interior walls are green now. They used to be blue.
Now, for example, this wall right here, the surface has been matched to the other surface on the other side.
Now EnergyPlus knows that heat transfer is occurring between those two surfaces. It knows that those surfaces are interior and so you will no longer have that edge error...here.
The error that says the edge is either not anedge on another surface or it's sharing an edge on three or more surfaces.
Now, let us go ahead and save our model. We will save it as version four...
We can open up our model...let us see here...and we will now run the simulation and see if we get that error...
The model has run successfully. Let us open up that error file. We are going to have to open up the newer version of it that we saved.
Go to the Run folder...eplusout.err...it is still telling us that this Thermal Zone one is not fully enclosed. There may still be some geometry errors.
So, it may be good that we hard sized that volume and area.
It also says: The surface "Surface 2" has an edge that was used 6 times...
so, apparently some of these interior zones are are causing errors...
we should just separate all of these spaces into their own Thermal Zone. How would you do that?
There is a simple user script in SketchUp that you can use.
First, we will go to the thermal zones tab in OpenStudio. We will delete this Thermal Zone. Save it. Then, reload it in SketchUp.
If we go to "render by Thermal Zone", you can see that there are no thermal zones assigned. We do not have any of these spaces assigned to a Thermal Zone.
We can go to the extensions, OpenStudio user scripts, alter or add model elements, add new Thermal Zone for spaces with no Thermal Zone. I cover this in one of my other videos.
Now that we are rendered by Thermal Zone you can see that each one of these spaces now has its own Thermal Zone.
Save the model. Go ahead and revert to the saved in OpenStudio.
You can see that all these thermal zones were created. Now we will run the model.
The model was run successfully. If we go back to our error file, we will reload it and you can see that a lot of those errors have been resolved.
It is still calculating a Zone volume for thermal zone six. It is saying Thermal Zone 6 is not fully enclosed.
Again, we would have find that thermal zone six. Browse for it in the inspector tool...
Here we go. This was thermal zone six. Thermal Zone six is is obviously having some issues.
It could be a very small Gap in the wall. Or really anything. Like I said, you can hard size these.
You can calculate the floor area and space volume. You can calculate the floor area...so 1682 square feet.
If we render by Thermal Zone...we can say that the floor area is 1682 square feet. And, again, you can calculate the volume like I said before using SketchUp...
You can hard size the volume in there. So, that is how you solve the calculate volume error.
Then...the next error...surface 25 has an edge that was used only once. It is not an edge on another surface...
Let us take a look at surface 25...we can click surfaces, scroll down to 25...and...find out where that is...
We will select all connected. It looks like...yeah surface 25 is actually associated with this Thermal Zone. The one with problems.
So, surface 25...here we go...it is this surface here. It is saying it is not an edge on another surface.
It is not an edge on another surface.
We go back to 25...you can see that this surface 25 is an exterior surface. That is true. It is not an edge on another surface.
It looks like we found our gap in this in this volume. If we fix this hole that may correct the The Zone volume for that space. It may fix those errors.
Also, with thermal zones seven, it is not possible to calculate volume.
Again we might have one of those those holes in our space. So we will go ahead and try to resolve those errors.
That is enough for today. That is how you solve those two errors.
Thank you! Please like and subscribe.
28. OpenStudio Tips - Natural Ventilation-Windows
We discuss how to download and implement the OpenStudio measure "Add Wind and Stack Open Area". This measure simulates opening a casement or door type window for natural ventilation. It takes into account wind driven air exchange and thermal bouyancy "stack" effect air exchange.
Transcript:
I get a lot of questions about how to do natural ventilation. There is a number of ways that you can approach natural ventilation.
We will focus on one of them in this episode; adding a natural ventilation object to your windows on the building.
That object is called ZoneVentilation:WindandStackOpenArea.
This is a download that you can get from the Building Component Library. If we go to the BCL and we search for "stack"...
Here it is. It is called Add Wind and Stack Open Area. You can download this measure and put it into your my measures directory. I discussed this in some of my other videos.
Unfortunately this version in the building component library, at the moment, is an older version. It is not compatible with the most recent version of OpenStudio.
What can we do? We can go to GitHub.com. Search for Building Performance Simulation.
One of their repositories, OpenStudio Measures, has...they are updating many of the EnergyPlus measures to be OpenStudio measures.
We can go into their Library, measures, and then add_wind_and_stack_open_area here.
You would have to download all these folders and files and place them inside your my measures folder.
I discussed this in my previous video, but you can go to the measures Tab and easily open up your My Measures folder with this button down here.
So, that is where you would place these downloaded files. You would place them in their own folder called add_wind_and_stack_open_area. That way you can access those through OpenStudio.
So, what does this wind and stack open area measure do?
It is based on some ASHRAE research...it is based on a typical door or a casement type window that that swings outward. It has an opening area from the very bottom of the window to the very top.
From the very bottom of the door to the very top of the door.
If we look at casement windows...and...I am trying to find a good example...
A casement window is very similar to a swinging door. It opens very much like a door.
We can just take a look at this one right here...just do a Snipping tool...and we will just do this...so we can draw on this.
What does this add_wind_and_stack_area measure do? It looks at two different calculations from ASHRAE fundamentals.
There is a wind component and it uses this equation here. It is based on open area, the effectiveness, the angle of the window to the wind, the actual open fraction of the window, and the wind speed.
That is the wind component of the equation. The other component of the equation is a stack effect.
This equation here. It is based on a temperature difference between the outside air and the Zone temperature.
It is also based on a height difference between the neutral pressure level and the open area fraction...how open is the window...and then the actual window opening area and there is a discharge coefficient of the opening.
What is this stack effect doing? It is modeling a thermal bouyancy stack effect. Basically, when you open the window there is a neutral pressure level here somewhere in the middle of the window.
Air is getting sucked in at the bottom portion and air is discharging out the top portion of the window.
So, this measure is combining the stack effect and the wind effect as a quadrature sum. It is calculating a ventilation rate for that room.
Let us look at our model...we have a typical building. This was generated with the Department of energy prototype measure.
It is a typical, standalone, office building. It has a number of Windows and doors located around the building.
All of these windows on this model are are called fixed windows. So, the first thing to note with this measure; we have to change these windows to operable windows.
You can go to the spaces tab...and go to subsurfaces...we can search by subsurface type...we can look for fixed windows.
We want to change all of these to an operable window type. We will change that one and then we will apply to selected.
That changes all of our windows in the building to operable windows. You can change whatever windows you want.
For this example we are going to assume that all the windows in the building are operable.
We will click save. The next step is to go to the measures tab. The measure that we are looking for is located under Library, envelope, fenestration.
We will select the my measures one. As I said, the older BCL measure is outdated and it does not work with the latest version of EneryPlus.
We will do this one that we downloaded from GitHub. We will drop it into the OpenStudio measures spot.
We can click on it to edit the input variables...it gives you a number of options.
This drop down give the option to add this wind_and_stack_area object to all operable windows. Or, you can select the type of window that you want it to be applied to.
You may have multiple different windows in your project. For this example, we will just apply it to all the windows.
The next component is open area fraction schedule. It says "a typical operable window does not open fully, the actual opening area in a zone is a product of the area of upper windows and the open area fraction schedule.
It also says it defaults to 50 percent. What is that saying? With 50%, it is saying that the window is only open 50 percent.
This is just a default open fraction schedule (of 50%). If we wanted to adjust that opening, we can create a fractional schedule.
You would go to schedules tab, schedules. Then, add a schedule. Select fractional. Click apply.
Suppose we wanted the window to be open 75%. We would hover over it and type 0.75. That would be the window opening percentage of total area.
We could just call this...natural vent window fraction schedule.
Suppose, the window is closed at night...we can double click and say at night time it is at zero.
The windows are always closed at night. They are only open during the day and when they are opened they are opened to 75%.
We could say that the people go home around four o'clock and close the windows before they leave.
There is our open area fraction schedule. This is this is the first part of it.
We can go back to the measures tab, select the measure, and then select our custom fraction schedule. This one that we just created. Natural vent window fraction schedule.
There are also a bunch of other parameters that we can input.
Minimum indoor temperature; this is the indoor temperature below which the windows are shut closed.
Even though we have this fraction schedule, if the indoor temperature is below this value, the occupants will not open the windows.
Alternatively, you can specify a custom temperature schedule if the occupant preferences vary throughout the day.
You can create a custom schedule; for instance, the occupants would never open the windows in the mornings unless the indoor temperature was a certain value.
But, they might open it in the afternoons if the indoor temperature was a certain value. So you can create a temperature schedule for that.
Moving on...there is a maximum indoor temperature above which the windows are closed shut.
If the temperature inside the room gets above this value, the occupants will always close the windows.
Likewise, you can create a custom schedule. For example; it would be above a certain value in the mornings, but maybe above a different value in the afternoons. So, you could create that custom schedule.
The next one is maximum indoor-outdoor temperature difference. This is the temperature difference below which the ventilation is shut off.
Three degrees is quite small. You would not get much natural ventilation below three degree temperature difference.
It is pointless to open those windows if there is a temperature difference below three degrees (unless it is windy).
Based on the stack effect, that ventilation is driven by temperature difference. The higher temperature difference between the indoors and the outdoors the more natural ventilation you are going to have.
Below a certain value, it is not effective and it is not necessary to open those windows for ventilation.
You can also assign a custom schedule if that temperature difference varies throughout the day or varies based on the season. You could assign a schedule.
All of these values pretty much have a constant number or you can assign a varying schedule that changes throughout the year.
The next one is minimum outdoor temperature; this is the outdoor temperature below which the ventilation is shut off.
If the outdoor temperature gets too cold, the occupants will close the windows. Again, you can create a custom schedule.
The next one is maximum outdoor temperature; this is the outdoor temperature above which the windows are closed shut.
If the temperature outside gets too high, the occupants might close the windows at that value.
Finally, the last component is the maximum wind speed in meters per second. Above this wind speed, the windows are shut.
If it gets too windy outside, the occupants will close those windows.
We can go ahead and run the measure. We will go to the Run simulation Tab and click run...the simulation was run successfully.
We can look at the OpenStudio results for this. You will see that...well we don not have anything to compare...
We could save this model as version 2. We can run the simulation without the measure.
We will just delete the measure and click run. The model was run successfully. We can go to the OpenStudio results for that one.
Let us open up the previous one with the natural ventilation on the windows. We can compare the two.
This is the one with the natural ventilation. This is the one without the natural ventilation.
You can see that our site EUI without the natural ventilation is 33.26. With the natural ventilation it is 33.04.
So, you can see that the natural ventilation has reduced our energy use intensity.
We can look at the end use table. Make a comparison to evaluate savings.
Heating without the natural ventilation is 14,350. Heating with the ventilation is 14,549.
You can see that our heating went up, a little bit, with the windows being opened and closed.
But, you can see that with cooling, without the window natural ventilation, is 12,540. With the natural ventilation it got reduced to about 11,100.
So, you can see that our cooling load went down and our heating load went up slightly. But, there is a net savings from that natural ventilation.
Of course, this measure is dependent on climate zones. Some climate zones are better for the application of natural ventilation and other climate zones are worse for natural ventilation.
It will be highly dependent on what climate zone your building is located in.
This climate zone that we are looking at...it looks to be ashrae climate zone 5B. This is in Oregon.
What else can we say about these windows?...
As discussed, this natural ventilation measure is based on the window geometry and in particular the window area and difference in height because it is a stack effect.
There is a difference in height that is driving that stack effect.
What can we do to increase the natural ventilation of this model? We could increase the window height.
Let us go ahead and do that. We will open up SketchUp...and we will open up the model with the natural ventilation measure that we had placed in it.
We will save this as a version 3 (with the modified windows).
As discussed, this ventilation component is based on window area and window height. If we increased the window height on all of these, we could increase the natural ventilation of the windows.
The downside to this is that we are increasing the window area. By doing that, we are reducing the insulated value of the wall. We are also allowing a lot more sunlight into the building.
That may actually increase our cooling load. It will be interesting to find out if by doing this we actually find a savings or if it actually increases our energy use.
We will click save. We can open the OpenStudio model by launching OpenStudio. Then we can run the model...the model was run successfully.
If we look at the results, with the larger windows, we can say see that our energy use intensity actually increased in comparison to the model that did not have natural ventilation.
You can see that there is a balancing act that you have to do based on the window orientation to the sun and orientation to prevailing winds.
There are a lot of other variables; such as when the occupants open and close those windows. When the natural ventilation is allowed to be operable...
What seasons it is allowed to operate.
That is it in a nutshell. That is how you add a wind and stack object to your windows so that you can simulate a natural ventilation rate to those rooms.
One last thing that we should note; this measure is only based on the windows...I would take a snapshot of this here...
This measure is is driven only by the windows and so that natural ventilation for each of these windows is only active for those rooms that these windows are applied to.
It is calculating the airflow that goes into and comes out of that window. The window that is associated with that room.
Each one of these windows is calculating a natural ventilation rate but it is not taking into account the height of the building.
For example, if we had a roof vent up here...it is not calculating the temperature difference stack effect of a window taking in air and exhausting out of the top of the building.
It is only accounting for that height difference of the window itself.
So, that is how simulate window ventilation.
I think that is good for today.
Thank you! Please like and subscribe.
29. OpenStudio Tips - Natural Ventilation-Zones
We discuss how to implement the OpenStudio measure "Add Wind and Stack Open Area" on thermal zones. This EnergyPlus object simulates natural ventilation for a thermal zone. It takes into account wind driven air exchange and thermal bouyancy "stack" effect air exchange. By adjusting a few parameters and assigning to thermal zones, we can do a simple simulation of whole building natural ventilation.
Transcript:
We are back with another episode and we are still talking about natural ventilation.
If you did not see the previous episode; we talked about modeling natural ventilation with operable windows.
This time, we are going to talk about modeling natural ventilation with a more purposeful design of natural ventilation.
In this episode we are going to talk about using the whole building for natural ventilation.
Let us take a quick look at this. What does this look like? We will just take a snapshot of our building.
You can see that...in the previous episode we had a window, a simple window. The ventilation was coming in the bottom of the window.
It was circulating through the room and then it was going out the top of the window.
In this episode we will be modeling ventilation with the windows again, but in this instance the air is entering through the Windows and escaping through some exhaust/vent at the top of building.
That allows you to take advantage of the thermal buoyancy "stack" effect. It will allow for more natural ventilation into the building.
There is some terminology that we need to discuss, similar to last time, as part of this natural ventilation.
There is going to be what is called a "neutral pressure level".
It is an arbitrary place in the building where the pressure is causing the air to enter the building below this level and exit the building above this level.
This neutral pressure level can vary depending on the temperature differences between the inside and the outside and also the wind speed and wind direction.
For simplification, this neutral pressure level can be approximated as half of the distance between the top and the bottom. The inlet and the outlet.
So, this is the value we will be working with, right here.
Going back to our model; we took our model from a previous episode and we have saved it as a new version.
We can go to Thermal Zones...I am sorry, let us go to Measures first. We will delete the operable windows that we did last time.
Now we will go to Thermal Zones tab. Go to the library and go down to Zone Ventilation Wind and Stack Open Area.
This is the same object that was being used in the previous episode, but it was being applied to only the windows.
In this instance, it is being applied to the whole Thermal Zone. We can drag this in and apply it to our Thermal Zone.
You can apply this to any Zone you want. For this example, we are just going to apply it to the zones with Windows.
We will run this model and compare it to the previous one (with simple operable windows).
This model is assuming operable windows, but it is also assuming that we are going to have that ventilation coming into the window and escaping out the top of the building.
Let us take a look at this object. You will notice that almost all of these inputs are the same inputs as we used last time.
The first input is called Opening Area. We are looking at Zone 1, so let us take a look at Zone 1 here.
The opening area is going to be our Windows once again. We can have SketchUp calculate those window areas for us.
Hold down the shift key and select all of these windows. We can see that the total area is about 270 square feet.
This is actually in meters, so we can go to preferences, units, change it back to English...270 square feet.
The next input is the Open Area Fraction Schedule; this is the fraction schedule that we created in the previous episode. It is called Natural Vent Window Fraction Schedule.
We are going to use the same window opening schedule as we did previously.
The Opening Effectiveness is based on those equations that we talked about last time. You would have to look into the Input Output Reference Manual or the Engineering Reference Manual for EnergyPlus.
You will find those equations there. We will leave it to Auto calculate just as we did last time with the measure. The measure uses Auto calculate as well.
The effective angle; that angle is based on orientation from true north. If we go ahead and look overhead on our model you can see the green axis.
That is true north for our model. We will be using that as the direction of zero and it goes around clockwise in degrees. This Zone one is actually located at an effective angle of 180° from true north.
The height difference is going to be that distance between the middle of the window and the neutral pressure level. It is going to be this distance right here.
We can calculate that using SketchUp. We are just going to extend this out...midpoint of the windows...this...up here.
SketchUp is telling us that this line is 16 feet long, so it is going to be approximately half of that. Let us say...8ft (2.44m)
Discharge Coefficient for Opening; that is based on the equations that we talked about last time. You can find those in the reference manuals.
The minimum indoor temperature; we can look at our previous model. We will use the same numbers just so we are comparing "Apples to Apples" on this simulation.
The minimum indoor temperature was 21.67°C. I will have to change back to units, metric...21.67.
Maximum was 40°C. The delta-T was 3°C. The minimum was 18.33°C. The maximum was 25.556°C. The maximum wind speed was 5.4 m/s.
We will save the model. We are going to apply this object to all the other zones with operable windows. We can select these other three zones.
Select the object and apply to selected. The only thing that we have to change now is the opening area and the effective angle.
Let us take a look at zone 2. The effective area is 176 square feet (16.4 square meters).
Change this back to English...176 square feet. The effective angle for Zone 2 is 90° from true north.
Let us go to zone 3. It is facing true north and the window area is 180 square feet. Using true north.
Finally, zone 4. The window area is 120 square feet. It is facing 270° from true north.
Those are the parameters that we can input for our model. Now, we will run our model and compare it to the model that we created in the previous episode.
The simulation has completed successfully. We could take a look at the output reports and simply compare energy use intensity...
For this example we want to compare the ventilation flow rate of of this natural ventilation so we will we selected some output variables on the output variables Tab.
We are going to use DView to view those. These output variables record some variables during the simulation.
I cover this on some of my other videos, so we will not talk about that now. Go to the top right and click the show simulation button.
It will take you to the Run folder for the simulation. We are looking for the eplusout.SQL file. We are going to open that using DView.
We are going to select Outdoor Air Dry Bulb Temperature, Zone Mean Air Temperature for Zone 1, and Zone Ventilation Standard Density Volume Flow Rate for Zone 1.
Likewise, we are going to do that for the previous simulation we did; with just the operable windows.
This is simply the the operable windows...
This is the simulation using the operable Windows plus exhaust at the top of the building.
You can see there is a quite a bit of difference here. We are getting a lot more ventilation flow through the building using that stack effect versus just opening the windows.
You can see that this ventilation increases during the more temperate portions of the year and it decreases towards the more extreme conditions because we do have those upper and lower limits on our on our natural ventilation.
That is how you model natural ventilation in a Zone as opposed to doing natural ventilation just through windows.
Thank you. Please like and subscribe!
30. Building Energy Modeling in OpenStudio - Troubleshooting 5
In this series of episodes, we discuss some common simulation warnings and errors found in the EnergyPlus eplusout.err file. We will discuss these errors, and show common strategies to resolve them. Errors in this episode:
-CheckConvexity: Surface="SURFACE 321", vertex 2 is colinear with previous and next.
-CheckConvexity: Zone="THERMAL ZONE 6", Surface="SURFACE 321" is non-convex.
-CheckConvexity: Surface="SURFACE 321" has [1] collinear points that have been removed.
-CheckConvexity: Surface="SURFACE 321": The vertex points has been reprocessed as Sides = 4
-GetSurfaceData: There are 1 coincident/collinear vertices; These have been deleted unless the deletion would bring the number of surface sides less than 3.
-CalculateZoneVolume: The Zone="THERMAL ZONE 7" is not fully enclosed.
-CheckUsedConstructions: There are 5 nominally unused constructions in input.
-Output:Meter: invalid Key Name=
-Output:Meter:MeterFileOnly: invalid Key Name=
-Output:Table:Monthly requested with SimulationControl Run Simulation for Weather File Run Periods set to No so Output:Table:Monthly will not be generated
Transcript:
Continuing on our series of troubleshooting with EnergyPlus out errors (eplusout.err file);
We are looking at the next warning. It says: CheckConvexity: Surface="SURFACE 321", vertex 2 is colinear with previous and next.
Then it goes on to say: CheckConvexity: Zone="THERMAL ZONE 6", Surface="SURFACE 321" is non-convex.
It lists the vertices that are having the problems, and this looks related, it says: Surface="SURFACE 321" has [1] collinear points that have been removed.
CheckConvexity: Surface="SURFACE 321": The vertex points has been reprocessed as Sides = 4.
It even goes on to say: GetSurfaceData: There are 1 coincident/collinear vertices; These have been deleted unless the deletion would bring the number of surface sides less than 3.
For explicit details on each problem surface, use the output Diagnostics display extra warnings.
So, what does it say? What is this? Let us take a look at surface 321. We will just Search for 321...right here.
It is not readily apparent...but that is...so we can select the face and select all connected.
Okay, it is part of this Zone. Let us edit this...search again for the surface 321. Right here. Okay, here we go.
This is...right here. It appears to be this surface right here...um oh!
It switched to 25. We have selected 25. Let us hide 25. Okay 321. This appears to be overlapping with another surface.
It says the vertex is collinear with the previous and next. If we do unhide and we Search for 321 and hide 321...
We can see that it appears to be overlapping with this surface 25. I think we need to delete the surface 25 and recreate it.
We have got surface 25 there...surface 321 there. Now those surfaces are separated.
That should fix our problem. We will go ahead and save the model. Revert to the saved version. Run the simulation.
The simulation is completed successfully. Let us go back to our error out file. Reload it.
That looks to have cleared up that issue there. That is how you fix the issue of overlapping vertices.
The next error we have. It appears to be a severe error. As we discussed previously, severe errors.
While they will not always cause your program to crash they should be taken seriously.
For Thermal Zone Seven, it is not possible to calculate the volume from the surrounding surfaces so either provide the volume value or Define all of the surfaces to fully enclose the zone.
It says the Zone is not fully enclosed and we have already discussed this error before. Zone volume was not calculated and an error exists.
It looks like it is possible that it is related to the surface 112. It has an edge that was used only once and it is not an edge on another surface.
We have discussed that error in the previous episode, so let us take a look at these two surfaces 112 and 243.
It is associated with this Thermal Zone Seven. Yes. Thermal Zone Seven.
If we look at surfaces 112 and 243...surface 112...should be on...okay, right here. Again, the same problem.
It looks like we are missing a surface, so the best thing is to possibly just delete these and redo those.
We have a separate surface 212 here, a surface 112 here, 243, 111 and that was 112 and 243. That is how we solve that error because the surface was missing.
The warning was saying the Zone was not fully enclosed. Now that we fixed that error it should solve the problem. Save the model, revert to saved and click run.
It has run successfully. We can go back to our error out file and refresh it and that solves that error.
CheckUsedConstructions: There are five nominally unused constructions in input. Each unused construction is shown. We have covered this in previous videos, but we can go back over this again...
This is saying that you have extra materials or constructions in your model and they are not being utilized in the model. So let us take a look at this.
It says, construction interior ceiling is not being used, so we can go back to our constructions and we could say: see interior ceiling.
What is this interior ceiling? How is this being assigned? If we had a multi-storied building...say we had another space right above this, the ceiling in-between these two spaces is considered an interior ceiling.
We actually do not have a second floor in this building. The only thing we have is a ground floor, which is in gray and we have an exterior roof.
We do not have any interior ceilings, we can actually delete the interior ceiling from our construction set on this.
Likewise, we do not have any interior doors. An interior door would be for example: if we had a door that was right here, and it led to the inside on the other side to a door connected to the adjacent space.
We do not have an interior door. We would have to create doors in both of those spaces. There would be a door in this space and there would be a door in this space.
That would be inside the building. We do not have that. What we can do is delete that interior door on our construction set as well.
Interior subsurfaces, constructions, doors, and interior doors, we can delete this right here.
Interior floor...the same thing, we do not have a second story nor an interior floor, and again, the same situation but in this instance it would be the floor of, for example, this space here...
The floor of this space would be considered an interior floor because it is communicating with the space below it.
We can delete that construction as well as the interior floor. If we look at the interior, sorry, scrolling up, the interior surface constructions, and interior floor, so we can delete that...
You don't need that. Then interior partition...
What is an interior partition?...an interior partition is used for simulating exterior light coming into the office usually from the Sun.
The light goes through the window and strikes the floor, furniture, or for example, interior partitions.
If we had this space right here, and right now there is nothing in it...
You can model something like an interior partition...let us see if I can do that... We will just draw a right angle here.
Let us go overhead and we will change the camera to perspective.
If we have a cubicle here...and we would have to extend it up like that.
For example, if we had a cubicle like that, right now it is showing that this is a window.
I do not know why this was assigned a window...
It was probably because I drew it on the floor and it was thinking it was a skylight or some sort of window.
We can redraw it as a partition, then we can drop it back into our building.
That would be a cubicle. You would assign this as an interior partition construction.
The only thing that EnergyPlus does with these; it simulates the absorption and reflection of sunlight in the room...
You can assign this construction as an interior partition and whatever this interior partition is made up of if it is made up of wood for instance...
EnergyPlus will account for the thermal mass of the partition. If sunlight is shining on this for an hour, it would gain heat and then an hour later it would re-radiate heat into the room.
That can have a small effect on your simulation. If you are doing interior partitions, you would do that. We do not have any interior partitions so we can delete that.
Again go to construction sets and scroll down to the bottom, other constructions and interior partitions, we are going to delete this.
Then, interior windows, same thing. Just like I was saying with the interior door...
If we had an interior window for instance, instead of an interior door that communicated between one space and the other space then that would be considered an interior window.
We do not have any in this model. We can delete the interior window.
Tubular daylight domes and tubular daylight diffusers are all assigned interior windows. Fixed windows, and operable interior windows. We would not have any of these interior window constructions.
That covers those. Now that we have deleted them we can save the model. One last thing we should do is go into constructions and purge some of these.
These were the interior floors and interior ceilings. We need to purge those from the model so that EnergyPlus does not have to process those, click the purge button down here.
That gets rid of those. You will have to go through each category if you have those in there.
Then the same thing, go into materials and purge those. Some of those materials might get removed if they were associated with, for example, the interior windows and doors and interior ceilings...
Now that that is all purged we can go to the run simulation; click run. The simulation has run successfully. Let us go back to our eplusout.err file and reload it.
You can see that those errors have been removed...
The next thing that we can look at, it says: Warning Output: Meter: invalid Key Name="NATURALGAS:FACILITY" - not found.
It goes on to talk about: invalid Key Name=DISTRICTCOOLING:FACILITY" - not found...Output:Meter: invalid Key Name="DISTRICTHEATING:FACILITY" - not found...
It says Output:Meter:MeterFileOnly: invalid Key Name= "NATURALGAS:FACILITY" - not found.
These meters are saying that there was a meter requested, but since there is no equipment that uses natural gas, or District Cooling or District Heating in our model...
It is saying that there is no data for that. As soon as we add some piece of equipment to our model, for instance, if we have a Thermal Zone and we added a gas heating equipment to the Thermal Zone.
We could add a gas unit heater here to the Thermal Zone. Then, if we re-ran the simulation, this error would disappear because suddenly we do have a piece of equipment that is using natural gas.
These errors pop up all the time. It is not a big deal it is just saying that you do not have equipment in your model that is using those meters...
The last warning we have is Output:Table:Monthly requested with simulationControl Run Simulation for Weather File Run Periods, set to No, Output:Table:Monthly will not be generated.
What is this saying? It is saying that we requested an Output:Table:Monthly.
We are not running the simulation for the Weather File Run Period, it can not generate that data.
What is the monthly report? If you go to the simulation settings tab, you can scroll down to the output table summary report.
If you have this enabled, enable all summary report. You should be able to go to your results summary tab and see the energy consumption and all sorts of metrics on a monthly basis.
But that was not included in the report. The reason it was not included in the report is that we are not running the simulation for the weather file...
We are only running the simulation for the peak load period. If we go back to simulation settings and go to simulation control, you can see that we only have it selected to run the simulation for the sizing periods.
What are those sizing periods? If we go to the site tab, the sizing periods are the design days. Those are the peak days for cooling, dehumidification, and for heating during the winter.
It is not running it for a simulation for the entire year, it is only running it for a simulation for the design days.
Go back to simulation settings, to simulation control, then run the simulation for the weather file run periods.
That will generate all of our data for all of the months and that will be output on the monthly tables.
That will get rid of this error here. If we click run we can see that the simulation has been completed successfully. In fact, you can see that the simulation has simulated all of the months December, November, October, all the way back to January.
Let us go back to our eplusout.err file and see if this Output:Table:Monthly is being generated now.
We will reload it and of course, now that we have run a full simulation, there are additional warnings!
The key is to find if that Output:Table:Monthly is being generated and it looks like it is, because we have all of these warnings being generated for monthly output reports, but we don't have this equipment in our model.
That is it for today. we will continue to troubleshoot these warnings next time.
Thank you. Please like and subscribe!
31. OpenStudio SketchUp - Editing the User Script Ruby Programs
In this episode, we discuss how to edit the OpenStudio user script programs. We show where to locate the user script ruby files and give a quick example of changing text within the code.
Transcript:
Today we are going to talk about the SketchUp OpenStudio User Scripts. Those are located in: Extensions-OpenStudio User Scrips; it is all of these right here...
These are all written using the Ruby programming language. In particular, I am going to show you how to locate the Ruby Files and how to edit those; I am going to give an easy example.
There is a handy User Script here that Renames Thermal Zones Based On Space Names.
If we have a Space Name, and we want to have the Thermal Zone Name also very similar to that Space Name (so it is easier to locate the information in the Output Files);
You can use this User Script. It just puts a prefix on the Space Name; that is what it calls the: "Thermal Zone."
The prefix in this instance is: "Thermal Zone," and then it uses the Space Name. Although this is handy, it does tend to make the Thermal Zone names very long.
Sometimes they do not fit on the whole page. I like to shorten those with just: "TZ," which makes it easier to read.
How do you locate the Ruby File for this User Script? First, you need to go to your Computer, your Hard Drive, and then you would go to Users, your username, and AppData-Roaming.
We will search for "SketchUp" and the SketchUp version you are using, SketchUp again, Plugins-OpenStudio, and then we can go to: "user_scripts."
I think it is on the: "Altar Or Add Model Elements" Submenu. So, yes, we will go to: "Altar Or Add Model Elements," and then we need to search for it.
Here we go: "Rename Thermal Zones based on Space Names," and you can see it is a Ruby File, a "DOT RB" file (.RB file). So this is the program that renames those Space Names.
We will double-click to edit it. The quickest way to find that information is to search for this string of text.
So do a: "Ctrl-F" to find, and then we will: "Find All" in the Open Document..."Thermal Zone." And...so we will do "Find" in the Open Document and "Find All"; you can see it found in one instance here.
This is the string of text that puts the prefix on those Thermal Zone Names. So let us first get rid of some of these spaces.
We will change it to: "TZ. Then, we will hit: "save," which saves the Ruby file. After that, we have to close out SketchUp and reopen it, and this recompiles the program...
We have reopened it, and you can see right now it is Thermal Zone. If we rerun this User Script and look at the thermal zones again;
You can see it has now been shortened to simply: "TZ." That is how you edit the: "OpenStudio User Scripts"; and in the: "Ruby programming language."
Thank you. Please like and subscribe!
32. OpenStudio Tips - Boiler with Convectors/Radiators
We discuss how to implement a centralized hydronic boiler with hot water radiators / convectors.
Transcript:
So, we are back again with a D.O.E. prototype building. Right now the building does not have any heating or cooling in it.
We want to add a simple hydronic hot water heating system with boiler and some convective or radiative heaters in the thermal zones.
The quickest way to do that isto go to the HVAC systems tab. Go to the green plus button. Let us scroll down to this package rooftop VAV with reheat.
Tou can see it has got this raindrop here. It has got the red thermometer in it. That means it is a a hot water system.
So, this is going to automatically add a boiler Loop to our model for us so we do not have to do all of that work of adding it ourselves.
We are going to click add to model. We can take a look...so, it added this hot water loop here. It added the boiler pump. It has got a temperature set point.
It has also got some hot water coils over here in the system. We are going to disconnect these hot water coils from the loop.
We are going to go back to that VAV rooftop unit. It is always good to delete the items from the airloop or water loop first before you delete the loop itself.
We are going to delete this VAV air hander...so we are left with the hydronic hot water loop. It is an empty Loop Loop. There is nothing connected to it.
There is our boiler loop. We are going to go to the thermal zones tab now. Scroll down in our library files.
We can find baseboard radiant convective water or baseboard convective water. This is the simple convector and then this one is also a radiator and convector.
We are going to use a radiator/convector. Drag this into the Zone equipment. Click on it. You can edit these properties... for now um I think they all look pretty good.
I think the loop temperature is set for about 150, but the loop is rated at 212 so this is probably okay. Click on this chain link icon up here.
We are going to connect it to our new boiler hot water loop. Now we are going to add convectors to all of these other spaces. Apply to selected.
Now we can go back to our boiler hot water loop and take a look. You can see that all of those radiator/convectors have been added to our loop.
That is how you model a simple hydronic hot water boiler loop with radiant or convective heaters located in the thermal zones.
Thank you! Please like and subscribe.
33. OpenStudio Tips - Getting Information from Output Reports
We discuss the two standard output reports provided by OpenStudio/EnergyPlus and how you can get additional information to show in them. We also download a measure from the Building Component Library that provides even more information and will allow you to extract or link the report information for use in external spread sheets.
Transcript:
Today we are going to talk about the output reports that you can get from OpenStudio EnergyPlus.
I am going to show you a a handy measure that I wrote that you can download from the Building Component Library (BCL).
One of the default reports that you can install in the measures tab is the OpenStudio results report.
If you click on it, you can select whether it outputs the imperial system of units or the metric system of units.
You can select the various different categories of information that you can find in the report. So, that is one of the reports.
The other report that you can find, if you go to the project folder...go to the reports folder...
You will see that OpenStudio results report as an HTML file. You can also look at the EnergyPlus tabulation report.
It has almost the same information. If you want to get additional information in that report, you can go to the simulation settings tab and scroll down to the bottom.
You see Output Table Summary Reports and click enable on this. This will give you an expanded set of reports inside the EnergyPlus tabulation reports.
The other thing that you can do is download this measure that I wrote. It has some additional reports, including the Zone Component Load reports and the Airloop Component Load reports.
Those are pretty handy information to have when you are trying to diagnose things.
Go to Find Measures...Reporting...QAQC...Set output table to si units V2 or Set output table to ip units V2.
You can use either one of these to Output the EnergyPlus report to your units of choice.
We will select IP units v2...we will click download...so the Building Component Library is having some login issues today.
So, we can go ahead use uh either one of these...I have a backup in my measures. I also have a copy of the BCL SI units. We can just use this one for now.
You can click on it. There are no options here, so this this just is going to Output it to IP units.
But, it is handy. It will output the EnergyPlus report to IP units. It will also allow you to output the OpenStudio results report in IP units as well.
We are going to go ahead and click the run...and it is finished successfully.
If we go to the EnergyPlus output HTML file. Click Refresh on the web browser. It updated this...go to the table of contents.
You can see that these items were added. We now have Zone Component Load summaries and Air Loop Component load summaries.
These are useful information. This shows you a breakdown of the components that contribute to the loads in the zone.
It also has some handy engineering checks. It also shows you sizing and safety factor multipliers.
That is important information when you are looking at loads and sizing of systems.
This measure can also allow you to extract this information...you can certainly copy and paste on the web browser HTML file, but sometimes that is not so easy to do .
Alternatively, you can go to the project folder...go to the Run folder...now you will see that there is what is called an eplustbl.tab file.
This is a tabulation file. It is the same information that is in the EnergyPlus report we just looked at in the web browser HTML file.
The information is put into an Excel spreadsheet with tab delimited information.
If we open that up, we will see that it is basically the same report.
You can search for any type of information in here. We will just search for Zone Sizing Information.
This is the Zone sizing information table. You can simply copy and paste it to your um external Excel file...or even better...you can paste it as a link.
That will paste all of the information...all of that information is linked. Then, when you do update those calculations, that information will pull through to your to your external Excel calculation file.
That is that in a nutshell.
Thank you! Please like and subscribe!
34. OpenStudio Tips - Warning GetOAControllerInputs
We discuss the warning ** Warning ** GetOAControllerInputs: Controller:MechanicalVentilation="CONTROLLER MECHANICAL VENTILATION ... Cannot locate a matching DesignSpecification:ZoneAirDistribution object, what it means, and how to resolve it.
Transcript:
Hello all. We are back here with another episode. Real quick tip. This is a very common warning. It says "GetOAControllerInputs: Controller:MechanicalVentilation="CONTROLLER MECHANICAL VENTILATION".
It says it cannot locate a matching DesignSpecification:ZoneAirDistribution object for your Thermal Zone.
It goes on to say that it cannot find that so it is going to use "default zone air distribution effectiveness of 1.0 for heating and cooling".
This is a this is a common error. It is not a big deal. You can ignore it, but it depends on what your zone air distribution effectiveness is.
For example, if you have Supply Air from the ceiling level or Supply air from the floor level. And also where your return air is coming from.
This comes from ASHRAE 62.1; the ventilation rate procedure. We can take a look at that real quick.
You could go to any one of the mechanical codes and find the ventilation part of the code; which is based on the ASHRAE 62.1.
Mechanical Ventilation...outdoor air required...we can scroll down to the Zone Air Distribution Effectiveness.
If you have ceiling or floor supplies of cool air, your effectiveness is 1.0.
Ceiling or floor supplies of warm air with a low return the effectiveness is 1.0.
If you are supplying warm air from the ceiling, and you also have a a return on the ceiling, then your distribution effectiveness is 0.8.
That is what these numbers are. We can go to OpenStudio...this is the crux of the matter. We have an outside air controller that is trying to figure out how much outside air is required.
If we go to the Thermal Zones Tab...Cooling Sizing Parameters...we have this column right here: Design Zone Air Distribution Effectiveness in Cooling Mode.
If you have not edited these, by default these will be a blank in your OpenStudio file. When it gets translated to EnergyPlus, EnergyPlus does not know what to do.
It just automatically assigns a number 1.0 to that value. But, it is good practice to go through here and ensure that you do have the correct Zone Air Distribution Effectiveness for the type of system you are modeling.
If you want to get rid of that error; is type a 1.0 in here and then select all and apply to selected.
Likewise, for the Heating Sizing Parameters tab, we can do the same thing. Let us just assume that we have a ceiling supply diffuser and a ceiling return grille.
This is the Heating Sizing Parameters tab, so we will select all and apply to selected. Give it a second...
We can click over to Cooling Sizing Parameters, click back to Heating, and double check that was applied...yes, it was.
We can go to run the model. The model was run successfully. We can go take a look at our eplusout.err file.
We will reload it. We can see that that error was resolved.
Thank you! Please like and subscribe!