Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URL for gefs data python code broken #121

Closed
sckott opened this issue Dec 2, 2015 · 7 comments
Closed

URL for gefs data python code broken #121

sckott opened this issue Dec 2, 2015 · 7 comments
Milestone

Comments

@sckott
Copy link
Contributor

sckott commented Dec 2, 2015

http://sila.cee.wsu.edu/forecasts/WeatherAndClimateDatafromNWS.html

@potterzot

is the code somewhere else you could point to?

@sckott sckott added this to the v0.6 milestone Dec 2, 2015
@potterzot
Copy link
Contributor

Hi Scott - it appears that the link is down and I haven't gotten a
response. The change you made is great though. Thanks!


Nicholas Potter
http://potterzot.com

On Tue, Dec 1, 2015 at 6:07 PM, Scott Chamberlain notifications@github.com
wrote:

http://sila.cee.wsu.edu/forecasts/WeatherAndClimateDatafromNWS.html

@potterzot https://github.com/potterzot

is the code somewhere else you could point to?


Reply to this email directly or view it on GitHub
#121.

@sckott
Copy link
Contributor Author

sckott commented Dec 2, 2015

okay, hopefully they'll respond, i'll leave it open for a while in case you get a response soon

@sckott
Copy link
Contributor Author

sckott commented Jan 21, 2016

no response, just leaving as is

@sckott sckott closed this as completed Jan 21, 2016
@potterzot
Copy link
Contributor

Just FYI I did have a conversation with Von Walden, the author of the python code, and he said that the link is currently down, he's not that concerned about it, and he will let me know if/when it becomes available again.

@sckott
Copy link
Contributor Author

sckott commented Jan 21, 2016

okay, thanks. Anywhere else the code lived? on bitbucket/github/gitlab/anywhere?

p.s., did I already ask you this? Why are gefs_GET() and gefs_CONNECT() exported? seems like you don't lay out any examples for those, suggesting maybe they aren't meant to be used by users?

@potterzot
Copy link
Contributor

I don't think the code is available anywhere at the moment. He had it on his laptop, threw it on his site for me to work from, and then took it down again.

re: gefs_GET() and gefs_CONNECT(), I wasn't sure whether they should be exported or not. They are base functions not really meant to be used by users, so maybe I should remove them. I guess I was thinking that I still wanted someone to be able to use them if they really wanted to, but maybe that doesn't really make sense.

@sckott
Copy link
Contributor Author

sckott commented Jan 21, 2016

They just look like internal fxns to me at least, but your more familiar with them.

By the way, any thoughts on this #127

@sckott sckott modified the milestones: v0.6, v0.5.6 Apr 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants