algorithmic modeling for Rhino

Search Results - 【p26.pw】穀歌48小時快速收錄.260123142440

Comment on: Group 'FabCafe Tokyo': 思った感じになりません。 balls の代わりにplanarカーブを直接入れてみましたがエラーが出ます。ファンクションにしてみたところ、forループので作った数値が反映されていません。ファンクションのインスタンス？を出力していないと思い上記のようにしましたがエラーが出てしまいます。以上の事から自分の認識が正しいのかよくわからなくなりました・・・ python自体の深いところをわかっているわけではないので余計こんがらがりました。そこで、for b in ballsはどのような条件または使い方であれば使えるのでしょうか？そして、上記のように別のオブジェクトに対しての使い方はどのようにすればできるのでしょうか？２：同じファンクション内のdist = rs.Distance(self.pos,b.pos)についてですがこの文章も　for b in balls によってｂはBallのインスタンスであると定義？されたためb.posがｂの位置であると分かるのでしょうか？ pythonは定義しなくても動いてしまうのでどのような時に使えるのか文章見ただけではよくわかりません・・・大変細かいことかもしれませんが、よりpythonをしっかりと理解するためにも、どなたかわかる方ご教授いただけると幸いです。…; Added by Inu to FabCafe Tokyo at 9:48am on March 1, 2015

Here are 50 of the most widely recognized tips and traps that have turned out to be a piece of the regular work process for some 3ds Max® clients.

1. Utilize the Rename…

Added by Leana Mirrow at 5:36am on March 18, 2016

Comment on: Topic 'Rule-based design, can grasshopper do it?': I live on my computer and I even sleep with it, so learning all this is probably within my reach but I'm a complete beginner as of now. I'm downloading the 32 bit version of rhino 5 since the 64 bit doesn't seem to work with your downloads Jon. I haven't grasped everything you have made yet Jon I can't even begin to understand what your IFC stuff is actually capable of, but just to be clear I'm not interested in solely being able to tell that something is colliding as there are already software that can do that beautifully. What I want to do is bypass that step altogether by never having collision-checking back and forth go on, even collisions which aren't physical collisions, but rather just violations by code. The simplest way to do this would be to simply make the geometry of the beams 2 feet wider than they are in real life, so that way you could put a light right next to the 'over-sized' beam and it would still be within the rules. But that would be extremely primitive and I'm sure there's a way to do it mathematically. Just to clarify, I'm the fire sprinkler designer in the architectural circus. The sprinkler designer (me) doesn't really get the luxury of telling the other trades that they're colliding with my stuff and they should move. Rather, I get their drawings, find out I'm colliding with them, and move around them. So it would be of great use to me to have this be automatic - that is, to automatically space my sprinklers the neccesary distance away from all obstructions. There are different spacing rules for different obstructions - walls, beams, open web steel, unit heaters, hvac ducts depending on how wide the ducts are, lights, fans, high rack storage, basically anything that would obstruct the water spray from a sprinkler needs to be taken into account and spaced away from. It's therefore a very attractive idea to be able to just draw a rectangle (representing the walls of a simple room) for instance, have the sprinklers automatically spaced as far apart as possible within the rectangle according to the rulebooks (to minimize the amount of sprinklers needed which minimizes the material cost of the job). Then add obstructions inside the rectangle, such as a beam, and have the sprinklers relocate themselves or add new sprinklers to accommodate for the new obstruction.. Keep adding obstructions until you have the realistic 3d model of the room, with the sprinklers spaced accordingly, and you have an up-to-code sprinkler system. There is one example where sprinklers actually need to be spaced really close to, rather than away from, an object.. and that is the ceiling (sprinklers must be within 12 in of ceiling typically). If the HVAC guy decides to reroute his ducts right through my sprinklers, then I could draw 3D HVAC ducts (I usually get 2D drawings coming in) going right through the room and the sprinklers would relocate and auto-space away from the ducts, without actually having to tell the HVAC guy he is colliding with me because all that will do is require me to do a redesign anyway. And presto, the HVAC guy loves me because I didn't complain to him at all and seemingly did all this work by moving around him when all I really did was use the computer to do it, the job gets done much faster and I don't have to worry that I'm going to lose my job in court because I made a silly human error when I was patching my system manually because some HVAC guy made me redesign 12 times in different places. From what I have been reading from you guys, doing this is possible although (I realize) ambitious. The end result would be vastly increased productivity, less error making, cheaper design cost, etc. Using programs like Rhino, architects are getting more and more funny-shaped buildings and making it difficult for guys like me to make sprinkler systems within the rules, and I see it as an inevitability that computers will be making almost all of the typical design decisions in the future when it comes to life safety systems, I'm just trying to see if it's possible to start implementing this extra aid today. …; Added by Luke W at 4:26am on May 19, 2012

