algorithmic modeling for Rhino

Search Results - 【p26.pw】GoogleにあなたのWebサイトを迅速にインデックスする方法.260125105255

Comment on: Topic 'Into to Grasshopper Webinar - feedback, recording, and files': his comes in the form of an HTML page with links to every component, so you will need to view it in your web browser. (I use Chrome and it doesn't seem to be working correctly, but when opened in IE its fine.) 2) Included in each help topic for each component is the Inputs and Outputs descriptions and data types. 3) You supply the data. What you supply and how you supply it is for you to decide. There are umpteen different ways. Are you asking for a list of those ways for each input? 4) Points can either be Rhino objects or 3D co-ordinates. To create a point you can use any of these methods, but it mostly comes down to user preference. I like using Panels as this displays outside of the component. 5) Because of the nature of vectors they represent magnitude and direction but they don't have an independent location, so there is a component that will display vectors in Rhino. 6) The user. 7) There is a Primer on the front page. Here you find the Basics, but because GH is ever evolving in its current beta state you might find things that aren't relevant any more or simply don't work the same. And here is the reason why nobody is writing an update because it could be soon out of date. 8) Importing images by either dragging them from explorer onto the canvas or right click context menu Image... 9) Single line = Single Item of Data. Double line = Multiple items of data on the same Branch. Dashed Double Line = Multiple Data on Multiple Branches. 10) User preference 11) Toolbar management is probably the bane of David's life. Most things are logically placed. For example the Curve Tab, Primitives are any simple curve types that you are creating from scratch. Similarly Splines is for more complex curve types created from scratch. Analysis is where you find components that are finding answers supplied by curves, control points, curvature, parameters, end points etc. Division is a subset of this category but has a group of its own. And Utilities is where you find curve related actions that you want to perform, offsetting, rebuilding projecting, exploding etc. 12) I would image it would have been the Point On Curve component in Curve>Analysis. Why that group? You are not putting a point on a curve you are analysing a curve for the location of a point based on some parameters that you are supplying. For example "what is the mid point?" I hope this goes some way towards answering you questions. No doubt this will have generated more so don't be afraid to ask, it took me several releases of Explicit History (aka Grasshopper) before I realised what the egg did, it never occurred to me that I could put my objects into Rhino when I was finished. Or the fact that I could use panels to 'see' data outputs. Al the best, Danny…; Added by Danny Boyes at 3:48am on December 9, 2010

Comment on: Topic 'Clusters 3.0': a "use as input" or "use as output" button" I don't want to replace the arrow ui, because the arrows allow you to specify the order of inputs/outputs (the order -top to bottom- of the arrows on the screen controls the order of cluster inputs/outputs). Also, they allow you to create a single input for multiple parameters without actually creating that parameter. Finally, they make it very clear which parameters act as gateways between clusters and their owners. If it turns out that it's really annoying to have to deal with the arrows I can try and come up with a secondary ui as well, but I'd like to post-pone that as long as possible. "'Update Cluster' allows to update a cluster with a new ghx definition or replace it with another." I can see that being useful, but then that's probably useful to have as a generic feature, not just clusters. It would be nice to be able to switch out script or expression or division components in the same way. "Another feature that would improve cluster sharing is editable input and output descriptions to explain the cluster functionality." Agreed. "'Explode cluster' would allow to revert it to an unclustered state" Agreed. "'Cluster properties' would allow to set author name, help information, revision, a URL to update the cluster, to see the path of the loaded definition, name, nickname, description, Category, subCategory, icon... " Agreed. Do note that you can set the icon (of any object, not just clusters) just by dragging a 24x24 pixel image from Windows Explorer onto the object. "Since asking isn't the hard part...'Share cluster' could upload it to a component sharing website where users can download and rate..." We've been discussing a sharing system for GHAs, clusters, userobjects, example files etc. etc. for a while within McNeel. It looks like the Food4Rhino web-server could host all this stuff, we just need to write a proper UI for this. This is definitely low-priority compared to getting clusters up to snuff. "Clusters could also record if a Grasshopper plugin is being used in it. When you insert a cluster and the plugin is missing it dispays a warning and a link to download it." I suppose. The same would go for just standard gh/ghx files that use components from special libraries. I think I'll add that mechanism first as it affects more people. Then it should be fairly easy to also enable it for clusters. "This is it... not much right?" Pff, piece of cake. I'm just surprised you didn't ask for password protection of clusters :) -- David Rutten david@mcneel.com Poprad, Slovakia…; Added by David Rutten at 4:30am on November 28, 2011

