se enseñan los principios de modelado básico y orgánico en Rhinoceros. En Grasshopper se estudian los principios de Parametrización, panelización y análisis en Grasshopper, así como el proceso de manufactura digital para maquinaria de corte Láser y CNC.
UN solo pago anticipado $5,000.00
Pagos diferidos $5,500.00*
*reserva tu lugar con el 50%
De lunes a viernes de 10 am a 18 pm
Del 23 al 27 de julio de 2012
DURACION: 40 HORAS
SESIONES: 5 DE 8 HORAS
o info@dimensiontallerdigital.com
informes al 55 (50 16 0634) con Mayri Gallegos (o al cel. 55 28 85 24 73)
Incluye material para corte digital.…
ky.exe did not accept -p parameter and made empty sky.cal file.
----
Edit: solved run problem, Bee did not download OpenStudioMasterTemplate.idf
Get it here: https://github.com/mostaphaRoudsari/Honeybee/issues/119
Now get empty HDR:
C:\ladybug\prox\imageBasedSimulation>rpict -i -t 10 -vtv -vp 245.129 -226.458 20 0.405 -vd -0.549 0.656 -0.518 -vu -0.332 0.397 0.855 -vh 42.862 -vv 26.991 -v l 0 -vs 0 -vl 0 -x 800 -y 600 -af prox_RAD_Perspective.amb -ps 8 -pt 0.15 -pj 0.6 -dj 0 -ds 0.5 -dt 0.5 -dc 0.25 -dr 0 -dp 64 -st 0.85 -ab 2 -ad 1024 -as 175 -ar 150 -aa 0.200 -lr 4 -lw 0.050 -av 0 0 0 prox_RAD.oct 1>prox_RAD_Perspectiv e.unf rpict: 0 rays, 0.00% after 0.0000 hours rpict: skybright`c__ladybug_skylib_cumulativeSkies_SINGAPORE_SGP_SINGAPORE_SGP_1 : undefined variable rpict: 1020 rays, 4.91% after 0.0000 hours
----
Hi friends,
trying to get a cumulative sky image metric to run and encountered an issue with the image-based metrics component. It throws:
Runtime error (KeyNotFoundException): honeybee_materialLib Traceback: line 768, in main, "<string>" line 1442, in script
I guess this is some sort of setup issue on my end, or I messed up the definition? Any help appreciated.
Thanks,
Max
…
rasshopper (only compatible with IRC5 controllers). I made some tests with kinect and phones and tablets and it works (so if you have a good position for your kinect you can already know when a user is too close to the robot and stop the execution or slow it), but due to controller limitations I am now working on a different way of sending and managing data to the robot to minimise the latency of the system.
Galapagos will not allow you to switch between configurations and toolpaths, since configurations are computed by the IK solver and managed by several informations in the code, that can only be overrided or changed depending on the interpolation you use (MoveJ/MoveL/MoveAbsJ etc.). And once again, some configurations are not reachable depending on the rotation domains of certain joints (4th one for example) or also because linear interpolations cannot work for targets necessiting more than 90° of rotation. HAL computes by default the most "accessible" configurations in order to minimize 4th axis flip (which is a pain), and the next update will have a fix to allow to count the laps you do with the joints allowing more than 360° of rotation in order to prevent to reach the max values (otherwise the robot is locked and the application is stopped), there is a little bug on the 6th axis on the current version. IMHO these questions are much more important to solve for the design of your application than the approximaton of the workspace (it is very easy to measure the max radius of rotation, and singularities can always been reached using moveAbsJ).
By the way, all those things are not exactly trivial to solve (some are with the new verson of HAL, but not all of them), so depending on how far you need to go, I hope you don't have a deadline soon...…
eople use different methods and components was the way that I learnt most of what I know (and it might solve parts of other's problems)! It's always apparent from forum posts that everything is work in progress.
The "divide curve" components gives you tangents (T) to the curve at the points you've made. You want the perpendicular (right angle) to the curve, so need to rotate this vector around point on the curve (P) by 90 degrees or Pi/2 Radians .
It seems you're finding your lengths as required, but then passing them through a unit Y vector - so they are only ever going to move in the Y direction. You need to use an "Amplitude" component with the perpendicular vectors from above and the lengths you've calculated.
Before sweeping you'll need to properly align the rectangles such that they are also perpendicular to the curve.
…
Added by Joe Allberry at 10:33am on August 4, 2015
se the final panels that you want to rotate, or is this file just an example? Do you also have panels in other facades (in other planes)? Is the positioning of the panels random? Is it completely random, or are there some rules? Are the dimensions of the panels fixed or can they change, and how?
2. If I understand correctly, you want to have 2 different rotations, right?
2a. The first rotation is around the edge of the panel that lies on the facade and you want it to be between 0 and 90 degrees, right? How is the angle for each panel defined? Based on the sun's beams direction and, if yes, how exactly?
2b. The second rotation is around the X axis, on the right point of each panel (which is fixed on the facade) and you want the angle of rotation to be specified based on an attractor point, right? Is there a minimum and maximum angle or do the panels always align with the attractor point?
For a better understanding of these questions, see the attached definition (open it together with your 3dm file). Here the first rotation is the same for all panels and is controlled by a slider (until you explain how you want to define the angles). The second rotation doesn't have any constrains, so the panels always "look" at the attractor. But, as you can expect, strange thing happen this way: Panels hit into each other, rotate until their solar side is looking downwards, etc.
Still, I believe, if you answer the above questions we will get somewhere.
Cheers,
Nikos…
Added by nikos tzar at 5:42am on September 24, 2015
s. Now ... I want from you to do the proper combo of columns for the job: I want a dynamic solution worth the name not some stupid columns going vertically. Use the tree regions in order to avoid distorting the glass modular floor. Say like this:
The truss must engulf the trees. Killing a tree is a crime (even touching it should be a crime). How to do it? Same for the rotating fins. Assembling the truss must take provision of the branches (if they are fragile).
Plaza must being divided as follows: a perimeter ring (critical) separates the glass floor panels from the ugly buildings AND the tree regions. Fine grey pebbles are OK for that. Then the panels deploy in the remaining region. Panels must be all the same: 90*90cm. Solve this "arrangement" with GH. Measure the drainage slopes and calculate the Buzon pedestals with GH (how far we need to adjust them: critical for ordering).
Cover the existing pavement with a 5cm thick layer of black pebbles (bonus: hide the cables for the led arrays and the rings [no WiFi required]). Create variations of these arrays in GH.
Create something for servicing the whole thing.
Greenhouse effect can raise the temperature below the glass flooring (BTW: panels are at 1-2 cm distance [Buson spacers] each other [rain + escaping gases]).
…
ese seem to have one issue which I need to be addressed for my application.
The grids which are produced using the methods on here follow the surface and tend to be equally spaced in two dimensions. What I need is to create a grid which keeps the distance between the path lines equal whether the angle between the lines is 90 of 45 degrees. At the moment the grids act a bit like contours on an OS map but they bunch up in the lower parts of the curves and spread out in higher parts.
Below is a picture of what I produce via grasshopper so far but using a grid formula from elsewhere on the forums along with Rhino to connect up the paths. In this example they seem equally spaced but they differ by anywhere between 0.755mm and 0.785mm which if scaled up would be a problem.
Any Ideas how to help me split the surface up equally in all dimensions, meaning that if I were to sweep the tool path with a circle radius of half the distance between the lines/rails, there would be no gap between the beads/filaments?
I appreciate any help or advice hugely.
Philip
…
st between those two applications. But as soon as every frame is re-calculated I noticed that intersection function is very slow. It is actually so slow, that maximum number of polygons to play with is only 10 or less.
Could you help me to find a faster solution for my script?
calculation of intersection lines;
//////////////////////////////////////////////////////////////////////////////////////////
import ghpythonlib.components as ghcompimport rhinoscriptsyntax as rsdef ctr(crv): pts = ghcomp.Explode(crv)[1] pts = ghcomp.CullDuplicates(pts,0.001)[0] return ghcomp.Average(pts)pts = []lines = []ctr_c1 = ctr(C1)for crv in C2: if ctr(crv) != ctr_c1: int = ghcomp.CurveXCurve(C1, crv)[0] if int: [pts.append(x) for x in int] lines.append(rs.AddLine(int[0],int[1]))
/////////////////////////////////////////////////////////////////////////////////////////////
The overall description of the script:
a)Processing+ghowl is used for moving objects and physics
b)python script (slowest part) calculates intersection lines
c)intersected parts of polygons are rotated in 90 degrees.
I have attached grasshopper and processing files. (processing is not necessary to test the script)
Thank you in advance,
Pereas.
…
width of the other letter
find the intersecting shape with Solid Intersection
re-orient final shape
This process sometimes breaks when a letter has one or more "holes" in it (eg: B, O, R). When this happens, the Solid Intersection component experiences an error and says "Boolean intersection set is empty". I don't know what that means.
I have tried the quick-fixes of flattening and grafting to no avail.
Could somebody shed some light on this issue?
I have internalized the letters into the attached GH def, but am also attaching the illustrator file that I'm using.…