ASS 2017 Conference in Hamburg, Germany. Join them to:
Learn how to use simulation-based optimization in Grasshopper
Learn about the differences between optimization algorithms in Grasshopper and when to use them
Learn how to assess the performance of optimization algorithms
Learn about differences between single and multi-objective optimization algorithms
Experiment with benchmark problems
Experiment with optimization problems from your own practice and research (bring your own optimization problems)
Experiment with optimization and visualization tools not yet released publicly
Thomas and Judyta are researchers in architectural design optimization. Thomas is the lead developer of the machine learning related optimization tool Opossum and Judyta a co-developer of the particle swarm optimization tool Silverye. Adrian is the founder and the owner of Architektura Parametryczna – the biggest Polish consultancy company in parametric design. (Find Thomas’ and Judyta’s work on ResearchGate here and here.) Registration closes on Tuesday, July 25, 2017.
Registration through the IASS website:
https://express2.converia.de/frontend/index.php?folder_id=943
Facebook event page:
https://tinyurl.com/ycv24m8g
…
ceros. Parametrización, panelización y análisis en Grasshopper, así como el proceso de manufactura digital para maquinaria de corte Láser y CNC.
UN solo pago anticipado $4,000.00
Pagos diferidos $4,500.00*
*reserva tu lugar con el 50%
Martes y Jueves de 7 a 10 PM
Del 15 de Mayo al 14 de junio
DURACION: 30 HORAS
SESIONES: 10 DE 3 HORAS
o info@dimensiontallerdigital.com
informes al 55 (50 16 0634) con Mayri Gallegos (o al cel. 55 28 85 24 73)
$4,000.00…
discussions during this period.
The major topics discussed for GH2 during this period will be:
Documentation/Help
GHA/Cluster/VB/C# App-Store
Localization (i.e. languages other than English)
Constraint Engine implementation
Improved VB/C#/Python development tools
Multi-threading the solver
Building a Mac version
If you feel something important was left out, please let us know here. Note that incremental improvements and bug-fixes are not worth discussion as we'll try and get around to them no matter what. Topics on this list have to fit the "Are we going to try and do X?" format.
--
David Rutten
david@mcneel.com
Tirol, Austria…
Added by David Rutten at 4:07am on October 11, 2013
r.
Jon has already done some very interesting stuff with regard decomposing matters using IFC schema (I'm not a strong admirer of any schema policy mind - for a variety of reasons).
Now the chaotic case:
1. This is deliberately fuzzy, faulty and chaotic in order to indicate the need (at least IMHO) for a next step with regard handling and visualizing (on a per individual data item basis, not on a per branch basis) data trees.
2. Why this Tree Manager future thing could boost GH up to an unseen level? Exploit the PDF attached - use Saved views and/or the Model Tree "decomposer" (file is greatly reduced in detail - only 1 out of 5 floors shown, no envelope stuff, stripped out of everything actually etc etc etc). Among a variety of things observe that there's transformations that are "selectively" applied whilst various components remain intact (in other words: invite existed "static" objects into the smart chaos) - this means that we need a far better control VS the series (of various type of data) that outline the solution of similar things.
3. What could/should do such a "visual" Tree Manager? Could he function within the existed "one Canvas for all things" environment? Do we need N "sub-canvas" (kinda the Views in any CAD app these days) to handle and visualize complex tree operations? Do we need control on a per data item basis? Do we need a re-mapper of a totally different kind? Do we need a Bake Manager? Do we need a Scenario (parameter combos stored etc) Manager?
Let's the debate begin
Best, Peter
…
imply lets you communicate with the chip in real time with other peripherals. In my case, I'm using the Xbox Kinect to read visual movements, assign a point ID to something like the left and right hand, translate its x-coordinate into a number, and have that number move a robotic arm servo. Sorry if this sounds like your upcoming robotic apocalypse.
My problem is that because my hand is always moving, it is continually reading the data in real time and crashing Arduino because it is continually processing the rotational distance (in degrees between 0-179). For example, if my hand was moving from 1 to 50 degrees, it's computing 1, 2, 3, 4, 5, 6, ..etc instead of 1 and 50 as two separate states.
Is there a way to have a component refresh its value in a certain interval? This would mean it could read my hand at different intervals and print a value at timed increments instead of doing it all in real time. A simple practice exercise would be to create a random component and have the component refresh so that every 1 second or so it would produce a different number. The app is essentially refreshing. I thought the Timer component worked, but I misunderstood what it's used for, and I don't think it does what I intend it to do.
I've attached some pictures to show what I'm attempting.
And a file to recreate the problem with a different instance.
Thanks so much for your help! …
question. Why are you using Win 8 or Win 10, instead of staying with Win7 ?The 102 page long EULA from Microsoft asks you to accept, prior to the install, should give any thinking person pause, and to think carefully before he or she is accepts the consequences of installing Win 8 or Win 10.No IT profession would allow any company to install Windows 8 or 10 on their companies computer networks. Imagine for a moment your Doctor installed Windows 10, and now all his daily clients details are shared with Microsoft. Or imagine for a moment your Lawyer installed Windows 10, and now all his daily clients details are shared with Microsoft.Win 8 or 10 is an open apps shared OS that lacks any sense of network security.... stay with Win 7!…
really nice because kangaroo give us kick feedback about how the structure could work; with this data in our hand modifications and redesign was really straight forward.
For final steps because the nature of the project (we design 2 big supports attached to the structure and floor with steel wires) we needed to use multi-step calculus.
My experience in this workflow is that Kangaroo in impressively good and quick for first design stages but when things comes harder, you always will need a good FEA app.
You can see that I implemented a simple interface to check compression-traction bar state.
Best.…
els of freedom in the actual node are different as well - totally different "linkage" design.
Dealing with the actual node combo requires far more complex plane arrangements since (a) the connecting ring lays in the planes already calculated BUT (b) the adapter primary axis must align with the dihedral for a given edge: the angle of the neighbor faces. Meaning in other words: connectivity [edge-to-face, point-to-point, etc etc] trees (for internal use only).
So the only thing that this test node (2 layers used) does correctly is to lay (with regard the ring primary axis) at the right place (plane, that is): linkages are NOT moving at all.
But in general is a rather useful indication upon how to deal with component based designs (where a void instance has the ring as child that has N adapter instances as childs etc etc). Place the test node [NOT bake anything] and export [STEP 214] a test R file to some CAD/MCAD app that works that way (CATIA, NX, Microstation etc etc).
best, Peter …
the contours they show are all generated from 3 arc second SRTM files, even if in the United States where higher resolution data is available from 1 arc second. Also the contours are likely 2D in their map since. Granted, their contours may look nicer, but I think it's just because they're processing the HGT file with the GDAL Contour app to generate a Shapefile.
That being said, starting last year the USGS started releasing 1 arc second SRTM data for the rest of the world outside of the US. It's not the friendliest website, but I've been accessing it from here (be warned it will probably take a few minutes to load). You could download the appropriate tile and use the SRTM Topo component and get better looking resolution than you've seen with the 3 arc second data.
There's also the possibility you could do the same thing OSM is doing, but with the higher resolution data. Download the GDAL library and run the gdal_contour.exe file on the 1 arc second HGT file and you'll get a shapefile with all the contours. Elk doesn't directly work with shape files, but you could use Meerkat GIS to import the shapefile. I've only done a few quick tests, but I've had trouble with the scaling with this method, both using Meerkat and using Autodesk's Map3d to read the shapefile, so perhaps it's my inexperience with gdal_contour. It also looks like it's making the 1°x1° tile's square instead of scaling the X values as it goes farther from the equator. Nothing that's insurmountable, but still you should watch out for it.
Regards,
-Tim
…