Electricitymap-contrib: Countries offline: AG, PE, RU-1+RU-2, AU-WA

Created on 3 Jan 2020  路  11Comments  路  Source: tmrowco/electricitymap-contrib

Most helpful comment

Just to keep this up to date, I sent a mail to our contact at the russian tso. I will let you know when he gets back to me.

All 11 comments

Hey @alixunderplatz, happy new year to you! :tada:

I ran the AR parser locally and got this back. Initially I thought the service was down (very common as it's a big pile of spaghetti) but it looks like the HTMl has changed.

(EM) chris@ThinkPad:~/electricitymap$ python parsers/AR.py 
fetch_production() ->
Traceback (most recent call last):
  File "parsers/AR.py", line 964, in <module>
    print(fetch_production())
  File "parsers/AR.py", line 832, in fetch_production
    gdt = get_datetime(session=None)
  File "parsers/AR.py", line 640, in get_datetime
    find_hour = timesoup.find("option", selected="selected", value="1").getText()
AttributeError: 'NoneType' object has no attribute 'getText'

I'll send a PR for this.

Hey @systemcatch , thanks, happy new year to you, too!!!
One thing I could recently find for Argentina is the breakdown of the renewables in one diagram:
https://despachorenovables.cammesa.com/renovables/
No need for a mapping for these. I feel like "hidraulico" might only include small hydro which needs to be added to large hydro.

@alixunderplatz that's useful, I can take a look at adding that to the parser.

Hi, I've worked on fixing Western Australia, just putting up a PR now.

@robertahunt any chance you could check the EM server to see why the RU parser is failing? I remember when I ran it locally everything was fine.

Hey @systemcatch! I am having no luck with tracking down the error on the server-side on my own. It looks like the data is fine and the feeder processes it properly in my tests. I will catch up with oli on this tomorrow.

@systemcatch , Unfortunately our server is getting a 404 response from the data source, which is why our parser is failing. @corradio suspects this is because our server's IP address has been blocked by the Russion TSO due to a high volume of requests. I have it on my to-do list to ask them to whitelist us, but I am not sure what else to do. Any other suggestions?

@robertahunt hmmm that's annoying, as to what to do asking them to whitelist us is a good idea. If they refuse maybe using a proxy is possible ( if Tomorrow is comfortable with that).

Maybe the EM needs to have a review of how often they are requesting data in general, some of the sources aren't really designed to be used by outsiders and too many requests might result in being blocked.

Just to keep this up to date, I sent a mail to our contact at the russian tso. I will let you know when he gets back to me.

RU parsers look to be working again!

I noticed that the Western Australia parser was offline again with a different issue - I've put up another PR.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

alixunderplatz picture alixunderplatz  路  4Comments

ghost picture ghost  路  5Comments

corradio picture corradio  路  4Comments

systemcatch picture systemcatch  路  5Comments

corradio picture corradio  路  5Comments