ole new realm?
This Parametric Design Workshop will provide you with the necessary knowledge and ability to use Grasshopper, a free visual programming plugin in Rhinoceros. The workshop will also include a hands on parametric project.
If you already know Grasshopper and would like to uplift your parametric knowledge, then you can choose option 2.
Option 1: General Workshop for Beginners - 16 hours: Start 14.07.2018
Option 2: Intensive Workshop for Intermediates - 8 hours: Start 21.07.2018
Kindly reserve your Tickets here:https://billetto.eu/en/e/parametric-design-workshop-rhino-grasshopper-fablab-berlin-tickets-293212…
hole new realm?
This Parametric Design Workshop will provide you with the necessary knowledge and ability to use Grasshopper, a free visual programming plugin in Rhinoceros. The workshop will also include a hands on parametric project.
If you already know Grasshopper and would like to uplift your parametric knowledge, then you can choose option 2.
Option 1: General Workshop for Beginners - 16 hours: Start 15.09.2018
Option 2: Intensive Workshop for Intermediates - 8 hours: Start 22.09.2018
Kindly reserve your Tickets here:
https://billetto.eu/en/e/parametric-design-workshop-rhino-grasshopper-fablab-berlin-tickets-300416…
on and off with scripting a 'marching tetrahedra' approach for a while, but never got around to finishing it. I can't see myself having the time to finish this off myself at any point over the next month, but maybe some sort of open collaboration is possible. I don't know exactly how this might work, but it could be interesting to try. Anyway, I'll post some of my ideas on this here in case anyone is interested in taking it further.
The best intro to this I know is Paul Bourke's page
My personal preference is for marching tetrahedra over marching cubes because it avoids an awkward ambiguous case and just seems generally much simpler with only 8 possibilities for the way the surface can pass through 1 cell instead of 256.
Using midpoints of edges gives a very chunky looking result, whereas linear interpolation should be good enough for most purposes and is pretty straightforward to do.
For anything other than the coarsest mesh, I think checking for intersections in every single sub-cube would be really slow, so I guess one should use an octree approach to narrow it down.
Anyway, just my 2c…
tant (if you don't change them manually).
First thing you should clarify is, what features of the sound you want to visualize/use. Like Level(Volume), Frequency content, whatever... The raw input data as it comes form the soundcard is giant blob of mostly noise. To smoothen it, usually means filtering out high frequency compnents. Typically this also results in slower samplerates.
GH isn't meant to be a real-time audio processor. It's single threaded, so GH uses only one of my availabe 8 cores. Most of GH's data management would be avoided in an audio environment. Moving data from one component to the next will take some time. This is why I suggested to do all the data manipulation within a single script component. Like Andy already said, for one second of mono sound, the capture component will return 22k samples(points). (Which already is half the data rate of CD Audio.) So basically everything you do with sound in GH is likely to freeze your PC.
On my PC, making a point for each sample in 1 second of captured sound and interpolating a curve though them already takes about 0.6 seconds. No smoothing, no nothing... no chance for real time.…
haven't tried too hard to break this, and I'm just getting into Python coding. Please let me know how and when it fails. In the off-chance it does something cool for you, please let me know.
…
. Sometimes the result has less "Number of Parts" than what I choose because in the end result I get some of the items as an invalid mesh. For example here I wanted 10 parts but I get only 8 and the rest are invalid.
3. How can connect the results to Octopus and Colibri so it iterate automatically? I want to do optimization through ladybug tools.
Thank you,
…
you still have left, what matters is how much memory Rhino is using compared to how much Windows is prepared to give it. On 32-bit systems this is usually 2, sometimes 3 Gigs. On 64-bit systems it's such a high limit that it's unlikely you've reached the limit.
You're low on or out of specially allocated memory/handles. Certain processes such as GDI drawing or winforms UI elements require a handle per instance. Every window, every label, every button, every slider, every bitmap... each one has a unique handle associated with it. Depending on the windows version, you either get a few, some, a bunch or lots of these handles to play with. When you start running out, usually the first sign is that the UI goes all wonky. Text disappears, fonts suddenly look terrible, parts of windows go missing. When all the GDI handles that are allowed have been claimed, the application will crash. The same may be true for OpenGL or DirectX handles, I'm not an expert on those.
There's an arithmetic error causing an overflow error. Sometimes these are handled gracefully and you get a proper crash or error message, sometimes they cause software to start accessing the wrong memory.
It's just some random crash that decides to manifest as an out-of-memory crash. This happens a lot and it makes these crashes very difficult to track down.
Since your images start going black before the crash, I'm tempted to think we're dealing with a #2 crash here. Maybe all these images we're saving out are hogging GDI handles and choking the system. If the handles or GDI objects assigned to Rhino keep going up and up as you write out these images, that'll be good supporting evidence. You can use the Windows 8 Task Manager to keep an eye on these values, or if you're running an older version of Windows I recommend installing Sysinternal Process Explorer in lieu of the Task Manager.
…
Added by David Rutten at 1:20pm on February 28, 2015
ruses could follow. Then cones are made and some other things.You can move the cones around via the equivalent slider. If the cones "touch" then ... well .. test it and see what's happening,
2. Interactive capability is not present: assume that you have 666 paths/cones > by what means you think that you could control what's happening? By adding 666 sliders? (not in a million years).
3. Rhino is amusing with regard the solid union Method. Depending on Karma you can get this:
or that :
4. Leaving aside N3 .. if the real-time response goes AWOL with just 8 cones what would be the situation if you add 666 cones? This is the reason for using K to solve this ... obviously with "some" compromises yielding "vault" stuff like this:
or like that (an Alien billiard (C)(Tm)(US patent pending) for planet Zorg):
Moral: stick to the Soap_opera approach.…
indexsequential philosophy. This stands for a sequential access to data organized in logical records addressed by a key formed by two Integers.
CDBASE may be seen by the programmer as an unlimited number of sequential streams organized in the form of a linked list. Physically CDBASE is formed by a direct access diskfile with fixed record length and a memory buffer to enhance IO-Operations. For parallel access an enhanced version using pvm is available."
"Locking is done via special entries in the database and the possibilities provided by the operating system (lockd / SHARE etc.) The lowest level ensures that writing of directory entries or requesting dataspace is only possible by a single process at the same time.
The next level locks a complete key. If you write to a key you will lock implicitly all records within the key. Other processes may lock other keys at the same time. You may lock a key explicitly by a call, then have to remove the lock explicitly by an other call. The implicit locks created by a writing process is implicitly released by a read from the same process."
As for the initiation, a function returns current status of the database: int sof_cdb_status ( int Index )
the current status of the file with Index is returned
Index Index of DB Returnvalue Stat Bitpattern CD_STAT_AKTIV (1) CDBase is active CD_STAT_OPEN (2) Index is connected to file CD_STAT_SWAP (4) File has ByteSwap CD_STAT_READ (8) File has been read CD_STAT_WRITE (16) File has been written CD_STAT_LOCK (32) File has active locks CD_STAT_PVM (64) File is opened via pvm server
I hope it answers your questions, I am very uncertain in this topic.…
ky.exe did not accept -p parameter and made empty sky.cal file.
----
Edit: solved run problem, Bee did not download OpenStudioMasterTemplate.idf
Get it here: https://github.com/mostaphaRoudsari/Honeybee/issues/119
Now get empty HDR:
C:\ladybug\prox\imageBasedSimulation>rpict -i -t 10 -vtv -vp 245.129 -226.458 20 0.405 -vd -0.549 0.656 -0.518 -vu -0.332 0.397 0.855 -vh 42.862 -vv 26.991 -v l 0 -vs 0 -vl 0 -x 800 -y 600 -af prox_RAD_Perspective.amb -ps 8 -pt 0.15 -pj 0.6 -dj 0 -ds 0.5 -dt 0.5 -dc 0.25 -dr 0 -dp 64 -st 0.85 -ab 2 -ad 1024 -as 175 -ar 150 -aa 0.200 -lr 4 -lw 0.050 -av 0 0 0 prox_RAD.oct 1>prox_RAD_Perspectiv e.unf rpict: 0 rays, 0.00% after 0.0000 hours rpict: skybright`c__ladybug_skylib_cumulativeSkies_SINGAPORE_SGP_SINGAPORE_SGP_1 : undefined variable rpict: 1020 rays, 4.91% after 0.0000 hours
----
Hi friends,
trying to get a cumulative sky image metric to run and encountered an issue with the image-based metrics component. It throws:
Runtime error (KeyNotFoundException): honeybee_materialLib Traceback: line 768, in main, "<string>" line 1442, in script
I guess this is some sort of setup issue on my end, or I messed up the definition? Any help appreciated.
Thanks,
Max
…