default text dot font size), then 12, 10, 8 and the column on the far right 6.Indeed when you try to print them, they all look the same:
which seems to be some limitation of Rhino 5.I attached below a new python component which will bake text instead of text dots. Rhino 5 does not have a problem with printing of their sizes.Replace it with previous text dots baking python component.
The "Refresh" button should be pressed before you decide to bake…
ipt, not after any churning:
Runtime error (IndexOutOfRangeException): index out of range: 0
Traceback:line 13, in script
Before that step, the curve array forms fine in Grasshopper, all 13K of them. It does churn extremely slowly away if I comment out line 13, and I can have it print the CURVES_CONTAINER size to see it grab two curves at a time out of it:
CURVES_CONTAINER.Add(Rhino.Geometry.Curve.JoinCurves(pair)[0])
Ah, it's the [0] part which I use since Rhinocommon so often spits out a list of outputs instead of just giving me my geometry.
I get the same error with just:
print Rhino.Geometry.Curve.JoinCurves(pair)[0]
Taking off the [0] which grabs the first item says the pair is empty:
Array[Curve](())
Switching back to a smaller balloon mesh, I see the healthy output:
Array[Curve]((<Rhino.Geometry.PolyCurve object at 0x00000000000000E3 [Rhino.Geometry.PolyCurve]>))
...and after adding [0] back, it prints:
<Rhino.Geometry.PolyCurve object at 0x0000000000000253 [Rhino.Geometry.PolyCurve]>
Ah, it's because my little point comparison loop is getting no hits, no matches of points to endpoints. It may just be a tolerance thing on a bigger scale. The endpoints are returning with 14 decimal places.
...yet if I try to test for distance being less than 0.001 instead point equality, same thing happens.
Do I need an RTree?…
Added by Nik Willmore at 11:04pm on October 10, 2017
ntornos de trabajo, entre técnicas interactivas y soluciones algorítmicas, se examinan conceptos y casos de estudio que le permitirán al participante decidir como y en que momento estas tecnologías pueden ser utilizadas como aliadas en los procesos de diseño y fabricación. Tomando como plataforma básica Rhino, se explora y optimiza el diseño y fabricación de topologías complejas bajo los entornos de Grasshopper, RhinoNest y RhinoCam. Su duración será de 4 horas, cupo limitado.…
nth". It complains about "global name "orange" not defined. When you define this situation through Series component it works fine. Checked with other LB components that use input from the AnalysisPeriod and they seem to work well, so the issue is only with SunPath.
2. Another one with the same components: defining, for instance, fromHour 10 - toHour 15, in the model you get from 10 to 14 (one hour less than you asked for), even though that the report output and analysisPeriod input are correct.
3. If already there, defining the "center point" for the Sunpath will be usefull. Not always you want the 0,0,0, or the center of the model. I mentioned this after seeing the part of the video when you intersect the lofted sun positions with a building. Of course you can move the model or move the fan but this can make a shortcut for the user.
Thanks,
-A.…
r piece out of the mold if you reverse it, befor the porcelain shrink. The porcelain shrink approx 14% between the mold and the final piece after it have been baked.
You have your piece with only a 2 to 4 mm wall thickness It'sdepend of the time you let the "barbotine" dry in the mold before you empty it. Here the thickness is about 2 mm.
Yes the piece is bake in a kiln to approx 1000 °C .
With a thickness from 2 to 4 mm, you can play with the translucidity of the porcelaine to let the light come through like in my voronoî project in 2014 : http://www.grasshopper3d.com/video/vorono…
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
+3 (for Haifa), that should give you more accurate times?
As this is part of a much larger genetic algorithm, I have made some choices for speed over accuracy.
The script generates the time for each 3 minute within the timeframe of the selected day. The sun vectors of these build the basis of the solar path on that day. Each minute would be more accurate, but also take longer to calculate.
My first idea was to intersect each sun vector with the surroundings. This would give me (with an accuracy of a minute/3 minutes accordingly) the excact time of the block. It would also mean that I had to potentiale check 60 * 14 = 840 for interactions with all context. So my approach was a bit different. I know the length of the solar path. I know the exact time of where this path starts/ends. So I approximate solarPathLength/minutes = length of a unit along the sun path. When I find a block, I check the length of the block and see how many minutes this would approximately be. As this is all math, it is very quick. But not super accurate. It gives me the indication I need though.
Cheers, Eirik…
nizzati da Better Nouveau dedicati alle strategie computazionali applicate al design. Sono corsi intensivi in cui ricerca e formazione affrontano da vicino design generativo, interaction design, digital fabrication e physical computing.
Per informazioni
http://www.betternouveau.com/workshop/grasshopper_workshop.php…