an entry point named 'RHC_RhinoWeldMesh' in DLL 'rhcommon_c'. (line: 0)
Is this Method not implemented yet ?Any thougts ?
Many thanks,Philipp
Code which produces error :
Dim testPt As New Point3D(0, 0, 0)Dim testPt1 As New Point3D(1, 0, 0)Dim testPt2 As New Point3D(0, 1, 0)Dim testPt3 As New Point3D(1, 1, 0)
Dim test As New Mesh
test.Vertices.Add(testPt)
test.Vertices.Add(testPt1)
test.Vertices.Add(testPt2)
test.Vertices.Add(testPt3)
test.Faces.AddFace(0, 1, 2)
test.Faces.AddFace(1, 2, 3)
test.Normals.ComputeNormals
test.Compact
Dim deg As New Double deg = 5
Dim rad As Double = Rhino.RhinoMath.ToRadians(deg)
test.Weld(rad)
…
flat) and then subdivide your surface using the divide domain component and feed that into a surface box. Your base geometry, base geometry bounding box and surface boxes will all drive the box morph.
From the looks of your geometry, it appears that it is designed to nest in a particular way that isn't strictly rectilinear, but is more staggered, so that the top corner of one element fits into the bottom corner of an adjacent element. You can achieve this using the box morph, but you have to get pretty creative with how you subdivide your surface:
I'm attaching a couple of files...first of all is your definition with the changes in it to make the above. But also I used some components that I made recently (will release them in a package with a bunch more hopefully soon) called tree sloth, which helps manage data trees and lists. I used a couple of those components, so I'm also attaching the gha for those. Just copy that file into your components folder (under file-> special folders) and restart rhino/gh. The new components are just layered into different parts of the "Sets" components.
To explain what I did: you basically you want to have adjacent sub-surfaces along your guide surface to overlap at the top and bottom thirds. There are any number of ways to extract these surfaces...I just pulled out strips in each column and culled every fourth element, but shifted by one in alternating columns. So in the first column I take strips 1,2 and 3 and skip 4, take 5, 6 and 7, etc. and in the second column I start at number 3, 4, 5 and skip 6, then take 7, 8, 9, etc. Then I collect each of these batches of three strips and take the bottom left corner and upper right corner UV domains to create the target surfaces for the morph.
Hope this helps you out...…
Loop'. The fun part of the slower version is that you can see what it's doing while it's running. 'Fast Loop' gives no indication that it's working, so you want to test it with small numbers and be sure it's coded properly before bumping the iteration count up.
The GH profiler running the slow version showed between 1 and 1.5 seconds per loop, but the reality was more like ~10 seconds per loop toward the end of an 11 X 11 grid, or ~20 minutes total. It's easier to be patient because you know it's working.
The 'Fast Loop' finished the same grid in 1.6 minutes! An impressive improvement. I've been running it on a 30 X 30 grid (900 points) for ~23 minutes so far and see nothing yet. Not the ~12 minutes I had hoped for... Now 36 minutes on this loop for 900 points... hope it's not stuck. Not fast! Later - DONE!! Profiler says 59 minutes for 900 points but it was more like an hour and twenty minutes total. It succeeded, I have a single 'Closed Brep' from 900 extruded rings, baked to Rhino.
Another strategy to explore would be doing 'SUnion' on a smaller grid using the Anemone loop, then replicate it by moving it as needed to form a larger grid; then run the copies through another 'SUnion' loop. I went ahead and implemented that while waiting. It works and is fast! Started with 3 X 3 and ran the result again as 5 X 5 (9 X 25 = 225 total) in barely ~70 seconds!? Trying 36 X 36 now... 1,296 points appears to have succeeded in less than ten minutes! Though it seems to take quite awhile after the loop ends before control is restored to GH/Rhino. I'll let you do your own experiments and benchmarks.
I encapsulated the loop in a cluster called 'suLoop' (blue groups).
Internal of 'suLoop' cluster:
…
Added by Joseph Oster at 11:14pm on March 22, 2017
ells new products like the Firefly Interactive Prototyping Shield which mounts on top of your Arduino Uno and provides access to a number of useful input (ie. sensors) and output (ie. motors) devices. It includes features like:
Three linear slide potentiometers connected to analog pins 0, 1, and 2
Two-axis joystick connected to analog pins 3 and 4
Light sensor (photocell) connected to analog pin 5
Three push buttons connected to digital pins 2, 4, and 7
Red LED connected to digital pin 13
RGB LED connected to digital pins 3, 5, and 6
Two servo connections on digital pins 8 and 9
A connection to the Easy Stepper Driver (co-designed by Sparkfun Electronics and Brian Schmalz) to control stepper motors. The direction of the motor is controlled through digital pin 10 and the number of steps through digital pin 12
High-voltage MOSFET circuit capable of driving lights, valves, DC motors, solenoids, or anything else requiring higher voltage or current. The gate of the MOSFET is connected to digital pin 11 (PWM).
Some come take a look and let us know what you think!
…
(because 3 pins have been dedicated to inputs). So, if you want to control more than this, then you might need to bump up to the Mega. The important thing about controlling lots of servos is your power consumption. You need to provide enough power to support all of your servos. You need to find out how much current each of your servos draw and then multiply that by the number of servos you're going to use. Then you need a power supply that can handle that (typically 5V and however much current you calculated). The other thing to remember is to make sure you connect the ground of your external power supply to the ground on your arduino (all of your grounds need to be connected together). Other than that, it should be pretty straightforward.
Cheers,
Andy…
mum wall thickness of >1.0mm but I'm not sure about aluminium sintering. We have an Objet 3d printer at work that jets plastic media and we try to keep above 1mm wall thickness on that. It will print much thinner but it gets very hard to remove the support material without damaging the part.
You could create a tag attached by a thin section that protrudes from a discreet position on the inside of a corner piece? This could easily be removed during assembly.
Chris: looks like another good project! I'm currently trying to design moulds for all my corner pieces since there are 6 different corner pieces on my geodesic dome, 3 of which are split in half for ease of assembly, making 9 moulds! 3D printing was a bit out of my budget!…
Added by martyn hogg at 1:07pm on January 14, 2015
nt.
The real problem starts now: I get a datatree where, for each face, I get the index list of adjacent faces
i.e.
face 0 is adjacent to faces 2,3,1
face 1 is adjacent to faces 0,9
now i need to get two separate index lists looking like this:
list 1: 0 0 0 1 1 ...
list 2: 2 3 1 0 9 ...
any suggestions ??????
thx
…
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.…
he implementation of the Component more autonomous without the need for user intervention.
At present you have 1 main input for the data to be placed on a single sheet as per the input and the option to add more sheets manually.
Would it be possible to alter this to have a Data input and a Sheet Name Input so that the Path Structure dictates which sheet gets what data and the optional Name input gets applied.
For example
{0;0;0}(N=10) is Range A1:A10 on Sheet 1
...
{0;0;9}(N=10) is Range J1:J10 on Sheet 1
{1;0;0}(N=10) is Range A1:A10 on Sheet 2
...
{1;0;9}(N=10) is Range J1:J10 on Sheet 2
etc.
I realise that this would have to be very particular, making sure that only Place Holder A has influence over what sheet is used If there is a distinction of multiple sheet names.
For Example if you had a list of:
{0}(N=10)
{1}(N=10)
{2}(N=10)
{3}(N=10)
Place holder A could either be sheets or Rows so it would have to only work when there was a corresponding Sheet Names List for {0}, {1}, {2} and {3}
At present I have to do this manually using Explode Tree etc. Whenever I expand on the conditions (different Draft or Heel) Then I have to increase all of the outputs for the components highlighted in Pink
…
you post a screenshot of what the message coming from its readMe! output looks like?2) Close your Grasshopper and Rhino.3) Download "Revo Uninstaller Pro" from here. It is free for first 30 days, which is what we need.4) Right click on the RevoUninProSetup.exe and check if the file is blocked. If it is, unblock it.5) Run the RevoUninProSetup.exe file and install "Revo Uninstaller Pro".6) Uninstall "MapWinGIS" with "Revo Uninstaller Pro". It is important that "Revo Uninstaller Pro" deletes not only files from MapWinGIS installation folder, but also all other leftovers (as registry inputs). Here is a small tutorial on how to do that. Watch it from 6:10 till the end.7) Restart your PC8) When your Windows boots up, make sure that you are logged in as Administrator!9) In your Start menu's search box type: "UAC", which will find your User Account Control Settings. Click on it, and a new window will open. Set the bar on the left to "Never notify".10) Turn off your Windows Firewall.11) Then turn off your custom Firewall (in case you have another one, besides standard Windows Firewall).12) Completely turn off your Antivirus.13) Download again the MapWinGIS-only-v4.9.4.2-x64.exe.exe file from here.14) Right click on the MapWinGIS-only-v4.9.4.2-x64.exe file and see if it is blocked. If it is, unblock it.15) Right click on MapWinGIS-only-v4.9.4.2-x64.exe file and choose: "Run as"... Administrator.16) One the installation preparation steps start, choose "Full installation". Wait for the MapWinGIS installation to finish.17) Right-click on "Rhino 5" icon and then choose: "Run as administrator".18) Open the the ironpython_admin.gh file again, and again post a screenshot of the message coming from its readMe! output.19) Drop the "Gismo Gismo" component to Grasshopper canvas. Post a screenshot of the message coming out from its readMe! output.
So we will need in total three screenshots of the readMe! output messages.
Thank you once again for being patient, and sorry for the large number of steps.…
Added by djordje to Gismo at 1:52am on April 9, 2017