[ncl-talk] NCL wrf_user_vert_interp array size and time dimensions

[Bill Ladwig]

Hi Alan,

I'm going to put in a ticket for this.  All the issues you brought up are
bugs.  For now, if all you need are values interpolated to pressure levels,
you can use the wrf_user_intrp3d functions (or wrf_interp_3d_z which is
called by wrf_user_intrp3d).  Otherwise, you'll need to hack up your copy
of WRFUserARW.ncl until we can get a fix out.

Thanks,

Bill


On Tue, Apr 26, 2016 at 4:19 PM, Alan Brammer <abrammer at albany.edu> wrote:

> 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?
>
> Can ftp or email example script and data if needed but it's pretty run of
> the mill wrf output.
>
> Alan
>
>
> On Tue, 26 Apr 2016 at 13:38 Alan Brammer <abrammer at albany.edu> wrote:
>
>> Hi NCL/WRF help,
>>
>> 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.
>>
>> *ncl-team:  *
>> Documentation isn't quite complete enough about the input field to the
>> function.
>>
>> 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 :
>>
>>  field_out = wrf_vintrp(field,P,tk,qvp,ght,terht(0,:,:),sfp,smsfp,\
>>                          vcord_array,interp_levels,icase,extrap,vcor,logP)
>>
>>
>> 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.
>>
>>
>> *wrf-help:*
>> 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.
>>
>> 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).
>>
>> I made simple edits to the function to accept a TIME argument contained
>> in opts.
>>
>> 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?
>>
>>
>>
>> Alan
>>
>>
>>
>>
>> ##############################
>> Alan Brammer,
>> Post-Doc Researcher
>>
>> Department of Atmospheric and Environmental Sciences,
>> University at Albany, State University of New York, Albany, NY, 12222
>> abrammer at albany.edu
>> ##############################
>>
>>
> _______________________________________________
> ncl-talk mailing list
> ncl-talk at ucar.edu
> List instructions, subscriber options, unsubscribe:
> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/ncl-talk/attachments/20160427/2417f547/attachment.html