ee circles:
It took me a while to come up with a good Fitness Function but eventually I think I managed it. As you see the result is actually pretty good, it took about 5 iterations (1~2 minutes) of the Simulated Annealing solver to get this answer. I also attached the file, though you may not be able to open it even on the most recent publicly released version.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 6:50am on December 11, 2012
anually update the definition for the changes to have an effect. Also, it's not very user friendly to change data using commands (you can add them to the toolbar).
I recently did a definition that required custom attribute data per object. Since objects could vary in number it was easier to have the data attached to the object rather than in a spreadsheet. I only needed 3 or 4 values per object, so i just added them to the name of the object in the form of "a;3;500". I have the object properties window open all the time so this way it's easy to quickly change the values.
It would be great if rhino's GUI allowed to add and change custom attribute data easily. Cinema 4D does this very well. I think David was working on a plugin that did this but i doubt it's still in development.…
Added by Vicente Soler at 4:10pm on October 12, 2009
ple from 1 to 10)
It mean 9 000 transform in 1
9 500 transform in 5.5
10 000 transform in 10.
etc etc...
These number are generic (it can be from 587 to 629).
I start to try with functions, but I didn't find.
I aslo didn't find grasshopper tool for that...
So If any body have an answer, or an idea...
Thanks a lot!…
ntent.com/search?q=cache:c23wiy0_xv0J:www.grasshopper3d.com/forum/topics/faster-split+&cd=1&hl=nl...
That's why I proposed the planarsrf method, I tried it with more text and indeed it's also quite slow, but it does work. You should maybe not do the whole text at once but make surfaces sentence by sentence, that way you can also have more control over the size.
but look, this works:
…
assume we want to format two numbers, one integer and a floating point value. The integer represents an index and it should appear inside square brackets, then we want the floating point number rounded to a maximum of 4 decimal places (but always using at least one decimal place, even if it's zero), and then, in parentheses a scientific notation representation using 8 decimal digits of the number.
So, assuming the index is 16 and the value is 47.280006208, what we are after is:
[16] 47.28 (4.72800062E+001)
To make this work, we need a formatting pattern that looks like:
[{0}] {1:0.0###} ({1:E8})
The square brackets, spaces and parenthesis are just part of the output, they have no meaning whilst formatting. Everything inside the curly brackets though will be replaced with a specific formatting of one of the values.
When using the Format component as shown above, the formatting pattern is just text data. The component knows that it is supposed to use the Format() function using the pattern text and whatever additional data is provided.
When you invoke the Format() method in an expression, you do need to make sure that the pattern is actually text:
So here the pattern needs to be encased in double quotes, otherwise it will be treated as code, rather than text.
You cannot use the formatting method in the internal expression of a number parameter, because this method returns text, whereas the number parameter is only capable of storing numbers. Any expression that you put into a number parameter had better return numbers as a result.…
error, but resetting the height to <100m should fix things.
The height of the night boundary reflects the diurnal pattern of the urban boundary layer (image below). During the day the solar shortwave radiation heats up the urban surface, mixes with the air above creating a tall boundary layer. During the night the surface cools down, the boundary layer becomes more stable, and it's height is reduced. So typical heights for daytime is ~ 1000m, and for nightime ~ >100m.
So increasing it by a factor of 8 to 10 is likely what is causing issues with the UWG calculation for you. I started a github issue here: https://github.com/chriswmackey/Dragonfly/issues/11 so that we can fix this typo. Also we should figure out why exactly the calculation is failing so that can potentially put an upper bound to the inputs or a better error message. Thanks for catching it!
Finding some reference data linking weather layers to urban typologies is a good question, I'd like to find some too. Perhaps Chris/Mostapha might be able to provide some? You can check out the following thesis [1],[2] that the UWG algorithm is based on, which references three case studies for Singapore (Punggol), Capitoul and Bubble:
[1] https://dspace.mit.edu/handle/1721.1/107347
[2] https://dspace.mit.edu/handle/1721.1/59107…
) component, generate the raytracing path from Source to receiver only for 1 "Sensor"?
Would be optimal to be able to analyze, for example, all the sensors in the room, even with the PachIS, because I found that only with the PachRT + PachIS combination I can have a comparison similar 1 to 1 with a Odeon simulation.
Thanks and best regard
…
re are two new lines inside the code that let you deal this issue. However, the results for that type of geometry will be something like this:
I think the issue is because of some curves in crvList.. and to solve it you have to play around the start number as Michael told you.
Anyway, If you want, you can try the attached file where there is a method which should be fine for both geometries in your file: with holes or not.
The principle is to set the first number of the series component to half of height of floor (e.g. floor = 3 meters => start = 1.5 meters) and you can create a piece of workflow to do this operation automatically.
Best
Antonello…
mmed triangular NURBS surface. However, please notice that the parametrization will be small in the area of the two coincident vertices.
I'm attaching a very simple example (Gh 0.6.0059)
I hope this is helpful,
- Giulio
________________
giulio@mcneel.com
McNeel Europe, Barcelona…
speed.
Iam using a Q6600 Quad (2.4) and 6 gb Ram with a Nvidia 460 GTX (1024) GH runs well on it but with really complex Data it takes a few minutes until u get an result.
U should get a machine with this Hardware for less than 500 Euro. But i would get a faster prozessor.
Greetings…