Comment on: Topic 'Creating a 3D field': ch are cross-sections through "equipotential surfaces") for a magnetic dipole. In the image called 5.jpg you are showing the "stream lines" in three-dimensions of this dipole. These are not the same thing although they are intertwined concept (you should get one with the other and vice-versa). Have a look at this great explanation. According to your image called 5.jpg, you are trying to get the 3D "stream lines" of the magnetic dipole. I have tried the same exercise on my side. Using the field tools in the latest grasshopper (under the vector tab) I created a 2D field based on two points with one having a negative charge and the other a positive charge (like on a magnetic dipole). The result and definition are below (notice that the start points are located around a small circle located around on of the points): I might be wrong but I think the surfaces on the image called 5.jpeg are a "surface revolution" of these lines using either the line connecting the two points or one that is perpendicular to the line. See below first results: Now so far the points I have used to plot the stream lines were on the XY 2D plane. Once you start using three dimensional start points, like points on a sphere. you get the most amazing three-dimensional results: Which I guess you can loft and create cool 3d surfaces from too (be careful with the amount of lines though before you loft, it gets heavy quickly): I hope this helps (see definition attached)! …; Added by Arthur Mamou-Mani at 6:17pm on October 20, 2012

Comment on: Topic 'Thoughts on bouancy driven natural ventilation': . I wish there is a website where people vote for the most helpful and informative forum on the web. I am not sure how I can get a hold of fluent or phonics but thank you for explaining a good practice for using CFD i.e. to confirm the coefficients for a formula. Its beginning to take a shape on my head how to approach the topic. I am under the impression what you are referring to as a steady state is distinct from a transient analysis, which looks at the beginning and end of a system behavior. So I understand as a steady state analysis as an analysis about a kind of a "running" mode, at least in this context. so it makes sense that there would need to be a guess about an initial air flow. I just tried your definition and I can see the Nat Vat component and it is running without problem. However I got an error message "1. no eio file was found adjacaent to the .csv _resultFileAddress.results cannot be read back into grasshopper without this file." from the honeybee read EP result component. so I double clicked the unnamed.idf file, and EP-launch popped up. and I clicked simulate button, and now in the folder there is an eio file. now I run the Honeybee_run_simulation component again and this time the read EP component works without error, and as a result I do get an operative temperature for zone graph, though mine looks different, and based in san fransisco Intl AP. Anyways, I do get a result, I just did not know that running EP-launch from the unnamed.idf file was a part of the workflow so if anyone is trying this chimneyExample File and getting an error about a missing eio file, just double click on the idf file created by the Run_Energy_Simulation component. About what you said Chris, " Once you get CFD air flow values for a given temperature difference between your zone and outside air, you can use the orifice equation and solve for your discharge coefficient (Cd). You can then plug this discharge coefficient into your HB energy model and get a sense of airflow through the chimney for the whole year" I have to try this workflow since I am preparing a CFD analysis. My only question right now is, Chris, which one of "operative temperature" and " meanRadTemperature" output from Read EP result component equivalent to temperature values for surfaces or heat flux values for surfaces ? Thank you again! hope to share a result of coupling a CFD and Honeybee-ladybug soon, hopefully by the end of this month. might be next month because I have a different presentation at the end of this month.…; Added by yj to Ladybug Tools at 11:28am on January 19, 2015

Blog Post: ECOLOGIC PATTERNS | CORSO AVANZATO GRASSHOPPER | ROMA 09 > 13 MAGGIO: ________________________________________________________________________

ECOLOGIC PATTERNS | GRASSHOPPER + PLUG…; Added by Arturo Tedeschi at 6:59pm on April 17, 2012

