d 'outletBoundary' components in which the 'temperatures_' represents?
The 2nd ques is more about thinking how to achieve more potentials by BF. I am doing a project that is trying to implement the construction method of 'DOUBLE-GLAZED' facade, which will conduct air flow inside a building and save more energy. Since I also use LB&HB for time-based analyses, so I`m wondering if BF could use time-based-srf-temperature to achieve a more dynamic simulation in a day, let`s say, a hot summer day, 10:00 to 16:00?
And the last what is the definition of these recipes(pic no.2)? what do they mean?
Thanks in advance for the helps!
Best wishes,
Lei…
ragazzi ciao =) , una domanda. Ma i file che vengono nominati nel manuale, dove li posso trovare? Perchè quando ho scaricato il manuale mi è uscito solo il pdf. (es. pag 89)
Added by chiar molino at 11:10am on November 1, 2017
see, the results indicated in the error for pressure are, well I don't think I know the name for those numbers. But values of XE+118 mean the simulation was diverging. I would recommend you to update BF, if you haven't already, re-run the case and test after.
Also, you can post your mesh settings here. Most other times is mesh quality causing this.
Kind regards,
Theodore.…
ng long in the x axis and three in the y and they don't all intersect each other... I wrote a script to Boolean difference them but its not working like i want it to . I included a rhino result that id like to achieve in the file. THX -ethan
heres the script:
import rhinoscriptsyntax as rs
b1 = []for i in range(b1L): b1.append (x)print b1bb= len(b1)print bbb2 = []for j in range(b2L): b2.append (y)print b2bc = len(b2)print bc
def bool ():....for i in range (bb):........for j in range(bc):............a = rs.BooleanDifference( b1,b2, False).....return (a) a = bool ()…
nt B2[i] so B1[i]<=0 means no new connections allowed for point i ,so point i is deleted from B1, B2 updated accordingly.
Initialization:
B1: max number of connections x number of points
B2: all the points
B3: nothing (well null or something, need to create the branch)
Algo:
Get first point in B2, get his allowed number of connections N in B1, find N closest points in B2, create lines in B3, update B2 accordingly. Erase points with max connections (including the first point)
Next
Stop when no points available
At end of loop, B3 stores the created lines.
…
he potential of BF to assess such cases. In your search, try and be specific on what you want, cause validation can focus on codes (i.e software environments like OF and Fluent), solvers (e.g. RNG vs kEpsilon vs kOmega, etc.), meshers, and so many more. Additionally, I'm sure there's a lot of CFD studies of Atrium spaces.
Myself, I haven't been involved in any validation studies as I have always used CFD on the practical side of things. Therefore, I always trusted OF since it has been heavily validated over the years.
The beauty of BF, or at least its end goal, is that you can easily test design alternatives directly from a friendlier and possibly better-known environment of Rhino3D.
I would suggest therefore to just try things out. Design your geometry, in this case the atrium, in Rhino. Decide which are the parameters that you wish to investigate and incorporate those to a GH definition that produces different design alternatives for the range of those parameters (i.e. your parametric model). Then run the cases through BF. There's a couple of examples that come with BF and a few others users are providing either here or on github.
I'm afraid trial and error is painful with CFD but it's the best way forward. Also, I suggest you bookmark cfd-online.com and skim through everything in there. Most if not all of what we are discussing has been discussed there.
Good luck!
Kind regards,
Theodore.
…
ases where you have angled shades and the component is doing trigonometry to figure out how close the blinds could be to the glass without touching. I just re-wrote the code so that, now you cannot have the blinds closer to the glass than half of the blind slat depth, which seems to be the limit of what E+ will tolerate.
Also, E+ does not like it when you input blinds that are perfectly at 90 degrees so I changed the component to automatically write out shades at 89 degrees when you connect up 90.
Using the Shade geometry as context worked perfectly for me and I am not sure what was wrong in your situation.
See your working file attached.
-Chris…