Re: how to avoid the warming messages in the example of lcmask_4.ncl

Guangshan,

I couldn't reproduce this problem, so I'm guessing you are not using the dataset that comes with this example.

You are getting these warnings because an unexpected type is being passed to an NCL function.

To help figure out which function is the problem, temporarily comment out the main "begin" and "end" lines in your code, and run it with the "-x" option.

   ncl -x lcmask_4.ncl

This will echo every line as it is executed, and you should be able to see which function or procedure is the problem.

Once you have this information, please email ncl-talk again and let me know which line is producing the warnings.

Thanks,

--Mary
On Nov 22, 2011, at 10:39 AM, Guangshan Chen wrote:

> Dear all,
>
> When I try the example of lcmask_4.ncl on
> http://www.ncl.ucar.edu/Applications/lcmask.shtml, I got some warming messages as the following:
>
> warning:Argument 1 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 1 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 1 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 1 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
> warning:Argument 2 of the current function or procedure was coerced to the appropriate type and thus will not change if the function or procedure modifies its value
>
> I don't like these kind of warming coming out. Is there anyway to avoid these?
>
> Thanks in Advantage!
>
> Guangshan
>
>
>
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk

_______________________________________________
ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Tue Nov 22 11:16:46 2011