Comment on: Topic 'Best Uniform Remesher For Patterning Organic Suraces': variable. It's a short enough script for normal users, along with Stackoverflow and Google English language searches to debug in the future. Just try isolating the problem in a copy of the script, paring it down to a few lines that still fail the same way, then ask around, since then you'll likely only have a basic Python issue to figure out. import Rhinoimport subprocess# TO MAKE THIS WORK, RIGHT CLICK RHINO.EXE AND OPENFLIPPER.EXE TO ACCESS THE PROPERTIES>COMPATIBILITY TAB AND CHECK "RUN THIS PROGRAM AS ADMINISTRATOR."# ALSO MAKE SURE TO EDIT THE OPENFLIPPER CORRECT VERSION NUMBER AND INSTALLATION PATH THAT I HAVE HARD-WIRED TO VERSION 3.1, BELOW.# Write an ASCII format STL file for the input mesh, for OpenFlipper to operate on:stl_file = open("C:/NIKS_OPENFLIPPER_PARSER_TEMP.stl","w")stl_file.write("solid OBJECT\n")Input_Mesh = Mesh # Let's not use the Rhino term Mesh in the script itself.Input_Mesh.Normals.ComputeNormals() # NITM ("Not In The Manual") but this is needed first.verts = Input_Mesh.Vertices # Get all vertices of the mesh from Rhino.for i,face in enumerate (Input_Mesh.Faces): # Rhino gives faces by vertex index number.stl_file.write(" facet normal %s\n" % str(Input_Mesh.FaceNormals[i]).replace(",", " ")) # Rhino gives normals!stl_file.write(" outer loop\n")stl_file.write(" vertex %s\n" % str(verts[face.A]).replace(",", " ")) # Rhino has ABCD properties for face vertex index numbers.stl_file.write(" vertex %s\n" % str(verts[face.B]).replace(",", " "))stl_file.write(" vertex %s\n" % str(verts[face.C]).replace(",", " "))stl_file.write(" endloop\n")stl_file.write(" endfacet\n")stl_file.write("endsolid OBJECT\n")stl_file.close()# Generate an OpenFlipper script on the fly in order to alter settings not accepted on its command line:openflipper_script = open("C:/NIKS_OPENFLIPPER_PARSER_TEMP.ofs", "w")openflipper_script.write("core.loadObject(\"C:\\\\NIKS_OPENFLIPPER_PARSER_TEMP.stl\")\n")openflipper_script.write("id = core.getObjectId(\"NIKS_OPENFLIPPER_PARSER_TEMP.stl\")\n")openflipper_script.write("remesher.uniformRemeshing(id,%s,%s,%s,true)\n" % (TargetEdgeLength, Iterations, AreaInterations))openflipper_script.write("core.saveObject(core.getObjectId(\"NIKS_OPENFLIPPER_PARSER_TEMP.stl\"),\"C:\\\\Out.stl\")\n")openflipper_script.write("core.exitApplication()\n")openflipper_script.close()# Windows command line execution of OpenFlipper with argument to run our script:OFS = "C:/NIKS_OPENFLIPPER_PARSER_TEMP.ofs"subprocess.call(['C:\Program Files\OpenFlipper 3.1\OpenFlipper.exe',OFS]);# Read in the OpenFlipper output STL file back into Grasshopper:mesh = Rhino.Geometry.Mesh() # Initialize "mesh" variable as a blank mesh object to hold each face.MESH = Rhino.Geometry.Mesh() # Initialize "MESH" variable as a blank mesh object to accumulate faces.with open("C:/Out.stl") as f: for line in f: if "vertex" in line: q = line.replace("vertex ", "") q = q.replace("\n", "") q = [float(x) for x in q.split()] mesh.Vertices.Add(q[0],q[1],q[2]) # Fill mesh with three vertex lines in a row. if "endloop" in line: # File itself tells us we are done with three vertices for one face. mesh.Faces.AddFace(0,1,2) # Create a single face mesh. MESH.Append(mesh) # Magically build a real multi-face mesh while removing redundant vertices. mesh = Rhino.Geometry.Mesh() # Reinitialize empty mesh object for each mesh face.MESH.Normals.ComputeNormals() # Gives nice mesh and preview but makes the script take longer.…; Added by Nik Willmore at 4:32pm on October 9, 2017

