|
[Sponsors] |
Can any ambiguous function found in both report and field function creates problem? |
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
May 12, 2021, 05:06 |
Can any ambiguous function found in both report and field function creates problem?
|
#1 |
New Member
Abhishek
Join Date: Sep 2020
Location: Magdeburg, Germany
Posts: 10
Rep Power: 6 |
What things should I need to take care of if I am getting warning in Star CCM+ output window as mentioned below:
//Warning: Function "eta_T" is ambiguous, found in multiple sources: 'Field Functions' and 'Reports' //Warning: Function "H_HPO" is ambiguous, found in multiple sources: 'Field Functions' and 'Reports' Additional Information: These both functions are my objective functions, which I want to monitor and plot over iterations (for steady case) and add as a stopping criterion (when these both function values become stable... simulation converges...). Definition of field function: eta_T= function(input parameter, parameter obtained during simulation(e.g. volume fraction of oil)) 1. I created user field function eta_T=1-(Vol.fraction at outlet/vol.fraction at inlet) 2. Then I created a report. 3. Then I created a monitor and plot. 4. Over the number of iteration these value will improve. I did that to observe this value over an iterations (steady case) and then set into stopping criteria. Similarly the other objective function = function (input parameter, parameter value obtained during imulation) Last edited by AbhishekShingalaCFD; May 12, 2021 at 13:48. Reason: More helpful |
|
May 12, 2021, 13:27 |
|
#2 |
Senior Member
Matt
Join Date: Aug 2014
Posts: 947
Rep Power: 18 |
It would help if you showed the definitions of these functions.
|
|
May 12, 2021, 13:52 |
|
#3 |
New Member
Abhishek
Join Date: Sep 2020
Location: Magdeburg, Germany
Posts: 10
Rep Power: 6 |
Hello Matt, thanks for reply.
I have tried to explain definition in the questions. I am wondering simulation still runs fine (because these are just warning). Furthermore, I have experimental data also, so perhaps I will compare simulation result soon to check if these warning has any effect on solution and should I rely on the result or not. Meanwhile, if you can guide further than it would be helpful. |
|
May 12, 2021, 13:56 |
|
#4 |
Senior Member
Matt
Join Date: Aug 2014
Posts: 947
Rep Power: 18 |
Without seeing the actual text that you entered that Star-CCM+ finds ambiguous, I cannot be of much help. If you can share the definitions of these field functions, perhaps someone will be able to spot the issue.
|
|
May 12, 2021, 15:30 |
|
#5 |
New Member
Abhishek
Join Date: Sep 2020
Location: Magdeburg, Germany
Posts: 10
Rep Power: 6 |
I found the reason, I was unnecessarily defining functions in user field function, which could also define in report>>Expression.
|
|
May 12, 2021, 16:15 |
|
#6 |
Senior Member
Lucky
Join Date: Apr 2011
Location: Orlando, FL USA
Posts: 5,760
Rep Power: 66 |
You have both a field function and a report with the same name. Usually this does not happen because star will give them default names that have function and report in their names unless you manually go in and rename their named references to be the same.
|
|
May 13, 2021, 00:00 |
|
#7 | |
Senior Member
Chaotic Water
Join Date: Jul 2012
Location: Elgrin Fau
Posts: 438
Rep Power: 18 |
Quote:
As soon as your simulation becomes reasonably complicated and customized containing more than few Field Functions and Reports referencing each other - you'll get very confused about which function or report (having the same name) you're calling inside another function or report. Debugging and unraveling such a tangle will be very painful. Last edited by cwl; May 13, 2021 at 06:20. |
||
Tags |
star ccm+, steady, user field functions |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Cannot evaluate field function Density | karahan | STAR-CCM+ | 5 | February 25, 2021 12:20 |
Field function for force report's vector position (X, Y, Z) | Allante | STAR-CCM+ | 2 | December 10, 2020 12:25 |
field function report new value each iteration | hebeldebel | STAR-CCM+ | 7 | September 6, 2017 03:01 |
Field function | lcg44 | STAR-CCM+ | 1 | November 30, 2011 00:13 |
Force Report help~ or maybe Custom Field Function | sailor | FLUENT | 0 | April 13, 2011 04:45 |