This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Josh- > The dataset is at http://www.meteo.psu.edu/~jmg498/wrfdatahgt2.v5d. What's > odd > is when you plot U10/V10 vectors using the grid menu, it works fine. But if > you used the ones under derived in the 2D field, it comes up with an error. It ends up being a problem with the no units again. U10 and V10 are aliases for grid relative u and v winds. So, the derived field is to create true winds and that code expects units convertible with m/sec which the Vis5D units are not. The 3D Grid derived field is for grid relative flow vectors not true. You can use the Grids->Create flow vectors formula and select U10 and V10 for now. I've changed the code to account for these Vis5D units and the fix will be in the next successful nightly build. > While I've got you, you wouldn't by chance know of a good golor scheme for > turbulent kinetic energy (TKE_MYJ variable from WRF) for use in the IDV, would > you? None of the default schemes I work try and since the values of TKE seem > to change so slightly, I can't seem to modify the scheme to create one very > well either. Sorry, I don't. In the file you sent, it looks like TKE_MYJ varies from .1 to 2.1. Is there a particular area you are trying to highlight? Have you tried setting the range on the color bar to accentuate the area of interest? For example, if you are trying to highlight the area between 1.8 and 2, then set the color range (right click on the color bar in the legend and select Change Range...) to be 1.8 to 2.0 and select a color table with good contrast between the ends (VisAD works pretty well). Values less than 1.5 will be the same color as 1.5 and values > than 2 will be the same color as 2. Don Murray > On Tue, Apr 22, 2008 10:29 AM, "Unidata IDV Support" > <address@hidden> wrote: > > > Hi Josh- > > > >> Thanks so much for your help! Unfortunately I couldn't get it to compile. > > I > >> got the following errors: > >> > >> IPO Warning: can not find "ARWpost.o" > >> IPO Warning: can not find "input_module.o" > >> IPO Warning: can not find "output_module.o" > >> IPO Warning: can not find "v5d_module.o" > >> IPO Warning: can not find "process_domain_module.o" > >> IPO Warning: can not find "module_interp.o" > >> IPO Warning: can not find "module_basic_arrays.o" > >> IPO Warning: can not find "module_diagnostics.o" > >> IPO Warning: can not find > >> > >"/home2/jmg498/ARWposttest/ARWpost/../WRFV3/frame/module_internal_header_util.o" > >> IPO Warning: can not find > >> "/home2/jmg498/ARWposttest/ARWpost/../WRFV3/frame/module_machine.o" > >> IPO Warning: can not find > >> "/home2/jmg498/ARWposttest/ARWpost/../WRFV3/frame/pack_utils.o" > >> IPO link: can not find -lwrfio_int > >> ifort: error: problem during multi-file optimization compilation (code 1) > >> make: [ARWpost.exe] Error 1 (ignored) > >> > >> I first tried to compile it using WRFV2 but then realized it likely needed > >> WRFV3 so I built and installed WRFV3 then ran the ARWpost configure. I > >> even tried copying over the old configure.arwp file from the current > >> version of ARWpost that is compiled and changed the WRF directory to WRFV3 > >> but that didn't work either (same errors). > > > >Yes, it looks like there is a big difference between 2.2 and 3.0 and > >I don't have any experience compiling either. The only suggestion > >I have is to make sure you've done a make clean or whatever to > >get a fresh start. > > > >> Intersetingly, with the IDV, I don't think the unit exception for the flow > >> display was due to missing units. When I went to Data -> Formulas -> > >> Grids -> Make Flow Vectors and chose the U10 and V10 data from the 2D > >> grid, it plotted them up. But if I go directly to "derived" and try to do > >> it, it errors out. Could it be an issue with how IDV is deriving the > >> field? > > > >Can you post the file that has this problem. The one I got before had > >all 0 for the U component. > > > >Thanks. > > > >Don > > > >> > >> On Thu, Apr 17, 2008 12:20 PM, Don Murray <address@hidden> wrote: > >> > > >> Josh- > >> > > >> >I got this tar file from the ARW support people which should > >> >support adding units to the Vis5D file. Can you try it out? > >> >Thanks. > >> > > >> >Don- > >> > > >> >ARWpost_test.tar.gz > >> > > >> > >> > >> > >> > >> > >> > > > > > >Ticket Details > >=================== > >Ticket ID: COT-972342 > >Department: Support IDV > >Priority: Normal > >Status: Open > > > > > > > > > > > > > > Ticket Details =================== Ticket ID: COT-972342 Department: Support IDV Priority: Normal Status: Open