algorithmic modeling for Rhino

Search Results - 双色球72期中奖号码的真实规律『1TBH·COM』12月5号号双色球开奖号2023年3月20日16时23分40秒.H5c2a3.n95r9dznb

Topic: SmartGeometry 2011: Conference speakers and New Website: earch Founder ofPachube.com and CEO of Connected Environments LtdBillie Faircloth KieranTimberlake Research DirectorCraig Schwitter & Gijs Libourel Buro Happold + Adaptive Building Initiative Lisa Amini IBM's Smarter City Lab Dublin, LeaderMette Ramsgaard Thomsen Head of the Center for Information Technology and Architecture (CITA), Denmark Additional speakers for the Talkshop day, including panel sessions and workshop reviews, will be posted to the website soon. For more information, click here. We are also very pleased to announce the launch of our new website at www.smartgeometry.org. It is a soft launch, meaning we are still adding new features to the page. However, Workshop Clusters are setting up their online homes for use before and during our workshops, and we'll be premiering all sorts of new features and content over the build-up to sg2011. Come check it out to see how things are developing!…; Added by Shane Burger at 7:48am on March 9, 2011

Blog Post: RGSS vol.32 Information

RGSS (rhino & grasshopper study session)　Tokyo　vol.32 will take place on 09 March.

Around 7pm, @…

Added by Yusuke Oono at 7:15pm on February 27, 2012

