-
Notifications
You must be signed in to change notification settings - Fork 73
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
Update master for release #73
Conversation
Update the normalized_energy info in degradation_year_on_year
…es from production-weather merged files (csv or pickle)
…es from production-weather merged files (csv or pickle)
…tion rates from production-weather merged files (csv or pickle)" This reverts commit 09fbb33.
…tion rates from production-weather merged files (csv or pickle)" This reverts commit 47c996e.
This reverts commit 0b2f357.
This reverts commit 92faee7.
Merge issue_57 branch with development branch
Enables users to specify the size of the returned confidence interval
Fix erroneous check for two years of data
Irradiance rescale stability
Some changes in the notebook were overwritten by update from development branch. Also explicitly set method = ‘iterative” in rdtools.irradiance_rescale()
… nosie Previous version used approximations such as 52 weeks in a year. This version uses 1 year = 365 days regardless of the frequency. It also adds noise so that the confidence interval calculations can be tested. Finally I simplified the structure.
Issue 59 confidence interval
* closes #56 * running `2to3 rdtools/` shows the only incompatibilities are the relative imports already addressed in #67 so merge #68 to fix imports * running `2to3 tests/` shows python 2 print commands, so rerun 2to3 with `-f print -w -n` to add parentheses to print statements to make them calls instead of commands, altho these should really be replaced by logging, so TODO: make another issue and PR to add logging to tests Signed-off-by: Mark Mikofski <bwana.marko@yahoo.com>
Signed-off-by: Mark Mikofski <bwana.marko@yahoo.com>
support Python 3
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.
Hi @mdeceglie. Thanks for putting this release together.
I ran python setup.py install
in clean environments for both python 2.7 and python 3.6 using the latest development branch. Both installed without error.
When running tests/run_tests
, in both python versions, all tests pass but I received the familiar FutureWarnings about pandas-statsmodels. Issue is already noted in #27. Not a show stopper for this release.
I get installation errors in new environments of Python 2.7 and Python 3.6 with my Win10 machine. When installed into my existing environment, there are no errors. Python 2.7: Python 3.6: This appears to be a known bug with statsmodels for Windows 10 machines: |
Update: if I use 'conda install statsmodels' followed by 'pip install .' to install the development branch, then everything works in py2.7 and py3.6. Is there any way to install statsmodels through conda rather than pip in our setup.py file? |
@cdeline I was able to recreate this in a clean environment with only We could add a note in the readme encouraging people to install requirements by hand if they run into trouble. Do you think that would help? |
OK, I'm good with this approach. If you could include an extra line in the readme about manually installing components using conda if they get errors during install, I'm fine with this. |
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.
Update readme to include a line about manually installing components using conda if necessary. Otherwise, everything installs and runs correctly.
Agreed @cdeline, how's the updated readme look? |
Thanks for the input everyone! |
This incorporates changes that address issues: #67, #61, #59, #57, #56 as well as:
degradation_year_on_year
irradiance_rescale
All changes have ben through review when incorporated into the
development
branch. The purpose of this PR is to check that this version of rdtools installs and runs correctly.For me, it passes everything in the release procedure, with the exception of the minimum requirement check on windows, but failure was due to problems building old versions of some requirements.