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.…
ould you want to have the same name for several things), but that doesn't explain why it isn't working at present, because the code looks ok as it flattens all input volatile data:
<code>
foreach (IGH_Param param in Params.Input[2].Sources){ foreach (Object myObj in param.VolatileData.AllData(true)){ if (myObj is GH_Number && pCount < 8){ if(!criteria.Contains(param.NickName)){ GH_Number temp = (GH_Number)myObj; performas.Add(temp.Value); criteria.Add(param.NickName); pCount++;
}
}
}
}
</code>
Anyway, you can only have 8 performance criteria max, so I would suggest splitting your list and naming each performance measure accordingly:
As for the speed, this is very hard to tell without a file to go on. Ultimately biomorpher is doing practically nothing compared to the time it takes to calculate each grasshopper instance.
However, I would recommend reducing the population size and disabling the grasshopper preview (on the initial screen). Also, try running the thing but just inputting a simple mesh sphere instead of the actual geometry (whilst still inputting the correct performance measures), and see if you get any speed improvement then let me know. That would be interesting to know, because there might be ways I can improve the speed by not importing meshes necessarily.
Alternatively, just send me a cut down version of your definition and I'll have a look.
Thanks,
John.
…
h is attached below. it`s an arch, let`s say out of bricks with loads, represented with point loads which are taken from user-defined surfaces (to represent self-wight e.g).
goal of the study is to find a supporting arch which is inside the arch then (provided the strength of the bricks is high enough) the arch is ok -otherwise one have to change the geometry of the arch (make it thicker, or change the rise of the crown).
therefore i used kangaroo in combination with galapagos to find a catenary which fulfill the boundary conditions. it works very well. so the solution galapagos found is very satisfying.
it`s simple to prove the resulting forces in the arch if one knows the rise of the arch.
according to the formula N~ q*l^2/(8*f)
with q= 21 kn/m, l= 10.00 m and f= 0.965
one get N= 272 kn, which is very near on the solution which kangaroo founds in the middle of the arch (271 kn). due to the point loads this force have to get slightly higher the nearer one comes to the anchor points. this works perfect too.
but there is one irritating thing.
at the end of the catenary, near the anchor points, kangaroo gets two very different arch-forces. 281 kn in the next to last part. and 581 kn in the very last part. this is not possible and i am sure that the value of 581 kn is wrong. i calculated the example with a commercial fea-program too. it validates the kangaroo results except the first and the last one.
i think there is a problem with the calculated end length of the first (and last) element. they are twice too long as they have to be. or do i something wrong?
thank you for any reply and again for your work.
best peter
…
Added by pb to Kangaroo at 10:25am on October 22, 2011
So while working, I am first getting this error message:
Then when I click on "OK", I get this error message:
When I click on "Close" I get this one:
Then these three error screens repeat for a couple of times, and in the end I am getting a grasshopper with red canvas:
I am using 0.8.0066 version (yes, I know I need to update to the newest one, but some components I have do not work with 0.9+ version).
Any help with this? Or do I simply need more RAM?
This is my PC configuration:
Intel Core 2 Duo E4300 1800MHz motherboard MSI P4M890M3-V (MS-7255) 2x1GB DDR2 266 Mhz ASUS EAH4670 512MB Direct x 9.0c Windows XP SP3 (32bit)
It might sound strange, but is there a way I can avoid buying new PC or RAM memory?
Maybe by deleting the Panels and Param Viewers?I might be wrong, but I think the error starts when you cross over particular part of canvas (or definition to be precise) where there are a lots of Param Viewers.
Thank you.…
o Common - just like C#. But Rhino Python has a "Scripting Language Wrapper" which breaks commonly used taks down to simpler functions.
Here's a general Example:
Take a look at the code on this website http://wiki.mcneel.com/developer/rhinocommonsamples/addline). Generally it's Rhino Common code in three language to create a line. They look equally difficult.
But if you use Rhino Python Scripting you can use an simplified syntax to get the same result. It's very similar to Rhino Script.
The code would be:
import rhinoscriptsyntax as rsstart_point = rs.GetPoint("Get start point")end_point = rs.GetPoint("Get end point")line_id = rs.AddLine(start_point, end_point)
OK - No Error Tracking here, but still you can see that the syntax is much simpler. (And in the end you just have less lines of code you have to debug.
And the good thing about Rhino Python is, that you can mix these approaches. Once you reach a level where Rhino Python Script doesn't get you there, which by the way happens very rarely, you can still use the Rhino Common methods.
Also, in Python Sycripting 99% of what you probably would like to do is available as a "wrapped" script function.
Rhino Python Script is currently also better documented than Rhino Common for C# and VB.Net. If you have used Rhino VB Script before, these functions will be very familar to you.
I'm not sure, why it's currently a separate plug-in. I belive the reason is that Rhino 4 (which is supported by GH) doesn't support Rhino Python. Also it's currently WIP, so it needed to be updated more frequently than GH itself. In the long run (I believe) it might be integrated into GH as a general component
- Martin
P.S.: To use Rhino Python within GH is a little more tricky than my example - but nothing compared to developing C#
P.S.2 Here's the code with Error Tracking:
import rhinoscriptsyntax as rsdef AddLine(): start_point = rs.GetPoint("Get start point") if start_point is None: print "No start point was selected" return end_point = rs.GetPoint("Get end point") if end_point is None: print "No end point was selected" return line_id = rs.AddLine(start_point, end_point) return line_idAddLine()
…
l, you can find examples of parametric design using LB/HB, specifically the HB component pollinator workflows.
In these examples, a GH component (data recorder) is used to locally store either input parameters or output values of different model configurations and transmit them to pollinator. I can imagine, depending on how your facade is made parametric in GH, that you could save those input parameters (e.g. angle of surfaces or height of extrusion) and output variables for each iteration (e.g. annual shading).
This a search process through the design space. I do think that if you would set up the model as such, then it would be ok that the components in the PV workflow resetted after each iteration as the results would be saved. There is even a really good visualization platform Mostapha has shared to go along pollinator.
You can find examples of these workflows in the forum, simply search pollinator. I have one that I shared somewhere as well, although it was doing rudimentary things it would help.
This design space approach is a bit different than the optimization approach utilizing components like galapagos. It gives you an idea of the space of possible different desings and allows you to compare alternatives. Plus, it usually allows me to avoid all these issues of losing results between components in the workflo.
I also find it very handy and much more efficient than simply allowing a component optimize everything for me. However, it can ncrease almost exponantially (or is it geometrically, I am always bad at this) to the range and number of your input parameters. So, if each square on the wall has more than a couple of input values for a a few input parameters, I would expect this to take a long time. Thankfully, the components in the workflow will let you know exactly how many iterations.
If this method is interesting to you and you follow it I would suggest a few things to hasten the process like utilizing only the squared above and on the sides of the PV panel, since the others won't really affect shading, selecting just 2 or 3 characteristic angles for extrusions, and perhaps approximating energy production through annual shading numbers (since I imagine they have an almost linear relationship).
I do hope that I have understood what you want to do and the above information helps. I'm sure Djordje will give much better feedback on the specifics of the PV workflow. I will try and keep this page saved so that I can send over the example once I'm back at work mid of next week.
Good luck!
Kind regards,
Theodore.
…
ough the curve i use. as you can see in the image, i managed to make my chain units grow in one direction. I aim to finish with a definition which allows me to alter the growth rate according to attractors; points or curves. I have more than one question, so i will list them, and any ideas or help will be appreciated :)
now let me be more specific;
1(UNEVEN SCALING DEPENDING ON ATTRACTORS) - i can apply existing attractor based definitions (somehow) in other discussions, but the continuity of the chain breaks that way; they will be scaled depending to the attractors but i need to fix the chain manually. So my first problem is to find a method for gradual increasing and decreasing of chain units in multiple points on my curve. in the upside image, it is ok in growing on direction, but i want to achieve a result like in the image below.
2(CHAIN CREATION METHOD)-How i achieve these chains requires a manual input; either i must decide the total number of chain parts along the curve, or i specify the lengths etc. i tried to make an automation which calculates the distance between the two ends of a chain piece, and reduces some amount of it (in order to link two pieces of chain, the movement length amount should be less than the length of one chain piece for not to overlap in ends).
but when i do it, the first copy is moved the exact spot that i want from initial piece, but the rest are overlapping on end points, because my definition needs to re-calculate for each item that is going to be copied, but i found no way to fix it.
I have an idea about a definition which checks for intersections of breps and moves the intersecting items till they don't anymore, but in a wavy curve in all x,y,z dimensions; i am not able to automatize each movement direction for each piece of chain.
what i want to achieve is just creating a definition which only required inputs are a curve to define the path of the chain, and a brep that will replicate through the curve. (and if i would be able to add the uneven scaling feature from question 1, the other input should be attractors)
3(BONUS:ORIENTATION)-in this case of orienting the brep along a curve, there is a problem, because all frames are in the same orientation and it is not a realistic way of a chain to stay like that as in the image below;
as you can see, all chain parts are directed to same orientation. what i want to achieve is like in the image below, but i am not able to scale my chain parts like in question 1 and orient them as they should be in the same time, so i'm stuck here too.
I tried to explain everything in my mind in details to be as specific as possible, hope that this long post won't intimidate you. :) I added my study files. scaling chain ones are for question_1, the messed up definition for question 2 is also included. There are no specific definition files for question 3, all my oriented files have that problem.
thanks for any ideas, any help and for any efforts that you will make to enlighten me. …
umbers behave differently from the reals, in that when they are squared they give a negative result. They are written as multiples of the imaginary unit i, which is defined so that:
i*i=-1
Complex numbers are numbers which have two parts (hence the name complex) - a real part and an imaginary part.
For example:
3+4i,
or more generally:
a+bi, where a and b are some real numbers.
Well that's a definition, but I guess you might be wondering what is the point of them - I've not said anything yet about why they are interesting and useful...
Solving cubic equations was one of their first uses, but I doubt that is what most of you are interested in.
Where they really get fun is when you start looking at them geometrically.
The Argand plane is a setting that allows us to treat complex numbers a bit like vectors.
Each complex number a+bi defines a point relative to an origin (0,0), much the same as a vector with an x and y component.
Like vectors we can add and subtract them to get a new point.
But when we multiply them, unlike vectors, we add the angles (measured anti-clockwise from the positive real axis, also called the argument) and multiply the lengths (or the modulus of each number).
This all follows naturally as a consequence of the definition of i as the square root of minus one.
........
That is just dipping a toe into the great depths.
Complex number math, and in particular complex Analysis (calculus with complex numbers) is a vast subject that I obviously can't cover much of here.
If you are interested in learning more :
The Math department at Cal State Fullerton has some very nice Complex Analysis pages.
Chapters 5 and 6 of the film Dimensions covers complex numbers very visually. You can watch it online here, or read the description here.
Complex numbers on Wikipedia
on MathWorld
Hans Lundmark's complex analysis pages
The book Indra's Pearls is about making certain types of fractals with complex numbers, and includes a good introduction, along with lots of pseudocode.
To really engage with some of the true depth and power of complex numbers I particularly recommend the beautiful Visual Complex Analysis. This was the book that made me love this subject.
I'm really looking forward to seeing more designers make use of complex numbers. I think it is a wonderful tool. It is an advanced branch of mathematics, requiring some serious study to understand, but because of its strong geometric connections, I think relatively accessible to those who tend to think more visually. Now that David has included them in Grasshopper, starting to explore them should be easier than ever.…
Added by Daniel Piker at 4:38am on November 25, 2009
got today. If you were thinking how to spend the extra hour we have some stuff for you that should take around 15 minutes!
Radiance recently released the new version of 4.2.1 and short after that we had several reports about having issues with generating .gif/.tiff files from .hdr images. It turned out to be a bug in Radiance. The great Greg (Ward) and Rob (Guglielmetti) fixed the issue in less than a day and now you can download the new version which works like a charm!
Here is the direct link and here is link to github release page. All you need to do is to download the new version and install it in C:\Radiance. It will replace the current version and you should be good to go.
(WARNING: As you can see, there is no "Program Files" in the installation path! Make sure to modify installation folder.)
OK. It should take you 10 minutes to read up to here and also install the new version of Radiance, but don't stop reading! There is one more thing that you need to do. The new version of gendaymtx in Radiance is also changed and we needed to modify genCumulativeSkyMtx component to handle the changes.
You need to replace the component manually. I will attach the UserObject to this discussion so you can download it and replace it with the current one. This video shows how you can do it in 13 seconds!
Done with installation! Here is some updates about development and resources:
If you are looking to get started with Ladybug here is some good news for you. With help of So Young, videos of the Ladybug workshop from UPenn are ready to watch. I personally think that the videos are slow, so I suggest you to watch it if you are a beginner with Grasshopper and need some videos to follow along while getting used to Grasshopper. If you want to watch shorter videos check Chris's video series for Ladybug and Honeybee here.
Also Chien Si is developing a number of components for advanced HVAC modeling using the OpenStudio component. If you have been waiting to model some real HVAC systems in a parametric environment and want to test it while it is getting developed, here is your chance! Right now he is working on air side systems.
I think my 15 minutes is over! Enjoy the rest of the extra hour and have a good week.
Cheers,
Mostapha…