Event: DIGITAL TOOLING vol.1: を進める。後半で行われるコンピュテーショナル・デザインの技術を使った料理の展開を紹介し、試食も行います。 ■第2部18:00～21:00（ワンドリンク制￥500） RGSS KANSAI(仮) 昨今、デザインの最先端で見られるようになったコンピューテーショナルデザイン。すでにスタジアムや大型建築、プロダクトデザインなどの分野で認知されてます。デザイナやデザイナを目指す人達には今後必須の技術と言えるのではないでしょうか。 RhinocerosとGrasshopperをつかえば、今までプログラムの知識が必要だったアルゴリズミックな3Dデザインもスクリプティングを要さず生み出すことができます。首都圏では数年前からRGSS（コンピューテーショナルデザインのコミュニティ）が存在し日本におけるコンピューテーショナルデザインの裾野を拡げています。コンピューテーショナルデザインに関する技術や知識の交流が発生し、関西におけるデザイン技術の底上げを期待しています。当日は2~3名のプレゼンテーションを予定。まずはキックオフ的にはじめてみて、続けていくことで形作っていければと思います。　大前道久　OPH（おっさんパワーハウス）主催　15年間ジュエリーメーカーで勤務し、　制作からデザインまで様々な部署を経験してきました。　Grasshopperの恩恵を受け、新しい表現や効率的な　モデリングを実践しています。　私なりの、コンピューテーショナルなジュエリー制作を　見ていただきたいと思います。 FBイベントページ：https://www.facebook.com/events/709226442478364/…; Added by Michihisa Omae at 9:09pm on August 23, 2014

Event: ESCULTURA DIGITAL (RHINO + GH + FabLab): s o alguna de sus partes con la máquina de control numérico de ControlMAD. La finalidad es entrar en contacto con las herramientas disponibles ( control numérico, corte por láser, brazo robótico, scanner 3D..) para construir formas y superficies de geometría compleja a partir del 3D del ordenador. El curso se acompaña de visitas para conocer de primera mano el trabajo con estas herramientas digitales.Duración: 48 horas:Clases de 3D: Modelado con RHINO (16 horas) + GRASSHOPPER (8 horas) + Vray (4 horas)Proyecto personal tutorado y fabricado en su totalidad o en la parte más significativa con la máquina de control numéricoVisitas programadas:Taller de maquetas. Maquetas de arquitectura para estudios como Zaha Hadid o Moneo. Trabajan con láser y control numérico.Fundición Capa: han realizado esculturas para Dalí, Oteiza o Manolo Valdés entre otros. Trabajan con scanner 3D y brazo robótico.Pasarela sobre el Manzanares, de D. Perrault.…; Added by Diego Cuevas at 9:24am on June 23, 2011

Event: McNeel Asia - Rhino原厂培训中心暑期课程开始接受报名: 设计业制定的曲面造型技术精粹课程，涵盖基础内容到高级经验技巧。与常见的以介绍软件功能为主的培训课程不同，不仅培养学员全面的曲面造型的技能、介绍曲面造型的经验和技巧以及如何综合的运用到建筑造型中，且提供一整套基于Rhino平台的造型、表皮、钢构、施工图与模型信息化的解决方案与技能，这种“技能”的学习才是是本课程的价值所在！点击了解课程详细介绍... Grasshopper 参数化课程基于Rhino平台的参数化解决方案课程，授课注重培养学员灵活使用编程技术以解决实际问题的能力。课程深入到编程的整个过程，从编程思维方式、工具运行原理到用法细节做详尽的解释。辅助学员掌握整个过程中遇到的思路和技术等方面的问题，主要包括反向逻辑思维能力的培养、建立清晰的编程逻辑思维能力、GH 的程序设计理念与并行数据结构深入理解和控制。点击了解课程详细介绍... V-Ray for Rhino 建筑渲染表现课程全面讲解V-Ray渲染引擎高级渲染表现方法，全面剖析渲染技巧以及更进阶的运用、并且得到更加拟真的渲染影像，轻松完成设计所需的照片级的提案图片。无需繁琐的转档即可在Rhino中享受 Vray 的高效、快捷与超真实表现方法。点击了解课程详细内容... 课程报名课程即日开始报名，开课一周前停止报名，名额满提前报名结束。现在就在线提交报名表、报名参加课程... 提示：近期大陆地区有部分培训机构冒充Rhino授权原厂培训机构或原厂授权培训讲师，目前在大陆地区仅有 McNeel Asia 原厂培训中心，并没有授权其他培训中心展开原厂的相关课程，敬请留意。可以在我们网站查询相关资料。查询大陆地区原厂授权培训中心名单... 授课时间安排联系人 McNeel 深圳办事处: Jessesn (0755-29642189) McNeel 上海办事处: Dixon (021-56496412)…; Added by Jessesn at 1:09am on May 20, 2013

Event: 2019新课程 | Grasshopper参数化产品设计高级课程: 程连续6天课程，这是本课程的主体部分。该阶段课程对参数化设计方法进行系统性和细致性的介绍和学习。第一阶段的课程内容并不侧重于某个具体的设计行业，是一个设计业通用的专注于介绍参数化设计方法课程。其中包括：参数化设计的运行规则、逻辑思路的分析、相关方法和概念的补充，工具的使用技巧和工作流程等等。本阶段课程的详细介绍请参考参数化设计系统课程。第二阶段：参数化产品设计深入课程本阶段课程以工业设计行业实际应用的案例为主。侧重介绍参数化设计在产品设计行业中普遍和典型的应用方法和流程。并强调在产品设计行业中遇到的一些普遍的技术难点和解决办法。这个阶段的课程以实际范例的制作过程为主，反映产品设计行业中普遍会遇到的技术难点是什么，以及该用什么方法或流程去解决，是对第一阶段学习到的方法和理解的深入运用。请注意：本阶段课程并没有新的参数化设计知识点，事实上所有本阶段运用到的参数化方法和理解都是在第一阶段课程中学习到的。因此学员必须首先完成第一阶段的参数化设计系统课程。现在就报名参加课程... 了解课程更多详细介绍... …; Added by Jessesn at 8:39am on June 8, 2019

