Re: PyNGL-NCL interferance

From: Mary Haley <haley_at_nyahnyahspammersnyahnyah>
Date: Mon Jan 14 2013 - 14:28:31 MST

Hi Sam,

I think you just need to set the NCARG_ROOT environment variable (via setenv or export) to the root directory (~/usr) of where you installed NCL.

  setenv NCARG_ROOT /home/slha/usr

  export NCARG_ROOT= /home/slha/usr

PyNGL shouldn't require any settings, but if that's giving you grief, then for PyNGL you can try
setting the PYNGL_NCARG environment variable to /home/slha/usr/lib/python2.4/site-packages/PyNIO/ncarg.

If this doesn't help, then can you type the following and send me the output:

   which ncl
   env | grep NCARG
   env | grep PYNGL
   ncargpath bin
   ncargpath root


On Jan 14, 2013, at 5:44 AM, <> <> wrote:

> Hi,
> In compiled NCL (some time ago) into my home directory under ~/usr. I later did the same with PyNGL, putting into my local site-packages. I now find that when I run NCL scripts, they fails as NCL appears to be picking up files associated with PyNGL, see below.
> warning:TextItem:libncarg Error:PLCHHQ/PCFOPN - ERROR OPENING PWRITX DATA FILE /home/slha/usr/lib/python2.4/site-packages/PyNIO/ncarg/da.../Plotc
> Any suggestions as to how I clean up the mess, preferrably without recompiling both packages, or have I overwritten an NCL file with something associates with PyNGL?
> Thanks,
> Sam.
> Sam Hawkins
> R&D Engineer
> Vattenfall Research & Development
> _______________________________________________
> pyngl-talk mailing list
> List instructions, subscriber options, unsubscribe:

pyngl-talk mailing list
List instructions, subscriber options, unsubscribe:
Received on Mon Jan 14 14:28:42 2013

This archive was generated by hypermail 2.1.8 : Mon Jan 14 2013 - 14:34:44 MST