ifically: I have a 100' vertical plane lofted between curved top and bottom profiles. I contour it every 8' (normal direction is Z, giving me 13 horizontal curves). I use Divide Curve to divide each contour into 10 segments. The "Points" output of Divide Curve now yields 13 branches with 11 items each, corresponding to 13 contours with 11 points from the left end of the curve to its right.
I now want to string "vertical" lines, and connect all the 2nd items in each branch together, all the 3rd items, etc... in order to make a polyline that travels between each 2nd point or 3rd point. i don't want to use Cull Pattern/Nth/Index because the number of subdivisions could change (11 could become 20, etc).
How do I connect the Nth item of each branch in this tree? Moreover, how do I connect all values in a branch with their corresponding values in all other branches?
Thanks for any replies,
Richman Neumann
Solomon Cordwell Buenz Architects
…
aph relaxation in 3D and more). There is much more already in our GitHub repos and more to be added. For getting an idea of our future direction check this lecture out. For getting a better understanding of graphs and graph theory watch this lecture and this lecture on a gamified spatial configuration process. Stay tuned for more and do not hesitate to post Python questions in the meantime.
ps. If you are having installation problems, please check the remedy suggested below:
Comment by Iman Sheikhansari on August 26, 2019 at 8:33amDelete Comment
HiIf you are encountering a problem with rhino 6 versions don't worryFollow these steps.1. Download SYNTACTIC from https://sites.google.com/site/pirouznourian/syntactic-design2. Install it and go to the installation folder, Drag & drop SYNTACTIC(green one) over your grasshopper canvas.3. Close your rhino and reopen it. 4. Type GrasshopperDeveloperSettings5. Tick the Memory load *.GHA assemblies using COFF byte arrays option6. Run grasshopper and enjoy plugin
…
):
import rhinoscriptsyntax as rsstart=rs.AddPoint(0,0,0)end=rs.AddPoint([10,0,0])divide=20vec=rs.VectorCreate(end,start)vec=rs.VectorDivide(vec,divide)centerList=list()for i in range(divide): newVec=rs.VectorScale(vec,i) centerList.append(rs.CopyObject(start,newVec))for center in centerList: rs.AddCircle(center,2.0)any help appreciate thanks,roy…
Added by roy orengo at 4:03pm on November 15, 2016
):
import rhinoscriptsyntax as rsstart=rs.AddPoint(0,0,0)end=rs.AddPoint([10,0,0])divide=20vec=rs.VectorCreate(end,start)vec=rs.VectorDivide(vec,divide)centerList=list()for i in range(divide): newVec=rs.VectorScale(vec,i) centerList.append(rs.CopyObject(start,newVec))for center in centerList: rs.AddCircle(center,2.0)any help appreciate thanks,roy…
Added by roy orengo at 3:09am on November 16, 2016
ls of access and sometimes different ways to compute, it begins to be quite confusing.
A simple exemple: let's say I have a component that can work the same way with different sets of inputs. I can have a few inputs that never change, since they are always required in all methods. Then I usually put a "Method" or "Mode" integer value, where you can choose the kind of set to listen to. Then I have all the inputs that may be used for the sets, and of course they are not always optional anymore when the "Method" input changes. It's quite useful to do all-in-one components (taking less space in the toolbars, even more when the toolbar is already full).
Dumb exemple:
//SURVIVAL IN LONDON//
Name: Your name
Difficulty: 0=Easy, 1=Medium, 2=Hard.
EasyOption: OPTIONAL // If you are in Easy mode, are you afraid of burgers?
MediumOption: OPTIONAL // If you are in Medium mode, are you afraid of kebabs?
HardOption: OPTIONAL // If you are in Hard mode, are you afraid of chicken katsu?
Of course the list of option here is simple, but it often gets messy with some "If you are in Easy or Hard Mode and your name becomes by a T then this input works with another one" kind of things, etc.
At the end, anybody who wants to use the component just takes a huge thing on the canvas with so many inputs that they don't even want to understand the tooltips anymore.
So I was thinking that maybe it would be useful to have some font style to help a bit. If they can be associated and updated with other things (the "Mode" switch thing) then it's even better, but just simple optional / not optional stuff would already be really helpful I suppose.
…
he "source_" = 0 (SRTMGL1) is limited to 60 degrees North. The bug is fixed. Check the attached file.
Thank you for posting the link to ArcticDEM! I was not aware of it, it certainly looks very intersting!The 2 meter resolution also sounds wonderful!
Gismo at the moment only generates terrain and underwater terrain from three upper mentioned sources: SRTMGL1, AW3D30, GMRT.
https://www2.jpl.nasa.gov/srtmhttps://www.eorc.jaxa.jp/ALOS/en/aw3d30https://www.gmrt.org/services
The reson for this is because all thre of them are supported throug opentopography.org's query terrain web service, which enables to get the DEM data only for defined boundaries (in Gismo's case the _location and the radius_ inputs). This means that the terrain model is automatically generated by just defining these two inputs.The same principle is followed for openstreetmap shapes - automatic generation for given two inputs.
Geting DEM from services as ArcticDEM, would require finding the appropriate DEM tile containing the desired _location, downloading it manually and then loading it to Gismo.Even though this is possible and "under the hood" Gismo and MapWinGIS have methods capable of performing such task, I am still reluctant to do it. My assumption is that it may create a number of questions about reprojections, and non-alignment caused by the use of different coordinate reference systems.But if this feature is asked from a certain number of users, I assume that in the end I would have to provide it.
Let me know if the upper used "source_" = 1 (resolution 20 to 30 meters) fulfils your current terrain requirements.…
Added by djordje to Gismo at 9:30am on April 7, 2019
is means both E+ and Daylight simulations share the same lighting schedule. So I assume their results should be more or less similar or not that different, even though there might be some difference in their calculation methods.
But, having tried many times, the result generated by the "Honeybee_Daysim Electrical Lighting Use" is usually much less than that generated by the "Honeybee_Read EP Result" (e.g. 160.5 kwh vs 369.425 kwh as in the current parameter).
In addition, in "Honeybee_Lighting control Recipe", default parameters (lightingPower = 250, lightingSetpoint = 300, ballastLossFactor = 20, standbyPower = 3, delayTime = 5) were used in the current case except "control type" - [5] Always on during active occupancy hours with auto dimming.
In short, both E+ and Daylight simulations have already shared the same lighting schedule. As for Control type and Lighting Setpoint, they are only required in daylight simulation.
Best,
Ding…
to Daniel Pikers' Tutorial mesh relaxation tutorials we are already pretty far.
The Idea of our design is a hanging structure suspendend in a gap between buildings, where you can find places to rest, read or even to sleep. You can find privacy in the cocoons, that are connecting the planes with each other.
As structure we have a net in mind, that is tighter in the area of the cocoons and more transparent in the common areas, but we really don't know whats the right way to get to this point.
In the end of the project we need a printable geometry. We start our boxy design in Sketchup, and remesh it in Rhino. After that we feed it in our kangaroo definition.
1. A nurbs surface could give us more freedom (for postprocessing in tsplines) to form meshes with shorter and longer edges, representing our net. But I see now easy way to get a surface out of the relaxed kangaroo mesh.
2. Working with the kangaroo mesh could also work fine, if we'd find a way to control the edge length of the mesh (for example 20 cm in the common area and 5 in the privates) with an attractor point. Remeshing with Daniel's Plankton Plugin sadly doesn't work, I always get the "runaway faces circulator"-error.
3. It woud be great to convert the mesh to a hexagonal mesh, but I don't know any possibility to remesh an existing one...
You see, we're full of questions, but I really hope to get some help here :)
Agostino & Johanna
…
greatly appreciate it!!
You can write the number of the question and write your answer next to it, example:
1) a
2) c
3) a) Washington University in St. Louis
4) 2 weeks (1week+1week shipping)
5) 130
6) b
7) b
The survey questions are as follows:
1)
Did you 3D print before?
5)
How much did it cost (in dollars)?
a.
Yes, for a school project
a.
Between 20 & 50
b.
Yes, for a personal project
b.
Between 50 & 80
c.
Between 80 & 120
2)
Print size
d.
Please specify if otherwise: _____ dollars
a.
Between 2 & 6 cubic inches
b.
Between 6 & 12 cubic inches
6)
Do you think the price was expensive?
c.
Between 12 & 20 cubic inches
a.
Not at all
d.
Please specify if otherwise: ____cubic inches
b.
A little bit expensive
c.
Very expensive
3)
Where did you print your object?
a.
School
7)
Were you satisfied with the printed object?
b.
Outside school: _________________
a.
Yes, it was a great print without problems
b.
Not bad, some issues
4)
How long did it take to print?
c.
I was not satisfied, very bad quality
a.
___ days
b.
___ weeks
Thank you very much to all!!
PS: If you did many 3D prints, you can post multiple answers.
Wassef…
en la práctica de nuevos métodos de diseño y fabricación utilizando herramientas digitales. Estos procedimientos emergentes están cambiando radicalmente la manera en que nos aproximamos al proceso de diseño en términos de concepción y producción. Los participantes serán introducidos en el uso de softwares de modelado 2d y 3d para la generación de geometrías que serán posteriormente mecanizadas in situ en una máquina de control numérico CNC de 3 ejes.
¡AL FINAL DEL CURSO TE LLEVAS TU LÁMPARA A CASA!
Profesores: Equipo MEDIODESIGN* + TOOLINGROUP*
*Official Rhino Trainners. Acreditación otorgada por McNeel, desarrolladores del software Rhinoceros.
Lugar: Mediodesign. Pallars 85-91 5-2 BCN
Duración: 16 / 20 horas
Fecha: sábado 9 / domingo 10 julio de 2011
Horario: de 10h a 14h / de 16h a 20h
Plazas: 20 participantes
REQUISITOS
< Dirigido a estudiantes y profesionales de la arquitectura, diseño y profesiones afines.
< Ordenador portátil.
< Softwares instalados. En el momento de la inscripción, los participantes recibirán las instrucciones para la descarga e instalación de versiones gratuitas (trials) de los softwares.
CONTENIDOS
< Introducción al diseño avanzado y la fabricación digital.
< Entorno Rhinoceros y sus plug-ins.
< Herramientas y estrategias de trabajo CNC.
< Materiales y sus características.
< Planteamiento del ejercicio: diseño de una luminaria
< Desarrollo del archivo de RhinoCam para el mecanizado CNC.
< Mecanizado y post-producción.
< Entrega de propuestas: Presentación en formato digital del proceso de diseño y fabricación (pdf, powerpoint, etc…) y del prototipo de luminaria realizado.
INSCRIPCIONES
Precio: 199 € Materiales incluidos.
Forma de pago: mediante transferencia bancaria.
Límite fecha de inscripción: lunes 4 de julio 2011
Se otorgará certificado de asistencia. …