two initial sections that define the starting point appear as curved lines in the top view - not what I expect from intersecting a surface with two planes?
So in the final result, the top view doesn't have a single straight line of points, though that is partly a result of the shape... a half peanut shell above, an ellipsoid below. Neither of my methods would achieve this.
Note that on page 118 (p. 132 of the PDF), it says:
With the grid generation tool it was found that bending curvatures become too large when the laths of the grid are bent to a (semi-)spherical surface. This problem was also found in the physical modelling process. [...] Large force was needed to pull the structure into a position, creating tension in parts of the structure (Figure 6.74). This effect can be compared with the tensioning of the fabric of a hyperbolic tent structure. Together with the results of the grid generation tool, this results show that it is hard to create a (semi-) spherical surface with a gridshell structure. It is therefore advisable to avoid such shapes when a gridshell structure is applied.
So the solution (obviously?) cannot depend on the nature of the surface; characteristics that apply only to one surface (a sphere) and not others.
Finally (for now), the code described in the PDF is RhinoScript, not Grasshopper, and I'm not confident that a solution is possible using GH alone. Iteration, recursion, stitching together the edges of the four quadrants - GH just isn't designed that way, and all appear to be necessary for this.
Not giving up but not confident either. There are some code guys here who would probably love this problem. Cheers.…
owever, LBNL has not yet implemented the ability to define the 'Gas Fill' from a .THMX file (all custom frame cavity models just default to air materials). As I understand it, there are a few features that the LBNL team has not implemented yet on the .THMX file type, which it is planning to implement in the future:
1) Ability to set 'Gas Fill' of materials other than air in a .thmx file
2) The ability to set the Gravity Arrow from the .thmx file
3) The ability to associate .thmx files with THERM and have them automatically open when double-clicked (this will save us from having to open THERM and navigate to the thmx file every time we want to bring it in).
I am hoping that the Honeybee components will give LBNL a good reason to implement these features on the thmx file soon. I plan to send the LBNL team an email about these critical missing capabilities.
To be in line with the current limitations that LBNL has set for the time being, I have changed the type_ input on the "Honeybee_Therm Material" component to be cavityModel_ instead. This way, you can set a cavity model if you are creating a gas material or you can just leave it blank to create a solid material.
I should also mention that, if you are using the "Import from WINDOW" workflow, the THERM polygons for the glazing system will automatically account for the gas fill by using the "effective conductivity" of the gas that WINDOW computes for you. This is what THERM does when you import a glazing system (THERM doesn't create a custom frame cavity material and set the gas. It just uses this effective conductivity).
Given that most exotic gasses get used between window panes and not in the frame cavities, the current capabilities should hopefully satisfy most needs. Still, it doesn't hurt to put a bit of pressure on LBNL to implement the features above.
-Chris…
st shortest path. The guiding splines would work like a forcefield so that paths are "drawn" towards them with a user defined strength and radius of influence.Since each path is basically independent, it should be relatively straight forward to multithread. I downloaded the C# code for the pathfinding node and have to see if I'm up to it.
Would also be interesting to know how far away the first beta of a multithreaded GH 2 is.
I also had some hopes when "Fabric Engine" showed a demo of a Rhino exporter, since its "Canvas" is an extremely optimized node system that's fully multithreaded and optionally uses the GPU, which could be interesting to explore for some heavy lifting if they for instance would attach it to GH. But I guess it does not make much sense for them as a target.
Above image uses 20000 random points. In Softimage XSI ICE this would not be much, since it's nodes are fully multithreaded and optimized for huge numbers of particles and point deformation. In GH, with anything above 500 points, things get rather "meditative".
Illustrator takes up to half an hour after each and every change to colour, line style, blending mode etc. I have one even more complex file with over 3 GB size and there Illustrator (CS6 x64) goes into some kind of trance and after some hours of thinking moves on to some advanced psychotic, catatonic state to never fully return... ;-)So usually I run it in the background while doing something else...
I recently tried different other vector graphics apps (Inkscape, Affinity Designer, Xara) but they were even worse if they were able to open the files at all. Maybe I should give Corel a try too.
Cheers and thanks for your offer! Your work is a major inspiration for me while learning Grasshopper!
Tom…
ver I decided to change the part system (nuts and bits taken straight from some real-life "similar" project in your country - I'll mail you some photos some day).
New ball pivots are only used in the T cable system. The one related with the Jansen style roof tubes is replaced with a classic U-Joint in order to handle any strut extension angle.
This system is way more capable to deal with clash situations and is 3 times more expensive. Notice the ultra beefy thingy at the atrium lips (forces are considerable: "equivalent" (kinda) with the ones in pre stressed concrete slabs). This peripheral mount freaky combo uses ball pivot as well for obvious reasons
More IF Valentino wins the next race.…
, I scaled each curve (vertical line) using its bottom end point as the center. This left the bottom relatively flat and exaggerated only the top points. Then I used the middle point of each curve to scale it. Finally, I realized that a common point of reference for all curves was more accurate, so I got the median of all the mid-points using 'PtCloudCntr': 'PtCloudCntr':
Next, looking at the scaled curves, I noticed that many of the bore holes had multiple curves! I confirmed this by creating sets using the X and Y coordnates for each curve's start point: There are 178 unique X/Y coordinates (bore holes), not 303 (the number of curves on this soil layer). This is a MAJOR DIFFERENCE from my initial assumption that each hole had just one curve per soil layer! It explains why the Delaunay mesh from all start or end points is so complex and not easily resolved into a single surface. Not quite sure yet what to do with this information? One possibility would be to combine multiple curves for each hole by using the top point of the top curve and bottom point of the bottom curve, ignoring the stratification indicated. This would likely yield a "cleaner" top and bottom Delaunay mesh. Or...?
…
Added by Joseph Oster at 8:52am on January 22, 2017
st action(join it in one(flatten it))?
or do i have to do it in a tree
in this case there this as error message:how do i get it public?is it this { get; set; } thing?
also change it from divideByLength to divideByCount to get the endpoints, just if you wonder about this strange move int he first line(probably you dont -so many strange moves,hehe)
also found this one:
do you have connections to papa noel or just went far away to get bestest sardines?
regards
…
first appeared in software like maya I believe where there are options for the translations (move, scale, rotate) called discrete move, discrete scale, and discrete rotate. This meaning you can only move, scale, or rotate them by specified interval values.
"Are there non discrete vectors and polylines" A single vector is of course discrete. The discrete we refer to in the image above is about discretisation across the collection of vectors forming a polyline. A polyline is discrete after it is made. This discrete is about the process of making that polyline. Telling the polyline to be "x" amount of angles only in advance.
Vectors and lines are already discrete in segments when compared to curves yes, but not in angle as there is an infinite possible number of angles in a world axis (continuous). There is no control over how many angles. A curve might subdivide into 100 angles when converting into a polyline in which case it may not be as useful for the construction of some joints or bends, say you wanted only 1 joint type then you would force the polyline to only have 30 degree angels with discrete vectors (of course this wont follow the curve as close but will be more optimized from a fabrication or bending standpoint) Consider these as more discrete - discrete lines (discrete in segmentation and angle). Rather than a polyline having infinite possible angles to represent a curve - these can have a pre-determined amount of angles - in the case of this image it looks like there are only 14 possible directions the line can move. As for the fillet, that is just after the fact - the important thing is how the original lines were generated.
Think of it a bit like AutoCad's Tracking settings that lock you into drawing at specific angles.
Anyway check out the plug-in here and I am sure you will understand as soon as you open the example files: http://www.food4rhino.com/app/discrete-vectors…
to the topmost green capsule, representing the best fitness found so far.
How can I evaluate my fitness function?
You don't. Galapagos evaluates the function all the time, that's how it knows when changes lead to improvements or not.
Is that for instance mean that the beginning of the run it is more fit?
This run shows that in Generation 2 a (marginally) better solution was found. The little plus-icon at the top of the orange graph at G=2 means that the fitness distribution went up. After that no better solutions were found.
If you're worried the solver is stuck in a local optimum, you can manually 'nuke' the population a few times to increase genetic diversity and maybe kick some genomes into a different optimum. Might work, might not, depending on how far away the other optimums are and how small their basins-of-attraction are.
[...] but I would like to understand more on the fitness function of it.
The fitness function is entirely your responsibility. Galapagos has zero understanding of the problems it is solving, it only knows whether a change made things better or worse. And it only knows that because it looks at the fitness function you wrote.
Is it correct my interpretation that the beginning of the run of the solver it is more fit than a later stage?
No, it did start out with a high fitness, but it was marginally improved near the start. After that, no further improvement could be found which means that Galapagos starts looking further and further afield for new solutions. This typically results in a worse average fitness for the population (the dropping dark orange line in the middle of the graph), but the fittest (best) solution is maintained, and that's the only one you care about.…
Added by David Rutten at 9:22am on November 20, 2017
ram of creating sightline.
In the diagram formula is N=[((R+C)x(D+T))/D] - R where R is the vertical distance of eye above point of focus and D is the horizontal distance from eye to point of focus.
So I have very simple test script.
Call main()
Sub main()
Dim D,R,N
Dim T,C
T=1
C=1
For D=0 To 5 Step 0
D=D+T
For R=0 To 5 Step 0
N=(((R+C)*(D+T))/D)-R
R=R+N
Call Rhino.addpoint(Array(D,R,N))
Next
Next
End Sub
Basically I want to make all variable "D","R","T" and "C" as parametric number slider in GH
and repeat "D=D+T", "R=R+N" and "N=(((R+C)*(D+T))/D)-R" until certain times.
The question is how to make a incremental loop in GH.
If anyone think that there is a better solution to do this please teach me.
Thanks for your time!!
…
owatt) of grasshopper definitions? Specifically how to make energy calculations for buildings modeled in rhino / grasshopper.Provided that you have defined a perhaps complex parametric designed building in rhino / Grasshopper. You know now more or less the wall/roof areas, window areas, building volume etc., you have information about ventilation need, heating reuse, air tightness, solar orientation, local weather data and you also want to implement active energy items such as solar cells, etc. Knowing all these factors, it must be possible to configure it parametric in a Grasshopper definition/ definitions, so all details are linked together from data about the building shape and its geometry to data about solar orientation to data about the U-values for walls/roof/windows etc. etc. Nearly all elements configured variable in grasshopper. In the sense that you could follow the energy changes 'live' (energy consumption per m2 / energy production) in line with modifications in the building shape / wall thicknesses / windows areas / solar cell areas and etc.If it will become possible in grasshopper / rhino to work parametric with energy issues and building design in a single interactive design workflow it becomes just fantastic.Products/initiative I know of in this area are:Ecodesign from Graphisoft: www.graphisoft.com/products/ecodesignAutodesk Ecotect Analysis: http://usa.autodesk.com/adsk/servlet/pc/index?id=12602821&siteID=123112And from this Grasshopper forum, sun studies made by Ted Ngai from studio Ngai: www.tedngai.netIs there anyone in here who have worked in this direction by using grasshopper?Best regardsPeter…