-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add historical data to l3 #252
Conversation
f364c08
to
fe7149c
Compare
…laciology-and-Climate/pypromice into add-historical-data-to-l3
This comment was marked as resolved.
This comment was marked as resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't looked at join_3 yet.
352774f
to
c1a8735
Compare
…gging, attributes and tests,
…258) * numpy dependency <2.0 * resample rules updated (deprecation warning) * fillna replaced with ffill (deprecation warning) * get_l3 called directly rather than from file * process action restructured
renamed new variable.csv moved old variable.csv renamed new variables.csv recreate variables.csv
c1a8735
to
96e6674
Compare
instead of just reading the stid to join
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've looked through it and generally I think it looks fine - there will be edits we need to make after all of these changes, but they can wait. @ladsmund has done a very thorough job reviewing this, and I just want to keep this moving forward. I just had one thing about the "ressources" module, which I opened in a PR to this branch #261.
…her it's a Nead file
…laciology-and-Climate/pypromice into add-historical-data-to-l3
…tly from the dataset when sorting
This PR builds on top of #251. It:
toL3
on that L2 file