starting mesh. The geometry of the lines is then modified, through the formfinding routine.
In my second vb component, I need to build an array with 4 columns. Each row represent one face of the mesh (row 0 for face 0, row1 for face 1, ...) and each column represent the number of the edge element. If ABCD is the quad face, column 0 is the number of the edge AB, column 1 is BC, column 2 is CD and column 3 is DA.
So to build this array, I extract the edges of each face with FaceB component then Explode component, and I build the array by comparing each line coming from this to each line coming from MEdges component, with a 2 level nested loop. Here is where I am looking for an efficient way to compare 2 lines...
Is there an easier and faster way to build this array ?…
ame as the example: http://vimeo.com/25182853
But with my script, I canot align the center of gravity with the center of buoyancy longitudinally.
What I would like to do is to have 3 inputs:
- Heel angle (Degrees)
- Displacement (Tons)
- Center of gravity position of the ship (X, Y, Z)
And the script acts on the hull depth (like now) AND on the trim angle, so the GC and BC can be aliged longitudinally.
Anobody has an idea ?
Simon
…
ceros.
Public concerné /
Architectes et designers, utilisateurs de Rhino souhaitant paramétrer Rhinocéros à l’aide de Grasshopper,
programme associant des composants et une structure de graphe interagissants avec le modèle Rhino.
Une bonne connaissance de Rhinocéros est nécessaire. La langue de la formation est le français.
Structure et Objectif de la formation /
La formation se déroule sur 3 jours : les 2 premières journées sont consacrées aux « fondamentaux » de
Grasshopper avec en préambule une introduction au design et à l’architecture paramétrique et leurs impacts
dans la conception, la création et la construction.
La troisième journée sous forme d’atelier est dédiée à l’étude de cas concrets proposés par les stagiaires, qui,
quelques jours avant la formation, pourront envoyer leurs projets par mail à - info AT rhinoforyou DOT com -
Les stagiaires, après la formation, pourront rester en contact avec les formateurs de HDA par le biais du
blog complexitys.com et le twitter @HDA_Paris. La durée de cette formation permettra d’atteindre une
autonomie et une bonne compréhension basée sur des exemples concrets.
Programme ind icatif des notions traitéES pendan t la formation /
Introduction à la conception Paramétrique . Rhinoscript, Grasshopper: différences et similarités . Interface
graphique de Grasshopper . Objets, Données, Listes . Opérateurs scalaires : La mathématique de
Grasshopper . Gestions des données : la logique de Grasshopper . Vecteurs, Points, Lignes, Surfaces : La
géométrie de Grasshopper . Listes, Arbres, Branches . Le dessin paramétrique: exercices divers et exemples
. Références, Bibliographie, Support de cours . Ateliers d’architecture et design paramétrique (3ème jour) .
Moda lité de la formation /
Venir avec un PC portable équipé de Rhinocéros version 4.0 SR 7 et de la dernière version du plug-in
Grasshopper (téléchargeable sur www.grasshopper3d.com).
Le coût du stage de 3 jours est de 1050 € HT par personne.
Réserver votre place dès que possible car les places sont limitées à 10 participants maximum.
Inscriptions et renseignements: Jacques Hababou, info AT rhinoforyou DOT com
Pour en savoir plus sur l’architecture paramétrique: www.complexitys.com…
. etc. So it's 80020 which is ~1058. Assuming you're allowed to use the same component more than once.
1058 × 1049 = 10107 total possible algorithms. When talking about big numbers I only have three frames of reference. The distance from us to the edge of the observable universe is roughly 1029 millimeters, the observable universe contains 1080 protons and the volume of the observable universe is roughly 5×10105 cubic nanometers. So you could more or less put a different valid Grasshopper algorithm into every cubic nanometer of this universe.
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
in the .gh-file below. However, it takes a very long time to generate this calculation, even four about five panels or so, while I have about 1600 on the hyperbolic paraboloid. You once told me in another discussion that the TOF component did less calculations than the PV Surface component and would therefore be faster. However, it seems to go even slower when you have multiple surfaces.
So what I would like to know is how to have an idea of which PV panels would be worth of keeping on the hyperbolic paraboloid. For instance, to visually represent the panels with a TOF of >90%, >80%, >70% and so on, without too long calculation time.
(You will have to zoom out quite a bit to see the surfaces. The TOF component is in the red group and there is some part of the code that is irrelevant for this question, but it's quite clear.)…
gn-by-many-designbymany/
The first sponsored challenge is to create a parametric version of Buckminster Fuller’s Dymaxion House.
It would be AWESOME to see it done in Grasshopper! And.. You can win a pretty sweep HP desktop plotter. The deadline is this Friday.
Hope to see you on the site and look for some new GH and RhinoScript videos coming soon.
Thanks,
Dave…
Added by David Fano at 12:28am on December 15, 2010
onsidered period.
Even if the end of July for the mediterranean climate is not the best period to perform an adaptive comfort analysis (it's just a pretest to define a LB model) I want to refine the Adaptive comfort Chart (AC) by changing the external air temperature data imported from the .epw file with that of monitored data as reported here below:
Where the monitored ext air temperature are in this form (green panel below):
I have used the comfortPar component to set the following parameters:
Adaptive chart as defined by EN 15251
90% of occupants comfortable
the prevailing outdoor temperature from a weighted running mean of the last week
fully conditioned space (even if it is not properly in line with AC as already discussed)
The question is this: the AC component could correctly apply the code below if there is only a list of external temperature data for a restricted period (without indication about the limits of this period) and not for an entire year?
else: #Calculate a running mean temperature. alpha = 0.8 divisor = 1 + alpha + math.pow(alpha,2) + math.pow(alpha,3) + math.pow(alpha,4) + math.pow(alpha,5) dividend = (sum(_prevailingOutdoorTemp[-24:-1] + [_prevailingOutdoorTemp[-1]])/24) + (alpha*(sum(_prevailingOutdoorTemp[-48:-24])/24)) + (math.pow(alpha,2)*(sum(_prevailingOutdoorTemp[-72:-48])/24)) + (math.pow(alpha,3)*(sum(_prevailingOutdoorTemp[-96:-72])/24)) + (math.pow(alpha,4)*(sum(_prevailingOutdoorTemp[-120:-96])/24)) + (math.pow(alpha,5)*(sum(_prevailingOutdoorTemp[-144:-120])/24)) startingTemp = dividend/divisor if startingTemp < 10: coldTimes.append(0) outdoorTemp = _prevailingOutdoorTemp[7:] startingMean = sum(outdoorTemp[:24])/24 dailyRunMeans = [startingTemp] dailyMeans = [startingMean] prevailTemp.extend(duplicateData([startingTemp], 24)) startHour = 24
…
it we thought our stands will be made with a fixed depth (80 or 90 cm) and incremental heights like 30-32-34-36...cm, and that is the list you have to supply.
The script will iterate over the different possible measures until it finds the smallest one that complies with your desired C value, but it wont be the exact, just the best approximation within your list.
2. Changing this also depends on the combinations of riser height and depth you provide, if you enter 1m and 1m in both lists you will get an 45º slope.
Anyway, getting a fixed-c value script would be easier (much easier than what is already there) but IMO it wouldn't have a direct application in real stadiums unless you are ready to make each stand different from the rest, discarding any pre-cast solution.
Hope this helps.
Roberto…
raries folder, seems that you need plankton.gha.
Unlock, place in folder, restart rhino+gh...
That's all.
To use it... in a basic way:
Input 0. Plug geometry.
Input 1. Set target resolution, actually it refers to the mesh edge length.
Optional input 2 and 3. Sets anchors (as points or curves) for the remeshing not escape of these parts.
Input penultimate. Number of iterations. Here are two ways, the living form, you set a low value (as 5 or 10) of iterations and plug in a timer component (that allows you to see the remesh process); or just add the total number of iterations (I generally use 80, but its relative).
The last input, set false to turn it on, true to turn it off.
For advanced configuration, trial and error, or see the code on Pikers's github.…
ьютера за требуемое время не получен нужный отклик, или было разорвано уже установленное соединение из-за неверного отклика уже подключенного компьютера 178.63.48.217:80This component requires OSM data to be downloaded from openstreetmap.org. It has just failed to do that. Try the following two fixes: 1) Sometimes due to large number of requests, the component fails to download the OSM data even if openstreetmap.org website and their services are up and running.In this case, wait a couple of seconds and try rerunning the component. 2) Try lowering the "radius_" input. If each of two mentioned advices fails, open a new topic about this issue on: www.grasshopper3d.com/group/gismo/forum." …