<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi Scott,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">There are a few issues that I'll try to explain.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">[1] The "apt-get" version of NCL is not supported by us, and is provided by an outside party. We are appreciative that this was done, but the files are put in slightly different locations that what we recommend, which can cause problems as you've seen. Normally, you should only have to set NCARG_ROOT, and not all the other NCARG_XXXXX variables that you are setting.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">[2] I think by creating the "/usr/lib/ncarg" link, you probably don't even need to set anything but NCARG_ROOT, because ncl will look in $NCARG_ROOT/lib/ncarg for all of these files by default (/usr/lib/ncarg), which you appear to have.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Please try unsetting everything but NCARG_ROOT, and let ncl-install know if you continue to have problems.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">[3] This is an older version of NCL. The current version is 6.3.0, which doesn't require that you load most of these scripts. In V6.3.0, these scripts are loaded automatically: gsn_code.ncl, gsn_csm.ncl contributed.ncl, and WRFUserARW.ncl</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Hence, if you upgrade you may not have these issues. You could choose to go this route, but I don't think there's an "apt-get" version. It's pretty easy to install NCL from a precompiled binary, which I can help you with. In the future, we hope to get NCL under "conda" (a package manager used by many beefy python packages).</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">--Mary</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jan 21, 2016 at 10:04 AM, Scott Rabenhorst <span dir="ltr"><<a href="mailto:scott.rabenhorst.ctr@nrl.navy.mil" target="_blank">scott.rabenhorst.ctr@nrl.navy.mil</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Dear NCL developer,<br>
<br>
I have installed the following NCL packages on my Debian 8.2 machine
through the apt-get interface:<br>
<font color="#3333ff"><tt>dpkg -l | grep -i ncar</tt><tt><br>
</tt><tt>ii libncarg-bin 6.2.0-3+b1 amd64 NCAR
command-language library - development tools</tt><tt><br>
</tt><tt>ii libncarg-data 6.2.0-3 all NCAR
command-language library - Data</tt><tt><br>
</tt><tt>ii libncarg-dev:amd64 6.2.0-3+b1 amd64 Development
files for the NCAR command language library</tt><tt><br>
</tt><tt>ii libncarg0:amd64 6.2.0-3+b1 amd64 NCAR
command-language library</tt><tt><br>
</tt><tt>ii ncl-ncarg 6.2.0-3+b1 amd64 NCAR
Command Language and NCAR graphics</tt></font><br>
<br>
which places package files in the following directories:<br>
<font color="#3333ff"><tt>/usr/bin/* ...</tt><tt><br>
</tt><tt>/usr/include/* ...</tt><tt><br>
</tt><tt>/usr/lib/x86_64-linux-gnu/* ...</tt><tt><br>
</tt><tt>/usr/share/doc/* ...</tt><tt><br>
</tt><tt>/usr/share/man/* ...</tt><tt><br>
</tt><tt>/usr/share/ncarg/* ...</tt></font><br>
<br>
and therefore I set environment variables in the ~/.bashrc file
accordingly:<br>
<font color="#3333ff"><tt>export NCARG_ROOT=/usr</tt><tt><br>
</tt><tt>export NCARG_MAN=$NCARG_ROOT/share/man</tt><tt><br>
</tt><tt>export NCARG_INCLUDE=$NCARG_ROOT/include</tt><tt><br>
</tt><tt>export NCARG_LIB=$NCARG_ROOT/lib</tt><tt><br>
</tt><tt>export NCARG_NCARG=$NCARG_ROOT/share/ncarg</tt><tt><br>
</tt><tt>export NCARG_COLORMAPS=$NCARG_NCARG/colormaps</tt></font><br>
<br>
Since these packages do not conform to the traditional directory
structure, I added the following symbolic link to point ncl to the
ncarg directory:<br>
<font color="#3333ff"><tt>sudo ln -s /usr/share/ncarg /usr/lib/ncarg</tt><tt><br>
</tt><tt>ls -lh /usr/lib/ncar*</tt><tt><br>
</tt><tt>lrwxrwxrwx 1 root root 17 Jan 14 14:11 /usr/lib/ncarg
-> /usr/share/ncarg/</tt></font><br>
<br>
However, I am perplexed by a bizarre error when loading scripts as
shown below:<br>
<font color="#ff0000"><tt>ncl<br>
Copyright (C) 1995-2014 - All Rights Reserved<br>
University Corporation for Atmospheric Research<br>
NCAR Command Language Version 6.2.0<br>
The use of this software is governed by a License Agreement.<br>
See <a href="http://www.ncl.ucar.edu/" target="_blank">http://www.ncl.ucar.edu/</a>
for more details.<br>
ncl 0> load
"$NCARG_ROOT/lib/ncarg/nclscripts/wrf/WRFUserARW.ncl"<br>
fatal:Could not open
($NCARG_ROOT/lib/ncarg/nclscripts/wrf/WRFUserARW.ncl)<br>
fatal:error at line 0<br>
ncl 1> load
"$NCARG_ROOT/lib/ncarg/nclscripts/wrf/WRFUserARW.ncl" <br>
</tt></font><br>
However, if I repeat the same load command again, it works the
second time. This is quite problematic when running a batch of
scripts with multiple ncl instances (e.g. ncl -nQ
SomeScriptThatCallsLoad.ncl) which all abort with an error after the
first load command. Hardcoding the path appears to solve the
immediate problem, but eventually results in errors because of other
scripts that call load with environment variables:<br>
<font color="#ff0000"><tt>ncl</tt><tt><br>
</tt><tt> Copyright (C) 1995-2014 - All Rights Reserved</tt><tt><br>
</tt><tt> University Corporation for Atmospheric Research</tt><tt><br>
</tt><tt> NCAR Command Language Version 6.2.0</tt><tt><br>
</tt><tt> The use of this software is governed by a License
Agreement.</tt><tt><br>
</tt><tt> See <a href="http://www.ncl.ucar.edu/" target="_blank">http://www.ncl.ucar.edu/</a>
for more details.</tt><tt><br>
</tt><tt>ncl 0> load
"/usr/share/ncarg/nclscripts/wrf/WRFUserARW.ncl"</tt><tt><br>
</tt><tt>fatal:Could not open
($NCARG_ROOT/lib/ncarg/nclscripts/csm/contributed.ncl)</tt><tt><br>
</tt><tt>fatal:error at line 1 in file
/usr/share/ncarg/nclscripts/wrf/WRFUserARW.ncl</tt></font><font color="#3333ff"><tt><br>
<br>
</tt></font>Although ncl errors state the above scripts cannot be
opened, file/directory permissions show everyone has read/execute
access. Furthermore, these files are verified to exist when using
the exact same environment variable syntax on the shell command
line:<br>
<font color="#3333ff"><tt>ls -lh
$NCARG_ROOT/lib/ncarg/nclscripts/wrf/*.ncl</tt><tt><br>
</tt><tt>-rwxr-xr-x 1 root root 9.7K Oct 10 2014
/usr/lib/ncarg/nclscripts/wrf/WRF_contributed.ncl</tt><tt><br>
</tt><tt>-rwxr-xr-x 1 root root 156K Oct 10 2014
/usr/lib/ncarg/nclscripts/wrf/WRFUserARW.ncl</tt></font><br>
<br>
Could you please provide some suggestions regarding what may be
going wrong? Any help would be greatly appreciated.<br>
<br>
Thanks!<span class="HOEnZb"><font color="#888888"><br>
Scott<br>
</font></span></div>
<br>_______________________________________________<br>
ncl-install mailing list<br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/ncl-install" rel="noreferrer" target="_blank">http://mailman.ucar.edu/mailman/listinfo/ncl-install</a><br>
<br></blockquote></div><br></div>