Topic: [solved] [urgent] error probably related to wrongly written IDF file on the class of SizingPeriod: value=WINTERDESIGNDAY, in SIZINGPERIOD:DESIGNDAY=SINGAPORE ANN HTG 99.6% CONDNS DB ************* IDF Context for following error/warning message: ************* Note -- lines truncated at 300 characters, if necessary... ************* 53 SizingPeriod:DesignDay, ************* indicated Name=SINGAPORE Ann Htg 99% Condns DB ************* Only last 10 lines before error line shown..... ************* 57 23.5, !- Humidity Indicating Conditions at Maximum Dry-Bulb ************* 58 101133., !- Barometric Pressure {Pa} ************* 59 2, !- Wind Speed {m/s} design conditions vs. traditional 6.71 m/s (15 mph) ************* 60 320, !- Wind Direction {Degrees; N=0, S=180} ************* 61 0.00, !- Clearness {0.0 to 1.1} ************* 62 0, !- Rain {0-no,1-yes} ************* 63 0, !- Snow on ground {0-no,1-yes} ************* 64 21, !- Day of Month ************* 65 12, !- Month ************* 66 WinterDesignDay,!- Day Type The relevant lines in the IDF file is shown below: SizingPeriod:DesignDay, SINGAPORE Ann Htg 99.6% Condns DB, !- Name 23, !- Maximum Dry-Bulb Temperature {C} 0.0, !- Daily Temp Range {C} 23, !- Humidity Indicating Conditions at Maximum Dry-Bulb 101133., !- Barometric Pressure {Pa} 2, !- Wind Speed {m/s} design conditions vs. traditional 6.71 m/s (15 mph) 320, !- Wind Direction {Degrees; N=0, S=180} 0.00, !- Clearness {0.0 to 1.1} 0, !- Rain {0-no,1-yes} 0, !- Snow on ground {0-no,1-yes} 21, !- Day of Month 12, !- Month WinterDesignDay,!- Day Type 0, !- Daylight Savings Time Indicator WetBulb; !- Humidity Indicating Type ! SINGAPORE_SGP Annual Heating 99%, MaxDB=23.5°C SizingPeriod:DesignDay, SINGAPORE Ann Htg 99% Condns DB, !- Name 23.5, !- Maximum Dry-Bulb Temperature {C} 0.0, !- Daily Temp Range {C} 23.5, !- Humidity Indicating Conditions at Maximum Dry-Bulb 101133., !- Barometric Pressure {Pa} 2, !- Wind Speed {m/s} design conditions vs. traditional 6.71 m/s (15 mph) 320, !- Wind Direction {Degrees; N=0, S=180} 0.00, !- Clearness {0.0 to 1.1} 0, !- Rain {0-no,1-yes} 0, !- Snow on ground {0-no,1-yes} 21, !- Day of Month 12, !- Month WinterDesignDay,!- Day Type 0, !- Daylight Savings Time Indicator WetBulb; !- Humidity Indicating Type It seems that there is an empty line after the line for "!- Humidity Indicating Type" field, and nothing is specified for "! SINGAPORE_SGP Annual Heating 99%, MaxDB=23.5°C" field. May I ask why this happens and how to correct the error? Thank you very much!…; Added by Grasshope to Ladybug Tools at 2:20am on July 22, 2016

