H2RAD. See attached.
This is the change that I made to your simulation.
It's usually not a good idea to have space in the path, as you do for "Projeto de Pesquisa", when dealing with Radiance.
cc: Mostapha/Chris. The culprit is the octree resolution setting of 2048. I guess most users won't run into issues with that kind of setting. So, I am not sure if a fix is needed for this at all.
…
Parametrica.Con grasshopper puoi gestire progetti complessi dal punto di vista della forma e dell'organizzazione con un solo strumento , dal design dell'oggetto , allo spazio dell'architetture , all'organizzazione urbanistica.Grasshopper è un software open source , in continuo aggiornamento da parte degli utenti , TRA POCO POTRESTI CONTRIBUIRE ANCHE TU AL SUO SVILUPPO !!!Sabato 11 MAGGIO 2013durata di 6 ore : dalle 10:00 alle 17:00presso : STUDIO REMODESIGN (via dei marsi n° 41)per prenotare chiama il numero : 3498381249oppure manda una mail all'indirizzo : contact@ivoambrosi.itvisita il sito: www.ivoambrosi.it…
hilst settings concern only the currently selected instance.
For instance assume that you are in the Bermuda Shorts business and you want various ideas concerning a new ad campaign:
Or assume that the 4 horsemen want from you to quickly present some concept proposals related with a terminal event that they have in mind:
…
till quite rough.
I went through your attached log but it seems to be a successful run, perhaps the error log wasn't attached. In any case, I believe we have identified this issue. The goal of the update fvSchemes component was to apply schemes to finalized meshes in an automatic way. While this is useful for new users it is also a dangerous thing to do in CFD studies.
The component works by relating mesh quality to the mesh non-orthogonality, which the checkMesh component reports. While non-orthogonality is one of the important criteria of mesh quality it does present difficulties on some kind of meshes, especially like the simple cases that BF has been meshing so far.
The example case of simple box buildings in a wind tunnel above for instance will appear as a good quality case for even the lowest of cell-count meshes, simply because it is an orthogonal geometry. That means that checkMesh will probably report low values (imagine an empty blockMesh of 10m blocks has a non-orthogonality of 0) which in turn means that higher order schemes might be paired with actually low quality meshes. This I believe is causing problems.
I posted a possible solution to this here https://github.com/mostaphaRoudsari/Butterfly/issues/57. The idea is that Buttefly provides additional options to the users, enabling them to choose between first-order (faster, more robust, but lower quality schemes) and second-order (slower, less robust, but more accurate) schemes depending on mesh quality, stage of assessment, etc. In cases like the above mesh quality a first-order scheme might provide a better option. To test this I am attaching an fvSchemes file you can use by replacing yours in the /system folder of the case.
As a note however, I would like to stress there is so much that a tool like Butterfly can provide in this area. Meshing is a quite complicated and demanding part of the process, involving a lot of trial and error. Sometimes the problem is just the mesh and not the solution options (GIGO stands true in CFD as well). It does however get easier with experience. The safe advice is the simplest one: when changing solution options doesn't help, refine mesh and run again.
Kind regards,
Theodore.…
Grasshopper. So, I once made an attempt to bind ms sqlServer in order to get frozen definitions at some states, to avoid managing baked objects in Rhino and also be able to retain whole results without using the GH state manager that rebuilds everything.
But at that time GH's VB.Net component didn't properly read referenced dlls and I forgot it since then.
At first, I was surprised by Slingshot's extensive interface : I was still having in mind my own old project, a tool that would have acted at the Rhino's geometry object level, and auto creating the needed tables.
The bd would have consisted of a main table, owning the objects ID and name, and related tables containing the necessary information relative to the main objects.
For example, a Brep is made of so and so underlying objects, passed to respective tables, according to GH objects definition layout (just the way they are written in the xml schema).
Then, on a db, query an object by name, and retrieve the whole object or underlying objects (e.g. at the bounding curves level, or points level for a Brep).
With Slingshot, I made a few attempts to cheat GH with BLOB data fields, but no way to get a whole object. It seems that GH simply provides an object.toString ... and GH is definitely not conceived to produce persistence outside of Rhino. If I have some spare time, I will try to extract
About points and colors, I am now simply using a single field with CHAR(asLargeAsNeeded...), as GH parses String to every Point (or Vector or Color) entry of any component.
I do so because it need less to display on the canvas...
Whatever I wrote before, I really like your conception, as opened to relational interactions between ...whatever you need or dream of !
One last thing : GH can't open the definition file "Genome_DB_Template.gh" that I've downloaded from your site : http://slingshot-dev.wikidot.com/database-genome. I was expecting to learn a lot from your very smart stuff ! (I am running GH 08.00.13 and Slingshot 0.7.2.0)
Slingshot is running great, opened to any use...Thanks again.
Best,
Stan
…
l Mtro. José Luis Lechuga.
&
Departamento de Arquitectura TEC-CEM.
Con la Presidenta de ASES Est. de Arq. Iraís de la Fuente.
FORMA Y CUENTAS DE DEPÓSITO BANCARIO / ASES
Registrate y aparta tú lugar! -Acceso a externos-
http://bioarchitecturestudio.wufoo.com/forms/z7x4a3/
Información y preguntas:
bioarchitecturestudio@gmail.com
cc: mexdf@krfr.org…
stall with Visual Studio Express, which is something that I highly recommend doing.
As far as a basic guide, I think most of the beginners books that are out there are going to cover the topics that are going to be used within Rhino/GH fairly well. On one hand, the books out there are all pretty decent, but its more that programming with GH doesn't really require using all of the features of dot NET. As long as you get things about syntax, flow statements, data types, an introduction to OOP, and coverage of using collections, they you'll be fine in regards to programming in GH.
The one that I have here, which is useful but not a stand out, is Beginning VB.NET. I've liked Apress recently, so their book Beginning VB 2008 might be worth a look. I have the O'Reily book VBscript in a nutshell, which is leans more towards reference with a good introduction. Although I can't say with certainly, their VB 2005 in a nutshell book seams to be along the same lines.
Also, I've yet to find a book that is very relevant to Rhino/GH or doesn't have a bunch of stuff that winds up going largely unused in the context of Rhino/GH. Its not that those topics are useless (they might be if you choose to take your programming in a more "typical" direction), but within Rhino/GH they just don't get much face time. The topics that are useful will always require some translation as well, since the examples use some generic kind of issue to demonstrate the topic at hand.
Lastly, I've gotten more mileage out of books that are more specific than the general ones, so if there are some specific issue that you think you might want to explore you might want to see if there's a book out there that's more useful. Since I think OOP is a important concept to grasp to program well with the SDK, I'd take a look at Beginning Object Oriented Programming as its been a very useful book for me.…
Added by Damien Alomar at 8:43am on January 11, 2010
r even a geometry.
We want to develop open source architecture, and be able to reuse easily open source elements of projects shared by the community.
We are interested to display the 3D files in the browser, thanks to connection with external services like http://beta.speckle.xyz or others though at the moment it is not yet available.
When I discovered the grasshoper forum, I liked the fact that people talk very openly about their modelling problems and share definition files...
But I think Bricks could be a complementary publication mode, to find in a glance an element with all its geometry and a link back to the forum post to join the discussion.
Indeed when I work as an architect, I have not always the time to browse a forum with all its discussions to find a suitable element for my project.
I've quickly reposted 2-3 forums posts to test it out.
I would love to have your feedbacks on this new way of publishing grasshoper definition files and more globally 3d reusable geometries.
Here you can see a single definition or the list of definitions that can be classified at the left thanks to custom categories.
If you create an account and upload a few definitions and 3d images and files, you could also tell us, what you think of this process.
Sébastien
www.twitter.com/sebastien_lucas…
ra' nella finestra di Grasshopper, in alto, insieme agli altri set di componenti come 'Params', 'Maths', ecc.
Si tratta di un esperimento per cercare di ampliare in qualche modo l'ambito di utilizzo di Grasshopper.
Come sappiamo Grasshopper e' nato per consentire l'utilizzo parametrico di Rhino. Le definizioni di Grasshopper permettono di registrare i passi necessari per costruire gli oggetti, nonche' di variare i dati utilizzati dalla definizione, ad esempio oggetti geometrici, lunghezze, angoli, ecc.
Quando modifichiamo i valori utilizzati dalla definizione Grasshopper automaticamente ricalcola il tutto e ci mostra la preview del risultato.
A questo punto, se il risultato e' soddisfacente, possiamo dire a Grasshopper di inserire gli oggetti in questione nel documento di Rhino, cosicche' li vedremo apparire nelle viste come veri e proprii oggetti Rhino.
Questo modo di lavorare ha avuto un grande successo tra gli utilizzatoti di Rhino, rendendo molto piu' agevole la costruzione di oggetti nel caso in cui sia necessario procedere per tentativi, verificando il risultato prima di stabilire la forma finale da ottenere.
Il successo di Grasshopper pero' ha anche mostrato quanto sia comodo poter definire graficamente le procedure di costruzione, e in generale poter utilizzare Rhino tramite i componenti, ad esempio gli slider, che tutti noi, suppongo, vorremmo avere a disposizione anche quando usiamo Rhino nel modo classico tramite pulsanti e comandi.
Quindi col passare del tempo sono apparsi sempre piu' Add-on per Grasshopper che permettono di eseguire operazioni particolari o anche di utilizzare Grasshopper in ambiti diversi dal concetto originale di 'History programmabile'. Accodandosi a questa tendenza, edoc prova a costruire dei componenti che permettano di operare direttamente sugli oggetti Rhino, cioe' curve, superfici, layer ecc. appartenenti al documento Rhino su cui stiamo lavorando. L'idea e' permettere di utilizzare la comoda interfaccia utente di Grasshopper anche per operazioni che solitamente sono eseguite in modo tradizionale con pulsanti e comandi, o anche tramite script.
Come gia' detto, e' un esperimento. I componenti nascono, muoioni e cambiano molto spesso, nel tentativo di capire cosa puo' essere utile e cosa puo' fuzionare o meno.
Segnalazioni di bug, suggerimenti, considerazioni ecc. sono benvenuti.
se qualche anima pia volesse tradurre questa presentazione gli faremo un monumento equestre!
grazie e scusate
gg
…