Search Results - 双色球2o17年88期号玛『9TBH·COM』a8彩票平台2023年3月19日7时37分37秒.H5c2a3.tttiwhlts

Comment on: Topic 'Catenary Surface with attracting points in the middle of plane?': 1. Buy some anti gravity tissue (available on request by Fotiadis ACME Industries: any color you want, payment in advance, cash only). 2. Create a pavement with a rectangular hole. Use Buchtal Bosco tiles (the most expensive stuff around > we live once). Avoid trees (it's too late) and/or anything (Less is more). http://www.agrob-buchtal.de/en/cd/produkte/produkte_seiten_2_19881.html?pe_id=88 3 .Put Vodka into the hole (I do hope Russian top stuff). 4. Do a semi submerged grid of tissues (vertical due to 1 - or your money back). 4. Provide armchairs to the spectators (these things take time). Put ZZTop on the stereo (or Cure). Empty your mind. Reset. 5. Wait for some appropriate wind and/or the 4 horsemen (whatever comes first). Moral: ResetNowForEver…; Added by peter fotiadis to Kangaroo at 7:16am on April 3, 2016

Comment on: Photo 'Trigonometry': an be given as 88° and 95°. All three angles must sum up to 180, and we're already 3 degrees over balance. Or maybe the user specifies three edge-lengths: 21, 12 and 8. 21 is bigger than 12+8, so even if the triangle was stretched flat, the two short edges cannot reach the ends of the long edge. The above is easy to test for and I add errors to the component if an invalid triangle is provided. However there are also many angle+edge length combinations which result in invalid triangles. I could of course test for these as well, but the problem is now tolerance. What if the user specifies a redundant angle of 54.7°, whereas the mathematics tell us that the actual angle is 54.7002°. Is that an error? If so, is the angle wrong or is perhaps one of the edges wrong? Or has the triangle simply been over-constrained? Is there a mathematically robust way of dealing with this? And if so, would that also be the most user-friendly way of dealing with it?…; Added by David Rutten at 2:23pm on August 23, 2014

Topic: FabTools & Rhino 6: 3D Text throws error: d' and no extension method 'AnnotativeScalingEnabled' accepting a first argument of type 'Rhino.Geometry.TextEntity' could be found (are you missing a using directive or an assembly reference?) (line 94) Along with some warnings: 1. Warning (CS0618): 'Rhino.Geometry.AnnotationBase.Text' is obsolete: 'Use RichText or PlainText' (line 88)2. Warning (CS0618): 'Rhino.Geometry.AnnotationBase.FontIndex' is obsolete: 'Use Font property instead' (line 92) 3. Warning (CS0618): 'Rhino.RhinoDoc.Fonts' is obsolete: 'Use DimStyles table instead' (line 92) I've downloaded the latest version of FabTools. I've completely un-installed and re-installed. I've Googled everything I can think of to find a solution, but most references are circa 2013 which is probably under Rhino 5. Which works totally fine, BTW. Does anybody know of a solution? Thanks, Michael …; Added by Michael Blase to FabTools at 9:35am on April 1, 2020

Blog Post: 毛竹和金属构件或者毛竹和再生金属在空间和人文环境中的重新排序（之一） Reordering of bamboo and metal or bamboo and recycled metal components in the human environment (one)

这个创作是用一些不同个体的逻辑方式，通过沟通和技能、技艺的执行，

作为可被认知的数学、物理、空间生产和艺术价值，为可能的相关领域铺就进步的台阶。

行为的过程大于结局，如同树与枝。

This creation is a logical way of communication and skills…

Added by zlyx at 1:10pm on September 29, 2011

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 'What does it mean when I have this error message ?': .0004. [1 of 7] Writing simulation parameters...5. [2 of 6] No context surfaces...6. [3 of 6] Writing geometry...7. [4 of 6] Writing materials and constructions...8. [5 of 7] Writing schedules...9. [6 of 7] Writing loads and ideal air system...10. [7 of 7] Writing outputs...11. ...... idf file is successfully written to : c:\ladybug\unnamed\EnergyPlus\unnamed.idf12. 13. Analysis is running!...14. c:\ladybug\unnamed\EnergyPlus\eplusout.csv15. ...... Done! Read below for errors and warnings: 16. 17. Program Version,EnergyPlus, Version 8.2.7-777c1f8d79, YMD=2015.02.28 16:09,IDD_Version 8.2.718. 19. ** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.20. 21. ** Warning ** Version: in IDF="'8.2.7'" not the same as expected="8.2"22. 23. ** Warning ** ManageSizing: For a zone sizing run, there must be at least 1 Sizing:Zone input object. SimulationControl Zone Sizing option ignored.24. 25. ** Warning ** ManageSizing: For a plant sizing run, there must be at least 1 Sizing:Plant object input. SimulationControl Plant Sizing option ignored.26. 27. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=F73533B3C6894C67936B_GLZP_1228. 29. ** ~~~ ** Opening Surface creating error=F73533B3C6894C67936B_GLZP_12_GLZ_1230. 31. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=F73533B3C6894C67936B_GLZP_2532. 33. ** ~~~ ** Opening Surface creating error=F73533B3C6894C67936B_GLZP_25_GLZ_2534. 35. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=F73533B3C6894C67936B_GLZP_2836. 37. ** ~~~ ** Opening Surface creating error=F73533B3C6894C67936B_GLZP_28_GLZ_2838. 39. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_940. 41. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_9_GLZ_942. 43. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_1044. 45. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_10_GLZ_1046. 47. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_1148. 49. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_11_GLZ_1150. 51. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_1552. 53. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_15_GLZ_1554. 55. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_2456. 57. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_24_GLZ_2458. 59. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_2560. 61. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_25_GLZ_2562. 63. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_3064. 65. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_30_GLZ_3066. 67. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_3268. 69. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_32_GLZ_3270. 71. ** Severe ** GetHTSubSurfaceData: Surface Openings have too much area for base surface=4BDFD67E6D0E486796CC_GLZP_3472. 73. ** ~~~ ** Opening Surface creating error=4BDFD67E6D0E486796CC_GLZP_34_GLZ_3474. 75. ** Warning ** GetSurfaceData: Very small surface area[2.94495E-004], Surface=F73533B3C6894C67936B_GLZP_076. 77. ** Warning ** GetSurfaceData: Very small surface area[3.84753E-004], Surface=F73533B3C6894C67936B_GLZP_178. 79. ** Warning ** GetSurfaceData: Very small surface area[9.16905E-004], Surface=F73533B3C6894C67936B_GLZP_380. 81. ** Warning ** GetSurfaceData: Very small surface area[4.96186E-004], Surface=F73533B3C6894C67936B_GLZP_482. 83. ** Warning ** GetSurfaceData: Very small surface area[2.37373E-005], Surface=F73533B3C6894C67936B_GLZP_684. 85. ** Warning ** GetSurfaceData: Very small surface area[6.35824E-004], Surface=F73533B3C6894C67936B_GLZP_786. 87. ** Warning ** GetSurfaceData: Very small surface area[5.86549E-004], Surface=F73533B3C6894C67936B_GLZP_888. 89. ** Warning ** GetSurfaceData: Very small surface area[7.63765E-004], Surface=F73533B3C6894C67936B_GLZP_1090. 91. ** Severe ** GetSurfaceData: Zero or negative surface area[-8.09566E-004], Surface=F73533B3C6894C67936B_GLZP_1292. 93. ** Warning ** GetSurfaceData: Very small surface area[1.51701E-004], Surface=F73533B3C6894C67936B_GLZP_1394. 95. ** Warning ** GetSurfaceData: Very small surface area[9.29917E-004], Surface=F73533B3C6894C67936B_GLZP_1596. 97. ** Warning ** GetSurfaceData: Very small surface area[2.94451E-004], Surface=F73533B3C6894C67936B_GLZP_1698. 99. ** Warning ** GetSurfaceData: Very small surface area[8.03294E-004], Surface=F73533B3C6894C67936B_GLZP_17100. 101. ** Warning ** GetSurfaceData: Very small surface area[6.83026E-004], Surface=F73533B3C6894C67936B_GLZP_18102. 103. ** Warning ** GetSurfaceData: Very small surface area[9.29917E-004], Surface=F73533B3C6894C67936B_GLZP_20104. 105. ** Warning ** GetSurfaceData: Very small surface area[3.19851E-005], Surface=F73533B3C6894C67936B_GLZP_21106. 107. ** Warning ** GetSurfaceData: Very small surface area[7.63765E-004], Surface=F73533B3C6894C67936B_GLZP_23108. 109. ** Severe ** GetSurfaceData: Zero or negative surface area[-4.05899E-004], Surface=F73533B3C6894C67936B_GLZP_25110. 111. ** Warning ** GetSurfaceData: Very small surface area[6.35824E-004], Surface=F73533B3C6894C67936B_GLZP_27112. 113. ** Severe ** GetSurfaceData: Zero or negative surface area[-9.91146E-004], Surface=F73533B3C6894C67936B_GLZP_28114. 115. ** Warning ** GetSurfaceData: Very small surface area[2.70158E-004], Surface=F73533B3C6894C67936B_GLZP_29116. 117. ** Warning ** GetSurfaceData: Very small surface area[3.22781E-004], Surface=F73533B3C6894C67936B_GLZP_30118. 119. ** Warning ** GetSurfaceData: Very small surface area[4.67821E-004], Surface=F73533B3C6894C67936B_GLZP_33120. 121. ** Warning ** GetSurfaceData: Very small surface area[3.22737E-004], Surface=F73533B3C6894C67936B_GLZP_34122. 123. ** Warning ** GetSurfaceData: Very small surface area[2.65634E-004], Surface=4BDFD67E6D0E486796CC_GLZP_0124. 125. ** Warning ** GetSurfaceData: Very small surface area[4.70736E-004], Surface=4BDFD67E6D0E486796CC_GLZP_1126. 127. ** Warning ** GetSurfaceData: Very small surface area[3.42507E-004], Surface=4BDFD67E6D0E486796CC_GLZP_3128. 129. ** Warning ** GetSurfaceData: Very small surface area[5.89276E-004], Surface=4BDFD67E6D0E486796CC_GLZP_4130. 131. ** Warning ** GetSurfaceData: Very small surface area[1.91146E-004], Surface=4BDFD67E6D0E486796CC_GLZP_6132. 133. ** Warning ** GetSurfaceData: Very small surface area[9.71205E-004], Surface=4BDFD67E6D0E486796CC_GLZP_7134. 135. ** Warning ** GetSurfaceData: Very small surface area[4.34494E-004], Surface=4BDFD67E6D0E486796CC_GLZP_8136. 137. ** Severe ** GetSurfaceData: Zero or negative surface area[-3.60159E-004], Surface=4BDFD67E6D0E486796CC_GLZP_9138. 139. ** Severe ** GetSurfaceData: Zero or negative surface area[-1.11946E-004], Surface=4BDFD67E6D0E486796CC_GLZP_10140. 141. ** Severe ** GetSurfaceData: Zero or negative surface area[-3.41257E-004], Surface=4BDFD67E6D0E486796CC_GLZP_11142. 143. ** Severe ** GetSurfaceData: Zero or negative surface area[-8.21483E-005], Surface=4BDFD67E6D0E486796CC_GLZP_15144. 145. ** Warning ** GetSurfaceData: Very small surface area[2.65716E-004], Surface=4BDFD67E6D0E486796CC_GLZP_16146. 147. ** Warning ** GetSurfaceData: Very small surface area[4.84044E-004], Surface=4BDFD67E6D0E486796CC_GLZP_17148. 149. ** Warning ** GetSurfaceData: Very small surface area[7.12297E-004], Surface=4BDFD67E6D0E486796CC_GLZP_19150. 151. ** Warning ** GetSurfaceData: Very small surface area[6.14324E-004], Surface=4BDFD67E6D0E486796CC_GLZP_22152. 153. ** Warning ** GetSurfaceData: Very small surface area[8.88887E-004], Surface=4BDFD67E6D0E486796CC_GLZP_23154. 155. ** Severe ** GetSurfaceData: Zero or negative surface area[-9.89060E-004], Surface=4BDFD67E6D0E486796CC_GLZP_24156. 157. ** Severe ** GetSurfaceData: Zero or negative surface area[-1.14849E-003], Surface=4BDFD67E6D0E486796CC_GLZP_25158. 159. ** Warning ** GetSurfaceData: Very small surface area[4.00479E-004], Surface=4BDFD67E6D0E486796CC_GLZP_27160. 161. ** Warning ** GetSurfaceData: Very small surface area[6.63061E-005], Surface=4BDFD67E6D0E486796CC_GLZP_28162. 163. ** Warning ** GetSurfaceData: Very small surface area[1.09018E-004], Surface=4BDFD67E6D0E486796CC_GLZP_29164. 165. ** Severe ** GetSurfaceData: Zero or negative surface area[-2.49326E-005], Surface=4BDFD67E6D0E486796CC_GLZP_30166. 167. ** Severe ** GetSurfaceData: Zero or negative surface area[-3.17446E-004], Surface=4BDFD67E6D0E486796CC_GLZP_32168. 169. ** Warning ** GetSurfaceData: Very small surface area[8.60686E-004], Surface=4BDFD67E6D0E486796CC_GLZP_33170. 171. ** Severe ** GetSurfaceData: Zero or negative surface area[-2.48515E-005], Surface=4BDFD67E6D0E486796CC_GLZP_34172. 173. ** Fatal ** GetSurfaceData: Errors discovered, program terminates.174. 175. ...Summary of Errors that led to program termination:176. 177. ..... Reference severe error count=24178. 179. ..... Last severe error=GetSurfaceData: Zero or negative surface area[-2.48515E-005], Surface=4BDFD67E6D0E486796CC_GLZP_34180. 181. ************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).182. 183. ************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.184. 185. ************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.186. 187. ************* EnergyPlus Sizing Error Summary. During Sizing: 2 Warning; 0 Severe Errors.188. 189. ************* EnergyPlus Terminated--Fatal Error Detected. 41 Warning; 24 Severe Errors; Elapsed Time=00hr 00min 1.51sec190.…; Added by Ninja to Ladybug Tools at 3:11pm on February 28, 2015

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

