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
NO-NO3->SE and NO-NO1->SE exchange forecasts are invalid #1480
Comments
@maxbellec you need to check the forecast (not the actual exchange)
…On Tue, Jul 3, 2018 at 5:40 PM maxbellec ***@***.***> wrote:
$ python test_parser.py NO-NO3-\>SE exchange
parser result:
{'netFlow': 93.2333, 'datetime': datetime.datetime(2018, 7, 3, 15, 39, tzinfo=tzutc()), 'source': 'driftsdata.stattnet.no', 'sortedZoneKeys': 'NO-NO3->SE'}
---------------------
took 0.73s
min returned datetime: 2018-07-03 15:39:00+00:00
max returned datetime: 2018-07-03T15:39:00+00:00 UTC -- OK, <2h from now :) (now=2018-07-03T15:39:49.558835+00:00 UTC)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/tmrowco/electricitymap/issues/1480#issuecomment-402201363>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABlEKE4ZbhkWEIRvxCcdUkgEbb-1iIh_ks5uC5BWgaJpZM4U60J0>
.
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: