<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi NCL/WRF help,<div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class=""><b class="">ncl-team: </b></div><div class="">Documentation isn't quite complete enough about the input field to the function. <div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class=""> field_out = wrf_vintrp(field,P,tk,qvp,ght,terht(0,:,:),sfp,smsfp,\</div><div class=""> vcord_array,interp_levels,icase,extrap,vcor,logP)</div><div class=""> </div><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class=""><br class=""></div><div class=""><b class="">wrf-help:</b></div><div class="">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 class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class="">I made simple edits to the function to accept a TIME argument contained in opts. </div><div class=""><br class=""></div><div class="">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 class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Alan</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""></div></div></body></html>