I am not knowledgeable about google maps nor google maps api, but from what I read the two components will definitely show a bit different results due to different topography sources.If it is judging by this 2010 article, your Terrain Generator component offers much higher precisions for USA. Precision goes up to a couple of meters, which is amazing!!On the global scale it offers either SRTM 1 or 3 arc-second data or 30 arc-second GLOBE data. Again this is from the mentioned article, I couldn't find this information by searching the Google Maps website.Terrain Generator 2 component always uses SRTM 1 arc-second data from opentopography.org, and it is limited to 60 degrees north and does not have data for Antarctica. It does not come with satellite image either which is another very convenient feature that you have!I couldn't find information about the allowed radius provided by the Google maps api free account. I limited the "radius_" input to 100 000 meters, even though opentopography.org provides more than that (I successfully downloaded 300 000, but Rhino 5 was not able to create a topography on my PC from such a large amount of data).Even though I couldn't compare the results from two components, by looking at your upper example_LB_terrain_generator.gh definition: set the "I" input of "Surface from points" component to True. In this way the surface will be interpolated through points, which is what we want.
Again thank you for the permission, and I look forward seeing those high precision topography that Google maps offers!!…
lues are of any use from a display perspective as some IES files tend to have upwards of a 1000 numbers. That is why the candela values are visualized in the Rhino viewport.
2. Did you check out the (relatively) new Honeybee_IES Project component? It does produce a Bill of Quantity and also allows an export to Excel. I have explained this here: http://www.grasshopper3d.com/xn/detail/2985220:Comment:1474434
3. Eulumdat to IES is an easy fix. I wasn't aware that anybody had tested this using Eulumdat files. I will add this feature when I update the code next time.
4. Can you describe this simulation? The time taken by the simulation itself should not be that long because Radiance ( the calculation engine) has optimization algorithms to tackle multiple sources. My comment about multiple sources had more to do with Rhino than HB itself.
5. What do you mean by material design ? As in textures for surfaces?
Now, with regards to future work, we don't have a road-map of sorts at present as personally I am not quite sure about what might be useful to people who work exclusively with electric lighting. Most of the (vocal) users of Honeybee tend to be interested in Daylighting and that is where our development efforts have centered over the past year. You can read more about it here and here.
If there is some sort of consensus-based opinion from lighting designers on what would be useful we will look into adding new features.…
g a single design and you wish the others to be updated to that view also? There's a trade off here as we would need an extra button on the viewport (that we're trying to keep uncluttered as best we can)... I think it wouldn't be too bad. I'll put it on the enhancement list on git.
2) One of the best things about meshes in wpf is the simplicity... one of the worst things is lack of vertex shading which is a real pain. Getting into OpenGL, DirectX, etc. is not going to happen with the spare time I currently have, but what you suggest is quite a nice compromise (i.e. one colour per mesh). I'm still hoping I can figure a method to get vertex shading with wpf (stackoverflow shows others with similar struggles!), although it looks very tricky. We are looking into it!
3) It is, and yes this is a big problem when the mapping between genotype and phenotype is indirect (for example, the gh definition contains a random component or something). You can compare on the phenotype as you suggest, but this takes computational effort, such as some form of shape analysis. One hope is to compare genotype and phenotype 'solution' spaces (and thus give a measure of directness). On the TODO list!
4) Hmmm, not thought of that one. Good idea, a kind of import design into population. Thanks! That could work nicely.
5) Current idea is to maybe save a population history file, which would as you suggest act like a state manager of sorts. The data structure is quite complex in order to future proof the history approach, but we think we have a nice way of doing it and will be in the next release.
Thanks again for your feedback Chris, its much appreciated.
Best wishes,
John.
PS: What is that mesh shape you have there? Curious.
…
cooling energy" variable tangled with other output variables in one line in the idf file:
1. current code of line 2314 andd 2315:
2. current output variable section in the idf file:
3. revised code with the "\n" new line symbol added:
4. correct IDF file with the cooling loads outpu variable in a separate line:
5. cooling loads can now be correctly calculated and read:
Please kindly verify if this is the source of issue, and if this is the case, I'd appreciate if the current runEP component can be updated.
Thanks.
- Ji.
…
face:
3. However, the readEPSrfResult component cannot recognize this variable:
4. Nevertheless, for unknown strange reason, I'm unable to reproduce the above warning for this test file later, and it seems that this variable can be read by the readEPSrfResult component, for now....
5. I got the same warning in other GH file I'm testing which included the surface irradiance as output variable. So, I'm not sure why the warning is not consistent across different files ...
Appreciate if you can kindly advise.
…
way everything is consolidated and people can share their thoughts.
1. Cluster rollover tips
Id like to be able to create rollover help text for each cluster input. This could be a right click thing once the cluster is created or something specified before creating the cluster (a string input for the cluster input arrows?)
2. Disconnect all outgoing
I'd like to be able to right click on an output of any component and disconnect all wires coming out of it.
3. Disconnect all selected
It would be cool if you could disconnect all incoming or outgoing wires from all currently selected components (instead of just one at a time).
4. List item dynamic slider
There has been a lot of discussion about dynamic range sliders and the issues that they would cause. Id like one specifically for list item selection. This would be an integer slider that would have a range of 0 to the list length-1. If the range remaps and the previous value is no longer available, I think it's best to have the current value stay as close to the previous value as possible.
5. Cluster slider/toggle inputs
I think it could be valuable to cluster a series of variable inputs (like sliders or toggles) to make a sort of options cluster. In this case you could just have a list of sliders and toggles each connected directly to a cluster output arrow, select all and create your cluster. This would be great with the value list component as well.
6. Have a component that could output the x and y location of actual components on the canvas relative to the top left corner... Not sure exactly what you could do with this but I think someone could do something interesting with it.
7. 3d MD slider. I see the option is greyed out and don't see a way to activate it... Still under development? Seems like it could be just like the color picker. Would be cool.
That's all I can think of right now. I'm sure there will be more to come in the future.
Feel free to comment.
-Brian…
Added by Brian Harms at 2:22am on December 15, 2011
(http://www.food4rhino.com/app/quelea-agent-based-design-grasshopper) take like 40 seconds when the toggle activates to go from one end of the ramp to another.
With proximity 3d i'm analyzing each instance the agents are closer than x units. In picture 3 we can see that in 212 instances the agent are closer than those x units.
Finally all the genes that controll the ramps are connected to the G of octopus component and one of the conflicting objectives connected to the O of octopus component is the number of instance quelea agents get close.
So the thing I need is to iterate the ramps controling the genes with octopus but activating the boolean toggle (quelea run) each time the ramps are modified so the agents take 40 seconds to perambulate the environment, analyze the instance they get close and let octopus iterate again searching for a optimized environment.
…
stand everything so far but I will nevertheless try to give some feedback and then extend this list once oi gained more knowledge about it.
1) It would be nice if you could set and save a view vector for all models at the same time. that would make the comparison a lot easier because every model has different interesting views
2) Color could be helpful i think. Would it be possible to read the mesh vertex color values? If that not straight forward maybe the component could have another input which takes a list of colors for each mesh you input in the geometry input.
3) Is the closeness of two outcomes only computed by the closeness of the genes? Sometimes you have very ruff parameter spaces where a little shift in the genes can make quite big changes in the outcome. Would it be possible to compute closeness or similarity of two outcomes based on the outcome itself? For example compare the resulting meshes to each other?
4) It would be also great if you could replace a certain outcome with a solution that you manually generated by altering the sliders. That would be also a way to influence the direction.
5) I see that you are still working on the history. It would be great if one could use biomorpher as well to store you favorite versions of a definition. Something like a more advanced version of the state manager where you can also see the states and crossbreed them easily.
Best, Chris
…
y working on is a tensegrity structure that uses cables and a tensile fabric to apply traction. The basic cell of the structure is a sail with two parallel rods.
The easy one was the fabric anchored to the extremes of the rod. I got great results with the tensegrity model , very similar to physical models that I was working on.
But then I tried the same thing with the fabric anchored all along the rods, but it proved to be hard (read all the "rod discussion"). I tried the bending force, but was too unstable. The best model I got was by applying different stiffness to the mesh, specifically, to the lines that coincide with the anchors.
It's by no means the solution that I had in mind, but the next days I'll be testing it with the structure. I came across with the next thing to my ideal solution, Daniel's boat (https://vimeo.com/30128894), but I couldn't replicate it. Anyone has some idea of a different, more rigid solution? Even in K2, which I really don't understand yet, but any clue would be helpful.
Aside of that, I was also having trouble applying real values of stiffness. The third archive has the same definition that the first, but with real stiff values (the rods are wood, k=10^7 N/m, cables are nylon k=2x10^5 N/m). I adjusted the timestep and the subiterations, but it doesn't work as stable and smooth as the whatever-stiffness-sail. I don't know if isn't correctly calibrated, or my computer its too old (it pretty old and slow) or simply isn't a good definition.
If anyone has any idea it would be very much appreciated!
Antonio…
and 3d rapid prototyping using state of the art material simulation and optimisation. Participants will be guided through methods of advanced structural analysis and evolutionary algorithms implemented in Grasshopper, Karamba and Octopus in a 5 day workshop taught by Robert Vierlinger and Matthew Tam within the premises of the Academy of Fine Arts & Design in Bratislava, Slovakia. The workshop will cover the basics of setting up a karamba definition and more advanced form finding techniques with beams and shells through to preparing files for 3d printing and 2d documentation. For the Grasshopper newcomers there is a preparatory crash course on 20 July 2015 taught by Ján Pernecký. The workshop will be held entirely in English. VENUE Academy of Fine Arts and Design in Bratislava: VŠVU / AFAD, Hviezdoslavovo námestie 18, Bratislava, Slovakia ROOM 135 PRICING Early bird Student (until Jun 30, 2015) €320 Early bird Professional (until Jun 30, 2015) €380 Regular Student (from Jun 30, 2015) €400 Regular Professional (from Jun 30, 2015) €475 The fee covers only the tuition. Travel expenses, accommodation and food is to be covered by the participants. SCHEDULE Day 1 Lecture - Karamba in Projects from Competition to Construction Introduction to karamba - Setting up a basic karamba model Shells & Beams - Understanding the impact of load on geometries. Beams - Cross Section Optimization, Load Path Emergence Day 2 Extraction and Visualization of data from Karamba Complex Geometry - Processing of Free Forms for Karamba Force Flow - Understanding and Visualizing results on shells 3d Printing - Preparing geometries for rapid prototyping Day 3 Lecture - Form Finding in Karamba Isler Shells - Hanging Forms with karamba Shells - Shape Optimisation with Galapagos Trusses - Topology Optimization with Galapagos Columns - Positioning with Galapagos Multiobjective optimisation strategies with Octopus Day 4 Frequency Analysis & Non-Linear Analysis with Karamba Extraction and Visualization Part 2 BIS - Building Information Systems with karamba Day 5 Participant’s Examples and Topics Reviewing 3d Print Studies Large Complex Models Reviewing learn techniques and strategies Concluding lecture - public PARTNERS rese arch Academy of fine arts and design…