lts.
In the visualization, points is an interesting option. It's a matter of aesthetics I guess, I go with surfaces :) Also what you can try is selecting Filters -> Slice (you can also find it in the icons above the pipeline viewer), in the Slice options below the pipeline press Z normal and on the Z coordinate press some height relevant to the buildings (e.g. 1.75m a typical human scale). That would show you the flow around the buildings on that height. Experiment with selecting other normals and values. Keep playing with the filters there's some cool things in there. Also you can check out the mailing list and extensive paraview documentation.
Concerning the errors I apologize because I just downloaded your case.
It appears that the decomposeParDict is not included in the system folder. I am not sure if this is due to BF not going through the whole workflow yet or an ommission on our side. Please feel free to add it in Github. I will also note it down and pass it to Mostaph to check. In the meantime please find attached a VERY detailed decomposeParDict file. I took the liberty to set it at 4 processors (the numberOfSubDomains value) and also selected (that is uncommented) the scotch decomposition method. It's the easiest method to use since it is automatic and doesn't require any more inputs on how the domain is decomposed on the x,y,z directions (which would require you to change values in the attached file).
Now, the different folders created are simply snapshots of the current solution at the specific timestep. To control how often the solver is saving change the writeInterval number in the controlDict file. You can also change almost all these values on the fly, while OF is running.
Finally, concerning the other errors of parafoam it seems somehow parafoam is reading the intial condition names instead of actual results from the solution files and it doesn't like it.
Does this happen only when you open the case (i.e. at 0 time) or does it also happen when you move to an other timestep?
Also, are you using paraFoam, paraview or the paraFoam -builtin method?
The extension of the paraFoam file seems to be .foam which means you are probably using the built in viewer. That might be the issue but I'm not sure.
Can you try running paraview, navigate to your case folder, open the .foam file and see if there is still an error?
Also, if it isn't much trouble can you zip one of the time folders and attach it here? I'd like to take a look at what's inside to check against what the error report says.
Once again thanks for testing!
Kind regards,
Theodore.…
sinergetici associati alla compresenza simultanea di differenti strumenti di analisi e digital design all'interno di un processo di progettazione in svolgimento. I partecipanti utilizzeranno Grasshopper (modellatore parametrico per Rhino): l'uso di questo editor grafico di algoritmi si integra alla perfezione con gli strumenti di modellazione di Rhinoceros 3D espandendo le possibilità di corstruire modelli parametrici altamente complessi. Per generare una complessità simile saranno utilizzati collegamenti live ai diversi programmi elencati di seguito: . Autodesk Ecotect Analysis via GECO . FEA software GSA via SSI Durante questi intensi 3 giorni, i partecipanti impareranno il workflow dei plug-ins con l'aiuto di esempi esplorando una panoramica dei differenti software, le possibilità di testare le performances di un progetto o l'uso di strumenti addizionali non legati ad un singolo sistema (es. accentuazione, formazione, reazione parametrica) [english text] The focus of the workshop is to integrate and correlate the synergistic effect associated with simultaneous presence of different digital design- and analysis tools in an ongoing design process. The main attention is set on easy to handle interface , which should be used at a early stage of conceptual design to respond to external and internal influences in a intelligent and sustainable way. Participants will use the software Grasshopper as a parametric modeling plug-in for Rhino. The usage of this graphical algorithm editor tightly integrated with Rhino's 3-D modeling tools open up the possibility to construct highly parametrical complex models. To generate this complexity we will use live linkages to several programs listed below: . Autodesk Ecotect Analysis via GECO . FEA software GSA via SSI In this 3 intense days, the participants should learn the workflow of the plug-ins with the help of examples and get an overview of the different software's, there possibilities for evaluating the performance of a design or the usage of additional tools to be not chained to a single system . (e.g. parametrical accentuation, parametrical formation, parametrical reaction) [.] Dettagli : Istruttori: Thomas Grabner & Ursula Frick from [uto]. lingua del corso: inglese (saranno disponibili tutor di supporto ma è richiesta una conoscenza di base della lingua unglese).
Quote d'iscrizione (min 12 max 20 posti): educational* : € 280.00 + iva professional: € 450.00 + iva * studenti, docenti, ricercatori, dottorandi e laureati fino a un anno dalla data di laurea OFFERTA EARLY BIRD SPECIAL: le prime 5 domande di iscrizione pervenute entro il 31 Dicembre 2011 avranno diritto ad una quota di iscrizione scontata del 20% Quote d'iscrizione E.B. SPECIAL: E.B. SPECIAL educational* : € 224.00+ iva E.B. SPECIAL professional: € 360.00+ iva. ulteriori info, dettagli e iscrizioni: http://www.co-de-it.com/wordpress/nexus-advanced-grasshopper-workshop-with-uto.html…
radiance parameters to get rid of blotching. To add another level of complexity to my problem, I am running simulations with a translucent material with the following properties: void trans testTrans
0
0
7 0.478 0.478 0.478 0.000 0.010 0.178 0.635
I have had no issues with the renderings when I use clear glazing, as seen on this image:
However the blotching-issue becomes very noticeable when I introduce translucent glazing into the scene:
For the two above cases I used the following parameters:
_av_ is set to 0
xScale is set to 2
_ab_ is set to 6
_dc_ is set to 0.5
_aa_ is set to 0.2
_ad_ is set to 2048
_st_ is set to 0.5
yScale is set to 2
_ps_ is set to 4
_ar_ is set to 64
_as_ is set to 2048
_ds_ is set to 0.25
_pt_ is set to 0.1
_dr_ is set to 1
_pj_ is set to 0.9
_dp_ is set to 256
_dt_ is set to 0.25
_lr_ is set to 6
_dj_ is set to 0.5
_lw_ is set to 0.01
I ran another test with increased Radiance parameters and got the following output:
with the following parameters:
_av_ is set to 0
xScale is set to 6
_ab_ is set to 6
_dc_ is set to 0.75
_aa_ is set to 0.1
_ad_ is set to 4096
_st_ is set to 0.15
yScale is set to 6
_ps_ is set to 2
_ar_ is set to 128
_as_ is set to 4096
_ds_ is set to 0.05
_pt_ is set to 0.05
_dr_ is set to 3
_pj_ is set to 0.9
_dp_ is set to 512
_dt_ is set to 0.15
_lr_ is set to 8
_dj_ is set to 0.7
_lw_ is set to 0.005
Although the second blotching case is much better than the first, it is still very bad for hours when the sun is lower in the sky. The above images are rendered for a clear sky at 18:00 in Germany in a West-facing room.
Sorry for the long post! Can someone help? Kind regards, Örn
…
nside the zone. I would move your comfort evaluation surface to be 1 meter off the ground in order to be representative of typical human height.
Also, you did not intersect the ground with the rest of the zone geometry, resulting in an incorrect energy simulation. After intersection, you also get one surface of the ground zone that is not inside any buildings. I fixed these two things in the attached file ad it works:
I would also recommend breaking the top surface of the ground up into sub-surfaces so that you can capture the variation in ground surface temperature that happens across the outdoors. Second, I would recommend putting some windows on your buildings as the exterior surface temperature of windows can be very different than that of opaque surfaces. Finally, you should keep in mind that the outdoor maps are assuming a very basic outdoor wind profile by default and, to accurately understand outdoor comfort, you really should be incorporating wind patterns after running a CFD. This discussion has some information about importing CFD from other programs to GH:
http://www.grasshopper3d.com/group/ladybug/forum/topics/import-cfd-result-to-honeybee
-Chris…
ino al suo utilizzo per la risoluzione di tematiche di modellazione complessa di ARCHITETTURA e DESIGN.Durante le lezioni si insegneranno i comandi avanzati del software Rhinoceros ed inoltre i discenti, alla fine del percorso formativo saranno anche in grado di creare modelli attraverso il linguaggio della Plug-in avanzata Grasshopper(http://www.grasshopper3d.com/photo).
Il workshop si divide in due moduli che possono essere frequentati anche separatamente:
STRUTTURA
mod.1 _MODELLAZIONE BASE con Rhinoceros | Venerdì 14 Dicembre e Sabato 15 Dicembre | dalle 10,00 alle 19,00
Scadenza iscrizione: Lunedì 10 Dicembre
mod.2 _MODELLAZIONE AVANZATA con Rhinoceros e Grasshopper | Domenica 16 Dicembre e Lunedì 17 Dicembre | dalle 10,00 alle 19,00
Scadenza iscrizione: Mercoledì 12 Dicembre
SINTESI
mod.1 _MODELLAZIONE BASE con Rhinoceros
L’obbiettivo del corso è quello di insegnare in tempi brevi, gli strumenti base della modellazione 2D e 3D e la renderizzazione dei modelli creati. Le ore saranno dedicate allo studio dell’interfaccia del software Rhinoceros e all’apprendimento dei comandi base per la gestione del documento di progetto; si approfondiranno i comandi più utilizzati per l’editing e la costruzione del disegno per arrivare alle operazioni booleane semplici e complesse. Inoltre si imparerà a costruire e trasformare curve e superfici free-form. Le nozioni ed i metodi verranno trasmessi trattando temi e problematiche reali di design ed architettura.
mod.2 _MODELLAZIONE AVANZATA con Rhinoceros e Grasshopper
Il secondo modulo tratterà forme complesse implementando la modellazione avanzata di Rhinoceros con le potenzialità espresse dalla plug-in Grasshopper. La plug-in di Rhinoceros permette di disegnare abbandonando l’usuale interfaccia dei software di rappresentazione, consentendo un rapporto più diretto con il linguaggio proprio del computer: la programmazione. Questo cambiamento porta ad una radicale variazione del rapporto che il progettista ha con lo strumento di rappresentazione digitale. I partecipanti saranno orientati verso un nuovo rapporto con le forme create che oltre ad essere frutto di trasformazioni delle entità primitive che Rhinoceros propone, si costruiranno anche in relazione a parametri variabili.
Nel corso si imparerà a comporre algoritmi semplici, di carattere principalmente geometrico, in grado di generare forme e gestire i comportamenti delle stesse se sottoposte a variabili esterne.
In fine si imparerà a confrontarsi con un contesto evolutivo, che influenza i parametri della rappresentazione portando a dei modelli dinamici.
…
alità di Rhino, tra cui i comandi più avanzati per la creazione di superfici.
Struttura Le lezioni tratteranno in maniera sistematica argomenti riguardanti l'interfaccia utente, i comandi, la creazione e modifica di curve, superfici e solidi.
Risultati attesi Dopo questo corso lo studente dovrebbe essere in grado di: • Muoversi comodamente attraverso l’interfaccia di Rhino. • Identificare quando è richiesto modellare in maniera free-form o di precisione. • Creare e modificare curve, superfici e solidi. • Utilizzare ausili di modellazione per la precisione. • Produzione di semplici rendering per la visualizzazione dei modelli di Rhino.
Destinatari Questo corso è rivolto a progettisti e studenti che vogliono imparare in modo efficace i concetti e le caratteristiche del software di modellazione Rhinoceros. Le lezioni saranno ottimizzate ed esposte da un docente ART qualificato dalla McNeel. Alla fine del corso verrà rilasciata l’attestato di partecipazione ad un corso qualificato McNeel.
Prerequisiti Per affrontare il corso sono richieste competenze di Windows, passione e volontà di modellazione; precedenti esperienze di modellazione, anche con altri software, sono utili ma non indispensabili.…
ad informazioni provenienti dall’ambiente.
Il corso parte dalle conoscenze base di Grasshopper per la generazione ed il controllo delle geometrie e ha lobiettivo di arrivare a definizioni utili per concretizzare il modello virtuale in prototipo fisico attraverso tecniche di fabbricazione digitale. tutor: Amleto Picerno Ceraso
nb: è richiesta una conoscenza base di Grasshoppercosto: 250€ + IVAnumero minimo di partecipanti: 3deadline: 17 marzo
Per iscrizioni scrivi a info@medaarch.com specificando nome, cognome, mail, recapito telefonico e il nome del corso al quali sei interessato. In seguito all’invio del modulo di pre-iscrizione, i partecipanti riceveranno una mail contenente tutte le specifiche di pagamento.
Il cluster rientra in un fitto calendario di attività formative organizzate dalla Medaarch per lanno 2013-2014.…
is called TouchOSC (http://www.hexler.net/software/touchosc).
Basically, what TouchOSC does is sends a message over UDP, but it's formatted according to the OSC specification (http://opensoundcontrol.org/spec-1_0). Firefly (and Ghowl) both have UDP/OSC receivers (although they work slightly differently). Basically, you have a sender (your phone) and a receiver (your computer) and the sender has to know the IP address of the receiver and they both have to know which port they want to communicate on. The port can really be any number you want. So, when launching the TouchOSC app, you need to go into the settings and specify the IP address of your computer and the port you want to use. Then, just pick a layout and start moving sliders to send the data. On the Firefly side, just drop a OSC listener component onto the canvas and specify the same port number you put into the app. Then, connect a Timer component to the OSC listener to get it automatically refresh at a given interval. The data should come over as a data tree, and you can extract the header of the message, or the actual value using the standard Data Tree components.
The one thing you may want to know is that some networks will restrict communications over UDP (particularly those at schools, or other institutions). I would recommend starting out using your home router, which hopefully doesn't have these restrictions. If you do want to use it at a school, you may need to create an ad-hoc network and make sure your phone and computer are both on that same network. Other than that, it should be pretty straight forward. Hopefully this gets you started.
Cheers,
Andy…
ails.
Some word about the mesh... (see Image_01)
I took a flat 4 points NURBS surface as imput (very easy, it defines the total area of my pavilion) and some points (that defines the contact with the ground).
Then I extracted a grid of points from the NURBS (Surface_Util_Divide surface) and compared 'em with the contol points, in order to associate to each grid's point its own attractor (Vector_Point_Closest Point).
Than I moved the points down. I used the distance from each point to its attractor (inverted) as amplitude for the vector of the movement, in order to say: the nearer you are to the control point, the more intense your movement will be. During this operation I've passed the distances' data list into a graph mapper (Params_Special_Graph Mapper), in order to regulate in a very intuitive and interactive way the shaping of my canopy.
At the end of the process I asked GH for a simple Delaunay mesh (Mesh_Triangulation_Delaunay Mesh). It's a very cool command, I believe!!!
Ok, now some word about the component, it's design and it's repetition/adaptation to the mesh...
(see Image_02)
I took the mesh and extracted components on first and faces's information on second. Then I selected and separated the vertexes (1°, 2°, 3°) of each triangular face into threee well defined list.
Then I re-created the triangles' edges. Please pay attention because it's not the same if you use output information from Delaunay components, because here we need a justapposition of edges where triangles touches each others.
After this work I joined the edges and found their centroid. At the same time I found the mid point of each edge.
Now the component... (see Image_03)
It' a little bit longer to describe: I'll try to be synthetic.
Substantially it is a loft from a curve to a point, repeated three times for each triangle (Surface_Freeform_Extrude Point). The point is an elevation of the centroid of the triangle (you can choose if the exstrusion has a single height or it's related to an attractor. In my case it was fixed). The curve is combination of things. There's an arch, which starts on the edge (there's an offset from the corner) end terminates on the same edge (on the other side, obviously). While it's generation the arch passes through a third point which belong to another segment. This last connects the mid point of the original edge (base triangle) with the centroid. The result is a kind of polyline, with two segments and an arch. If you go back to the image of the component that I posted probably you'll understand what I'm saying better than with the definition.
The posit…