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

Vectorises ghcn #356

Closed
wants to merge 77 commits into from
Closed

Vectorises ghcn #356

wants to merge 77 commits into from

Conversation

eliocamp
Copy link
Contributor

@eliocamp eliocamp commented Jun 8, 2020

I thought it would be useful if the function ghcn() could accept a vector of station ids.

@sckott
Copy link
Contributor

sckott commented Jun 8, 2020

perhaps. ghcnd() is used within ghcnd_search(), which is used within meteo_tidy_ghcnd(). So this change will have to be checked carefully that it doesn't break those other 2 functions

@eliocamp
Copy link
Contributor Author

eliocamp commented Jun 9, 2020

I checked and both meteo_tidy_ghncd() and ghcnd_search() work with length one arguments and vector arguments (i.e. they inherit vectorisation for free 🤑 )

There is the issue of duplicated entries which arise if the user inserts duplicated ids. I don't know that would it be best to do in that case. I guess filter out the duplicates and run the functions with just the unique values?

EDIT: Had run the wrong test.

@sckott
Copy link
Contributor

sckott commented Jun 10, 2020

Thanks. Can you run any tests for ghcnd_search/meteo_tidy_ghncd and make sure they still work - and add some new tests for ghncd the vectorization

@sckott
Copy link
Contributor

sckott commented Oct 5, 2020

@eliocamp still plan to finish this? if not, lets close this

@eliocamp
Copy link
Contributor Author

eliocamp commented Oct 7, 2020

Ouch, sorry! It totally fell off my plate. I'll get to it this weekend. Apologies!

@eliocamp
Copy link
Contributor Author

There!
The relevant tests run well on my machine. I tried to test the whole package to see if I accidentally broke something else (not likely, since the changes are well contained to one function) but I got too many failures related to missing API keys.

@sckott
Copy link
Contributor

sckott commented Oct 12, 2020

Thanks @eliocamp ! Can you send a new pull request on a branch with a different name? There's so many files changed in this PR it makes it hard to know what's going on

@eliocamp eliocamp mentioned this pull request Oct 12, 2020
@sckott sckott closed this Oct 12, 2020
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

Successfully merging this pull request may close these issues.

2 participants