-
Content Count
8 -
Joined
-
Last visited
Posts posted by Mr. Sebastian Weickgenannt
-
-
Hi Tanzil,
In addition to what my collegues mentioned, you should be aware, that the Sobol does NOT give you (pseudo-) random numbers.
It is a sequence, which will always return the exact same values, if you don't change the boundaries for the design variables. Therefore the generation of a Sobol design engine within a feature will always yield the same n sets of p1 and p2 each time you execute the feature.
The Sobol sequence covers the design space way more evenly than pseudo-random numbers and might therefore be well suited for your task (?).
Read more on the Sobol here: http://en.wikipedia.org/wiki/Sobol_sequence
If you want pseudo-random numbers instead, you could use the command rand(), which returns values between zero and one. I.e. rand()*4+3 returns pseudo-random values between 3 and 7.
Cheers,
Sebastian
-
Hi Adam,
what you did is almost correct. Unfortunately you just selected the wrong axis for the area calculation, so the zero result is correct, but not wat you wanted.
The correct command would be:
MySections.getSections().at(X).getArea(2, 0, Z0, ZWL)
The first argument defines the axis for the area calculation, in this case 2 for the z-axis.
The second argument sets the area plane, here X (Y,Z).
The last two arguments specify the start and end position for the calculation with respect to the selected axis, in this case from the lowest point (i.e. Z0=0) to the waterline (ZWL=draft).
Of course you could compute the area of the complete section instead of only the submerged part by setting these bounds higher. Or use the y-axis instead for some reason.
Cheers,
Sebastian
edit: typos
- 1
-
Hi Karsten,
I like the idea, this is very useful!
I modified your feature to include optional settings. Now you can display objects with only clients and/or only suppliers as well. Not just zeros in the table now ;-)
Also the you get some numerical output and the current Table Viewer is turned visible automatically.
Cheers,
Sebastian
-
No updates on the multiRegionHeater error at this time.
Hi Brendan,
multiRegion postprocessing for OpenFOAM isn't really supported at this time.
Maybe there's some way to extract regions as single cases in OF, but generating VTKs or ensight files and importing those should do the trick as it is.
Cheers,
Sebastian
saving values for every variant after optimization process [sobol]
in Feature Programming
Posted · Report reply
Great!
Good luck!
Cheers,
Sebastian