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

[python #OQG-244028]: Python help

No worries. I'm still trying to figure out why a catalog resolved with an 
incorrect
path. It turns out the catalog with _anl points to the forecast grids, and not 
the
analysis grids. Even this one:

http://thredds.ucar.edu/thredds/catalog/grib/NCEP/GFS/Global_0p25deg_abcdefg/latest.xml

points to the latest forecast grids. Looks like there is a bug in the latest 
service of the TDS.

Cheers,

Sean

> Nevermind.. I think I misunderstood what the 250 hPa script was doing. I 
> thought it was plotting an analysis (probably because that's what I wanted to 
> do and brain just assumed..) but I guess what it is doing is plotting a map 
> that is closest to whatever time it is now, regardless of whether it's a 
> forecast or analysis from the most recent file.
> 
> 
> More coffee might help.
> 
> Pete
> 
> 
> 
> <http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>--
> Pete Pokrandt - Systems Programmer
> UW-Madison Dept of Atmospheric and Oceanic Sciences
> 608-262-3086  - address@hidden
> 
> 
> ________________________________
> From: Unidata Python Support <address@hidden>
> Sent: Tuesday, November 14, 2017 11:10 AM
> To: Pete Pokrandt
> Cc: address@hidden; address@hidden; address@hidden
> Subject: [python #OQG-244028]: Python help
> 
> Greetings Pete,
> 
> It looks like there is an issue with the url to the catalog you are reading 
> in. In your
> script you have:
> 
> http://thredds.ucar.edu/thredds/catalog/grib/NCEP/GFS/Global_0p25deg_anl/latest.xml
> 
> but it should actually be
> 
> http://thredds.ucar.edu/thredds/catalog/grib/NCEP/GFS/Global_0p25deg_ana/latest.html
> 
> That's 0p25deg_ana vs 0p25deg_anl...no idea why 0p25deg_anl returns 
> something, but it looks
> like it is returning a dataset from the forecast grids of the 0.25 deg GFS. I 
> need to dig into that
> a bit further to understand what is happening there (maybe a misconfigured 
> catalog).
> 
> Also, you need to remove the time portion of the ncss query, as the time you 
> pass in must
> intersect the time bounds of the grid, and there is only one value in the 
> analysis dataset.
> 
> Those two tweaks should do the trick.
> 
> Cheers,
> 
> Sean
> 
> 
> > The more I think about this, maybe it's not a python/siphon issue, but 
> > rather at thredds or java-netcdf issue? Why would thredds be returning a 
> > valid time of 3 or 6 for an analysis when the time base is the initial time 
> > of the model?
> >
> >
> > Just curious. I got around this for now by specifying the time to be 0 
> > instead of whatever thredds throws back at me, since that value seems to be 
> > wrong.
> >
> >
> > Pete
> >
> >
> >
> > <http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>--
> > Pete Pokrandt - Systems Programmer
> > UW-Madison Dept of Atmospheric and Oceanic Sciences
> > 608-262-3086  - address@hidden
> >
> > ________________________________
> > From: Pete Pokrandt
> > Sent: Saturday, November 11, 2017 11:12:28 AM
> > To: address@hidden
> > Cc: address@hidden; John Leeman
> > Subject: Re: [python #OQG-244028]: Python help
> >
> >
> > For what it's worth, the same thing happens if I just run the default 250 
> > hPa heights/winds notebook on the gallery. I just ran it now on Julien's 
> > alpha testing jupyterhub server on jetstream, at 11:10 AM CST, where the 
> > most recent model run should be 12 UTC, and the time on the plot shows 
> > 18:00 today.
> >
> >
> > 250hPa_Hemispheric_Plot.ipynb
> >
> >
> > Pete
> >
> >
> >
> > <http://www.weather.com/tv/shows/wx-geeks/video/the-incredible-shrinking-cold-pool>--
> > Pete Pokrandt - Systems Programmer
> > UW-Madison Dept of Atmospheric and Oceanic Sciences
> > 608-262-3086  - address@hidden
> >
> >
> > ________________________________
> > From: Unidata Python Support <address@hidden>
> > Sent: Friday, November 10, 2017 3:47 PM
> > To: Pete Pokrandt
> > Subject: [python #OQG-244028]: Python help
> >
> >
> > Pete Pokrandt,
> >
> > Your Ticket has been received, and a Unidata staff member will review it 
> > and reply accordingly. Listed below are details of this new Ticket. Please 
> > make sure the Ticket ID remains in the Subject: line on all correspondence 
> > related to this Ticket.
> >
> > 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 ID: OQG-244028
> > Subject: Python help
> > Department: Support Python
> > Priority: Low
> > 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.
> >
> > Please let us know how we can assist you further.
> >
> > Unidata User Support
> >
> >
> >
> 
> Ticket Details
> ===================
> Ticket ID: OQG-244028
> Department: Support Python
> Priority: Low
> 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: OQG-244028
Department: Support Python
Priority: Low
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.