[AbhishekShingalaCFD]

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)

[fluid23]

It would help if you showed the definitions of these functions.

[AbhishekShingalaCFD]

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.

[fluid23]

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.

[AbhishekShingalaCFD]

I found the reason, I was unnecessarily defining functions in user field function, which could also define in report>>Expression.

[LuckyTran]

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.

[cwl]

Can any ambiguous function found in both report and field function creates problem?

Yes, it can. And it will.

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.