pavilion) and from that i want to fabricate it using some paper or card bored .
for modeling the pavilion i used a simple kangaroo based algorithm to generate the desired form using mesh 3d plane faces . there was no problem with this part and i was able to get the mesh from geometry out put . then i wanted to use that output mesh to panelize it and then adding tabs and the nesting and cutting to get the parts. but the problem was every tutorial i looked up were using surfaces to panelize and nest so this was the first problem to convert the mesh into a surface and then panelazing and nesting . i tried using the mesh2nurbs but it didn't work out for me . (because i needed a single surface not some poly surfaces) . (attachment | input mesh )
so i started from the beginning and tried using a surface as an input for kangaroo and thus getting a surface as an output so i did that and tried to create a surface by the Surface from points component . and the result was not good the surface was kinda messed up and the the reason was the points were not ordered well i guess . so this was another problem for me . (attachment | input surface)(picture below)
so basically i have a few main questions :
1. is there a tutorial or any topic or book or somthing that explains from 0 to 100 from design to fabrication (as an example a pavilion) ?
2. can i use the mesh to panelize and nest and then fabricate ? and are there any tips or tricks to it ?
3. is the starting from surface for me a good idea or not ?
i am extremely sorry for talking this much and i'm grateful for the time you spent on reading this .
best wishes ; Babak.
…
nterior designers, architects and civil engineers)
certificates are offered from the center for continuing and professional education in BAU!
starting date 6/9/2021, end date 21/9/2021
( days:6-7-9-10-13-14-16-17-20-21)
10 days
2 hours/day
Total hours 20
(BAU fees 500 000L.L
Non BAU fees 700 000L.L
Foreigners fees150$)
videos links for workshop results
video 1 link:
https://baudom-my.sharepoint.com/:v:/g/personal/f_belok_bau_edu_lb/EUSs6VOpTv9BglgQHHk_nbsB0iLt9NsxKBj23acjmrpuyw
video 2 link:
https://baudom-my.sharepoint.com/:v:/g/personal/f_belok_bau_edu_lb/ETvjbvNd97lCss_cBJzwwAsBsoPl4WOGWGHD9WAF87TKuQ
TO REGISTER and for more details contact Dr. Fatima Yahya Belok through Facebook or the following number
Contact: 0096171447889
Email: fatimabelok21@gmail.com…
t. So here we go!
1. Honeybee is brown and not yellow [stupid!]...
As you probably remember Honeybee logo was initially yellow because of my ignorance about Honeybees. With the help of our Honeybee expert, Michalina, now the color is corrected. I promised her to update everyone about this. Below are photos of her working on the honeybee logo and the results of her study.
If you think I'm exaggerating by calling her a honeybee expert you better watch this video:
Thank you Michalina for the great work! :). I corrected the colors. No yellow anymore. The only yellow arrows represent sun rays and not the honeybee!
2. Yellow or brown, W[here]TH Honeybee is?
I know. It has been a long time after I posted the initial video and it is not fun at all to wait for a long time. Here is the good news. If you are following the Facebook page you probably now that the Daylighting components are almost ready.
Couple of friends from Grasshopper community and RADIANCE community has been helping me with testing/debugging the components. I still think/hope to release the daylighting components at some point in January before Ladybug gets one year old.
There have been multiple changes. I finally feel that the current version of Honeybee is simple enough for non-expert users to start running initial studies and flexible enough for advanced users to run advanced studies. I will post a video soon and walk you through different components.
I think I still need more time to modify the energy simulation components so they are not going to be part of the next release. Unfortunately, there are so many ways to set up and run a wrong energy simulation and I really don’t want to add one new GIGO app to the world of simulation. We already have enough of that. Moreover I’m still not quite happy with the workflow. Please bear with me for few more months and then we can all celebrate!
I recently tested the idea of connecting Grasshopper to OpenStudio by using OpenStudio API successfully. If nothing else, I really want to release the EnergyPlus components so I can concentrate on Grasshopper > OpenStudio development which I personally think is the best approach.
3. What about wind analysis?
I have been asked multiple times that if Ladybug will have a component for wind study. The short answer is YES! I have been working with EFRI-PULSE project during the last year to develop a free and open source web-based CFD simulation platform for outdoor analysis.
We had a very good progress so far and our rockstar Stefan recently presented the results of the work at the American Physical Society’s 66th annual DFD meeting and the results looks pretty convincing in comparison to measured data. Here is an image from the presentation. All the credits go to Stefan Gracik and EFRI-PULSE project.
The project will go live at some point next year and after that I will release the Butterfly which will let you prepare the model for the CFD simulation and send it to EFRI-PULSE project. I haven’t tried to run the simulations locally yet but I’m considering that as a further development. Here is how the component and the logo looks like right now.
4. Teaching resources
It has been almost 11 months from the first public release of Ladybug. I know that I didn't do a good job in providing enough tutorials/teaching materials and I know that I won’t be able to put something comprehensive together soon.
Fortunately, ladybug has been flying in multiple schools during the last year. Several design, engineering and consultant firms are using it and it has been thought in several workshops. As I checked with multiple of you, almost everyone told me that they will be happy to share their teaching materials; hence I started the teaching resources page. Please share your materials on the page. They can be in any format and any language. Thanks in advance!
I hope you enjoyed/are enjoying/will enjoy the longest night of the year. Happy Yalda!
Cheers,
-Mostapha
…
e following is the shading control part of my .hea file generated from honeybee. I believe the 1 underneath represents the number of the states I input. When I switch both of the "1" within the .hea. The batch files would start the process but there is another bug for the gen_gdp_profile. It was having problem with .oct that it is looking for outside_daysim.rad which is not exist in the tmp within the folder.
I am still running the gen_dc and I will update it over if I encounter any error after editing the .hea file.
…
to perform the kind of merge I want. Basically:
I have a series of three integers, each representing a radius measure:
Radii[0-2]
I have a three sets of series of 3Dpoints, each set with ~100-400 vals:
PListOne[0-333]
PListTwo[0-333]
PListThree[0-333]
I want to link the data paths up so that the Radii form the first dimension of the array, and that the second dimension is the corresponding points set. So
Radii[0] = 500 (the radius)
Radii[0][0] = 50,75,0 (the first point in PListOne)
...
Radii[2][99] = 44,66,0 (the 100th point in PListThree)
This should be really simple, but I cant seem tog et my head around the right components to do it. I've attached a file with number series in place of the radii/points lists. If someone could show me how to merge the components in the manner above, it would be extremely appreciated.…
seem to find a working solutution. Doing this by hand is not a option, as I need to export up to 500+ dwg files, so any kind of automation is usefull.
So in essence I need to export 2 layers, with each layer containing a couple of crv's to DWG. The dwg should include this layers structure when opened
In the forum I found two components that should have this kind of functionality, but neither seem to work or is still supported.
I am currently testing with the TTtoolbox plugin and its CADexporter, however this does not support the export of multiple layers. Only 1 layer can be exported.
The Finches components could possibly be useful for export batch processing, but the component is not longer for download as the makers (http://www.nicholas.demonchaux.com/) website is offline. I am currently on Rhino 5, with GH 0.9.0075, so if comeone can share a gha file of this, that would be much appriciated.
Are there alternatives that are being used by the community that i am aware of? As this seem to me has been of use to more people…
.
I had updated the components a few weeks ago but then got too lazy/busy to properly document that anywhere. Some of the additional features are:
1. It is now possible to substitute an IES file with a text string. For example one can paste the contents of an IES file into a text panel and connect that to the input for _iesFilePath. Alternatively, you can read a text file using the native Grasshopper "Read File" component, then embed (and internalize) that information inside the "Text" component.
So, either of the below two options will(should) qualify as an input for the _iesFilePath:
This makes it possible to embed IES data inside a GrassHopper file, thus doing away with the need for connecting to a file on a local drive.
2. I created a new component called Honeybee_IES Project which does the following:
1. It consolidates all the electric lighting RAD files for a simulation in one place. The single radFilePaths output from the component can be connected to the daylight simulation instead of connecting individual radFilePath outputs from every luminaire.
2. It creates a BOQ and luminaire schedule for all the luminaires used in the simulation. The schedule can either be viewed in a Grasshopper text panel or exported as excel.
The values for LLF, Candela Multiplier and Lamp Depreciation factor are printed out for each luminaire.
The effect of the multipliers on power consumption can be seen in the BOQ in the Total Power column:
Adding lumens to the output will be minor fix. I will update that within a few days.
I think the point-grid for the photometric and peak candela display are a great idea. I will add that functionality within a couple of weeks.
Are you implying the inclusion Type B photometry by "support for all ies file types" ? If so, that has been on my to-do list for a while. It might, however, be a while before I can get to it as it would require writing a convertor from Type C to Type B so that it can be visualized as a photometric mesh inside the Rhino viewport. I think the hackish way to get Type B photometry to work in Honeybee is to first convert the Type B photometry to Type C using something like the Photometric Toolbox.
Finally, the electric lighting components were initially written as a hack and they are still pretty much work-in-progress. I agree that calling the simulation a lighting simulation and adding separate inputs for electric lights would be a cleaner way of approaching these simulations. Mostapaha and I weren't sure of the traction that these new features might get. Based on the feedback received we will be simplifying and enhancing these components and the workflow to do electric lighting simulations.
(PS: Although I have heard a lot about Accelerad, due to the lack of compatible resources, I have never run a gpu-based simulation myself. I am not sure if Nathaniel requires additional flags or information to run Radiance simulations through Accelerad. If not, it should be possible to use files written through Honeybee to run Accelerad simulations. I will defer to Mostapha on the possibility of incorporating Accelerad in the Honeybee project).
…
me" module. Strangely enough, the multi-threaded one runs remarkably slower, whereas the order of the printed results is senseless. Does anybody have experience on how to make it work properly? Already checked the post here.
import System.Threading.Tasks as tasks import time, math
#single-threaded
start = time.time() for i in range(1,501): print i end = time.time() print "single = ", end-start
#multi-threaded
iterations = 500 def get_i(i): print i start = time.time() tasks.Parallel.ForEach(xrange(iterations), get_i) end = time.time() print "multi = ", end-start
1. As (a) the values are printed in random order and (b) the computing time is high, are there any clues what i am doing wrong?
2. Is there a more accurate way to compute the required time for a command or a chunk of a script?
Thanks and best,
jnm
…