component is checking ad, as, ar and aa values. This is just to make sure that the results are accurate enough.Good to go!Current working directory is set to: c:\ladybug\unnamed\DF\Runtime error (FileNotFoundException): Le fichier 'c:\ladybug\unnamed\DF\error.log' est introuvable.Traceback: line 327, in script
I never had this problem before... and I don't see the link between your python component and this error.
…
try now to integrate Geco in an interdisciplinary architectural engineering studio: hoping we can show you some nice applications of your tool, I'll keep you update and sending now details by e-mail. Here the file (very welcome to be shared). It most probably contais trivial errors by me, thanks for helping and giving some tip! Gr. Michela
FILE:
Ok, right, I see the outputs update correctly. Origin of problems must be in some different mistake I do:
- Incident radiation: I am not sure I understand what is going on: why I get so many 'not a number' ? (The Galapagos report is full of NaNs).
Bio-Diversity: 0.887 Genome[0], Fitness=NaN, Genes [89% · 44%] { Record: Too many fitness values supplied } ...
Genome[7], Fitness=NaN, Genes [74%] { Record: No fitness value was supplied } ....
Genome[9], Fitness=NaN, Genes [37% · 11%] { Record: Genome was mutated to avoid collision Record: Too many fitness values supplied }
- Daylight calculations: the geometry accumulates withouth deleting the previous models. As a consequance, results almost do not change after few varations (so, outputs get updated but do not vary). In current daylight definition: the first object being imported is the one where the grid has to fit; its setting makes it cancelling all the other objects during import. All the others, do not delete anything when imported. When running loops (manual or GA) that vary parameters, the entire geometry do not get cancelled - so I guess the loop does not pass back by the cancelling step, but imports only the geometry which has been varied by the parameters using the setting of that import component only? I will then try again by changing the order of the operations, but if you have specfic tips, let me know.
THANKS!
…
Simpsons episode were Bart goes into a mall and in the time he goes in and out of a shop all others have been turned into Starbucks.
I personally don't like it but you can't say they are crushing all competitors because, as far as i know, all owners of those software packages voluntarily sold their property for a good price. I would actually be more worried that an antitrust lawsuit was filed against Autodesk.
For example, this is what happened with Rockefeller's Standard Oil:
The antitrust case against Standard Oil also seems absurd because its share of the petroleum products market had actually dropped significantly over the years. From a high of 88 percent in 1890, Standard Oil's market share had fallen to 64 percent by 1911, the year in which the US Supreme Court reaffirmed the lower court finding that Standard Oil was guilty of monopolizing the petroleum products industry.[32]
The court argued, in essence, that Standard Oil was a "large" company with many divisions, and if those divisions were in reality separate companies, there would be more competition. The court made no mention at all of the industry's economic performance; of supposed predatory pricing; of whether industry output had been restrained, as monopoly theory holds; or of any other economic factors relevant to determining harm to consumers. The mere fact that Standard Oil had organized some thirty separate divisions under one consolidated management structure (a trust) was sufficient reason to label it a monopoly and force the company to break up into a number of smaller units.
To economists, "predatory pricing" is theoretical nonsense and has no empirical validity, either.
In other words, the organizational structure that was responsible for the company's great efficiencies and decades-long price cutting and product improving was seriously damaged. Standard Oil became much less efficient as a result, to the benefit of its less efficient rivals and to the detriment of consumers.
From: http://mises.org/daily/2317
(Beware, that site is very ideologically charged)…
points within the bounds of the site boundary and use each location as an attractor point controlling a variable at each point in the grid (radius of a circle/height of a cube/colour based on a gradient etc.).This would be based on proximity to the attractor points with the effect of each attractor point essentially scaled by the percentage associated with it. For example a location with 88% visitor rates would have a more dramatic effect than a location with 26% visitor rates.
I've had a bit of a play around but can't seem to get beyond the point of what is shown in basic point attractor tutorials online. I'm definitely a novice.
Here's how I figured it would be done:
1) Create a grid of source points within a boundary curve.
2) Select 18 pre-defined attractor points.
2) Measure the distance between the source points and the attractor points.
3) Invert this data so that variables increase with proximity rather than decrease.
4) Give each of the attractor points a strength value from 1-100% based on the visitor rates.
5) Use the scaled data to control a variable at each of the source points.
6) Create some way to control the drop-off rate of the effect from each point.
It is at step 3 that I get completely lost.
I hope my description is clear. Any help would be greatly appreciated,
Adam
…
rendo posizioni lavorative fino a qualche tempo fa impensabili. Questo nuovo approccio ha infatti la caratteristica di avvicinarsi alla programmazione informatica, ma con un approccio facilitato grazie ai componenti visuali.Hai bisogno di un motivo in più per usare Grasshopper? Eccolo! Trattandosi di uno strumento ancora in fase di testing (anche se perfettamente funzionante) l’applicativo è completamente gratuitoScarica la tua versione e inizia subito ad usarlo!Corsi certificatiLe lezioni sono tenute da Antoni(n)o Marsala, docente certicato McNeel, con alle spalle oltre 5 anni di esperienza nell’insegnamento di Rhinoceros. Negli ultimi anni abbiamo tenuto in grande considerazione l’evolversi di questo plugin e abbiamo deciso di investire sulle sue potenzialità.Nel Febbraio del 2011, grazie ad Antoni(n)o Marsala, è uscito Algoritmi Generativi, edizione italiana del libro di Zubin Khabazi Generative Algorithms with Grasshopper. Entrami sono scaricabili gratuitamente e rappresentano dei validi strumenti per capire il mondo di Grasshopper.Da diversi mesi inoltre, il Mandarino BLU, ha attivato una collaborazione con La Bottega di Galileo di Pisa, officina del libero scambio di idee, presentando dei progetti formativi post universitari, per coloro che vogliono entrare nel mondo della progettazione di nuova generazione.Dalla collaborazione con Multiverso, nasce invece un progetto formativo più ampio sviluppato a Firenze in via Campo d’Arrigo 40rLeggi il nostro programma didattico o scarica la versione in pdf…
onnessione delle parti. Quelle forme nella foto sembrano abbastanza minime se non per le parti che sono, appunto, "fatty", grassottelle (questa parola nel contesto è divertente!)
Un approccio non minimo potrebbe essere con la suddivisione di una mesh più grossolana, per esempio con WeaverBird. Posto un esempio. Potresti poi rilassare questa o un altra mesh non minima, per esempio con Kangaroo, ed il plug-in minimizzerà le tensioni.
La parte più difficile è modellare una mesh di partenza. Alcuni comandi che ti potrebbero servire sono _3dFace, _Join, _UnifyMeshNormals e _DeleteMeshFace. Spero ti sia utile.
- Giulio
Edit: tra l'altro, potresti anche provare ad usare T-Splines per costruire questo oggetto.…
any workflow
-> would it make things easier if the component could accept only "pre-built" domains as inputs ?
in my mind I see extensive use of such a component for splitting lists, "debugging" definitions (maybe coupled with list-item) and all thae situations usually require the domain of a number slider to be manually set again
I think it might also make definitions "more adaptive", letting them work in different situations with less ad-hoc customization needed (I would use this component instead of a classic number slider in at least 75% of the situations)
I also imagine I would almost always use this instead of number sliders coupled with remap-numbers components
would it be helpful if I create a kind of detailed list of "situations" where the use of this component would save time and make new kinds of definitions possible?(maybe all this stuff goes on just in my mind, but I really see new horizons with the creation of this thing)…
ithin my TouchOSC interface. Check the definition below and see if it works for you.
Took a bit of time debugging (even though my solution shows a simple setup). For most of the time, however, I tried sending data to TouchOSC without gHowl's encoding algorithm (i.e. setting the Pattern parameter to '0' ASCII encoding). This yielded unexpected data -- a problem that is still unresolved.
If you pipe the data that you receive from TouchOSC in Grasshopper through a Python component with the contents:
a = repr(x)
as the code...you can start to gain a better understanding of the UDP data that is being sent between the listener and sender. Grasshopper panels, for better or worse, have a few metacharacters they natively recognize (e.g. '\x00' is a hexadecimal representation of an empty byte, which GH Panels don't display). This muddies the waters as far as debugging goes. It has tripped me up a few times now, so I am thoroughly in the habit of using the above, ad-hoc Python script. Good luck!…
n of an image across it (castle4.)
My first though was image sampler to the surface but I can not work how to get the sampler to view all the surface as one whole and apply the image across the whole thing regardless of the kinks.
just to ad because I'm not sure that this is very clear
I have 15 surface all connected by not a single surface due to the geometry and I would like the image to be a single image but across all the individual surfaces.
my end goal is a perforated façade based on the interpretation of the image
any help or direction would be greatly appreciated.
Thanks
Luke
…