ke 20 samples per day, 50 days out of the year for 1000 samples) from each panel and calculate the % of occlusion. Allow that % to be the % "open" of each panel. Design the opening in each panel to be something cool and proportional. Profit.
You could even break it down by a finite number of available panel types(say 0%, 20%, 40%, 60%, 80% open) and create an efficient production. All of these things can be paramterized to allow for more samples or more panel types as needed or based on your calculation limits.
The only exception would be proper environmental analysis, say, if you were trying to reduce solar gain in summer and allow for it in winter. You would want to split this calculation between when you need to be gaining heat and where you want to be shading. Then extrapolate the percentage between the two. You may even need a gradient of heat gain through fall/spring. The possibilities depend on how much you know about the mechanical requirements of the area/building.
That would be my approach. If I have more time tonight I will try and put something together on this as its been something I'd like to have in my back pocket....
Edit: You would also need to analyze the angle of incidence as it could have an effect on the amount of solar gain.....…
pproach of estimating wind loads using design codes such as ASCE7-05.
B) Hiring a wind expert to construct a physical model and and calculate wind pressures measured directly from a wind tunnel test.
A) will allow you to derive a site specific wind design pressure based on the height of the building, surface roughness, site location etc. Typically you then multiply this pressure by an appropriate co-efficent in the code for a given building shape.
The other atypical method it to use numerical approaches such as CFD. This approach is not yet accepted due to nuances such as of surface roughness.
Building deflection is again subjective. Doing a modal analysis and getting an idea of the frequency is better. You can increase the frequency by playing about with the building stiffness.
You need to modify the stiffness of the building to get the deflection down. i.e. play about with geometry, add extra members with stiffness, reduce weight, use material with higher elastic modulus etc
If you are getting a 7m deflection for a 400m building then I can right away that is way too soft. That is equivalent to 400m/7m or H/57. You want to be at least H/500 to H/1000 so aim for 80 to 40 mm.
Your wind load seems reasonable at 87 psf for that height of building
…
oks like all your GH components are disabled? I just tried baking the cone from my earlier code and using that but can't see anything at all.
OH! You had 'Display | Shaded Preview' disabled - why? Now I see that you have 80 X 55 'SFrames', which will be VERY SLOW. I never understood why you abandon 'PopGeo'? But that many points will be extremely slow either way. I won't wait that long.
You're making this way too hard for me, bobbi.
I said early on that it's best to work with a very low count until everything works properly. Solid unions are one of the ragged edges of Grasshopper; slow and prone to failure, depending on the complexity of the geometry (co-planar surfaces, etc.).
Good luck!
P.S. I can see two problems here:
Surface normal is in instead of out.
You didn't 'Cap Holes' on the lofted tubes so they aren't solid "Closed Breps".
I have no clue what you're doing. Do you? :)…
k on forum?
or
B) install from a networked location?
Second question.
If you download from link do you:
A) read the post because you want to see what changes have occurred?
or
B) ignore the post as you are too excited to get the latest version up and running?
Third question.
When confronted by a demanding LOL cat telling you to update software do you:
A) nod approvingly and think "I must do that"?
or
B) freak out and get a sudden urge to eat cheeseburgers?
In all seriousness question three can be omitted.
EDIT: 80 views and only two posters! (thank you Simone and Luis).
I am actually interested in the results
SOLUTION TO DLL ERROR: install this …
Added by Danny Boyes at 3:32am on October 25, 2011
umbrella of Urban Heat Island (UHI) and I am going to try to separate them out in order to give you a sense of the current capabilities in LB+HB.
1) UHI as defined as a recorded elevated air temperature in an urban area:
If you have access to epw files for both an urban area and a rural area, you can use Ladybug to visualize and deeply explore the differences between the two weather files. Ladybug is primarily a tool for weather file visualization and analysis and it can be very helpful for understanding the consequences of UHI on strategies for buildings or on comfort. This said, if you do not have both rural and urban recorded weather data or you want to generate your own weather files based on criteria about urban areas (as it sounds like you want to do), this definition might not be so helpful.
2) UHI defined by air elevated air temperature but viewed as a computer model-able phenomenon resulting primarily from urban canyon geometry, building materials, and (to a lesser degree) anthropogenic heat:
This definition seems to fit more with they type of thing that you are looking for but it is unfortunately very difficult and computationally intensive such that we do not currently have anything within Ladybug to do this right now. I can say that the state-of-the art for this type of modeling is an application called Town Energy Budget (TEB) and this is what all of the advanced UHI researches that I know use (http://www.cnrm.meteo.fr/surfex/spip.php?article7). Unfortunately for those trying to use it in professional practice, it can take a while to get comfortable with it and it currently runs exclusively on Linux (this does mean that it is open source, though, and that you can really get deep into the assumptions of the model). A couple years ago, a peer of mine translated almost all of TEB into Matlab language making it possible to run it on Windows if you have Matlab. He wrapped everything together into a tool called the Urban Weather Generator (UWG), which can take an epw file of a rural area and warp it to an urban area based on inputs that you give of building height, materials, vegetation, anthropogenic heat, etc. I would recommend looking into this for your project, although, bear in mind that is it not open source like the original TEB tool and that you may need to get a (very expensive) copy of MATLAB (http://urbanmicroclimate.scripts.mit.edu/uwg.php).
3) UHI as defined by a thermal satellite image of an urban area depicting an elevated average radiant environment that reaches a maximum a the city center and changes by land use:
This is the definition of UHI that I am most familiar with and was the basis of much of my past research. I feel that it is also a definition of UHI that is a bit more in line with where a lot of contemporary UHI research is headed, which is away from the notion of UHI as a macro-scale meteorological phenomena that is averaged as an air temperature over a huge area towards one that accepts that different land uses have different microclimates and (importantly) different radiant environments. While the air temperature difference between urban and rural areas usually does not change more than 1-4 C, the radiant environment can be very different (on the order of 10-15 C differences). The best way to understand UHI in this context is with Thermal satellite images, for which there is ha huge database of publicly available data on NASA's glovis website (http://glovis.usgs.gov/) or their ECHO website (http://reverb.echo.nasa.gov/reverb/#utf8=%E2%9C%93&spatial_map=satellite&spatial_type=rectangle). I tend to use thermal data from LANDSAT 5-8 and ASTER satellites in my research. Unfortunately, there is a lot f bad data with a lot of cloud cover mixed in with the really good stuff and it can take some time to find good images. Also, there aren't too many programs that read the GeoTiff file format that you download the data as. I know that ArcGIS will read it, a program called ENVI will read it (I think that the open source QGIS can also red it). I have plans to write a set of components to bring this type of data into Rhino and GH (I may get to it a few months down the line).
4) UHI as a computer model-able notion of "Urban Microclimate" with consideration of local differences and the local radiant environment:
This is where a lot of my research has lead and, thankfully, is an area that Honeybee can help you out a lot with. EnergyPlus simulations can output information on outside building surface temperatures and these can be very helpful in helping get a sense of the radiant environment around individual buildings. Right now, I am focusing just on using this data to fully model the indoor environments of buildings as you see in this video:
https://www.youtube.com/watch?v=fNylb42FPIc&list=UUc6HWbF4UtdKdjbZ2tvwiCQ
I have plans to move this methodology to the outdoors once I complete this initial application to the indoors. For now, you can use the "Surface result reader" and the "color surfaces based on EP result" components to get a sense of variation in the outside temperature of your buildings.
I hope that this helped,
-Chris
…
ce issue with Rhino and shouldn't make an issue with EnergyPlus but just to have cleaner geometries, I untrimmed base surfaces so zones are closed brep now.
I also noticed that when you are adding multiple openings to a surface, the surface doesn't show-up in the output of createHBZoneFromHBSurfaces. The surfaces are there though and show up once you explode the zone! Again should be a tolerance issue for join. I need to take a closer look to both of these.
Also, in a number of the zones you had wall surfaces connected to createZoneFromHBSurfaces both before and after adding glazing. I removed parent surfaces so you don't end up having duplicate surfaces.
Back to adjacency which was your question, the issue happens since you have couple of zones with the same name so component was assuming them to be the same zone so it wouldn't solve the adjacency (Yes! it shouldn't. That was a bug which is fixed now). I changed the names and now it should find the surfaces that you are looking for.
Moreover, once you solve the adjacency, next solveAdjacency won't overwrite the BC unless you set remCurrentAdj to True.
Mostapha…
correct:
- the right value in the 0. path {0;77} is the smallest one.
- right value in the 1. path {0;78} is the value which is closest to the chosen value in the preceding path
- ..and so on for {0;79} and {0;80}
but when the paths change their first level, the iteration should start from the beginning:
- right value in the 4. path {1;32} is the smallest one.
- right value in the 5. path {1;33} is the closest to the chosen one in {1;32}.
- right value in the 5. path {1;34} is the closest to the chosen one in {1;33}.
..to be continued.
..this is, what I want to achive in the VB code, I implemented at the beginning of the discussion.
..and this is how I designed the input-parameter of the VB-element:
if someone could help me .. super-great!
…
Mac due to its versatility , but given this new laptop will be using mainly on Rhino, GH , i have some doubts whether to switch to a window based laptop.
I have a look at some high-end window laptops, Dell Alienware for example, with same specs as MBP and found the price are even more expensive than MBP , about 10-15 %.
With the new Rhino 5 is coming , will Bootcamp be good and efficient enough to run Rhino, GH and some rendering programs?
From my experience i find Rhino and Gh run smoothly on Bootcamp , but never run those programs on window based laptop myself , it's impossible for me to know the differences.
Some say BootCamp only deliver 80% performance of the program , if it's true i would really consider switching to window based laptop.
Any suggestions?
and if you suggest me to switch , what brand should i go for ?
Thank you,
…