mponents.At Terrain Generator 2 component, the "origin_" input and "originPt" output represent a point of the terrain. So the terrain surface or mesh will be created starting from that spot, where that spot is actually lying on the very terrain.I noticed that this is not the case with "_basePoint" input of Terrain Generator component.In that case, in order for it to be able to use the Terrain Analysis component, one has to project the "_basePoint" to terrain mesh/surface.
We tried to fix the WebClient class issue with Mostapha and Chris last year, but without success. Eventually I will have to buy a new PC and install a newer operating system, which will remove the issue. Until then I will not be able to test some of other people's component's which use this class.I apologize if this is causing you any inconvenience.…
ead of "Terrain Generator 2" component. It will extract the elevation data from Google earth instead of Opentopography. The elevation data is different though, as they use different sources.By the way: I am already in love with the Karya project!!! It seems like a very interesting topic, and a perfect example of how environmental and computational aspects of design should be merged!I will definitely check the blog to read the new information about it, once in a while…
ese are some examples.
https://n-e-r-v-o-u-s.com/blog/?p=3983
https://mathematics.culturalspot.org/asset-viewer/10-000-circles-1/YgHExQHhZyL5_Q?exhibitId=QAJCFieRlsF8Lw
Thanks for the insight.
Shynn…
: Castellano
Horarios
Básico - miércoles
18.30 - 21.30 h
Avanzado - miércoles
15.00 - 18.00 h
Una vez finalizado el curso, el alumno podrá solicitar un diploma acreditativo del mismo.
Normativa: http://daetsam.aq.upm.es/servicios/cursos/informacion
Información cursos: http://daetsam.aq.upm.es/servicios/cursos/primavera2014
Métodos de pago: http://daetsam.aq.upm.es/noticias/2014/02/16/cursos-primavera-2014-aplicaciones-informaticas-e-idiomas
…
how Honeybee Set EP Air Flow worked but apparently not as it still opens the window when T(out) > T(in) (I get positive heat gains in this case).
I basically want to use sensible natural cooling when possible and relevant, i.e. when the 2 following conditions are met :
T(in) > 28°C
T(out) < T(in)
I know this is possible in EP but I have the feeling it is not yet implemented in HB ? Any help would be greatly appreciated.
Best,
Aurelien…
t difficult to know how to modify your curves.
But if the curves are too weird or too different, it won't get much better. Remember you can still move control points while kangaroo is running.
The wrong of this method is that you don't have real control.
Setting deviation to 0 is usually not very useful unless your curves are almost good. With the wavy curves you sent me, I was happy with 2 (Deviation is something like a % of the curve length).
I much prefer the other method. Curves with few control points, you're able to define tangencies, you've got high degree continuity. With 4 to 5 cp, Galapagos will have a wide range of shapes to explore. With more cp you'll get smooth tuning. You can still take the relaxed surface as a base to draw such curves.
Other ways to increase developability.
First is obviously Sampling. This one is quite tricky. Higher sampling might result in either better or worse results. It's very cpu expensive too, because it involves a little more than (Sampling)² operations each time.
Second is the surface type. Usually Network surface is the best, and allows to join multiple planks with less sampling. It's more expensive too, and runs only with Rhino 5. Loft tight is a decent replacement.
The "Reverse curve list" button, and the multi planks mode when you input more than 2 curves.
But everything depends on your tolerances and that I can't answer.
There are still some bugs here and there, especially in the cusp filter part. Sorry about the unit of Gaussian curvature, I forgot to fix it. It's model units, so it should be [1/m²] in your case.
About the pc slowing, it's really vital to block timers all the time and turn phasma on and off when you must. I experienced some slowing today though, and I was worried, but it's normal now so it must have been Windows or some GUI thing...
Fred.…
I change paramenters in GH sliders I see the progress in rhino with 4/5 seconds lag.
I think it is not an hardware issue, this is my configuration
Mainboard SuperMicro
Dual CPU Xeon x5650 (24 total core)
12GB DDRIII ECC
Hdd velociraptor 300Gb
Vga Nvidia Quadro FX3800
Hi, I attach the project files; when I move the slider bubbles trying to slide from a little value to another (like 50, 120, ecc) the result on screen is slowly to be shown.My question is, with the pc configuration listed above, is it normal with this project?There are parameters I can set in Grasshopper or Rhino to have faster results?There's a specific driver or configuration for my video card to improve performance?I would be very interested to see if the hardware on my system allows optimal performance with grasshopper or is normal with a definition so short ,even if it is the Voronoi , the system so slow to refresh when I move the slider
Thank you for your time…
combination is nearly 0 (of course with 1 try). You have about 100 (?) dimensions... its just impossible to do it well. Even with billions of random genotypes for 1st generation.
Its like 1:googol (10^100) to succeed. If youll try and run it on your pc, youll probably consume all the energy in universe, and it will take longer time than our universe will exist.
Sorry :(
EDIT : As David wrote in his post - every added dimension results with almost half of "success ratio". So as with one slider you have e.g. 1:2 ratio of success, with 100 sliders you have :
1:633825300114114700748351602688 (2^99)
To somebody more familiar with math -> correct me if Iam wrong :)…
ld be by no means a general benchmark of all arrays and lists, but it would give an idea of where List<T> and where T[] might be more appropriate.
Here is how you could set this up: on my PC, with 1'000'000 arrays/lists constructions and 50 inner loops on each, "arrays vs. list" has about 1:2 speed relationship, and "array vs. unknown length list" 1:9. You can test on your system and change the tests, too. If you do, remember to build in release mode and "Run without debugging".
- Giulio
____________________
giulio@mcneel.com
McNeel Europe, Barcelona…
ing red flag.
1. Solution exception:name 'scriptcontext' is not defined
Reading the script, i think, maybe what i am after is not possible, using named views.
It outputs the named views resolutions, but whatever named view i select get maximized and also gets set to whatever selected active view i have in Rhino. This makes the order of the named views, in a 4 view layout, to rearrange which messes the setup i have.
Fiddling a bit with the script setting viewMaximized to False, does not maximize the selected viewport, but stops the auto update of the viewport size too. I guess this happens because since its not maximized it does not register to ActiveNamed view.
So if getting the named views resolutions, without having to click in each,without getting maximized and set to the current selected view is not possible i thought of the following.
What i tried was the example given in rhinocommon
from scriptcontext import doc activeViewport = doc.Views.ActiveView.ActiveViewportprint "{1},{2}".format( activeViewport.Size.Width, activeViewport.Size.Height)
and i used it with a timer, so that everytime i click in view,named or not, it gets the resolution. But for some reason my pc hates timer and makes my system luggy. I could work with the above script if somehow the timer, or any other method, was embedded in it, so that when i click in a view it updates the resolution. I have a feeling this is something easy to.
*edit timer also forces a redraw of objects in viewport (hence the lag?)
thank you again
best
alex…