Topic: zone and max humidity errors: be done easier, but later on the geometry will change and therefore this seems the better option. But coming back to the problem First, there were some problems concerning the zone, although it seems solved still the “runenergysimulation” gives the following warning: 1. The simulation has not run correctly because of this severe error: ** Severe ** UpdateZoneSizing: Cooling supply air temperature (calculated) within 2C of zone temperature Do one of you know what went wrong? It probably will solve most of it. Second, “set Zone Thresholds” gives the following warning: 1. Solution exception:global name 'maxHumidity_' is not defined However, the component is missing the max humidity input on the list, has this to do something with the error? All the components are up to date. I hope it will be an easy fix. Gr Lars “set Zone Thresholds” runtime error {0;0;0}0. Runtime error (UnboundNameException): global name 'maxHumidity_' is not defined1. Traceback: line 80, in checkTheInputs, "<string>" line 282, in script "runenergysimulation” report {0;0}0. Current document units is in Meters1. Conversion to Meters will be applied = 1.0002. TypeError('Waarde kan niet null zijn.\r\nParameternaam: source',)3. Failed to copy the object. Returning the original objects...This can cause strange behaviour!4. [1 of 8] Writing simulation parameters...5. [2 of 8] No context surfaces...6. [3 of 8] Writing geometry...7. [4 of 8] Writing Electric Load Center - Generator specifications ...8. [5 of 8] Writing materials and constructions...9. [6 of 8] Writing schedules...10. [7 of 8] Writing loads and ideal air system...11. [8 of 8] Writing outputs...12. ...... idf file is successfully written to : c:\ladybug\unnamed\EnergyPlus\unnamed.idf13. 14. Analysis is running!...15. c:\ladybug\unnamed\EnergyPlus\eplusout.csv16. ...... Done! Read below for errors and warnings: 17. 18. Program Version,EnergyPlus, Version 8.3.0-6d97d074ea, YMD=2016.03.02 20:55,IDD_Version 8.3.019. 20. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.21. 22. ************* Beginning Zone Sizing Calculations23. 24. ** Warning ** GetInternalHeatGains: People="CLASSROOMOFFICEPEOPLE", Activity Level Schedule Name values25. 26. ** ~~~ ** fall outside typical range [70,1000] W/person for Thermal Comfort Reporting.27. 28. ** ~~~ ** Odd comfort values may result; Schedule="SCHOCCUPANCYSCHEDULE".29. 30. ** ~~~ ** Entered min/max range=[0.0,1.0] W/person.31. 32. ** Warning ** Calculated design heating load for zone=CLASSROOM is zero.33. 34. ** ~~~ ** Check Sizing:Zone and ZoneControl:Thermostat inputs.35. 36. ** Severe ** UpdateZoneSizing: Cooling supply air temperature (calculated) within 2C of zone temperature37. 38. ** ~~~ ** ...check zone thermostat set point and design supply air temperatures39. 40. ** ~~~ ** ...zone name = CLASSROOM41. 42. ** ~~~ ** ...design sensible cooling load = 25499.10 W43. 44. ** ~~~ ** ...thermostat set point temp = 0.000 C45. 46. ** ~~~ ** ...zone temperature = 15.334 C47. 48. ** ~~~ ** ...supply air temperature = 15.000 C49. 50. ** ~~~ ** ...temperature difference = -0.33433 C51. 52. ** ~~~ ** ...calculated volume flow rate = 197273.21341 m3/s53. 54. ** ~~~ ** ...calculated mass flow rate = 237634.19357 kg/s55. 56. ** Warning ** ManageSizing: For a plant sizing run, there must be at least 1 Sizing:Plant object input. SimulationControl Plant Sizing option ignored.57. 58. ************* Testing Individual Branch Integrity59. 60. ************* All Branches passed integrity testing61. 62. ************* Testing Individual Supply Air Path Integrity63. 64. ************* All Supply Air Paths passed integrity testing65. 66. ************* Testing Individual Return Air Path Integrity67. 68. ************* All Return Air Paths passed integrity testing69. 70. ************* No node connection errors were found.71. 72. ************* Beginning Simulation73. 74. ************* Simulation Error Summary *************75. 76. ** Warning ** The following Report Variables were requested but not generated77. 78. ** ~~~ ** because IDF did not contain these elements or misspelled variable name -- check .rdd file79. 80. ************* Key=*, VarName=ZONE PACKAGED TERMINAL HEAT PUMP TOTAL COOLING ENERGY, Frequency=Hourly81. 82. ************* Key=*, VarName=ZONE PACKAGED TERMINAL HEAT PUMP TOTAL HEATING ENERGY, Frequency=Hourly83. 84. ************* Key=*, VarName=CHILLER ELECTRIC ENERGY, Frequency=Hourly85. 86. ************* Key=*, VarName=BOILER HEATING ENERGY, Frequency=Hourly87. 88. ************* Key=*, VarName=FAN ELECTRIC ENERGY, Frequency=Hourly89. 90. ************* Key=*, VarName=ZONE VENTILATION FAN ELECTRIC ENERGY, Frequency=Hourly91. 92. ************* Key=*, VarName=EARTH TUBE FAN ELECTRIC ENERGY, Frequency=Hourly93. 94. ************* Key=*, VarName=PUMP ELECTRIC ENERGY, Frequency=Hourly95. 96. ************* Key=*, VarName=ZONE VENTILATION TOTAL HEAT LOSS ENERGY, Frequency=Hourly97. 98. ************* Key=*, VarName=ZONE VENTILATION TOTAL HEAT GAIN ENERGY, Frequency=Hourly99. 100. ************* Key=*, VarName=EARTH TUBE ZONE SENSIBLE COOLING ENERGY, Frequency=Hourly101. 102. ************* Key=*, VarName=EARTH TUBE ZONE SENSIBLE HEATING ENERGY, Frequency=Hourly103. 104. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.105. 106. ************* EnergyPlus Sizing Error Summary. During Sizing: 3 Warning; 1 Severe Errors.107. 108. ************* EnergyPlus Completed Successfully-- 5 Warning; 1 Severe Errors; Elapsed Time=00hr 00min 4.65sec109.…; Added by Kraakie to Ladybug Tools at 1:01pm on March 2, 2016

