ight. Note that i added the Ladybug component to simplify the inputs...
Here are some functions i'd love to see:
1. Ability to cull down to a partial year / date range AND hours range. Currently the DSchedule component can only truncate time of day. But if for example i want to look at averages just during the summer months between 9am - 6pm, i have to do that in the excel .ill file. It seems that the components may allow this already, just not sure which settings need to be set (seems that the reporting frequency has something to do with this...)
2. I'd also like to be able to look at a subset of the points to look at averages in a part of the grid. The easiest i presume would be just to pull item #s; maybe there's a way to add visual identifiers to the selection option? Again, have been doing this in the .ill file.
3. Provide, as an alternative to the .pts file, the option to input the point geometry directly from the rhino file - maybe this would help with #2?
4. I read up on your explanation on showing point-in-time values but can't seem to get that working. Would love to be able to do slider animations of the point-in-time calcs over a day like the bottom right of this (here i used Ladybug but the DA output would be more accurate).
5. Visualization Bounds doesn't seem to work on the daylighting side - would like to be able to manually change.
6. Showing the peaks is a fantastic addition! But all that information is bundled in the python script - would love a way to parse it out to just show the peak numbers for example.
7. Similarly to how DIVA shows data, it'd be great to add a component that visualizes the simulation parameters and color scale in the Rhino viewport...:)
i'm sure there's more as i continue to use it...
great script.
dan
…
思った感じになりません。
balls の代わりにplanarカーブを直接入れてみましたがエラーが出ます。
ファンクションにしてみたところ、forループので作った数値が反映されていません。
ファンクションのインスタンス?を出力していないと思い上記のようにしましたがエラーが出てしまいます。
以上の事から自分の認識が正しいのかよくわからなくなりました・・・
python自体の深いところをわかっているわけではないので余計こんがらがりました。
そこで、for b in ballsはどのような条件または使い方であれば使えるのでしょうか?
そして、上記のように別のオブジェクトに対しての使い方はどのようにすればできるのでしょうか?
2:同じファンクション内のdist = rs.Distance(self.pos,b.pos)についてですが
この文章も for b in balls によってbはBallのインスタンスであると定義?されたためb.posがbの位置であると分かるのでしょうか?
pythonは定義しなくても動いてしまうのでどのような時に使えるのか文章見ただけではよくわかりません・・・
大変細かいことかもしれませんが、よりpythonをしっかりと理解するためにも、どなたかわかる方ご教授いただけると幸いです。…
and my Rhino 5 stopped in SR 7 and I´n not let the program in automatic update.
So we installed the SR 10 release and update to SR11 after re install the Rhino 5
After this novel I tried to grab something and for the first time after rebuting and it does not work!
:(
I checked the .net and tried to install the newest but installation did not work and they say that a have the last version...but I´n not sure if it is true...
Next week i´ll see with the Grab component works in the university machines, because in my laptop it does not work.
I´ll try to Grap with the kinect (with openNI) to make an interface with an robot arm if its works, I sow some examples that you show to us and I think it is possible to control a Kuka by the grap component. We don´t have the KUKA yet but other university in Brazil is trying to by one, but they ask 6 time the KUKA´s price to install the machine...and for a public school it is to much money. I´ll try to find an alternative way for my students...
Thanx for the help
Art
…
GH viewport in the past, so I am not sure how things are accessible.
I am looking under File>Preferences>Display
Unsuccessful attempts to get the default display back have included:
Restarting computer, Uninstalling GH and Reinstalling. I backed up my custom components, and Special Folders to a jump drive... prior to uninstalling, but I don't think I am really uninstalling correctly... because when I load a fresh install of GH 9.0006, my old plugins and User components are already loaded up.
Has anyone else experienced this changed GH viewport?
Any advice is welcome.
I will post again if I figure it out.
Thanks.
btw, I am using Windows 7 (64bit), Rhino 4 SR9, Lastest GH 9.0006
…
ns about them.
It's a direction for Kangaroo I very much intend to continue developing - and I am still getting to grips with the possibilities and experimenting with how different optimization and fairing forces work in combination with one another, so I would value your input and experience.
For those interested in some background reading material -
[1] http://www.cs.caltech.edu/~mmeyer/Research/FairMesh/implicitFairing.pdf
[2] http://mesh.brown.edu/taubin/pdfs/taubin-eg00star.pdf
[3] http://www.pmp-book.org/download/slides/Smoothing.pdf
[4] http://graphics.stanford.edu/courses/cs468-05-fall/slides/daniel_willmore_flow_fall_05.pdf
[5] http://www.evolute.at/technology/scientific-publications.html
[6] http://www.math.tu-berlin.de/~bobenko/recentpapers.html
[7] http://spacesymmetrystructure.wordpress.com/2011/05/18/pseudo-physical-materials/
[8] http://www.evolute.at/technology/scientific-publications/34.html
[9] http://www.evolute.at/software/forum/topic.html?id=18
At the moment the Laplacian smoothing is uniformly weighted, which tends to even out the edge lengths as well as smoothing the form, which is sometimes desirable, and sometimes not. It also tends to significantly shrink meshes when the edges are not fixed.
I plan to try some of the other weighting possibilities, such as Fujiwara or cotangent weighting (see [1] and [3]), as well as other fairing approaches, such as Taubin smoothing [2], Willmore flow[4], and so on. This also has applications in the simulation of bending of thin shells.
Planar quad panels are often desirable, but I'm finding that planarization forces alone are sometimes unstable, or cause undesirable crumpling, so need to be combined with some sort of fairing/smoothing, but the different types have quite different effects, and the balance is sometimes tricky.
There's also the whole issue of meshes which are circular (I posted a demo of circularization on the examples page), or conical (this one still isn't working quite right yet), and their relationship with principal curvature grids and placement of irregular vertices, all of which is rather different when the whole form is up for change, rather than having a fixed target surface [7].
I'm also trying to get to grips with ways of making surfaces of planar hexagons, which need to become concave in regions of negative Gaussian curvature (see this discussion)
and I hope to release soon a component for calculating CP meshes, as described in [8], which I think could have many exciting construction implications.
While there are a number of well developed smoothing algorithms, their main area of application so far seems to be in processing and improving 3D scan data, so using them in design in this way is somewhat new territory. There can be structural, fabrication or performance reasons for certain types of smoothness, but of course the aesthetic reasons are also often important, and I think there are some interesting discussions to be had here about the aesthetics of smoothness.
Anyway, that's enough rambling from me, hopefully something there triggers some discussion - I'm really keen to hear about how all of you envision these tools might be used and developed.
…
You are able to write an expression for parameter components, but as of yet I haven't found a variable that doesn't throw an error. For an "Integer" parameter, for instance, neither "Int" nor "7" works. :)
2) I know Clusters is still probably on the list for a major overhaul. But in the meantime... is it possible to add edit functionality that will actually update the component in the original definition?
3) Along separate lines... can we please please have edit user object capabilities? I find that now and then I want to edit one of my user objects and then I am forced to recluster, re-assign icon, rewrite description, re-add to user objects, etc. Would love to be able to just edit.
4) I'm getting used to the middle mouse menu... but I still don't like it. I don't find that it adds any real functionality or time savings, in fact I am generally faster at grabbing the icon from the menu bar I think. I don't think it's about how difficult it is to teach to newbies, for me it's more about making something more complicated than it needs to be. Also, the modal buttons don't really want to be buried in a hidden menu. If your solver is locked, for instance, you should see that modal toggle at all times. We had a student who had inadvertently locked his solver and it took a few minutes of debugging to discover what had happened, since the button is hidden in the spider-menu.
5) Any progress on Remote Control Panel or a custom Control Panel Mode as in Max/MSP?
I'm sure there are other things, but those are the biggest ones off the top of my head.
Cheers!
Marc
…
oducts/207700-profile-connectors/25/1 ). Find one that can being fixed.
3. Design a custom aluminum beam (or contact Fipa) - BTW. Chinese do custom stuff for peanuts money.
4. Create the vault LBS first using the beams (the "skeleton").
5. Study Migua elastic inserts (critical) and Ceresit PE/S sealants. Get the gist of bridging gaps as a pro.
6. Use marine grade plywood only as a facet top cover (and some proper false ceiling). Plywood dimensions are usually 1.20 * 2.20 m. A 25 mm sheet could be OK for a small vault. DO NOT varnish the plywood. Epoxy glue linear aluminum L (10/10 mm) along the upper lips (in order to allow silicone to adhere properly (not shown in the image below) : failing to do that ... buy an umbrella).
7. Use trigonometry to calculate the variable beam placement per module.
Do this:
…
s the "Surface Populating" definition: I manage to populate my geometry over the surface, but after I bake it, I have to delete the boxes that define my components limits as well! Is there any way of populating and baking only the chosen component, without having to delete the boxes afterwards?
Secondly:
Basically: I am trying to cover a surface with two types of components [ an open one and a closed one] , which will be proliferated over my tubular surface according to the main sunlight direction.
1. I introduce the surface component.
2. I use "Divide Interval2" in order to have division into U and V.
3. i generate the target boxes [ "surfaceBox"] .
4. I use "Isotrim" ( same intervals) and "BRepArea" to find centroid of each area.
5. My "Curve" component introduces sun angle, with its "End Points".
6. I use "Vector 2Pt" to specify sun-light direction.
7. I want to measure the angle between sun-light and the surface normals, at the position of each component; after generating the centre points, I need the normals of each centre point to get the surface's points' UV, and "Evaluate" the srf at points.
8."Angle" and "Vector" components: I use them in order to evaluate the angle between the sun direction and the srf.
9. I convert this angle to degree by using a "Function" [ to see if the angle is bigger from the max.angle or not...]
10. Function "x,y" gives me boolean data.
11. Data become "Dispatch"ed...
12. Two "Morph" components , each one linked to one part of the "Dispatch" data, generate "closed" and "open" components over the srf.
The result should have been different types of components, based on the surface's curvature, diraction and sun-light direction...
I do not understand where the mistake is in this definition...
Thx in advance1
Spyros K.…
t to work. I was getting an error message on the OSMshapes components. I searched the forums and followed these steps:Close your Grasshopper and Rhino.2) Restart your PC3) When it boots up again, in your Start menu's search box type: "UAC". Click on it, and a new User Account Control Settings window will open. Set the bar on the left to "Never notify".4) Completely turn off your Antivirus.5) Check once again if your access control to the C:\MapWinGIS_installation_folder\gdal-data\osmconf.ini file is still set to the values you previously reported in this post.6) Right-click on "Rhino 5" icon and then choose: "Run as administrator".7) When Rhino boots up, run Grasshopper, and open the newest create_3dbuildings_trees_streets.gh file from here.This got the script to work and eliminated all of the error messages. The thing is... The omsconfig file's settings switch back after a some time passes, so I have to keep going back to change them. Also If I don't right click on rhino and choose "open as an adminstrator" the script won't work. I'll get those same error messages when I open Rhino normally. I'm also not super comfortable turning off my antivirus software during the time that I am working.Are there more permanant solutions that I can employ without going through these steps every time?
Thanks,
Robert…
st variety of papers (mostly related with LIDAR airborne sampled clouds) ... but ... hmm ... no code (other than some "abstract" algos that may (or may not) work). Reason? A very hot cake that one these days: from reverse engineering to DARPA founded future defense systems and up to cruse missiles pattern recognition algos.
The solution (obviously doable only via code) is the so called flat hard clustering ... were points are sampled into clusters based on the coPlanarity "rule". For large amounts recursive octTrees (an oriented box divided in 8 "partitions") subdivisions are used and then pts are processed in parallel (and then clusters are re-evaluated in order to "absorb" other clusters with same plane A,B,C,D vars etc etc).
See what's happening in a very carefully made test point collection:
3.7 ms and the "ideal" clustering (7 search loops VS the max 42M theoretical threshold):
Depending on the pts "preparation" ... a considerable more time/search loops is required ... and ... well ... also "valid" clusters (4 points and up) made:
So "ideally" speaking in your case:
1. Mesh faces center points (or alternatively: mesh vertices) are sampled into a pts collection .
2. Hard flat coPlanarity clustering is attempted yielding pts/planes in equivalent DataTrees.
3. Planar Breps are made with respect the planes (like the black things captured above) and sampled, say, into a breps List.
4. The method Brep[] solids = Brep.CreateSolid(breps); is used for attempting to create your desired "engulfing" brep. This method is very slow mind (other waaaay faster approaches also available).
…