Topic: Multiple Attractors Scaled by Independent Percentage Values: points within the bounds of the site boundary and use each location as an attractor point controlling a variable at each point in the grid (radius of a circle/height of a cube/colour based on a gradient etc.).This would be based on proximity to the attractor points with the effect of each attractor point essentially scaled by the percentage associated with it. For example a location with 88% visitor rates would have a more dramatic effect than a location with 26% visitor rates. I've had a bit of a play around but can't seem to get beyond the point of what is shown in basic point attractor tutorials online. I'm definitely a novice. Here's how I figured it would be done: 1) Create a grid of source points within a boundary curve. 2) Select 18 pre-defined attractor points. 2) Measure the distance between the source points and the attractor points. 3) Invert this data so that variables increase with proximity rather than decrease. 4) Give each of the attractor points a strength value from 1-100% based on the visitor rates. 5) Use the scaled data to control a variable at each of the source points. 6) Create some way to control the drop-off rate of the effect from each point. It is at step 3 that I get completely lost. I hope my description is clear. Any help would be greatly appreciated, Adam …; Added by Adam_M at 11:26pm on March 10, 2016

Event: DIGITAL TOOLING vol.2: ったことないけど興味がある方♥ ぜひおこしください。必ずハートに火が着きます-* どうやったらできるの？オススメ参考図書など、みんなで情報を共有する刺激的な勉強会です。 ” DIGITAL TOOLING は未来のつくるの勉強会 ” DIGITAL TOOLINGではRhinoceros、Grasshopperに限らずコンピューテーションを幅広くとらえ共有する関西での交流、勉強会です。 ◼︎今回のフードは「タコ焼き」を予定しています。 ◼︎ワンドリンク制 500円、2杯目以降 300円 ■ゲスト *鈴木雄貴 / AP-LENS http://suzuki11.tumblr.com/ UI/UXデザイナー京都北山のsoftdevice inc.に所属し、SD LABで空間・立体を素材とするインタフェースをデザインしている. 個人活動として、アーティストのメディア・オーサリングやパーソナルプロダクトのデザインをしている. 京都精華大学　プロダクトデザイン学科 PCDコース卒業情報科学芸術大学院大学（略称：IAMAS）メディア表現研究科(メディア表現修士) 卒業 *砂山太一　http://tsnym.nu/ 建築家/美術家/プログラマ。コンピュータメディアや先端技術を応用した芸術表現および理論の研究をしている。その他、マテリアライジング展企画運営や kwwekやgh/eなどのアートユニットもてがける。 Ecole Speciale d’Architecture（パリ）マスター課程修了。多摩美術大学彫刻学科卒業。 JAKOB+MACFARLANE , Bollinger+ Grohmann Parisなどに勤務・協働。 2012-2013東京大学工学部非常勤講師。現在、京都市立芸術大学総合芸術学科特任講師、工学院大学建築学部非常勤講師、東京藝術大学大学院美術研究科後期博士課程。 ■運営 *大前道久 OPH（おっさんパワーハウス） 15年間ジュエリーメーカーで勤務し、制作からデザインまで様々な部署を経験してきました。Grasshopperの恩恵を受け、新しい表現や効率的なモデリングを実践しています。私なりのコンピューテーショナルなジュエリー制作をご紹介したいと思います。 http://www.tukuru.me/?p=2426 *木山潤平　sacsac 代表３Dプリンターやレーザーカッターなどのデジタル工作機を使える場所を運営。これまでアナログのモノづくりに没頭してきたことを活かし、デジタルとアナログの間に立って、アウトプットできる環境を提供していきたいと思います。DIGITAL TOOLING(DT)を機にGrasshopperを勉強している初心者です。みなさん一緒にはじめましょう！ FBページ https://www.facebook.com/events/886427334718542/…; Added by Michihisa Omae at 5:51am on September 23, 2014

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