on 2: I think the reason to draw a fitness landscape is to highlight graphically the presence of local minima, even in a simple optimisation problem. In architectural terms, this means getting an idea of how many sub-optimal solutions there are in a problem, which helps while exploring conceptual design proposals.
Have a look at this very basic example (which I published with two colleagues on "Shell Structures for Architecture", chapter 18): a shell footbridge (24m x 4m footprint), which is generated by two parabolic section curves (the two apex heights are the two design variables). The maximum displacement of the structure under gravity load and self-weight is the objective function. Simple example, but several local minima and interesting shell forms (image below).
@AB,
The expression used by David in the Number of Samples Input is a simple “x+1”. By grafting the Divide Curve Output, he got 81*81 lenghts (6,561 values). You have to make sure that number is divisible by the no. of samples. The second expression used for the Length output is only a scaling factor (my guess), to control the height of the fitness landscape drawing.
Cheers…
n account of the position of the sun and weather cannot be expressed in terms of a single set of luminous intensity values (which is what IES files do).
With regards to your example files, I agree with Chris. The primary reason for the low illuminance levels is that the light bounces are getting lost in the tube. Have you checked with the manufacturer/distributor if the location of the IES file should be inside the tube and not flush with the ceiling? Physically modelling such tubes in lighting software like Radiance (which is what HB uses) or AGI32 is a fairly expensive proposition. This is one of the reasons why manufacturers provide photometric data for such devices (however simplistic that data might be).
The candelamultiplier increases or decreases the luminous intensity values. So it will have a direct impact on the calculation. The primary reason for having that input was to enable users to do some testing with different lamp types and environmental factors such as dirt depreciation. You need not change them for your simulation. Assuming that the IES file is inside the tube, in order to make this calculation work inside HB you'd have to crank up the calculation settings to a very high level (start with -ab 10 -ad 4096).
Finally, due to shortcomings in the annual simulation software (Daysim), IES files will not work directly work with annual calculations. However, there is a fairly easy workaround for that issue. In case you are planning to run annual calculations with IES files, please let us know here.
Sarith…
ing illuminance and limiting exposure (lux hours). Hours with direct solar irradiance are likely to exceed the limiting illuminance thresholds, which range from (200 to 50 lux as per Table 3.4 in CIE 157:2004). It makes sense to consider direct illuminance (an ab=0 simulation in Honeybee) separately from a normal illuminance calculation.
Assuming that the museum exhibits have low to high responsivity to light, an ideal solution would minimize direct sunlight. For daylight from the sky and reflected light, it might be enough to keep the illuminance levels below the recommended thresholds and then sum up lux-hours.
Daysim, the annual daylighting engine used by Honeybee and DIVA, is not very accurate for direct-sun calculations. You will get more accurate results if you run your analysis with Radiance directly.
Instead of considering the horizontal illuminance grids, one can create grids that correspond to the dimensions of the exhibit and then average those values. I think single points, as shown in your gh file might not suffice. Calculating lux-hours is by far the simplest part of such a simulation. It will only require averaging these points, extracting them into an array and then summing up that array.…
the number of desired lines.
Example, if I have a height of 100 lines, lines 1,2, 3 ... 50.52, 54.57 ... will be blue and 100.99, 98 ... 51.49, 47.43 ... will be red.
maybe the image is more helpful
But if I chose a lot of lignes, to didn't see the lignes, visually.
More something like that!
…
alidated the entire RhinoCivil Engineering solution and migrate to a purely Rhinoceros solution.
85 components for Grasshopper among other analysis of a field study of linear project or study platform. Dedicated to the construction and engineering firms using topographic data.
FoodForRhino
Look to YouTube
Blogger
Support email: rhinodeveloppements@gmail.com…
up d'entre vous connaissent pour l'excellent support qu'il a prodigué chez l'éditeur McNeel !
Dates : lundi 9 et mardi 10 décembre 2013
Niveau : Débutant
Pré-requis : non, mais connaissances en langage de programmation ou Grasshopper seront un plus, connaissances en anglais car le cours sera dispensé en langue anglaise.
…
m in the first place. What would I use to create these sets in a simple object which I can plug everything into. i.e. a mathematical script which uses one number (the number of items in the column). to join every neighbouring pair together. in this case, 21 rows, in 12 columns. Collecting the sets - 1 to 21 with 22 to 43 then 44 to 65 with 66 to 87 etc etc etc.
The selecting curves for the columns are drawn in Rhino, and are all equal in number (in height) as shown in Top view.
…
ius, like the image below. I have a string with all of the 8 radii in a group of data. I was using the Divide Surface command, but there are two problems. First, the resulting points have a tree structure shown in the screenshot below, with {8; 2; 3}. How do I assign radius so that the six holes on the same panel has the same radius? The second problem is, the divide surface command generates points along the edges, too, where I don’t need any holes. How can I get rid of them?
…
o simulate is someone standing a foot or two from their window, drinking their morning coffee and enjoying their view of the nearby mountain or body of water or whatever landmark is interesting in the area. I realize I'm sort of using the component backwards, but it is really useful in the context I'm applying it in, it is just returning un-realistic results in some situations (where the space needle is 98 degrees off the normal of the window, for example).
The weighting factor could also be folded into this, views closer to normal get more weight for example. In my firm I'm asked to produce this analysis a lot, but I hate giving caveats about this angle issue. It also returns counter-intuitive results, making our shaping of the building seem less impactful than it really is.
Anyways, that is my 2 cents. I might bone up on my vector maths and see if I can't crack it.
Thanks!
Shane…
), my script is triangulating slabs by drawing line in a crossreference way. This part was "easy"
What I want to do now is to link those slabs together
ie : if a slab is a surface AxBxCxDx
I want to link A1 to A2, B1 to B2, C1 to C2 etc.
I know it's a simple question of restructuring the tree in my Pshift component, so that I can use the line component with shortest list, and link each of those points.
Any ideas on how to fix that?
Thank you
Simon…