[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #OVR-601731]: IDV Problems Using CF Compliant WRF Files

> Yuan,
> 
> Can you please be more specific about what you mean by "add both x and y 
> stagger dimensions back," hopefully by an example, since stagger dimensions, 
> as far as I understand dimensions, are already in my problematic file out.nc:
> 
> west_east_stag = 1002
> south_north_stag = 1002
> 
> I assume that you got my data to display properly, so maybe you can send me 
> the metadata or anything else for the file that correctly displays cross 
> sections. Actually, if you were able to send me the .nc that display 
> properly, I would be able to reverse-engineer it if needed. I can retrieve 
> the files via Globus if that would help.
> 
> Thanks!
> 
> Jim

Jim,

A little misunderstanding here, I thought you have solved the problem.

In your second out.nc, there is no x and y stagger dimesnions:

netcdf /Users/yuanho/Downloads/out (1).nc {
  dimensions:
    Time = 1;
    DateStrLen = 19;
    south_north = 1001;
    west_east = 1001;
    bottom_top = 51;
    bottom_top_stag = 52;
  variables:


This is the difference between out.nc and sandyC300000sigmaMF.nc. Could you 
help me understand why you want to run ncl to generate another stagger gridded 
output?

Yuan
> -----Original Message-----
> From: Unidata IDV Support <address@hidden>
> Sent: Friday, July 13, 2018 12:34 PM
> To: address@hidden
> Cc: address@hidden; address@hidden
> Subject: [IDV #OVR-601731]: IDV Problems Using CF Compliant WRF Files
> 
> > Yuan,
> >
> > In case you need it, I also now uploaded the sandyC300000sigmaMF.nc input 
> > file for my NCL script WRFtoIDV.ncl, which is the file that correctly 
> > displays vertical cross sections for QVAPOR and any other 3D variables.
> >
> > Jim
> 
> So the difference is to add both x and y stagger dimensions back and result 
> is now corrected.
> 
> 
> Yuan
> >
> > -----Original Message-----
> > From: address@hidden <address@hidden>
> > Sent: Thursday, July 12, 2018 7:26 PM
> > To: address@hidden
> > Subject: RE: [IDV #OVR-601731]: IDV Problems Using CF Compliant WRF Files
> >
> > Yuan,
> >
> > I added the ZNU and ZNW variables back in and the results are attached. I 
> > am also uploading the new and larger .nc file that fails to vertically 
> > scale properly on the IDV cross section plot.
> >
> > Jim
> >
> > -----Original Message-----
> > From: address@hidden <address@hidden>
> > Sent: Thursday, July 12, 2018 3:40 PM
> > To: address@hidden
> > Subject: RE: [IDV #OVR-601731]: IDV Problems Using CF Compliant WRF Files
> >
> > Yuan,
> >
> > It makes no difference if ZNU and ZNW variables are in our out with the 
> > current small file - I get the same result. I will add them back in and 
> > send you the new .nc file, but I can assure you that the result will be the 
> > same - I did a substantial amount of testing on this. I have to run now but 
> > I can send it in an hour or two.
> >
> > Jim
> >
> > -----Original Message-----
> > From: Unidata IDV Support <address@hidden>
> > Sent: Thursday, July 12, 2018 3:31 PM
> > To: address@hidden
> > Cc: address@hidden; address@hidden
> > Subject: [IDV #OVR-601731]: IDV Problems Using CF Compliant WRF Files
> >
> > > "File has been uploaded", Yuan.
> > >
> > > Jim
> > >
> > > -----Original Message-----
> >
> > Jim,
> >
> > There is no ZNU and ZNW variables, we discussed this in the earlier email.
> >
> > Yuan
> >
> > Ticket Details
> > ===================
> > Ticket ID: OVR-601731
> > Department: Support IDV
> > Priority: High
> > Status: Open
> > ===================
> > NOTE: All email exchanges with Unidata User Support are recorded in the 
> > Unidata inquiry tracking system and then made publicly available through 
> > the web.  If you do not want to have your interactions made available in 
> > this way, you must let us know in each email you send to us.
> >
> >
> >
> >
> >
> 
> 
> Ticket Details
> ===================
> Ticket ID: OVR-601731
> Department: Support IDV
> Priority: High
> Status: Open
> ===================
> NOTE: All email exchanges with Unidata User Support are recorded in the 
> Unidata inquiry tracking system and then made publicly available through the 
> web.  If you do not want to have your interactions made available in this 
> way, you must let us know in each email you send to us.
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: OVR-601731
Department: Support IDV
Priority: High
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.