add another "trivial" constrain to the puzzle (for instance the PC sheets are 1.2*2.2m > meaning the obvious). This is addressable ONLY via the black bill (don't even think to use GH components for solving similar stuff).
3. One-off nodes are probably OK BUT for larger scales you'll need MERO type of approach > meaning assembly/component concepts > meaning dealing with instance Rhino definitions: blocks in plain English (don't even think to use GH components for solving similar stuff).
4. "Engulfing" type of strut extrusions are rather the best option (use aluminum in this case) > meaning profiles that can "wrap" the triangle content edge (be that "paper" or Lexan/PC).
5. The whole thing appears "easy" but on a pro level is rather quite challenging and obviously totally undo able without the black pill.
6. So: mesh relaxation <> adapter topology matters <> pack issues <> component design <> triangle content design <> cost <> you named it (for <> read "interact").
Such a "simple" case ... eh? …
nstalling of 3 previous versions of Ladybird and Honeybee but nothing different happened. This was all happening on a desktop PC running windows 10 and with a wired connection to the internet router (via a switch). I then tried installing Ladybug and Honeybee on a MacBook Pro running Windows 7 on bootcamp. This computer was wirellesly connected to the same router. The installation of the latest version was very smooth and all the right files of the right sizes appeared without any problem on the first import of Honeybee-Honeybee. I then copied the files over to the other computer. Solved.
1. good thing I didn't know that as I wouldn't have kept on trying to resolve it!
2. Ok, sticking with it - besides I would hate miss out on such a major release!
3. Makes sense.
4. ok, I thought that that was the main file because of the EP in the title - I now have them both anyway.
5. Now that you say this when I click on the file in github and download it from the view raw link then I do get the right file size. But when I have been trying to download it directly from the root folder (i.e.Honeybee/resources) with "save link as" then I get the 36kB. Could it be that Honeybee_Honeybee was doing something similar?
Many thanks again to both of you - great work out there!
best,
Alex…
need to download those dll, right, it should be the same for the trees?Is there anyway to make it more precise? Analising the geometry with the google maps it seems that unfortunatelly some parts are missing.…
component I just used different components and GH tools to do the same - and this become part of my short paper submission for SimAUD 2016). My solution compares the height of the same points of different solar envelope and then chose the lowest one. I read about the improvement you are working on and it is good but I think it is not yet what I need (or how the solar envelope tool could be more complete).
What I need is a solar envelope that would guarantee on different facades with different orientations (the example I sent you) a certain amount of direct sunlight, say 4h per day in a given period for example all the month of June at 60°N. So to guarantee the south facing facade I should chose the vectors from 10 to 14. But these are not ok for all the other facades because in this timeframe the East and West facing facades get only 2 hours and the North get 0 hours.
So the fist step would be have the possibility to chose different sun vectors for different facades. For the example I did (the 4 hours in June at 60°N) the south facing facade would need from 10 to 14, the East facing for example from 8 to 12, the West facing facade from 12 to 16 and the North facing facade from 6 to 8 and from 18 to 20.
If I would chose a single longer time frame that could get all these hours, from 8 to 20 then the resulting solar envelope would result probably smaller than the sum of the four solar envelopes.
But this is not complete yet. I mean the use of different sun vectors on different facades. The reason is that for example when I chose the sun vectors from 8 to 12 for the four hours on the East facing facade how do I know that the sun hit on the facade in that time frame or maybe it is obstructed by surrounding buildings? Since the sun at 60°N (where I live) in June rise at around 3.15 then maybe for that specific facade the sun hit from 4 to 8 and not from 8 to 12.
I did an extreme case talking about 60°N and that maybe the sun hit on a facade at 4 instead than 12, but it is just to make understand the logic. My suggestion for a more advanced solar envelope it should be integrated with the Sunlight Hours tool of ladybug. So the input should not be the sun vectors because I don't know when the sun hit on the facade but the input should be just the desired number of hours and the possibility to specify different number of hours for each facade. Then this last component that sum different solar envelope (I didn't use it yet but I understood what it does) should be integrated yes so the result would be one single solar envelope more likely using the lowest points (the highest I don't understand what for).
Let me know what you think!
…
K. I can do everything I need to with Rhino4, and I'll re-install my PC in a month or two... I guess everything will be fine afterwards ;)
Thanks again for your help.…
again but now I have no components on Rhino 5 Grasshopper. And it still is the 8004 version (minus any components!) I loaded the microsoft plug in for 64 bit ok.
Any suggestions on how to fix this? Many thanks in advance. Karen…
obviously) with a gorgeous girl (she's learning the basics).
2. 5 Cigars (Partagas obviously)
3. 7 triple espressos (Huan Valdez obviously)
Next phases: canopy stressed cables, design the base of the whole thing, planar glazing facade, putting real stuff (made in Microstation) into place.
…