algorithmic modeling for Rhino

Search Results - 分分快3最准高手助赢计划-『8TBH·COM』福利彩票开奖结果012期查询--2023年3月19日6时48分50秒.H5c2a3.5jexii16x-gov-hk

Comment on: Topic 'FLICKR API and Grasshopper': doing this with the current tools or a bit of scripting since the Flickr API allows you to make requests in a REST format, but utilizing the Flickr.net API library makes it much simpler. First and foremost, you need a Flickr API key...do you have one of those? A great way to get to know the Flickr API is with the API Explorer. Here is a link to the page for the flickr.photos.search method explorer: http://www.flickr.com/services/api/explore/flickr.photos.search The cool thing about this page is that it generates the REST Http call towards the bottom. So, here is what I did: 1. Grab the coordinates of the bounding box per Flickr API request: bbox (Optional) A comma-delimited list of 4 values defining the Bounding Box of the area that will be searched. The 4 values represent the bottom-left corner of the box and the top-right corner, minimum_longitude, minimum_latitude, maximum_longitude, maximum_latitude. Longitude has a range of -180 to 180 , latitude of -90 to 90. Defaults to -180, -90, 180, 90 if not specified. Unlike standard photo queries, geo (or bounding box) queries will only return 250 results per page. Geo queries require some sort of limiting agent in order to prevent the database from crying. This is basically like the check against "parameterless searches" for queries without a geo component. A tag, for instance, is considered a limiting agent as are user defined min_date_taken and min_date_upload parameters — If no limiting factor is passed we return only photos added in the last 12 hours (though we may extend the limit in the future). So, I went to Google Earth, picked a city (London, UK) and dropped two pins: This gave me two locations, which I can put into the Explorer Page next to the bbox option. Here is what I put for these two points: -0.155941,51.496768,-0.116783,51.511431 2. Check has_geo 3. In extras, type in geo 4. Make the call! You will see a list of responses in an XML format, these responses will be from the first page. Geolocated photos are limited to 250 / page, so you will have to grab them page by page. If you want to add more options (minimum upload date, maximum upload date, etc) you can do this as well) The best is at the bottom, you get the full http call for this: http://api.flickr.com/services/rest/?method=flickr.photos.search&api_key=ffd44f601393a46e86aa3a5f8a013360&bbox=-0.155941%2C51.496768%2C-0.116783%2C51.511431&has_geo=&extras=geo&format=rest&api_sig=b42330e5d1523bd5fe60c2ad43acde99 Notice this call has some other api key, you should eventually replace this with your own. You could copy and paste this into a browser and you will get the results with the latitude and longitude: So this is really what you need to know to do this through GH. Since gHowl has an XML parser component that can access files on the web, you should be able to use the same http call into this component. Eventually, we get a response, and we need to grab the lat and lon data. With gHowl we can map these to xyz coordinates, and generate the heatmap...this is just a linear mapping: Attached are both the Rhino file and the Grasshopper file, as well as the image underlay. I am working on a series of components that makes this more straightforward, but for now, this should get you started. …; Added by Luis Fraguada to gHowl at 3:45am on March 1, 2013