Comment on: Topic '[QUESTION] How many components and parameters has GH currently?': ay how many valid permutations exist. But allow me to guesstimate a number for 20 components (no more, no less). Here are my starting assumptions: Let's say the average input and output parameter count of any component is 2. So we have 20 components, each with 2 inputs and 2 outputs. There are roughly 35 types of parameter, so the odds of connecting two parameters at random that have the same type are roughly 3%. However there are many conversions defined and often you want a parameter of type A to seed a parameter of type B. So let's say that 10% of random connections are in fact valid. (This assumption ignores the obvious fact that certain parameters (number, point, vector) are far more common than others, so the odds of connecting identical types are actually much higher than 3%) Now even when data can be shared between two parameters, that doesn't mean that hooking them up will result in a valid operation (let's ignore for the time being that the far majority of combinations that are valid are also bullshit). So let's say that even when we manage to pick two parameters that can communicate, the odds of us ending up with a valid component combo are still only 1 in 2. We will limit ourselves to only single connections between parameters. At no point will a single parameter seed more than one recipient and at no point will any parameter have more than one source. We do allow for parameters which do not share or receive data. So let's start by creating the total number of permutations that are possible simply by positioning all 20 components from left to right. This is important because we're not allowed to make wires go from right to left. The left most component can be any one of 20. So we have 20 possible permutations for the first one. Then for each of those we have 19 options to fill the second-left-most slot. 20×19×18×17×...×3×2×1 = 20! ~2.5×1018. We can now start drawing wires from the output of component #1 to the inputs of any of the other components. We can choose to share no outputs, output #1, output #2 or both with any of the downstream components (19 of them, with two inputs each). That's 2×(19×2) + (19×2)×(19×2-1) ~ 1500 possible connections we can make for the outputs of the first component. The second component is very similar, but it only has 18 possible targets and some of the inputs will already have been used. So now we have 2×(18×2-1) + (18×2-1)×(18×2-1) ~1300. If we very roughly (not to mention very incorrectly, but I'm too tired to do the math properly) extrapolate to the other 18 components where the number of possible connections decreases in a similar fashion thoughout, we end up with a total number of 1500×1300×1140×1007×891×789×697×...×83×51×24×1 which is roughly 6.5×1050. However note that only 10% of these wires connect compatible parameters and only 50% of those will connect compatible components. So the number of valid connections we can make is roughly 3×1049. All we have to do now is multiply the total number of valid connection per permutation with the total number of possible permutations; 20! × 3×1049 which comes to 7×1067 or 72 unvigintillion as Wolfram|Alpha tells me. Impressive as these numbers sound, remember that by far the most of these permutations result in utter nonsense. Nonsense that produces a result, but not a meaningful one. EDIT: This computation is way off, see this response for an improved estimate. -- David Rutten david@mcneel.com Poprad, Slovakia…; Added by David Rutten at 12:06pm on March 15, 2013

Topic: Input Parameters Conflict: no python editor, however when I attempt to run the script using grasshopper I am getting a solution exception run-time error. I think this has to do with the inputs I am using in grasshopper as that is the only part I changed. When I change the "BackSide" input hint from ghdoc to surface the error I get in the GH python tester changes from an error in line 40 to an error in line 72. But I cannot seem to find the proper combination to get all parts to function. Attached are the .gh and .3dm files I have been testing with. Thanks in advance, Peter…; Added by Peter Schmidt at 9:23am on December 14, 2012

Comment on: Group 'FabCafe Tokyo': 金岡さんへ解法例有難うございます！ただすみません、私の説明不足ですが、Surfaceではなく、Close Brepへの方法でした。。。自分でも再度もっかい考えてみたのですが、途中のShift pathが間違えていました。 http://youtu.be/dj_UHPOvISg 自己解決ですみません。考えていただいて有難うございます！; Added by UTB01 to FabCafe Tokyo at 6:43am on February 17, 2015

Topic: 放射状のワッフルについて: を、rotateを使って、ジオメトリを中心にして円状に配置 ↓ ジオメトリとの交線を取ってサーフェスを張るという手順でいけると思います。 …; Added by FabCafe Tokyo to FabCafe Tokyo at 6:00am on October 2, 2014

Topic: Viewing numerical values of section forces: have duplicate values. For example, I have 72 nodes, so on each node there are 3 numbers superimposed and I can't read any of them. The problem is not with some duplicate beams or points because they are correct, I checked... So if anyone knows how to control this, it would help a lot. Plus, I want to view the values in the 'middle' of the beams, but I can only view them on the end nodes... Thanks!…; Added by Yafim Simanovsky to Karamba3D at 5:19am on January 2, 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

Comment on: Topic 'merge/union on multiple surfaces': ar to be that fast. Working on a smaller data set (9 X 9), it slows down noticeably by the ~20th iteration or so and freezes GH/Rhino completely for quite awhile until it finishes. Seems far slower than my 'suLoop' cluster on the same data, using Anemone 'Fast Loop'. Harder to benchmark though because the profiler shows the time for each iteration of your loop (847ms for the last one) instead of timing the complete loop. My only other comment for now is that the idea I demonstrated of doing a 6 X 6 loop (for example), then making 36 copies of the result and running them through a second loop... uses only a total of 72 'SUnion' operations instead of 1,296. That's a major reduction, even though the unions in the second loop are more complex than in the first loop. Would need to try different combinations to see what works fastest. Like 10 X 10 followed by 2 X 5 (1000 total), for example, vs. 2 X 5 followed by 10 X 10.…; Added by Joseph Oster at 8:21am on March 23, 2017

Comment on: Topic '(14/09/15)クラスA サンプルファイル': Cにカーブ、Lに分割ピッチを入力 ③各分割点の接線方向のベクトルを出す。　　　※ベクトルをRhino上で確認したい「vector display」　　　 A（ancor point）にはPのポイントを、Vのベクトルには接線ベクトルのTを入れる。 ④各接線ベクトルからZ方向を排除し、world座標のX-Y平面に平行なベクトルに揃える。　　　　接線ベクトルをxyzに分解　⇒　「deconstruct vector」　　　　これを「vector xyz」によって再構築する。（x,yのみを入力すればよい）改めてvector displayで確認してみるとよい。 ⑤各点ごとに座標系を定義する。　⇒ 「construct plane」で、OとXに、それぞれPとＶ（再構築したベクトル）を入力。　　　　※各分割点での座標系（平面）が小さく、確認できない場合がある。　　　　display　⇒　preview plane size　を100くらいに設定すると、良く見えるようになる。 ⑥階段のステップ（四角形）を描く。⇒ 「rectangle」を使用。以下のパラメータを入力。　　　　P・・・使用する平面（先ほど作ったもの）　　　　X・・・300 　　　　Y・・・800 　　　　※長方形が階段状に表示されるが、原点がまちまち。 ⑦長方形の中心を、各分割点の原点に合わせる。　　　　「area」コンポーネント　⇒　面積を出すコンポーネントだが、同時に重心も出せる。　　　　「vector 2 Pt」コンポーネント　⇒　AからBへのベクトルを作る。　これで原点から長方形の図芯へのベクトルを作成する。　　　　「move」で長方形と、先ほど作ったベクトルを選択することで、全ての長方形の図芯を各座標系の中央に移動させる。 ⑧階段に厚みを付ける　　　　長方形をサーフェイスに変換。　⇒　「boundary Surface」に長方形のジオメトリを入れて、サフェースにする。　　　　面に厚みを付けて立体にする。　⇒　「Extrude」に、ジオメトリと、方向（Z軸）を入力。　　　　Z軸は、ダブルクリック⇒zと入力⇒　「unit z」　⇒入力に数値（ベクトルの長さ）を入力。 ⑨手すりのカーブを作成する。　　　　最初に参照したカーブを左右にオフセットさせる。　　　　⇒「offset」で、カーブのアイコンのものを選択。　　　　Cにはカーブ（最初のカーブ）を入力　　　　Dにはオフセット距離を入力。　　　　階段幅（先ほど800と入力したモノ）の1/2を入れればよい。　　　　「division」を使用。固定値は、「number」コンポ―の右クリック⇒setnumberで2を入力。　　　　反対側も同様に用にして作る。　　　　「marge」で2つのカーブを統合。　　　　「move」でZ方向に800オフセット。 ⑩手すりを作る。　⇒「pipe」 Cに先ほどマージしてmoveしたカーブを入力。Rに50を入力。 ⑪縦のパイプを作る。　　　　divide lengthで両側の手すりのカーブを分割する。ピッチは最初にステップを分割したものと同じモノを持ってくる。　　　　「line SDL」で縦のラインを作成する。　　　　Sには先ほど分割した手すりの分割点。Dには方向（-z方向）、Lには距離（手すりのラインをオフセットさせた距離と同じ）を入力。　　　　pipeでラインに沿ったパイプを作成。＊＊＊…; Added by Yusuke Takei at 8:24am on September 16, 2014