rves that "intersect" a plane placed on Z=6 above the first circle. I did this to have a collection of points from which to choose 3 and make a 3pt-circle.
[this second circle "fits" the catenary at a certain height, that's what I wanted to do]
Maybe it's obtuse but anyway that's the way I managed it.. I then used the "intersection" of the top circle with the original catenary curve to "split" the catenary into 2 parts, I then "Rail Revolution" the first part of it around the axis of the original circle, using the circle as a "rail", and I get a Brep surface.
It is a "open brep" surface, so now i'm having the problem of managing it if I want to subdivide it with Isotrim or other commands to control the number of subdivisions.
Is there a better way to go about this?
I am attaching the file.
About the image, I checked my code about 10 times to understand why it has those "lines" every 1 meter in the Z, and they already appear in the "rail revolution" component when it is visible, but in the "brep components" I can see the individual points along the rail curve.
I think this is what might be causing the brep to surface problem, but for the life of me I can't understand why the rail is not smooth and is "divided" into the 7 points instead of just one smooth revolution...
Thanks! :)
…
I said to myself : post (again) something in the errors/bugs category. But then I said (also to myself) : why ? everybody knows that ... post something fun(?) in the examples that can(?) guide(??) people out of the rabbit hole.
And here we are : 4 test surfaces, 4 paneling methods, 2 profile "classes", 2 orientation options, 3 methods to skin a cat, 2 methods to find intact panels (in "any" surface - trimmed or not with or without holes), 2 presentation alternatives, 7 gates, 2 filters, 1 Branch controller(?), 1 secret component (related with sardines) = let me make the maths : about 123,45 Loft examples (a bit primitive to indicate the main issue).
NOTE: GH quite frequently (a) fails to internalize data (b) internalizes them and reports the data as "null". Use Rhino file if this is your lucky day.
NOTE: Lunchbox is required
NOTE: Proper Named Views were defined ... but then components are moved ... blah blah: make your own.
best, Peter
…
nergy plus silulation and this is the error text:
Current document units is in MetersConversion to Meters will be applied = 1.000Duplicate surface name! Name is changed to: Pelle_Sopra_DupDuplicate surface name! Name is changed to: Pelle_Nord_Dup[1 of 8] Writing simulation parameters...[2 of 8] No context surfaces...[3 of 8] Writing geometry...[4 of 8] Writing Electric Load Center - Generator specifications ...[5 of 8] Writing materials and constructions...[6 of 8] Writing schedules...[7 of 8] Writing loads and ideal air system...[8 of 8] Writing outputs......... idf file is successfully written to : C:\Users\Personal\Desktop\TESI\x006\THOR001\EnergyPlus\THOR001.idf
Analysis is running!...C:\Users\Personal\Desktop\TESI\x006\THOR001\EnergyPlus\eplusout.csv......
Done! Read below for errors and warnings:
Program Version,EnergyPlus, Version 8.3.0-6d97d074ea, YMD=2016.01.05 20:08,IDD_Version 8.3.0
************* IDF Context for following error/warning message:
************* Note -- lines truncated at 300 characters, if necessary...
************* 160 ScheduleTypeLimits,
************* indicated Name=ANY NUMBER
************* Only last 2 lines before error line shown.....
************* 161 ANY NUMBER, !- name
************* 162 ScheduleTypeLimits, !-
** Severe ** IP: IDF line~162 Invalid Number in Numeric Field#1 (Lower Limit Value), value=SCHEDULETYPELIMITS, in SCHEDULETYPELIMITS=ANY NUMBER
************* IDF Context for following error/warning message:
************* Note -- lines truncated at 300 characters, if necessary...
************* 258 ScheduleTypeLimits,
************* indicated Name=ANY NUMBER
************* Only last 2 lines before error line shown.....
************* 259 ANY NUMBER, !- name
************* 260 ScheduleTypeLimits, !-
** Severe ** IP: IDF line~260 Invalid Number in Numeric Field#1 (Lower Limit Value), value=SCHEDULETYPELIMITS, in SCHEDULETYPELIMITS=ANY NUMBER
** Warning ** IP: Note -- Some missing fields have been filled with defaults. See the audit output file for details.
** Severe ** IP: Possible incorrect IDD File
** ~~~ ** IDD Version:"IDD_Version 8.3.0"
** ~~~ ** Version in IDF="8.3.0" not the same as expected="8.3"
** ~~~ ** Possible Invalid Numerics or other problems
** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
...Summary of Errors that led to program termination:
..... Reference severe error count=3
..... Last severe error=IP: Possible incorrect IDD File
************* Warning: Node connection errors not checked - most system input has not been read (see previous warning).
************* Fatal error -- final processing. Program exited before simulations began. See previous error messages.
************* EnergyPlus Warmup Error Summary. During Warmup: 0 Warning; 0 Severe Errors.
************* EnergyPlus Sizing Error Summary. During Sizing: 0 Warning; 0 Severe Errors.
************* EnergyPlus Terminated--Fatal Error Detected. 1 Warning; 3 Severe Errors; Elapsed Time=00hr 00min 0.30sec
thanks for any help
Lhor…
r more details: workshop information
The 2012 Workshops:
1. "ALGORITHMS & MATHEMATICS" - Leader: Edmund Harris with David Celento, Brian Lockyear (Rhinoscript + Grasshopper / McNeel) 2. "ROBOTIC FABRICATION" - Leaders: Proto and Kruysman (SCI-Arch Staubli Robot + Maya, Autodesk) 3. "CASE STUDIES IN PARAMETRIC DESIGN" - Leader: Andrew Kudless with and Andrew Heumann (NBBJ) (Grasshopper) 4. "ROBOTIC PROTOTYPES" - Leaders: Shiloh, DeLeon, Johnson (Arduino + Grasshopper + Firefly) 5. "COMPUTATIONAL DESIGN STRATEGIES WITH DESIGNSCRIPT" - Leader: Robert Aish with Fisher, Tierney (DesignScript / Autodesk) 6. "PYTHON SCRIPTING WITH REVIT / VASARI" - Leader: Nathan Miller (Python + Revit + Vasari / Autodesk) 7. "GIS DRIVEN PARAMETRIC DESIGN" - Leaders: Sandoval, Faichney, de Monchaux (Grasshopper, Finches, LocalCode, GIS)
About ACADIA 2012
The conference will highlight experimental research and projects that explore the reciprocity and synergy between bits and atoms, the digital and the physical, and between digital code and material logic. The conference will bring together designers, researchers and practitioners who engage, question and aspire to stretch these boundaries. Architects, fabricators, engineers, media artists, technologists, hackers and others in related fields of inquiry are invited to participate.…
d C)
(3)
(4)Then I made the edges rigid (like in your model):
(5) The paper deals with this in two ways, one is crumpling:
(6) The other way is curved edges:
(7) The curved edges allow for a developable shape that consits of two cone sections (joined by the green line, which is also the location of your extra fold.) Centre points are A and C.
I guess crumpling is tricky to do in Grasshopper (perhaps something for Kangaroo?),
so I would use the two cone sections to create an accurate model in GH.
Or, actually, stick with the extra fold! (A folded surface is also developable, and you've already made lots of other folds).
Good luck!…
re_Never_Ends_V666".
3. Delete the left C# that does the Ziggurat (and feeds the truss maker with the "skin").
4. Remove all the comments of type "don't touch ..." > be brave.
5. Create any spiral surface (like the ones shown as demos) in Rhino. Or Any List of surfaces (say: one spiral surface and some others - but better start with ONE test surface). DO NOT use trimmed surfaces (only my "pro" C# truss maker does this - but it's incredibly complex to handle it). In fact ... you can use them ... but forget it, for the moment.
6. Feed this green GH component shown (aka: the Red pill [Matrix], he he) with your surface(s) > surrender to the crazy world of trusses.
7. Listen to some appropriate stuff .
…
ick to the Bezier span option (because this "guarantees" the LESS visual gap when lofting - actually that's a lie but stick to the plan) .
1. If we had ONE pair "suitably" oriented then things could be a bit more easier. But ... there's a bunch of pairs around and IF your pairs are different (in the true sense of the liquid madness, he he) ... well we need a policy:
2. Find either (a) the centroids of (b) the min distance points and define an "axis".
3. Find the ccx pts (case a) or use points from (b) and change the curve seams to these. This yields curves that start/end at some controlled "neighbor" points (critical if your curves are different or "twist" - as pairs - etc etc). This is ALSO critical when you want peace of mind when lofting (or use sweep1) because don''t get for granted what the Loft options component claims by the "adjust seams" thingy.
4. Optionally change the 2nd curve orientation in order to get a clock wise + anti clock wise pair. More on that later (is related with other methods to "fuse" this with that).
5. Define points at each curve using a pair of double values (0-1 if the pair domains are 0-1).
6. Split the curves (get the segments that you want) and define pairs of vectors (at end/start segment pts) that could give us 2 bezier spans.Don't forget to control the vector "lengths".
7. Unite the spans with the segments.
If all the above fail ... well... there's always the Plan B: I could post the C# that does this and several other ways to "fuse" curves plus a curve maker that is rather suitable for your tower adventures.
best …
to problems. If anyone wants to take a look at the attached file "605b-3" and try to help me, that would be awesome.
The way I'm thinking about creating the louvers:
1. Contour the shape (could be any shape, but I attached the one I'm trying to do it to)
2. Divide those contour curves
3. Find the 4 points on those curves that are furthest away from the center of each curve
4. Move those points slightly away from the center of each curve
5. Replace the unmoved points with the moved points
6. Interpolate/NURBS curve through the new list of points
7. Loft the new curves with the original contour curves
I think I'm close, but I'm getting stuck at the end- I thought shifting lists would be the best way to solve my problem, but I'm a little confused as to how grasshopper is organizing the list of new curves and how to match that organization to the original curves.
Attached is an image of where I am stuck. I can only create a surface in the gap that I'm trying to create by the louvers. Either that, or one or two of the curves tends to create a "tornado" looking thing and i can't figure out how to fix it without individually breaking up the list. Is there a way to set all the curve seams to be at the same location in a list?…
ed according to list C.
I tried replace members, but it consists of geometry, so it doesn't worked.
In list C I filtered all the indices that need to be replaced.
All items in {0;0} from C need to be replaced by List B {0;0}
All items in {0;1} from C need to be replaced by List B {0;1}
And so on...
In the end everything needs to be fed into a orient component.
G is the geometry behind list B
A is the new list (but I don't know how to create)
B is the list A of all 60 panels
To wrap up the question:
I need to have entry 1 from list B in a new list on position: 0 1 2 3 5 6 7 10 11 12 15 16 21
I need to have entry 2 from list B in the same new list on position: 4 8 9 13 14 etc. etc. etc.
I wonder how I can do this :) Thanks in advance!
…
mainly grasshopper. (If it were just Rhino it perhaps would have been easier for me). I've been working on it for a while now and I unfortunately am a bit stuck.
Below are some of my concerns:
1) I know the theory of what I'm suppose to do which is to have the rectangular base and scale it then array it up. However I noticed that the thickness of the each lath and support varies. There are 25 laths in all and from the structure diagram I have gathered that there are basically 4 groups of the same thickness from the base going up its the first 9, then 7, then 5 and then the top 3. I just can't seem to figure out how to vary the thickness. I would assume the attached lath and support definition diagrams would help but unfortunately I don't know how to read it. I've tried some formulas which didn't exactly work but I still included them in the file.
2) I also need to figure out how to create the hole in the structure which is the entrance. I know in Rhino I could just Boolean it out but is there a way to do it in grasshopper?
3) I also need helping figuring out the definition for putting the vertical supports in between each row. The diagram says something fancy about "Testing acceptable constraints in flexion and in shear, we find an acceptable eccentricity that varies with each row." Ok maybe it wasn't so fancy but I have no clue how to do that with grasshopper!
4) My lecturer wants a Structure Simulation which I'm going to assume is what number 3 is all about?
I've attached my progress so far and would appreciate any help possible. I'd prefer if anyone could guide me using basic things (without any fancy plug-ins unless it's absolutely necessary).
However, any help is appreciated! Thank you so much in advance.
Cheers!
Jo
…