s: the nut's width is divided in equal segments resulting in queal spacing from string center to string center but the spacing bewteen the top strings is smaller than between the lower strings. It's not very comfortable to play, on bass guitar it's really awkward
2. equal spaces: the nut is divided so that the spacing between the outer edges of all 6 strings is the same. Since eachstring has a different width (gauge) this requires some calculations but is much more comfortable to play
i have attached my pathetic simple attempt at creating this. It works for 'equal centres' but i can't really figure out several things:
A. how to use a table or list of values as an input for the string gauges. Ideally i would like to select from different 'sets' of strings so that i can create different nut templates for different thickness strings easily. So ideally i would like to select a preset like: 'light', 'ultra light', 'medium', 'light top heavy bottom' and then it would adjust everything according to the different string gauges defined in those sets/lists.
B. how to use metric units for the spacing of the top and bottom strings to the fretboard/neck edge. I have tried to do it by eyeballing it with the 'point on curve' element which i'm pretty sure is not the way to do it properly. I want to be able to simply input this in mm, so for example a 4mm distance from the strings to the fretboard edge.
C. how to figure out the 'equal spaces' and divide the bridge and nut curves accordingly so that the distance from the outside edge of the top and bottom strings to the fretboard is equal, and the spacing between the strings outer edges (not the centres) is equal.
would really appreciate any help or tips to point me into the right direction :)
…
ject that involves the design of an app that allows people to interact with a 3d model through some sliders.)
Ok, imagine you have a symmetrical shape like the one i drew:
What I intend to do is to have different 3 sliders that allow me to adjust the 3 distances (x, y, z) independently of one another.
-1st question: my idea is to draw the curves in rhino, then use the "divide" and "list item" components to extract the points I need. Is it correct? :D
-2nd question: the "move away from" component can be used in a symmetric way?
(I try to be more specific: with only one slider, can I move both points 5 and 6 simultaneously about the axis i drew?)
-3rd question: is there a way that allows the curves to reshape themselves as I move the slider related to the distance between a couple of points?
I hope I have been clear ;) I would greatly appreciate any help you can give me!
Matteo…
3 arms and 6 legs (PS: Remember: in real-life our fee is proportional to the budget > thus > like Godzilla > the bigger the better).
In the mean time (auto detection of struts < min Allowed == true) get the gist of the whole "torque" issue, the other gist not to mention the other-other gist.
Of course you can opt for NOT making the cables (green) that stabilize the "extension" part of a given tensegrity strut ... yielding the Mother in Law syndrome (fat and ugly):
But ... hmm ... well ... are you really the chosen one? Here's your chance for the ticket to Paradise (full Lord's assistance, that is). Identify this engine, name the designer and the related immortal racer (when men were men).
Moral: Heaven can wait. …
rring to the above image)
Area
effective
effective
Second
Elastic
Elastic
Plastic
Radius
Second
Elastic
Plastic
Radius
of
Vy shear
Vz shear
Moment
Modulus
Modulus
Modulus
of
Moment
Modulus
Modulus
of
Section
Area
Area
of Area
upper
lower
Gyration
of Area
Gyration
(strong axis)
(strong axis)
(strong axis)
(strong axis)
(strong axis)
(weak axis)
(weak axis)
(weak axis)
(weak axis)
A
Ay
Az
Iy
Wy
Wy
Wply
i_y
Iz
Wz
Wplz
i_z
cm2
cm2
cm2
cm4
cm3
cm3
cm3
cm
cm4
cm3
cm3
cm
I have a very similar table which I could import to the Karamba table. But I have i_v or i_u values as well as radius of inertia for instance.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
dimensjon
Masse
Areal
akse
Ix
Wpx
ix
akse
Iy
Wpy
iy
akse
Iv
Wpv
iv
Width
Thickness
Radius R
[kg/m]
[mm2]
[mm4]
[mm3]
[mm]
[mm4]
[mm3]
[mm]
[mm4]
[mm3]
[mm]
[mm]
[mm]
[mm]
L 20x3
0.89
113
x-x
4,000
290
5.9
y-y
4,000
290
5.9
v-v
1,700
200
3.9
20
3
4
L 20x4
1.15
146
x-x
5,000
360
5.8
y-y
5,000
360
5.8
v-v
2,200
240
3.8
20
4
4
L 25x3
1.12
143
x-x
8,200
460
7.6
y-y
8,200
460
7.6
v-v
3,400
330
4.9
25
3
4
L 25x4
1.46
186
x-x
10,300
590
7.4
y-y
10,300
590
7.4
v-v
4,300
400
4.8
25
4
4
L 30x3
1.37
175
x-x
14,600
680
9.1
y-y
14,600
680
9.1
v-v
6,100
510
5.9
30
3
5
L 30x4
1.79
228
x-x
18,400
870
9.0
y-y
18,400
870
9.0
v-v
7,700
620
5.8
30
4
5
L 36x3
1.66
211
x-x
25,800
990
11.1
y-y
25,800
990
11.1
v-v
10,700
760
7.1
36
3
5
L 36x4
2.16
276
x-x
32,900
1,280
10.9
y-y
32,900
1,280
10.9
v-v
13,700
930
7.0
36
4
5
L 36x5
2.65
338
x-x
39,500
1,560
10.8
y-y
39,500
1,560
10.8
v-v
16,500
1,090
7.0
36
5
5
I have diagonals (bracings) which can buckle in these "non-regular" directions too, and they do. If I could add those values then in the Karamba model I could assign specific buckling scenarios..... I can see another challenge which will be at the ModifyElement component, I will not be able to choose these buckling lengths, in these directions.
Do you think this functionality can be added within short, or should I try to find another way to model these members?
Br, Balazs
…
ink you shared back then is not valid anymore.
I would really appreciate it. Thank you,
Helena
---------------------------------------------------------------------------------------------
Permalink Reply by Mostapha Sadeghipour Roudsari on November 30, 2015 at 6:35pm
Hi Caludio and Tatos,
For Daylight modeling you can use Radiance's image-mapping. I published a paper recently that discusses the process (http://www.simaud.org/2015/program.php#a-new-approach-to-modeling-f...). They haven't send it online but I can email you the paper if you're interested to read it in details.
Permalink Reply by Mostapha Sadeghipour Roudsari on November 30, 2015 at 7:44pm
Here is the link to the paper: https://copy.com/okY7JzPoVjbF6LrL
…
your fully glazed building). Once a person looks away from the glazed building, they no longer experience glare. If you know the view that someone will have looking at your building, Honeybee has a large number of tools that will give you real and reliable numbers for glare.
I know that you are planning to use a different method here but I point out the above just to be clear that you are not necessarily sure that people will experience glare if you are just looking at the times of the year when direct sun will be bouncing off of the glass building onto another building. However, I can see this as a good starting point to assess the hours where there is a risk of glare in the building where light is being bounced to.
With that preamble out of the way, I can say that you are using a version of Ladybug that is 6 months old and I have updated your file for you. To update your components and to be sure that the file below works correctly, you should re-download the user objects from the main Ladybug page and drag them onto your canvas.
If you want to look at sunrays for a whole year, I would keep your number of test points low by increasing your grid size (I think 5 should suit your purposes). Also, you should only set the number of bounces to 1 as you are only really concerned about the one bounce off of the glass building. With these two things done, you can then hook up an analysis period and have it do bounces for every sun-up hour of the period an not take for ever to calculate on your machine. Perhaps an easier way to do this would be to take a sun-up hour for every month instead of a full analysis period, as I have done in your attached file.
Finally, you need to make the last bounce length long enough to intersect the neighboring building (I increased it to 15 meters). Then you can use the native grasshopper components to count the number of intersections.
You can see this all in this file:
https://www.dropbox.com/s/poe7i1zwut2fjg6/Glarescript19sept_CWM.gh?dl=0…
ntroduces a set of components for creating angular and distance dimensions. These components are not entirely finished yet, especially baking is still a bit rough in places. Also note that a new Tab has been added and some components have been moved from their old position into this new tab.
GH1 Beta 5 was never officially released, though it was the default download for a while. Look in the Grasshopper Version History for a detailed list of changes over time.
List of changes:
A new Display tab has been created for components that show stuff, rather than do stuff.
[Blend Colours] component has been hidden, we recommend [Interpolate Data] instead.
[Point List] and [Point Order] components have superceded the original [Point List] component.
[List Item] retrieval performance is now much better for large amounts of indices.
Added [Linear Dimension] component (Display.Dimensions panel).
Added [Aligned Dimension] component (Display.Dimensions panel).
Added [Line Dimension] component (Display.Dimensions panel).
Added [Marker Dimension] component (Display.Dimensions panel).
Added [Angular Dimension] component (Display.Dimensions panel).
Added [Arc Dimension] component (Display.Dimensions panel).
Added [Circular Dimension] component (Display.Dimensions dropdown).
Added [Serial Dimemension] component (Display.Dimensions dropdown).
Scribble objects no longer rotate by default when dragged.
Scribble objects can now be realistically dragged by holding SHIFT.
Fixes:
Persistent Data stored in generic parameters would sometimes fail to deserialize, this is fixed.
--
David Rutten
david@mcneel.com…
Friday. I also have some work being exhibited which is in the last link.
My understanding is that the event is out of student seats but that there may be some professional seats to the workshops still available.
Regards,
Jonathan
-
Houston. Friday, 02/11/11 through Sunday, 02/13/11 - University of Houston College of Architecture
TEX-FAB is a Texas-based network of companies, institutions, and individuals focused on providing a platform for the exchange and exploration of issues related to parametric design and digital fabrication. We are focused on providing a platform for the exchange and exploration of issues related to parametric design and digital fabrication and in leveraging the immense resources found in some of the largest metropolitan centers across the United States.
TEX-FAB is uniquely positioned to serve as a bridge between academia, the professional design office, and industrial fabricators throughout the state. Our primary efforts are expressed through three fundamental avenues: lectures, workshops/exhibitions and competitions/commissions. Collectively these components combine to provide a forum for the exchange of ideas, information, and the mutual interest in transforming the design process through digital technology.
http://tex-fab.net/category/workshops/
TEX-FAB Lectures
Branko Kolarevic, Chair in Integrated Design and co-directs the Laboratory for Integrative Design (LID) at the University of Calgary will be lecturing on Thursday 2/10/11 at 6:00 PM. He authored, edited or co-edited several books, including the recently published “Manufacturing Material Effects: Rethinking Design and Making in Architecture” (with Kevin Klinger), “Performative Architecture: Beyond Instrumentality” (with Ali Malkawi) and “Architecture in the Digital Age: Design and Manufacturing.”
L. William Zahner, CEO/President of Zahner and Company will be speaking on Friday February 11th at 4:30 PM on "Adding Intelligence to Building Surfaces"
http://tex-fab.net/category/upcoming-lectures/
BONE MACHINE
http://formpig.com/blog/?p=2815…
ours looks like). Anyway, you'll probably want to start with a Fader 1-way. I set mine up to go from 0 to 300 over the course of 6 seconds. Then I just wrote a very quick C# component to check the output of the Fader component and whether it met one of three conditions. Here's the code (very simple). Note: you'll need to use the input manager to remove one of the Y input and the output manager to add 2 more outputs (B & C).
if (x <= 100) { A = true; B = false; C = false; } if (x > 100 && x <= 200) { A = false; B = true; C = false; } if (x > 200) { A = false; B = false; C = true; }
Now, we know if at any given Fader value if it's in the first phase, second phase, or third phase. I output a boolean value which can also be considered a 0 or 1 if converted to an integer. So, if I multiply those boolean values by 255, then the one that is true will be 255, and the others will always be 0. Now, you should have your color scheme which switches depending on what phase its in. Simply connect that to the Uno Write component (with the Firefly Firmata sketch loaded on your board) and send the color values to the board as PWM values.
Some things I should note... You probably notice the Fader component looks a little different (it's missing the start input and I'm using the GH_Timer). I've decided (for good reason) to abandon the Form Timer I was using in a lot of the Firefly components in favor of the newly re-written GH_Timer component. So, in order to get the Fader component to update in the next version, you have to connect a Timer and turn it on (not that much different). But, it's significantly faster. Part of the reason is that the form timer just wasn't fast enough to get really smooth results... Now, it's blazing fast. I've incorporated this Timer scheme in a lot of the Firefly components and the results are roughly 10x faster. Since, you're only switching values (and not trying to quickly modulate the PWM values) the current version of Firefly should be just fine (just use the Start input to start the Fader component). But, when we release the next version (hopefully very soon), this may change a bit. Anyway, I hope that clarifies it a bit. I've attached a screenshot below. I didn't include the file because I've got a newer version of Firefly that would just crash on you (or not open properly)... but hopefully you can get how to do it.
…