ias profesionales.Se trata de que cuento con una base de datos de 10 mallas que describen pies diferentes y únicos, aunque también las puedo presentar en nube de puntos, el objetivo es obtener un promedio de esas 10 mallas, es decir una malla única que me representa la morfología de la base de datos, promediando las formas de estas mallas que describen 10 pies humanos mediante algún metodo y el resultado sea solo una malla que sea el promedio de todas, no se si por medio de el plug-in grasshopper sea posible.Joredu_455@hotmail.com477 117 89 81…
ils.ExceptionUtils.RemoveData(System.Exception, System.Object)'.
Traceback: line 67, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\types.py" line 6, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\abc.py" line 11, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\_abcoll.py" line 83, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\UserDict.py" line 398, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\os.py" line 9, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\linecache.py" line 6, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\warnings.py" line 43, in <module>, "C:\Program Files\Rhino WIP\Plug-ins\IronPython\Lib\random.py" line 5, in script…
he Cordyceps. Maybe some of you find this helpful/useful.
So basically, the Cordyceps is a physical module with 4 knobs and 1 slider. The knobs give an output between 1 and 1000, while the physical slider outputs 0-359. And of course, for this physical module I wrote a plugin to communicate with it. The knobs are intended to be the variables that modifies the design, while the physical slider is intended to be connected to the camera component.
Here I will put up "the recipe" for all to make their own module. You will be able to download the plugin as well.
Please send me a message if you want the 3D-files for the knobs, the box and slider knob. They've been made to directly 3D-print.
Plugin:
https://github.com/zakadjeb/Cordyceps/blob/master/Cordyceps/Cordyce...
Code for Arduino IDE:
https://github.com/zakadjeb/Cordyceps/blob/master/Arduino/_Arduino_...
What you need:
1x - Arduino (Leonardo, UNO or whatever)
4x - Potentiometers
1x - Sliding potentiometer
1x - Breadboard
Bundle of jump wires.
1. So, a potentiometer is a variable resistor, which is basically a component that changes the resistance between the voltage and the ground.
If A is supplied with 5V then B must be connected to Ground. The W will give "read" the resistance, and thus should be placed in Analog input (A0-A5) on the Arduino. The slider potentiometer works the same way.
2. Now connect the 4 pots to each their Analog input. The slider is supposed to be in A4. So to make sure:
A0: Knob1
A1: Knob2
A2: Knob3
A3: Knob4
A4: Slider
3. Now it's time to connect the voltage! Using the breadboard, the voltage can be sent through 1 line, the Ground as well. It should be quite easy to connect them.
4. Now, download the Arduino IDE and copy-paste the code I supplied above. In the IDE, you need to let it know which Arduino you're working with, and which port is should send the script.
5. Almost there. Download the plugin. Open the port you're using through the plugin. Set Start to True and the Cordyceps should be within you.
This recipe will be updated!
Let me know if there are any issues.
// Zakaria Djebbara…
he Cordyceps. Maybe some of you find this helpful/useful.
So basically, the Cordyceps is a physical module with 4 knobs and 1 slider. The knobs give an output between 1 and 1000, while the physical slider outputs 0-359. And of course, for this physical module I wrote a plugin to communicate with it. The knobs are intended to be the variables that modifies the design, while the physical slider is intended to be connected to the camera component.
Here I will put up "the recipe" for all to make their own module. You will be able to download the plugin as well.
Please send me a message if you want the 3D-files for the knobs, the box and slider knob. They've been made to directly 3D-print.
Plugin:
https://github.com/zakadjeb/Cordyceps/blob/master/Cordyceps/Cordyce...
Code for Arduino IDE:
https://github.com/zakadjeb/Cordyceps/blob/master/Arduino/_Arduino_...
What you need:
1x - Arduino (Leonardo, UNO or whatever)
4x - Potentiometers
1x - Sliding potentiometer
1x - Breadboard
Bundle of jump wires.
1. So, a potentiometer is a variable resistor, which is basically a component that changes the resistance between the voltage and the ground.
If A is supplied with 5V then B must be connected to Ground. The W will give "read" the resistance, and thus should be placed in Analog input (A0-A5) on the Arduino. The slider potentiometer works the same way.
2. Now connect the 4 pots to each their Analog input. The slider is supposed to be in A4. So to make sure:
A0: Knob1
A1: Knob2
A2: Knob3
A3: Knob4
A4: Slider
3. Now it's time to connect the voltage! Using the breadboard, the voltage can be sent through 1 line, the Ground as well. It should be quite easy to connect them.
4. Now, download the Arduino IDE and copy-paste the code I supplied above. In the IDE, you need to let it know which Arduino you're working with, and which port is should send the script.
5. Almost there. Download the plugin. Open the port you're using through the plugin. Set Start to True and the Cordyceps should be within you.
This recipe will be updated!
Let me know if there are any issues.
// Zakaria Djebbara…
didn't look at it that closely), other than to say tree data structure is helping you and hurting you.
What I did to fix the file was work backwards. Looking at only the left panel you are trying to create 11 total planar surfaces from edge curves (8 curves per surface). That means you should be generating 11 of each type of curve so that you will have 88 total curves when you attempt to join them.
Tree data was in some cases giving you 121 of each type of curve (lists matching with tree structure...) so I worked backwards from your individual curves to flatten the inputs until ending up with only 11 (the expected number) of each type of curve.
…
use for some typical reasons why solar access can be important:
Solar Access for Passive Solar Heating - The conditional statement should request sun vectors for any hours below the balance point of the building (the temperature at which the building starts requiring additional heating). For residences, this can be as high as 18C and for commercial/retail buildings with high internal heat gains, this can be as low as 10C. 16C is around what you might find for some residences with better insulation and is probably the reason why that is chosen in the file.
Solar Access for Outdoor Thermal Comfort - The conditional statement should request sun vectors for any hours below the lower limit of outdoor comfort (UTCI uses 9C for this lower limit).
Solar Access for Health of Plants/Trees in a Park/Garden - This is a bit of the opposite of the other metrics since you want hours of the warmer season. In this case, I usually use solar radiation as the annualHourlyData with the conditional statement and I request hours that are above a certain radiation level (where the plants are benefiting the most). I then use an analysisPeriod to get rid of any months of the year when the trees don't have leaves on them.
Hope this helps,
-Chris…
d the number slider is going to take these values:
84
84.12903284.25806584.38709784.51612984.64516184.77419484.90322685.03225885.1612985.29032385.41935585.54838785.67741985.80645285.93548486.06451686.19354886.32258186.45161386.58064586.70967786.8387186.96774287.09677487.22580687.35483987.48387187.61290387.74193587.87096888.088.12903288.25806588.38709788.51612988.64516188.77419488.90322689.03225889.1612989.29032389.41935589.54838789.67741989.80645289.93548490.06451690.19354890.32258190.45161390.58064590.70967790.8387190.96774291.09677491.22580691.35483991.48387191.61290391.74193591.87096892.092.12903292.25806592.38709792.51612992.64516192.77419492.90322693.03225893.1612993.29032393.41935593.54838793.67741993.80645293.93548494.06451694.19354894.32258194.45161394.58064594.70967794.8387194.96774295.09677495.22580695.35483995.48387195.61290395.74193595.87096896.096.12903296.25806596.38709796.51612996.64516196.77419496.90322697.03225897.1612997.29032397.41935597.54838797.67741997.80645297.93548498.06451698.19354898.32258198.45161398.58064598.70967798.8387198.96774299.09677499.22580699.35483999.48387199.61290399.74193599.870968100.0
divided by 100, but that's not the big deal ... The big deal is:
at every frame I need to have a different colour for a specific object... How to do this?!…
i to usb cable and was able to connect Grasshopper with my digital piano realtime through a simple VB.NET component, no need for any other intermediate software. I used this library http://midiservices.codeplex.com/ (but there are several others).
The VB component outputs a list of 88 values that correspond to the intensity of each piano key at the current time (if the pedal is on and a key is depressed the value is halved, if the pedal is off the value is 0).
The rest of the definition is just to do something with this data. It uses these values to display each note as different floating colors that move with the wind (using Kangaroo). The strength of the wind changes as the music dynamics change.
If there are several devices connected you might have to change the line device.Open(0) to another number.
Definition: piano_midi.gh
…
an be given as 88° and 95°. All three angles must sum up to 180, and we're already 3 degrees over balance. Or maybe the user specifies three edge-lengths: 21, 12 and 8. 21 is bigger than 12+8, so even if the triangle was stretched flat, the two short edges cannot reach the ends of the long edge. The above is easy to test for and I add errors to the component if an invalid triangle is provided. However there are also many angle+edge length combinations which result in invalid triangles.
I could of course test for these as well, but the problem is now tolerance. What if the user specifies a redundant angle of 54.7°, whereas the mathematics tell us that the actual angle is 54.7002°. Is that an error? If so, is the angle wrong or is perhaps one of the edges wrong? Or has the triangle simply been over-constrained? Is there a mathematically robust way of dealing with this? And if so, would that also be the most user-friendly way of dealing with it?…
Added by David Rutten at 2:23pm on August 23, 2014