[RobR_CFD]

Hello most learned colleagues,

Looking for some help....

I have created a large number of rakes in my simulation domain using TUI via a spreadsheet. That was the easy part.

What I would like to do now is created a velocity report (specifically X-velocity) for each of the rakes.

I imagine it should be via the /report commands, but I can't see the sub commands that align with the surface reports option, specifically facet average.

Would any kind person out there be able to give me an example of the command line to do so?

Thanks

RobR

[RobR_CFD]

Getting there...
Looking in the wrong spot... its under /solve/report-definition/add
but I'd still like some help with the syntax post above!

[AlexanderZ]

could you clarify:
you want to make pictures of contours?
it that case you should create objects first:
THESE are commands for journal

(ti-menu-load-string (format #f "display objects create vector \"vector_xy\" ****continue with information from your case *****\n"))
(ti-menu-load-string (format #f "display objects create contour \"x_velocity\" field x-velocity****continue with information from your case *****\n"))

optinal settings:

	(ti-menu-load-string (format #f "display views camera projection orthographic"))
	(ti-menu-load-string (format #f "display set picture x 1920"))
	(ti-menu-load-string (format #f "display set picture y 1440"))
	(ti-menu-load-string (format #f "display set lights head no"))
	(ti-menu-load-string (format #f "display set lights light no"))
	(ti-menu-load-string (format #f "display set lights set-light 0 no 0.5 0.5 0.5 no 1 1 1"))
	(ti-menu-load-string (format #f "display set picture color-mode color"))
	(ti-menu-load-string (format #f "display set picture driver png "))

write picture to file, from "front view, you may put your own view (but create and read it in advance):

	(ti-menu-load-string (format #f "display set lights head yes"))
	(ti-menu-load-string (format #f "display objects display vector_xy"))
	(ti-menu-load-string (format #f "view restore-v front"))
	(ti-menu-load-string (format #f "display save-picture \"xplane_time~a.png\" " (rpgetvar 'flow-time)))

or you want to get average values of x-velocity?

(ti-menu-load-string   (format #f "report surface-integrals area-weighted-avg ****face name here*** () x-velocity yes my_x_velocity.srp q q"))

how are you gonna get it? during simulation or you've made all calculation and have all data already?

how to use TUI:
type "report" in console, press enter -> you will get the list of all available options

[RobR_CFD]

AlexanderZ,

You are a good mate to come through with that awesome info!!

Clarification - I just want the velocity value, not a picture - text only!

I see from your example for the value only, it looks to be you are writing this to a file?
As I have about 30 monitor points, I don't want to write 30 files - just one.

Can I just have the velocity monitor created at this point via TUI similar to as you have shown?. I can manually aggregate into a result file using GUI for low effort. My pain point is creating the large number of velocity monitors only.

Thanks in advance!!

Cheers

Rob

[AlexanderZ]

if you know coordinates of points in advance, you may create monitor points in TUI -> line 1

define report definitions with these points -> line 2

and define file to store the data from these points -> line

*separate report definitions names with space symbol*

(ti-menu-load-string (format #f "surface point-surface ***point-name-1*** 0 0 0 q" )) ;;; 0 0 0 are coordinates x y z

(ti-menu-load-string   (format #f "solve report-definitions add file1 surface-areaavg surface-names ****point-name-1*** () per-surface? no field x-velocity q q q"))

(ti-menu-load-string   (format #f "solve report-files add ***file_name***  active? file-name .\***file_name***.out frequency 1 frequency-of time-step itr-index 1 name flow-time ***file_name*** print? yes report-defs ****point-name-1*** ****point-name-2*** ****point-name-3*** () run-index 0 q q q"))

you may copy paste this code to console directly, or create journal file .jou (or even text file .txt) and read it
File -> read -> journal -> choose file

[RobR_CFD]

Beautiful - I think I get it!
Thanks Alexander
Have a great day!

[RobR_CFD]

okay, this is starting to drive me nuts. I can't see what I'm missing here??

>  (ti-menu-load-string (format #f "solve report-definitions add vx-r1 surface-names plane-inlet () per-surface? no field x-velocity q q q"))
solve report-definitions add vx-r1 surface-names invalid command [surface-names]
plane-inlet () per-surface? no field x-velocity q q q#t

any hints?

PS... I already have a point called "plane-inlet", and I want to create a velocity monitor at that point called "vx-r1"

Thanks

[AlexanderZ]

(ti-menu-load-string (format #f "solve report-definitions add vx-r1 surface-areaavg surface-names plane-inlet () per-surface? no field x-velocity q q q"))

I've forgot surface-areaavg in the command

[RobR_CFD]

Awesome - I owe you a beer.

[IBC]

Hi - I'm trying to do something similar. I want to monitor the fluid velocity magnitude at different locations. What would change in the command you provided (I copied it below)?

(ti-menu-load-string (format #f "surface point-surface ***point-name-1*** 0 0 0 q" )) ;;; 0 0 0 are coordinates x y z

(ti-menu-load-string (format #f "solve report-definitions add file1 surface-areaavg surface-names ****point-name-1*** () per-surface? no field x-velocity q q q"))

(ti-menu-load-string (format #f "solve report-files add ***file_name*** active? file-name .\***file_name***.out frequency 1 frequency-of time-step itr-index 1 name flow-time ***file_name*** print? yes report-defs ****point-name-1*** ****point-name-2*** ****point-name-3*** () run-index 0 q q q"))


Thank you!

[RobR_CFD]

Hi IBC,

This is not a direct answer to your question, but something I would like to share - might be of use.
I write my scripts using direct TUI command rather than using the "ti-menu-load" setup.
Makes it a bit easier to read. I understand there are some reasons to go down the other path but it hasnt been an issue for me.
I have attached a sample script for running an LES sim based on a pre-configured case file. Basically I build my mesh and load it into a case on desktop, and do the rest on HPC. That way I can do tweaks to the flow conditions, time steps etc all remotely in a single case. Anyhow thats my setup.
Because I do it that way, I have gone to some trouble with commenting in detail throughout the script. Thats where I think some of the value is in looking at what the different command strings are doing.
Things like "inlet" conditions change in format based on things like the turbulence model. So if you use SAS instead of LES, the combinations of "n n n y n" etc will change. Bit of a trap. I will be adding descriptor in my scripts for those in future.
I will have a specific look at your request when I get some time.
Cheers
RobR

[IBC]

Hi Robr - I also write my scripts using TUI commands and I understand that format better. Im also running my simulations in a Supercomputer. I create the case file and the scripts.
I am trying to monitor/report the velocity magnitude at different points and save that in 1 file.

I know this command: "report/volume-integrals/mass-avg" but the issue is that I need specific locations within the fluid in a 3D geometry.

Thanks,
IBC

[RobR_CFD]

Hi IBC,

Thats fairly easy to do.

First create the point for the report......
say we want a point called "p1" at coords x , y , z

/surface/point-surface p1 x y z

Then create a report definition for that point.
Say you want the x velocity and call the report p1-vx

/solve/report-definitions/add p1-vx surface-facetavg field y-velocity surface-names p1 () q

Finally send to output text file. Say you have done about for 3 points, p1, p2, p3 and have p1-vx, p2-vx, p3-vx. Call the report "result" and text output file "result.txt".

/solve/report-files/add result frequency 1 report-defs p1-vx p2-vx p3-vx () file-name "result.txt" q

Let me know if that gives you what you need.
I can go through some of the command switches in detail if you need.
Once you have a hang of basics, best way is to trial via listing tui options at each level of operation.

Cheers

RobR

[IBC]

RobR - Thank you for your help. I will try it.

[IBC]

Hi RobR - I'm a getting this error: myid (17): Fatal signal raised sig = SIGSEGV.

[RobR_CFD]

Not sure that is related to above.
Are you running on HPC?
If so you should get a *.trn file generated.
That is a transcript file of console from Fluent run.
If there is an issue with the TUI script you will find it in there.
If you want, post it online and I can have a look.
The other thing I would recommend....
The *.trn is the console from Fluent.
What I also do is pipe the run like a screen echo to a file that I can do debugging. I learnt that from an earlier version of Fluent which did not auto generate the *.trn.
Sometimes can be helpful in seeing where errors are generated.

[RobR_CFD]

found this....



fluentError: received a fatal signal (Segmentation fault).

might help.

[IBC]

Hi RobR - Im running this on a supercomputer using a batch script.
I typed the commands in the console, not in my script.

Below is the .trn file. I'm only exporting the velocity magnitude at two points every iteration. I'm not sure why it is saying that the characteristic-vibrational-temperature is unkown.

Thank you!

--------------------------------------------------------------------------------------
ID Hostname Core O.S. PID Vendor
--------------------------------------------------------------------------------------
n56-83 o0217.ten.osc.edu 28/28 Linux-64 27765-27792 Intel(R) Xeon(R) E5-2680 v4
n28-55 o0216.ten.osc.edu 28/28 Linux-64 30589-30616 Intel(R) Xeon(R) E5-2680 v4
n0-27 o0215.ten.osc.edu 28/28 Linux-64 21908-21935 Intel(R) Xeon(R) E5-2680 v4
host o0215.ten.osc.edu Linux-64 18124 Intel(R) Xeon(R) E5-2680 v4

MPI Option Selected: ibmmpi
Selected system interconnect: InfiniBand
--------------------------------------------------------------------------------------

Cleanup script file is /users/PAS1719/heldmanlab/025m_FullyOpen_Pointreport/cleanup-fluent-o0215.ten.osc.edu-18124.sh

> file/read-case-data 025m_velocitymonitor.cas

Multicore processors detected. Processor affinity set!

Reading "025m_velocitymonitor.cas"...

Buffering for file scan...



7850098 tetrahedral cells, zone 9, binary.
Warning: reading 5 partition grid onto 84 compute node machine;
will auto partition.
7850098 cell partition ids, zone 9, 5 partitions, binary.
15647876 triangular interior faces, zone 10, binary.
100096 triangular wall faces, zone 11, binary.
452 triangular velocity-inlet faces, zone 12, binary.
1817 triangular pressure-outlet faces, zone 13, binary.
1825 triangular pressure-outlet faces, zone 14, binary.
450 triangular velocity-inlet faces, zone 15, binary.
1334447 nodes, binary.
1334447 node flags, binary.

Warning: the rp-transition-model option is not available in this solver

Building...
mesh
auto partitioning mesh by Metis (fast),
distributing mesh
parts............................................. .....,
faces............................................. .....,
nodes............................................. .....,
cells............................................. .....,
inter-node communication reduction using architecture-aware remapping: 70%
bandwidth reduction using Reverse Cuthill-McKee: 93492/1652 = 56.5932
materials,
interface,
domains,
mixture
zones,
walls
int_fluid
left_inlet
right_inlet
left_outlet
right_outlet
fluid
Warning: property-info: unknown property: characteristic-vibrational-temperature

Warning: property-info: unknown property: characteristic-vibrational-temperature

Warning: For compressible (ideal and real) gas models with buoyancy,
it is recommended that you use a specified operating density value of zero:
define/operating-conditions/operating-density? yes 0.

parallel,
Warning: property-info: unknown property: characteristic-vibrational-temperature

Warning: property-info: unknown property: characteristic-vibrational-temperature

Done.

Reading "025m_velocitymonitor.dat"...



Parallel variables...

turbulent viscosity limited to viscosity ratio of 1.000000e+05 in 319747 cells
Done.

> solve/iterate 1
iter continuity x-velocity y-velocity z-velocity energy k epsilon time/iter
! 5818 solution is converged

Error: eval: unbound variable
Error Object: global

Error: eval: unbound variable
Error Object: global

================================================== ============================

Node 25: Process 21933: Received signal SIGSEGV.

================================================== ============================

================================================== ============================

Node 15: Process 21923: Received signal SIGSEGV.

================================================== ============================

================================================== ============================

Node 17: Process 21925: Received signal SIGSEGV.

================================================== ============================

================================================== ============================

Node 9: Process 21917: Received signal SIGSEGV.

================================================== ============================

================================================== ============================

Node 49: Process 30610: Received signal SIGSEGV.

================================================== ============================

================================================== ============================

Node 2: Process 21910: Received signal SIGSEGV.

================================================== ============================

================================================== ============================

Node 81: Process 27790: Received signal SIGSEGV.

================================================== ============================


===============Message from the Cortex Process================================

Fatal error in one of the compute processes.

================================================== ============================

================================================== ============================

Node 52: Process 30613: Received signal SIGSEGV.

================================================== ============================

================================================== ============================

Node 74: Process 27783: Received signal SIGSEGV.

================================================== ============================

[RobR_CFD]

Hey IBC - looks like your playing with thermal models which I am not familiar with.
Send me your TUI script and I'll see what might be triggering it.