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

[python #SEN-170351]: Siphon on Cheyenne/Casper

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.

  • Subject: [python #SEN-170351]: Siphon on Cheyenne/Casper
  • Date: Mon, 29 Aug 2022 16:44:20 -0600
Greetings!

I can confirm that I had no problems accessing the data behind the query you 
shared.

I'm not familiar with the use of Siphon on Casper/Cheyenne, or any limitations 
or problems, but I know it's common in supercomputing environments for external 
network access to be blocked. You can probably get a better idea by contacting 
NCAR's HPC support:

  https://www2.cisl.ucar.edu/computing-data/user-support

I'll add that the UWyoming site has been having some load issues lately, but 
those return a 503 error code rather than 403 as in your example.

Hope this helps,

Ryan

> Hi there,
> 
> I am a novice at using your Siphon package for retrieving sounding data
> from U. Wyoming on Casper-based (here at NCAR) Jupyter Notebooks. At the
> moment, I am getting a permissions type error:
> 
> HTTPError: Error accessing
> http://weather.uwyo.edu/cgi-bin/sounding/?region=naconf&TYPE=TEXT%3ALIST&YEAR=2022&MONTH=08&FROM=1100&TO=1100&STNM=DTX
> Server Error (403: Forbidden)
> 
> 
> Do you know if it's possible to use Siphon on NCAR-based Casper/Cheyenne,
> or is there a security issue that won't allow for it?


Ticket Details
===================
Ticket ID: SEN-170351
Department: Support Python
Priority: Low
Status: Closed
===================
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.