Event: International Workshop in Santa Catarina, Brasil: s meios acadêmicos e profissionais do Estado de Santa Catarina em parceira com a Escola de Design ELISAVA de Barcelona. Metodologia: Mediante um exercício prático os participantes poderão ter em primeira mão uma aproximação às técnicas mais avançadas de design e fabricação digital. Web: http://santacatarina.elisava.net/ e-mail: secretaria@sc.asbea.org.br As atividades estão divididas em 3 etapas. 1ª etapa: Roadshow (Ciclo de Conferencias) Palestrantes: Affonso Orciuoli, arquiteto, professor da Escola de Design ELISAVA de Barcelona, Univesitat Ramon Llullp.d. As conferencias do Prof. Orciuoli serão através de videoconferência desde Espanha Regiane Pupo, arquiteta, professora da UFSC, Florianópolis As conferencias da Prof. Pupo são presenciais. Datas: Lages 01/11Chapecó 03/11Caçador 04/11Criciúma 07/11Baln. Camboriú 08/11Blumenau 09/11Joinville 10/11Florianópolis 11/11 Horário: 18:00 horas Conferencia: Arquiteturas disruptivas. Design e fabricação na era digital. Palestrante: Prof. Arq. Affonso Orciuoli | Professor ELISAVA | Barcelona 2ª etapa: Curso on-line de Rhinoceros Durante o Roadshow será apresentado o curso on-line de Rhinoceros (http://www.rhino3d.com/). Entre 01 e 22 de novembro serão subministrados tutoriais a todos os estudantes e professores participantes, a título de se prepararem para o workshop, ver sessão ”downloads” 3ª etapa: Workshop E-luminárias Entre 23 e 27 de novembro de 2011, das 8:00 às 18:00 h (10 horas por dia) Workshop Internacional (50 horas) Diretor: Affonso Orciuoli Professores: Regiane Pupo | Ernesto BuenoLocal: InovaLab | Sapiens Parque | Florianópolis | Santa CatarinaInvestimento: R$ 150 (estudantes) e R$ 300 (professores & profissionais)Vagas: 50Obs.: Materiais para a fabricação incluídos. Objetivo: reunidos em grupos de 3 participantes, se desenvolverá um projeto completo de uma luminária, utilizando plataforma CAD. Posteriormente os participantes, com a ajuda dos instrutores, deverão preparar os arquivos para a fabricação na máquina fresadora e laser. Por último as luminárias serão montadas e expostas em conjunto. Cada participante deverá trazer um laptop com os programas instalados (“demos” do Rhinoceros, RhinoNEST, outros programas de CAD também poderão ser utilizados). Todos estes programas estarão disponíveis para serem baixados a partir do site da Escola de Design ELISAVA de Barcelona. Equipamentos presentes no workshop e à disposição dos participantes: Máquina CNC tipo fresadora de 3 eixos Máquina de corte a laser Máquina de impressão 3D (a título de demonstração)…; Added by Affonso Orciuoli at 2:46am on October 18, 2011