Topic: DataTree selection rules: will work slightly different from before. Sorry about breaking this, but it proved impossible to improve the selection logic with the fairly ambiguous notation that was implemented already. Not every change is breaking though and I hope that most simple matching rules will work as before. There will be a McNeel webinar on Wednesday the 6th of November where I discuss the new selection rules (as well as path mapping syntax and relative offsets within one or more data trees). This will be a pretty hard-core webinar aimed at expert users. The event will be recorded so you can always go and watch it later. I figured I'd briefly explain the new selection rules on Ning before I release the update though. ------------------------------------------------------------------------------- Imagine we have the following data tree, containing a bunch of textual characters: {0;0} = [a,e,i,o,u,y] {0;1} = [ä,ë,ê,ï,î,ö,ô,õ,ü,û,ÿ,ý] {1;0} = [b,c,d,f,g,h,j,k,l,m,n,p,q,r,s,t,v,w,x,z] {1;1} = [ç,ĉ,č,ĝ,ř,š,ş,ž] There are a total of four branches {0;0}, {0;1}, {1;0} and {1;1}. The first branch contains all the vowels that are part of the standard English alphabet. The second branch contains all non-standard vowels and branches three and four contain the standard and non-standard consonants respectively. So what if we want to select from this tree only the standard vowels? Basically include everything in the first branch and disregard everything else. We can use the [Tree Split] component with a selection rule to achieve this: {0;0} This selection rule hard-codes the number zero in both tree path locations. It doesn't define an item index rule, so all items in {0;0} will be selected. If we want all the vowels (both standard and non-standard), then we have several options: {0;?} = select all branches that start with 0 {0;(0,1)} = select all branches that start with 0 and end in either 0 or 1 {0;(0 to 1)} = ......................................... and end in the range 0 to 1. Conversely, selecting all standard vowels and consonants while disregarding all non-standard character can be achieved with rules as follows: {?;0} {(0,1);0} {(0 to 1);0} It is also possible to select items from each branch in addition to limiting the selection to specific branches. In this case another rule stated in square brackets needs to be appended: {0;?}[0 to 2] The above rule will select the first three vowels from the standard and the non-standard lists. Basically, rules work in a very consistent way, but there are some syntax conventions you need to know. The first thing to realize is that every individual piece of data in a data-tree can be uniquely and unambiguously identified by a collection of integers. One integer describes its index within the branch and the others are used to identify the branch within the tree. As a result a rule for selection items always looks the same: {A;B;C;...;Z}[i] where A, B, C, Z and i represent rules. It's very similar to the Path Mapper syntax except it uses square brackets instead of parenthesis for the index (the Path Mapper will follow suit soon, but that won't be a breaking change). You always have to define the path selector rule in between curly brackets. You can supply any number of rules as long as you separate them with semi-colons. The index rule is optional, but -when provided- it has to be encased in square brackets after the path selection rule(s). The following rule notations are allowed: * Any number of integers in a path ? Any single integer 6 Any specific integer !6 Anything except a specific integer (2,6,7) Any one of the specific integers in this group. !(2,6,7) Anything except one of the integers in this group. (2 to 20) Any integer in this range (including both 2 and 20). !(2 to 20) Any integer outside this range. (0,2,...) Any integer part of this infinite sequence. Sequences have to be at least two integers long, and every subsequent integer has to be bigger than the previous one (sorry, that may be a temporary limitation, don't know yet). (0,2,...,48) Any integer part of this finite sequence. You can optionally provide a single sequence limit after the three dots. !(3,5,...) Any integer not part of this infinite sequence. The sequence doesn't extend to the left, only towards the right. So this rule would select the numbers 0, 1, 2, 4, 6, 8, 10, 12 and all remaining even numbers. !(7,10,21,...,425) Any integer not part of this finite sequence. Furthermore, it is possible to combine two or more rules using the boolean and/or operators. If you want to select the first five items in every list of a datatree and also the items 7, 12 and 42, then the selection rule would look as follows: {*}[(0 to 4) or (6,11,41)] The asterisk allows you to include all branches, no matter what their paths looks like. It is at present not possible to use the parenthesis to define rule precedence, rules are always evaluated from left to right. It is at present also not possible to use negative integers to identify items from the end of a list. If you want to know more, join the Webinar on Wednesday! -- David Rutten david@mcneel.com Seattle, WA…; Added by David Rutten at 8:57pm on November 3, 2013