Refinement component at first, possibly using MeshMachine instead which is slow but actually gives many fewer triangles and adaptive meshing for tight curves too. Neither are easy to adjust on a deadline!
Then you have to sneak up on workable settings, using only a few lines, or Grasshopper will freeze perhaps indefinitely for 200 lines with extreme settings, especially the CS (Cube Size) setting that can blow up into a huge number if your scale is big.
Cocoon gives lots of nearly flat split quad faces so I quadrangulated those for fun:
Or MeshMachine can refine the mesh to make it efficient:
Whereas the Cocoon Refine component will merely return an equally fine mesh with more equilateral triangles but no serious remeshing to rid so many tiny triangles where they are not needed? Actually, it does seem to remesh also:
David said he used some of Daniel's MeshMachine code in there.…
rld.wolfram.com/EnnepersMinimalSurface.html
when i type the equations for z,y,z it says a syntax error so i obviously do not understand how to construct an expression. (screen capture attached)
Any help/explanation of using this function would be greatly appreciated
thanks so much
Capture.JPG…
r-School/
Registration deadline is 4th of March 2016
Official language: English with Italian and Arabic supportsTotal training hours: 120 hoursPlace: Sapienza University of Rome - Faculty of Architecture Final exhibition: Sapienza University of Rome - Rome - Italy4 professors and 8 tutors from University of Pennsylvania- USA, AA - London,politecnico di Milano- Italy, SAS-UNICAM-Italy, BAU - Lebanon , MSA, AAST and Cairo University - Egypt
final outcomes: scale 1 to 1 responsive façade; kinetic and optimized regarding to environment and users interaction. An official research will take in advance of how people interact with the kinetic Architectural object through the final exhibition survey .
to register …
rking at CITA http://petrasvestartas.com/Inflated-Restraint . Then I wrote my graph library in C# that has graph algorithms such as shortest paths(dijktra's, bfs, dfs), minimum spanning trees and etc. for Fox. It is not so difficult to read this book and implement graph methods in C# from pseudo-code: https://www.amazon.co.uk/Introduction-Algorithms-Thomas-H-Cormen-eb... The method that you pointing at is using multiple dijkstras for striping.
The thing with tiling use simple loop no recursion, at least this is more readable for me. Isosurface is also part of the Fox add-on. But as you know iso surface is just display thing, field value is what you checking at. Also colliding thing is faster if you do not check edge edge collision.
Another thing is you do those "aggregations" in 3D and you do not evaluate material properties of the real object, be it plywood, plexiglass or 3D print powder. It seems , if you make a physical prototype it will be strong as 3D, but it bends as tree branches because it holds only to one element. There are different way how to overcome that and make structure stable/lock it and branch back. Also take into account torsion forces of the connection.…
they may not always give you a clear picture of their precise functionality. I thought this may be an issue with many users so I decided to use this opportunity to list all the parameters with my quick take at describing their functionality. Here it goes:
DEFAULT VERTICAL SHIFT -- Number - Shifts panels vertically creating a custom-sized panel with height of the specified dimension at first row of skin.
DEFAULT HORIZONTAL SHIFT -- Number - Shifts panels horizontally creating a custom-sized panel with width of the specified dimension at first column of skin.
DEFAULT SKIN CHAMFERED CORNER--True/False - If "True" wraps panels around surface corners. If '"False" creates a custom-sized panel if necessary to complete the skin surface at the shared edge, defining this way a sharp corner.
RESET BAY AT POINTS-- True/False - When using Panel Bays (Group of Panels) this option restarts the panel bay at a surface corner.
FLOOR HEIGHT-- Number - The Floor To Floor value of the Skin generated. If Panels are shorter than this value, a leftover 'gap' will be seen at top of panels.
MINIMUM PANEL WIDTH -- Number - If the width of a panel (standard or customized) created during the skin generation is less than this value, the panel won't be created and the placement will be skipped.
MINIMUM PANEL HEIGHT -- Number - If the height of a panel (standard or customized) created during the skin generation is less than this value, the panel won't be created and the placement will be skipped.
MINIMUM PANEL AREA-- Number - If the area of a panel (standard or customized) created during the skin generation is less than this value, the panel won't be created and the placement will be skipped.
PANEL PROFILE TOLERANCE-- Number - If a resulting panel shape is within the specified tolerance value to any already created panel, this panel is used instead of creating a new panel shape. The tolerance specifically tracks the distance between each corner of the new panel and the corresponding corners of the existing panels. This parameter is mostly used in "SURFACE PANEL MODE'', where a large number of custom-shaped panels can be generated, to reduce the number of unique panels created.
GENERATE PANEL TYPES ONLY-- True/False - This parameter allows the Skin Generator to discard the creation of scene geometry but still have the grasshopper panel data being generated. The skin panels can be retrieved as grasshopper geometry using SkinDesinger's Display components.
RESET DF BETWEEN SURFACES-- True/False - When "True", the Design Controllers (Design Functions in v.01) resets to its initial values each time it starts a new skin surface. Used for instance to restart a layout pattern at every new surface.
SURFACE PANEL MODE-- True/False - The "SURFACE PANEL MODE" is used to generate panels matching the shape of the surfaces included in the "skinSurfaceList" input.
SURFACE PANEL ORIENTATION -- Orientation Type - When activating the "SURFACE PANEL MODE'', this parameter defines the orientation of the panel generated relative to the normal of the surface that defines its shape. The acceptable values (found in the "Surface-Panel Mode Orientations" dropdown) are:RESETFLIPROTATE 90ROTATE 90 FLIPROTATE 180ROTATE 180 FLIPROTATE 270ROTATE 270 FLIP
I hope this helps but feel free to reach out if you have any questions!
Santiago
…
cnicas y estrategias para resolver problemas que hoy se presentan en el diseño y fabricación digital de formas complejas y euclidianas. Se podrá entender mejor la diferencia entre el estilo Modernista y el Parametricismo que vivimos desde el 2000.
Tomando como plataforma básica Rhino, se explora y optimiza el diseño y fabricación de topologías complejas bajo los entornos de Rhino, Grasshopper y RhinoNest.
Instructores:
Andrés Gonzalez, McNeel Miami.
Director de RhinoFabLab.
MSc. María Mena Deferme, Directora de Arquitectura.
Tecnológico de Monterrey campus León, Mexico.
NOTA 1: Tendremos el patrocinio de LaserCUT.mx y podremos usar un Láser Industrial durante todo el taller, mas el laboratorio del iTesm.
NOTA 2: Estudiantes y docentes podrán adquirir Rhino 4.0 con un descuento del 50% sobre el precio de lista en USA.
Descarga el Outline del workshop PDF
http://www.screencast.com/t/M2FjOTBi…
at the same time just seems logical to me that a force would always seek the path of least resistance, so rather than making a 90 degree turn follow a more similar direction. The thought of separating stresslines into groups of tension and compression ist interesting from a design perspective. I wondered how tension and compression forces relate to the S1 and S2 lines, so what I did is pluging the outputs of P1 and P2 into the respective vector display for S1 and S2 and coloring the vectors blue for compression (negative values) and red for tension (positive values). So when you look at the upper side of the surface S1 (SC_02), Tensors along S1 show compression towards the middle and towards the supports Tension. However the Principal Stress Display of the Mesh Visualisation Component for the upper side shows it the other way round, again Red/ Tension and Cyan/ Compression as it says in your manual. Did I miss out on something ? When I look at the lower side (SC_03) I find it more or less matching up (I am just decerning between negative and positive values) so that might make the difference in the size of the compression area. So, does this mean that the S1 and S2 lines are related to the upper and lower side of the surface ? One beeing predominantely in compression(upper side) and one being stressed(lower side) ? That would also explain to me why S1 and S2 swap when you change the side of the surface. I am sorry, many questions... If you have time to explain, would be great. Also, maybe you have a book or article in mind which would explain those things more in depth....
Many thanks,
Philipp…
returned to GSA, it is solving. You might have to reset result scales using the GSA button.
Cheers,
Jon
Checking Input Data - this may take some time.
________________________________________
Data checks commenced at 23/08/2017 4:59:18 PM.
Checking input data for static analysis by GSS.
Shortest element (element 9) is 5 m long.Longest element (element 1) is 6 m long.
Data checks completed at 23/08/2017 4:59:18 PM. No errors or warnings found.
Analysis commenced at 23/08/2017 4:59:18 PM.
Analysis by Gss Static analysis
Initialising results modulesSolving for displacementsSolution statisticsSparse Parallel Direct 12 active nodes 14 active elements 2 analysis cases 24 degrees of freedom Minimum degree ordering 90 terms in stiffness matrix Maximum stiffness is 4.804e+009 at node 4 in direction z Minimum stiffness is 3.132e+008 at node 2 in direction yy Condition number of the stiffness matrix is ~ 5328. Maximum relative error in displacements will be 2.4e-10 percent. Factorization in 109 msSolving for element forces and reactionsCalculation completeAnalysis completed with no errors
Analysis completed at 23/08/2017 4:59:18 PM.Analysis time: 0.172 seconds
…