Event: DIGITALMED WORKSHOP IV EDITION SMART: INTERACTION BETWEEN PEOPLE /CITIES/ENVIRONMENT: bject of this edition focuses on the investigation of interactions between the environment and the human being, made through objects, mechanisms and architectures able to interact with who makes use of them. The aim of digitalMed IV is drawing a catalogue of projects/prototypes to insert them in an urban context, and to outline new future-cities profile. PURPOSES AND TERMS: The digitalMed Summer School IV edition aims to organize the flows of information, in which the city is absorbed, to adapt projects and to make them useful, no invasives, and suitable to establish an information exchange. The concepts of slow cities and smart cities are directed by all types procedures, from immaterial to materia, from information to the built. This is the iter that we will follow to reinvent the relationship between man, environment and cities. Through learning by-doing educational procedure, participants will acquire not only new metodologies and means, but also concrete cases where testing these ones. In this way, new acquired information won’t remain simple educational exercises, but will be notable elements in the portfolio participants. TOPICS: The planning approach of digitalMed Summer School IV edition will supply to participants all the technic knowledges and theoretical bases in order to work. The first days of workshop will focus on the outline of a shared vocabulary that allows to work from shared meanings. This phase is characterized by subjects occurring in the contemporary architecture such as computational design, digital fabrication and data driven, then systems, like Arduino, which allow the interaction with objects, and fields like permaculture and social innovation that nowadays contribute to the realignment of environment and city’ ideas. The participants will have the opportunity to learn the use of software for the parametric planning, like Grasshopper, and to test interactions between real information and virtual data (and viceversa) through the use of Arduino. PREREQUISITES: The workshop is open both to the students and to the professionals. It needs a basic knowledge of Rhinoceros 3D program. All the participants have to bring their own laptop. The programs for installing will be communicated during the registration act. HOW TO REGISTER: To register to the Summer School DigitalMed 2013 you must send an e-mail to info@medaarch.com, with the object: “Iscrizione DIGITALMED2013”. The mail has to contain: Name; surname; profession; telephone; e-mail. After the reception of the above-mentioned e-mail, the participants will be contacted by phone, as well as by e-mail, to be informed about payment methods Registrations are to be construed when the payment will be effective. DEADLINE: Registrations to the workshop close on July 19 h18:00. INFO: Organizational Segretary digitalMed IV Dott.ssa Francesca Luciano Web site: www.medaarch.com e-mail: info@medaarch.com tel : +39 392 5149075 fb: mediterranean Fab Lab tw: @medfablab …; Added by Francesca Luciano at 7:00am on July 11, 2013

Comment on: Topic 'Mcr influenced by BklLenZ': buckling length considered about the major axis strut buckling bklLen_Z = buckling length considered about the minor axis strut buckling bklLen_LT = buckling length considered in lateral torsional buckling What looks to be the case is: bklLen_y = buckling length considered about the major axis bklLen_z = buckling length considered about the minor axis and lateral torsional buckling bklyLen_LT = buckling length considered for warping in lateral torsional buckling I don't think there is anything intrinsically wrong with the use of bklLen_Z in this way, or the definition of the value used in bklLen_LT, but the name of bklLen_LT suggested something different to me. Background below: M_cr is calculated by a closed form analytical solution to the lateral torsional buckling problem, i.e. it is not a code dependent expression so easy to compare between the code and other documents: The first term in the square root term in the C++ is: SQR(lk_z/lk_LT)*Cw/Iz Which is the square of the ratio of minor axis buckling and lateral torsion buckling effective lengths inputs, multiplied by the ratio of the warping and minor axis bending constants of the section. In SN003b-EN-EU (https://www.steelconstruction.info/File:SN003b.pdf) expression (1) the corresponding term is SQR(k/k_w)*Cw/Iz (In fact SN003b calls Cw 'Iw' but I have substituted above to aid the comparison). Where: k = effective length factor to end rotation on plan. Which is analogous to the minor axis effective length in strut buckling. k_w = effective length to end warping. Usually taken as 1. So Karamba takes the input value of Bkl_LenLT to be the effective length specifically for warping of the section, as: SQR(lk_z/lk_LT) = SQR([k*L]/[k_w*L]) = SQR(k/k_w) (I originally thought it was the effective length for end rotation on plan.) Apart from naming/understanding of how the inputs are used, I could only see a problem with this approach if there were a situation where the minor axis strut buckling effective length was not equal to the effective length for lateral torsional buckling. I could think of the following situations: The lateral restraint force is related to compression in the section. A (rare?) situation could be where the lateral restraint system has sufficient strength to provide lateral restraint against lateral torsional buckling, but not the higher restraint force of strut buckling about the minor axis. This feels like quite a contrived situation and I can't think of a practical example. Where lateral strut buckling restraint is provided to the beam by connection to the web, which is less effective at restraining the top flange against lateral torsional buckling. In this situation you may want/need to define separate a minor axis strut buckling and lateral torsional buckling effective lengths. Where the lateral torsional buckling effective length is the lk_z value in the calculation. This isn't currently possible. Neither of the two situations apply to what I am currently looking at, so now I understand how bklLen_LT is used I can work around that!…; Added by Nick Simpson to Karamba3D at 3:47am on September 19, 2019

Blog Post: Form Finding Strategies_Milano 27>29 Maggio 2014