<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">Tom,</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">
NCL does not have a function to return the file variable's related path.</div><div class="gmail_default" style="font-family:verdana,sans-serif">We have never thought of such a function, as in NCL, one has to provide</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">explicitly a file name to addfile or files to addfiles, so it is assumed that</div><div class="gmail_default" style="font-family:verdana,sans-serif">the users know which the file path with correspond file-handle created.</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Surely that each file variable created in NCL has its file-path info associated</div>
<div class="gmail_default" style="font-family:verdana,sans-serif">with, but there is no direct function to return the path back to the user</div><div class="gmail_default" style="font-family:verdana,sans-serif">(as stated above that NCL assumes users already know this info).</div>
<div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">By request, we can certainly create a function which will return the</div><div class="gmail_default" style="font-family:verdana,sans-serif">
file-path of the file variable.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Thanks,</div><div class="gmail_default" style="font-family:verdana,sans-serif">
<br>Wei </div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><font face="tahoma, sans-serif">================================================</font><div><font face="tahoma, sans-serif">1850 Table Mesa Dr.</font></div>
<div><font face="tahoma, sans-serif">Boulder, CO 80307</font></div><div><font face="tahoma, sans-serif">Phone: 303-497-8924</font></div></div></div>
<br><br><div class="gmail_quote">On Thu, Aug 7, 2014 at 8:51 PM, Tom Roche <span dir="ltr"><<a href="mailto:Tom_Roche@pobox.com" target="_blank">Tom_Roche@pobox.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<a href="http://www.ncl.ucar.edu/Support/talk_archives/2008/0230.html" target="_blank">http://www.ncl.ucar.edu/Support/talk_archives/2008/0230.html</a><br>
[Dennis Shea Tue, 12 Feb 2008 06:33:50 -0700]<br>
>> You can not determine the path/file to which "file" is pointing.<br>
<br>
Is this still the case, API-wise? Because certainly a file (or as I prefer to say, a filehandle) knows its path:<br>
<br>
$ ncl -V<br>
6.2.0<br>
$ ncl<br>
ncl 0> refr_fp = "/project/inf35w/roche/met/24-layer/WRF_2008_24aL/12US1/mcip_out/METBDY3D_071222"<br>
ncl 1> refr_fh = addfile(refr_fp, "r")<br>
ncl 2> printVarSummary(refr_fh)<br>
<br>
Variable: refr_fh<br>
Type: file<br>
File path: /project/inf35w/roche/met/24-layer/WRF_2008_24aL/12US1/mcip_out/METBDY3D_071222<br>
Number of global attributes: 33<br>
Number of dimensions: 5<br>
Number of variables: 18<br>
<br>
<a href="http://www.ncl.ucar.edu/Support/talk_archives/2008/0233.html" target="_blank">http://www.ncl.ucar.edu/Support/talk_archives/2008/0233.html</a><br>
[Jan Ploski Tue, 12 Feb 2008 14:38:51 +0100]<br>
> I can pass the path used to create the file object together with the [filehandle]<br>
> to my procedure [but it's] rather redundant and ugly<br>
<br>
agreed! Tom Roche <<a href="mailto:Tom_Roche@pobox.com">Tom_Roche@pobox.com</a>><br>
_______________________________________________<br>
ncl-talk mailing list<br>
List instructions, subscriber options, unsubscribe:<br>
<a href="http://mailman.ucar.edu/mailman/listinfo/ncl-talk" target="_blank">http://mailman.ucar.edu/mailman/listinfo/ncl-talk</a><br>
</blockquote></div><br></div>