Re: debugging ncl scripts

Hi James,

Command line operators were added in the recent release of NCL. See:
http://www.ncl.ucar.edu/Document/Manuals/Ref_Manual/NclCLO.shtml

So, in your case:

ncl -x test.ncl

Will echo each NCL statement back to you, allowing you to see where the
warning messages are coming from...
Adam

James McPhee wrote:
> Hi, I'm executing a somewhat long script and sometimes I receive
> unexpected warning messages. Unfortunately the messages (like, "argument
> 0 of the current function was coerced...") don't say what function or at
> which line the warning message is originating.
> Is there an efficient way of debugging ncl scripts?
> Many thanks,
> James
> _______________________________________________
> ncl-talk mailing list
> ncl-talk_at_ucar.edu
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk

-- 
--------------------------------------------------------------
Adam Phillips			             asphilli_at_ucar.edu
National Center for Atmospheric Research   tel: (303) 497-1726
ESSL/CGD/CAS                               fax: (303) 497-1333
P.O. Box 3000				
Boulder, CO 80307-3000	  http://www.cgd.ucar.edu/cas/asphilli
_______________________________________________
ncl-talk mailing list
ncl-talk_at_ucar.edu
http://mailman.ucar.edu/mailman/listinfo/ncl-talk