avec Giulio Piacentino que je ne présente pas davantage sur ce site ! Toutes les informations sont accessibles, réservations possibles sur le site R4U, [cliquez ici]
…
the 'patch' command which I imported from Rhino. The script runs with no errors but the patched surface does not appear in my model.
If anyone can resolve this issue or tell me how I can create such a surface using another method, I will be grateful.
Below is a copy of the script that I am working on:
import rhinoscriptsyntax as rsimport Rhinoimport scriptcontextfrom Rhino.Collections import CurveList
p1 = rs.PointCoordinates("e798e82a-5abb-468e-8c33-c39e1e0d7180")p2 = rs.PointCoordinates("820afac5-c594-42ea-8723-f3646019b0af")p3 = rs.PointCoordinates("41e3c0aa-30ad-466f-b88b-3be98f67a485")p4 = rs.PointCoordinates("3e0857c5-b463-49aa-8549-0b11f847b226")p5 = rs.PointCoordinates("19d946ae-b416-4f9e-939c-ed9e31fbe8e7")p6 = rs.PointCoordinates("65342367-a297-4536-8bff-5935ab500a69")p7 = rs.PointCoordinates("70793197-e1de-4b4b-9be1-38ebb9fe5dd5")p8 = rs.PointCoordinates("4be53db2-98ad-4b8b-80de-1ca055bf63a4")p9 = rs.PointCoordinates("cc58b791-ccb3-41d7-ac2c-2b64f83d0210")p10 = rs.PointCoordinates("bee35659-25ec-42c8-ae3f-65d053cdc6f7")
points1 = p1, p3, p5, p7, p9, p1points2 = p2, p4, p6, p8, p10, p2
c1 = rs.coercecurve(rs.AddLine(p1, p3))c2 = rs.coercecurve(rs.AddLine(p3, p5))c3 = rs.coercecurve(rs.AddLine(p5, p7))c4 = rs.coercecurve(rs.AddLine(p7, p9))c5 = rs.coercecurve(rs.AddLine(p9, p1))
curves = c1, c2, c3, c4, c5
list1 = CurveList(curves)
Srf = Rhino.Geometry.Brep.CreatePatch(list1, 10, 10, 5)…
f applications
* comparison between Grasshopper and RhinoScript
* Rhino modeling tools
* logic functions in Grasshopper
* brief introduction to VB.NET scripting
* curves, points, vectors and arrays in Grasshopper
* geometry vs topology, linear geometry in Grasshopper
Instructor:
* Dimitry Demin (Dipl.-Ing. Architektur). Education at University of Architecture and Fine Arts of Rostov, Bauhaus Universität Weimar, Universität Kassel and ETH Zurich. Working experience at Bollinger-Grohmann Ingenieure and Schneider+Schumacher Architekten. Portfolio here.
Details and space registration...
http://www.flexicad.com/service/schulung/kurse/grasshopper.htm…
component gives a warning about buckling in 1 or 2 modes. This also happens when I reduce the loads on the top chord, there are no loads on the bottom chord. For example:
> 92 kN/m no warning
83 kN/m buckling in 1 mode
50 kN/m buckling in 2 modes
<50 kN/m no warning
Since the truss is supported in the top chord against global buckling, this warning must be about the bottom chord? But the bottom chord doesn't have compressive forces, then what could this warning be about? And is there a way to check where it buckles (the modes in the warning)?
Thank you in advance!
Kind regards,
Cansu
…
(1) I have been exporting small sections of a larger model into Maya from Rhino as FBX. In Maya I rotate and scale the models (-90 in X, Scale XYZ 0.001). The Named Views are being saved, but do not have a successful import into the Maya model. They do not appear as in Rhino, and the problem is not solved by scaling or rotating the cameras.
(2) If I try going the other direction, the cameras exported from Maya as FBX are also not aligning with the model in Rhino as they are in Maya.. I will do my best to post some images of the problem and hope you can help.
error !!
This is what the named views look like
here I am trying to the other way with a good view from Maya
strange placement..
This is the best result I can achieve, after I scale the camera by 1000
Any Advice???
Thanks, Robert.
…
ysim.ning.com/
When you run the simualtion you will notice on the batch terminal that Daysim is also being called, so you may want to consider how Daysim uses Radiance files & data.
Regarding your current problem, I think you stumbled onto something weird and interesting.
Interior and exterior readings appear to differ by 40 in the best case scenarios. Even setting the transmittance to 1 yields similar results. I tried changing from cummulative sky to climate sky and got similar values. Changing the test points did nothing either.
I think, (yet I'm too lazy to prove this) that the difference in values stems from diffuse radiation over the sky dome.
If you delete everything except the glass you'll notice that interior values are like 80-90% of the exterior values (this seems like the expected behaviour with a transmittance of 1). So, if we consider that a vertical window, part of an opaque box, is receiving radiation from 25% of a sphere, as you start to inset the interior test points the radiation they receive will be a fraction of the 25%.
Let me try to explain this better...The exterior surface receives radiation from a section of a sphere calculated by 180degrees on the xy plane (let’s call this angle theta) and by 90degrees (let’s call this angle phi) in azimuthal elevation. If you integrate this over spherical coordinates (theta from 0 to pi; phi from 0 to pi/2) you will find that it comes to a quarter of a sphere. By comparison, the interior surface will not integrate theta from 0 to 180degrees,nor phi from 0 to 90degrees, instead it will be the subtended angle from the exterior surface as a function of their separation; the farther in you go the smaller the view of the outside.
If my hypothesis is correct there shouldn't be that much difference since the separation is only 10cms...the subtended angle would be like 170 instead of 180 for theta and 85 instead of 90 for phi...overall if you integrate both spherical areas there should only by a difference of 10%.
In conclusion, I believe the unexpected behaviour stems from the previous subtended angle thing. If direct radiation was the only factor the difference would be the aforementioned 10%, which suggests that an additional source of energy is also affected by this. Perhaps indirect and diffuse radiation from other areas of the sky dome.
I’m definitely intrigued on why this is happening. Please post if you figure it out.
Regards,
Mauricio
…
TB of RAM. I think I'm going to start a GoFundMe campaign to buy one for myself :)
2- The server's cost is about $13 an hour. I get free access to supercomputer through my university and xsede.org because I earned an NSF Honorable mention last March, however, the supercomputers available through both resources are a little complicated for me to use, as opposed to the one available from amazon that has Microsoft server 2012 already installed.
3- I wanted to run 400 annual glare simulations for 400 different views.
4- I tried a to perform annual glare simulation for one view on my Dell XPS that has Intel Core i7-6700HQ processor and 16GB of system memory. The simulation took 2 hours to complete. Radiance parameter ab was set to 6.
5- I wanted to obtain the batch file for each view so I can run them on the server. So I used the fly component to run all 400 simulations and closed the cmd windows, that wasn't bad ( for me at least) because I asked my son to this job for me, he was just glad to help me :)
6- I created one batch file using this cmd command:
dir /s /b *.bat > runall.bat
This created a file with the path to each .bat file. I edited this file in Notepad++ to include the word "start" at the beginning of each line. This was done using the "find and replace" dialogue box.
7- I split my newly created batch file into 3 batch files, each one has about 130 file names and " start" before the file names.
8- installed radiance on my server
9- Ran the first batch file on the server, this started 130 cmd windows performing my simulations, CPU usage was anywhere between 90% to 100% and about 105 GB of RAMs were used.
10. It took about 5 hours to complete all 130 simulations, I expected to run all in 2 hours but can't complain because this would've taken about 260 hours to run on my laptop. After the simulations done I ran the second and then the third batch files ( total of about 15 hours).
11. I got 400 valid dgb files. Couldn't be happier!
…
he time to work with it.
the project is about facade strips which turns along height. the top angle is
parallel to the facade and the bottom is max. 90 degrees twisted, but the strips
should turn diffrently to achieve more dinamic look.
first i have tried to achieve this by calculating distance between the rotation angle from points of the grid and a single point.
then i have tried to ad some more effecting points and used the distance to the divided surface (the circles are just to control the area of effection):
i manually lofted it.
the result is a bit annoying becouse the points that effect the angle are always visible:
i have triend to solve this by drawing a line and divided it to recieve points along the bottom of the geometry. the result is not working properly:
Anyway,
there must be a better/smoother way to achieve this. i would like to effect the twist of the surfaces by distance to a spline, but im just lost. can you help me please?
the problems im encountering:
0- distance spline to grid to effect the angle
1- list of x/y coordinates and angle of rotation for each point of the grid
2- export points to excel
3- lofting lines in one direction only (x1, x2, x3...)
4- reduce the list data to 2 decimal (0,00)
5- maybe angle from radian to degrees
thx…
ssing some step that actually turns the separate text numbers into values that GH can understand? I am using a blank space as my separator for the split object. I've also tried it with comma without any success.
Thanks!…
nize grasshopper extention files (except for .ghx, haven't tweaked it). Do anyone know how to bring things back to normal (better without reinstalling GH)? I miss good old .gh icon.
…