0%3ATopic%3A160646&page=1#comments
I was trying to update the old VB component to my new 0.9.0006 GH release, copying and pasting, but as I'm new in this scripting world I'm unable to solve the error bounced at the line 97 when I link the surface component.
Any suggestion??
thanks in advance!!
…
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.…
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.
…
) function if you've already got a boolean value.
This expression:
x < 12
results in exactly the same things as this expression:
If( x < 12, True, False )
If() is only really useful when you want to return non-boolean data, like so:
If( x < 12, x, 100-x )
In this case, the expression will return either x, or 100-x if x is larger than or equal to 12:
x result
1 1
2 2
10 10
11 11
12 88
13 87
14 86
18 82
70 30
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 7:22am on August 10, 2011
): 'Rhino.Geometry.TextEntity' does not contain a definition for 'FontIndex' and no extension method 'FontIndex' accepting a first argument of type 'Rhino.Geometry.TextEntity' could be found (are you missing a using directive or an assembly reference?) (line 92) 2. Error (CS1061): 'Rhino.Geometry.TextEntity' does not contain a definition for 'AnnotativeScalingEnabled' and no extension method 'AnnotativeScalingEnabled' accepting a first argument of type 'Rhino.Geometry.TextEntity' could be found (are you missing a using directive or an assembly reference?) (line 94)…