Topic: Five-story building: as one element. Thank you Comment by karamba on October 7, 2014 at 11:27pm Hello Patricio, divide the beams in such a way that each boundary vertex of the shell becomes an endpoint of a beam segment. Best, Clemens Comment by Llordella Patricio on October 8, 2014 at 8:30amDelete Comment Hi Clemens, I did what you suggested but now assemble element doesn´t work properly. Could you please tell me how to fix it? Thanks in advance, Patricio 8-10-14losa%20cadena.gh Comment by karamba on October 8, 2014 at 11:59am Hi Patricio, if you flatten the 'Elem'-input at the 'Assemble'-component the definition works. The triangular shell elements have linear displacement interpolations whereas the beam deflections are exact. In order to get correct results you should refine the shell mesh. Best, Clemens Comment by Llordella Patricio on October 9, 2014 at 8:35amDelete Comment Hello, succeeds in creating the mesh to the slab, and built the beam segment, but when I see the deformations are not expected because the beam is deformed as the slab. Thanks for the help PS: maybe I'm using the program for a type of structure that is not the most appropriate, as I saw in the examples of other structures. But this type of structure is that students taught best regards Patricio 9-10-14%20Example%201.gh Comment by karamba on October 9, 2014 at 10:46am You could use the 'Mesh Edges'-component to retrieve the naked edges and turn them into beams - see attached file:91014Example1_cp.gh Best regards, Clemens Comment by Llordella Patricio on October 15, 2014 at 3:41pmDelete Comment Dear clemens I was doing a rough estimate of the deformation, and I can not achieve the same result with Karamba. When I make a rough estimate of the result with Karamba beams and mine are very similar, I think the problem is when I connect the shell, because there are no similar results. I sent the GH file, and an image of the calculation The structure is concrete The result I get is 0.58cm thank youPatricio 15-10-14%20Example.gh Comment by karamba yesterday Dear Patricio, try to increase the number of shell elements. As mentioned in the manual they are linear elements. A mesh that is too coarse leads to a response which is stiffer than the real structure. Best, Clemens …; Added by Llordella Patricio to Karamba3D at 12:33pm on October 22, 2014

Topic: Honeybee simulations for "curved NURBS surfaces": n be obtained for curved NURBS surfaces as well as unconventional window configurations". And I also noticed the following information form the optional input in the runEnergySimulation component. "meshSettings_: Optional mesh settings for your geometry from any one of the native Grasshopper mesh setting components. These will be used to change the meshing of curved surfaces before they are run through EnergyPlus (note that meshing of curved surfaces is done since Energyplus is not able to calculate heat flow through non-planar surfaces). Default Grasshopper meshing is used if nothing is input here but you may want to decrease your calculation time by changing it to Coarse or increase your curvature definition (and calculation time) by making it finer". 1) My case is an one-story, rectangular-plan large hall (40m*70m*25m) with a curved roof. The roof surface is a part of a standard sphere and the walls and floor are all planar (the each wall has one curved edge as showed in the image). For testing, I threw the original curved roof surface into daylight and energy simulations without making customized meshings, because I assumed that it might be automatically converted to meshs by Honeybee - Am I right? As showed in the image, how can I reduce the number of meshs in a proper way? Must two connected surfaces (i.e. wall and roof) be STRICTLY/SEAMLESSLY connected or not (considering different divisions of meshs in the respective surface)? - Is a connection tolerance allowed? 2) But, when I run the annual daylight simulation for this case, it gave me a lot of warnings "oconv: warning - zero area for polygon".- is that normal? and how to avoid this? Does the daylight simulation allow "curved NURBS surfaces"? 3) Moreover, when I run an energy simulation for this case, it costed extremely long time. It was just so long that I did not even have results out of one simulation. - I guessed it might be the problem caused by the curved roof surface (or automatic meshing?), but I don't have experience of converting a curved NURBS/spheral surface into correct meshs that can be recognized by Honeybee simulations (Daylight and Energy) in a proper way. 4) The large window on the wall was generated by the "_glzRatio". But the automatically generated wall meshs around this window are just too "fine", which might largely increase simulation time. Is there a proper way to get rid of it? (Considering that the size, shape and position of the window will have large influence on the daylight distribution in the building, it is worthy to keep the size, shape and position of the window as it should be in reality). In sum, considering all above, could your please provide me some suggestions/tutorials/links that might be helpful for dealing with "curved NURBS surfaces" in Honeybee simulations. Thank you all in advance! Best, Ding …; Added by Ding to Ladybug Tools at 5:32am on May 11, 2015

Topic: How could I divide a tree with branches of different sizes to multiple trees with the branches of the same size?: j 1 c e h k 2 f ------------------------------------------------------------------------------------------------- To these... 0;0 0;1 0 a i ------------------------------------------------------------ 0;0 0;1 0;2 0 b g j 1 c h k ------------------------------------------------------------ 0;0 0 d 1 e 2 f ------------------------------------------------------------ Thanx……; Added by sadegh at 9:52pm on June 15, 2015

