Grasshopper

algorithmic modeling for Rhino

Hey Guys,

I have a typical floor plan that we are trying to analyze to determine different glazing ECMs (glazing type and WWR). I'm noticing that the results from the Ideal Air Loads runs are showing very high heating demand (~350kWh/sm/year for example with a 2009 IECC glazing construction), also with the cooling demand high as well but not as equally outrageous (~50 kWh/sm/year). We were expecting something in the 25-30 kWh/sm/year range for heating and cooling loads each.  I've double checked all inputs and they seem to be legit. Any idea for these high loads? So perplexed.

I was hoping to be able to add a mechanical system to the model to get actual energy demand, not just the load.  When I used the component to change the mechanical system to one of the other off the shelf systems, the total thermal energy demand was not affected at all.  Was this because I did not have an air side and a plant side component plugged into the mech override component? What I was hoping to be able to do was to set a base off the shelf mech system, similar to the E+ example files that come with the E+ download.  Am I missing something?

Also, it seemed to consistently get errors when reading the surface data from the glazing.  I was unable to determine if this was causing the heating error.

We've modeled all of the zones around the perimeter as conditioned, and the core and plenum as unconditioned.  The floors are modeled as adiabatic.  Attached is the model and the gh script.   

Any help would be awesome. Thanks, Patrick

Views: 377

Attachments:

Replies are closed for this discussion.

Replies to This Discussion

Patrick --

I suspect the culprit is some surface normal issues. Look at the error file generated by E+ to see if the window or wall geometry are facing each other (not desirable) and not outwards as they should be (you can also check the orientation in grasshopper using Vector Display).  You will need to flip their orientation before E+ is able to treat these surfaces as proper windows/walls. Once these surfaces are oriented outwards you should see changes in energy use as E+ will be able to recognize the window geometry.

--J

Thanks J for your response.

I had a look at your suggestions.  Several notes:

1. I switched the simulation from "Full Interior & Exterior" solar distribution to run on "Full Exterior" solar distribution.  This switch did get all of the severe E+ errors to disappear.  Also, it initially got the glazing surface results to read.  Then I ran the simulation a second time and the results disappeared again.  Any idea why the surface results disappear the second go round?  

2.  As for the surface normals, the normals of the surfaces coming out of the "Glazing Based on Ratio" component do seem to be oriented both in the correct direction, both oriented outward. See the image below.  I've also tested it using the Child Surface method with the "addHBglz" component, and all of those surfaces are also correctly oriented outward.  When I rerun both simulations, the surface data still does not read surface results for the glazing (it does read the surface results from opaque portion of the wall).   

3. 3.Lastly, any suggests for getting an off the shelf mech system hooked up so the results will read as End Use Energy Consumption, rather than the Ideal Air Loads?  Any suggestions would be great!

Thanks for your help.

1. If you have concave surface EP won't be able to run Full interior and exterior analysis.

2. Honeybee should take care of normal directions for you (evenif the input is in the wrong direction), if it doesn't that can be a bug. Can you upload a simple example where this fails and I will take a closer look.

3. Have you tried OpenStudio components? There you can set-up couple of default systems. Here are the videos on how to get started:

Thanks Mostapha. These are very helpful.

This might be a very simple question, but I followed along w/ the tutorial and get an error from the "Honeybee- Export to Open Studio" component, stating Solution Exception: fuel type.  I can't seem to find any components to input a fuel type. Am I missing something?  Thanks. 

Any help would be great.  Thanks. 

Patrick,

Do you still have the issue with the latest version? If you can send me an example file I should be able to get it fixed for you.

Mostapha

RSS

About

Translate

Search

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service