CFD Online Discussion Forums

CFD Online Discussion Forums (
-   CFX (
-   -   A new error in CFX CEL expression (

Chander August 21, 2013 15:31

A new error in CFX CEL expression

1) Is there any upper limit to number of CEL expressions that can be used in CFX?

2) Is there any upper limit to number of monitor points that can be used in CFX?

3) I need to use velocity at a particular location in CEL expression. To access that value, I created a cartesian probe point and accessed Velocity w value as below:

avg vel w1 = abs((probe(Velocity w)@MPx1y1)
where MPx1y1 is a cartesian monitor point

However I get the following error before the start of iteration:
ERROR #001100279 has occurred in subroutine ErrAction. |
| Message: |
| An error: Illegal argument for callback function probe(Velocity w- |
| )@MONP266

The probe point is in liquid flow region and hence Velocity w should be defined there. How can I solve this error.

Thanks for your inputs

Best regards

flotus1 August 21, 2013 16:03

I count an odd number of brackets in the expression...

Chander August 21, 2013 16:05

Oh that is just a copy paste error. Sorry about that.

Thanks for your reply

Chander August 21, 2013 16:06

The CEL expression is

avg vel w1 = abs((probe(Velocity w)@MPx1y1))

ghorrocks August 21, 2013 18:48

Upper limit to CEL expressions - yes, but I am not sure what that is. It is certainly enough for most normal applications but I suspect if you have hundreds of them things might slow down and if you have thousands it might not work. Just give it a go and see. I also suspect some work was done in V15 beta to increase the number of allowable CEL expressions.

Upper limit to monitor points - yes, but again it will be a lot and enough for normal uses. The CCL is limited to a maximum length (not sure what it is) by the parser and if you have enough monitor points you will reach that limit.

Try "w" as the variable in your expression, not Velocity w. No guarantees, but worth a try.

Chander August 24, 2013 14:09

Thanks for your inputs

I realized that the problem was coming from the fact that CFX was revising the monitor point locations close to walls to locations on the walls. Shifting those monitor points slightly further away from wall solved the problem

All times are GMT -4. The time now is 12:41.