Topic: voronoi/facet dome pattern relaxation on a sphere surface: erning how to do that on a sphere. So I know already all the different approches of how to get a relaxed voronoi pattern on a free-form open surface, but still don't know how to obtain the same elegant effect on a sphere (or an ellipsoid closed surface, whatever), or how to relax the facet dome cells. Andrew stated on his site that he used kangaroo for this project, so the Spore Lamp consists in my opinion either of a relaxed voronoi 3d diagram (b-rep, b-rep intersection) on a sphere the cells of which have been planarized later on, or more likely it is a sort of relaxed facet dome. The trick is to: 1. obtain a nicely-balanced voronoish diagram (or facet dome cells) on a sphere 2. keep each cell/polyline planar (or force them with kangaroo to be planar) in order to move scale and loft them later on. Here is what I have by now.(files: matsys spore lamp attempt) That's the closest appearance that I got so far (simple move scale and loft of facet dome cells with the amount of transformations being proportional to the power of the initial cell area: bigger cell = bigger opening etc.) - with no relaxation of the diagram. But it's obviously not the same thing as the matsys design. Here are some of my attempts of facet dome relaxation, but well, it's certainly still not the right approach, and most importantly I don't know how to keep or force the cells to be planar after the relaxation. 1. pulling vertices to a sphere - no anchor points. That obviously doesn't make sense at all, but the relaxation without anchor points gives at the beginning a pattern that is closer to what I am looking for. (files: relaxation 01) 2. pulling vertices to a sphere - two faces of the initial facet dome anchored (files: relaxation 02) 3. pulling vertices to the initial geometry (facet dome) no anchor points (files: relaxation 03) The cell pattern of the lamp kinda looks like this: You can find it here: http://www.grasshopper3d.com/forum/topics/kangaroo-0-095-releasedgroupUrl=kangaroo&x=1&groupId=2985220%3AGroup%3A120977&id=2985220%3ATopic%3A972434&page=2#comments Done with Plankton (of course without the "gradient increase" appearance), but in fact not, I took a look at Daniel Parker's Plankton example files, and it's not quite the same thing. Also the cells aren't planar... The last problem is that during the relaxation attempts that I did, the biggest initial cells became enormous, and it's not like that in the elegant project by Andrew Kudless, that I'd like to achieve. So to sum up: Goal no 1: Obtain an elegant voronoi /facet dome cell pattern on a sphere (or an ellipsoid surface, whatever). Goal no 2: How to keep the cells planar in order to be able to loft them later, obtain those pyramidal forms, and assemble easily Have you got any ideas? Or maybe there's a completely different approach to that? Cheers, and thanks in advance…; Added by Benoit Martel at 12:30pm on March 2, 2016

Blog Post: MATLAB + Grasshopper

Matlab + Grasshopper

I’m writing this post as a response to …

Added by Mostapha Sadeghipour Roudsari at 4:05pm on January 4, 2013

Topic: Mesh Brep vs Mesh From Closed Polyline Rhino command: ch has a vertex in each of the vertices of the polyline. But, when I try to create the mesh using the Mesh Brep component, I get a simplified mesh, where the extra vertices in the edges of the polyline have disappeared. I think it is easier to understand what I am trying to say with the following screenshots: Polyline: Mesh created with the rhino command: Mesh created using grasshopper: The last mesh has less faces, as the Mesh Brep component gets rid of the extra vertices that define the polyline. Any suggestions? Thanks, Diego…; Added by Diego at 10:34am on July 27, 2012

Topic: Update + Happy Yalda!: 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 …; Added by Mostapha Sadeghipour Roudsari to Ladybug Tools at 3:54pm on December 21, 2013

Topic: Python inside C# Visual Studio: imeBinder.CSharpArgumentInfo.Create' Is it possible to solve this issue? using System; using IronPython.Hosting; using IronPython.Runtime; using Microsoft.Scripting; using Microsoft.Scripting.Hosting; using Microsoft.CSharp; namespace Bob.Meshes { public class pythonFromCShapr { ScriptEngine engine = Python.CreateEngine(); public pythonFromCShapr() { } public void something() { dynamic scope = engine.CreateScope(); scope.Add = new Func<int, int, int>((x, y) => x + y); Console.WriteLine( scope.Add(2, 3)); } } }…; Added by Petras Vestartas at 9:34am on June 13, 2016