-
Notifications
You must be signed in to change notification settings - Fork 1
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
Working first version #1
Conversation
…nd tests; reorganise utils
…add seasonality Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
…m core FM Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
Here is a question: Should we even leave the choice to the user whether they want to setup less than the set of supported sensors per weather station? In a more simpler world, we let them add a weather station and it gets all supported sensors. Of course, if that means you get six sensors, when all you wanted was one, you have too much data... |
But I still fail when a supported sensor has not been registered at all, so I'll work on that. |
…M] as console prefix throughout Signed-off-by: Nicolas Höning <[email protected]>
Actually, my preference would be to have only the |
I believe OWM can't be called for just one sensor at a time. This design is not making sense to me yet |
Signed-off-by: Nicolas Höning <[email protected]>
…on close enough Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
…ip on test fixtures; de-complexify saving to db function Signed-off-by: Nicolas Höning <[email protected]>
@Flix6x The |
I agree |
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
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.
Not a full review yet, but maybe there are already some useful comments in here.
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.
Just a little refactoring in the sensor specs requested, which should make more clear how the sensor is set up (while cutting some lines).
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
Signed-off-by: Nicolas Höning <[email protected]>
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.
Thanks! FYI, I can verify all tests pass locally on python==3.9
.
NOTE: This requires FlexMeasures/flexmeasures#352 I'll make a dev-version from that branch after the first round of review over there, and then I intend to make the tests work over here. That can be done in a new smaller PR, so this working version is published earlier.