<div dir="ltr">There also appears to be an error in the vertical coordinate handling. In our testing here the vertical coordinate seems to be unnecessarily reversed at the bottom of the function. This results in the variable and the coordinates not corresponding to each other. Did I do something wrong here or is it really an error in the script?<br><br>Can ftp or email example script and data if needed but it's pretty run of the mill wrf output. <div><br></div><div>Alan<br><br><br><div class="gmail_quote"><div dir="ltr">On Tue, 26 Apr 2016 at 13:38 Alan Brammer <<a href="mailto:abrammer@albany.edu">abrammer@albany.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi NCL/WRF help,<div><br></div><div>Tried to use this function and came across some issues. Not extensively tested so there maybe workarounds/solutions I missed. Was only working with interpolating to pressure levels. </div><div><br></div><div><b>ncl-team: </b></div><div>Documentation isn't quite complete enough about the input field to the function. <div><br></div><div>The function uses wrf_user_getvar(nc_file,"height",-1) and tries to match this dimensionality to the passed field variable. Unless the user also knew to use -1 then this function fails internally at : </div><div><br></div><div> field_out = wrf_vintrp(field,P,tk,qvp,ght,terht(0,:,:),sfp,smsfp,\</div><div> vcord_array,interp_levels,icase,extrap,vcor,logP)</div><div> </div><div><br></div><div>It would be better for the documentation to explicitly tell the user to match the dimensionality of wrf_user_getvar(nc_file,"height",-1) or the code could be improved as below. </div><div><br></div><div><br></div><div><b>wrf-help:</b></div><div>It would be better for the function to get the correct time or times based on the input field or other argument passed to opts. </div><div><br></div><div>If people write multiple times to the same file, this limitation will make this function basically useless to a number of users (e.g. myself, theres no way my machine can read in multiple entire 4d variables when all I need is a single time). </div><div><br></div><div>I made simple edits to the function to accept a TIME argument contained in opts. </div><div><br></div><div>I’m also not convinced about how terrain height is currently handled in this function. If the user has a moving domain then this function will only use the first time? </div><div><br></div><div><br></div><div><br></div><div>Alan</div><div><br></div><div><br></div><div></div></div></div><div style="word-wrap:break-word"><div><div></div><br><br><div>
<div style="color:rgb(0,0,0);letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div style="color:rgb(0,0,0);font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><span style="border-collapse:separate;line-height:normal;border-spacing:0px"><div style="word-wrap:break-word">##############################<br>Alan Brammer,<div>Post-Doc Researcher</div><div><br></div><div>Department of Atmospheric and Environmental Sciences,<br>University at Albany, State University of New York, Albany, NY, 12222<div><a href="mailto:abrammer@albany.edu" target="_blank">abrammer@albany.edu</a><br>##############################</div></div></div></span></div></div>
</div>
<br></div></div></blockquote></div></div></div>