Electricitymap-contrib: Exchanges referencing "US" zone no longer appear on map

[daveadotdev]

Change #1366 added a new zone which covers Washington State in the US under the Bonneville Power Administration, and I think since then the CA-BC->US exchange that used to show up on the map no longer does.

It looks like config/exchanges.json includes a few references to the "US" zone which no longer exists anywhere on the map, so that's probably why. Maybe.

Namely:

• CA-BC->US (should be changed to US-BPA?)
• CA-AB->US (should be changed to US-MT?)
• US->US-CA (Not sure about this one, the CSV imported in the parser contains only aggregate imports, not broken down by connection)

[jarek]

Possible reason is relation to #1391 which made internal back-end changes to how zones with no parsers are handled. Namibia is also impacted by this.

[corradio]

I think this is related to the changes we did with @maxbellec.
I won't have time to fix this weekend, but we'll look at that asap.
No data loss is involved, so that's a good start.

[systemcatch]

@daveachuk you're right the first 2 exchanges should be CA-BC->US-BPA and CA-AB->US-MT, do you want to correct them or shall I?

For US->US-CA that's an aggregate of all exchanges to CAISO which we just show as a generic arrow.

[jarek]

The exact details of these western Canadian exchanges are a bit of a meaningless difference because we know nothing about Montana, don't have real time data for BC, and the situation of BPA is not all that clear (http://explorer.watttime.org shows significant parts of Washington, possibly including the BC exchanges, as being outside the BPA area)

[systemcatch]

I think BC does have exchanges with BPA (https://www.bchydro.com/content/BCHydro/en/energy-in-bc/operations/transmission/transmission-system/actual-flow-data.html?WT.ac=sia_transmission_actualflowdata) mentions them by name, but you're right that this is mostly insignificant since there is no data.

[daveadotdev]

@systemcatch happy to let you make the changes as you see fit, I don't have a testing env set up so can't check that it works before submitting a PR.

Note that there is no real-time generation data for BC but there is real-time exchange data available for the CA-BC->US-BPA link, for as much good as that does. I think you know that but just clarifying for the record :)

[maxbellec]

actually this seems to be a front-end error, not a back-end one: exchanges are in the states. @jbuverud @corradio do you know what can be the source of this?

[jbuverud]

You're right @maxbellec, I think this is due to us now removing exchange information from countries with no data (like @jarek said). I'll change the implementation and see if I can get this problem fixed.

[jarek]

This is still an issue, although the PR #1416 has already been deployed a few hours ago. Is there more to the problem?

[maxbellec]

the website is only update when we update the backend. We will tonight

[corradio]

@maxbellec Actually I deployed it this morning: https://tmrow-team.slack.com/archives/C2DQPTHA6/p1526459994000026

[corradio]

Re-opening as issue is still happening

[jbuverud]

Which exchanges are not showing, exactly?

On Wed, 16 May 2018, 21:34 Olivier Corradi, [e-mail]
wrote:

Re-opening as issue is still happening

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tmrowco/electricitymap/issues/1403#issuecomment-389639529,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGtu527v7qvxjv8MWYvwFQM_d7ZiwYS9ks5tzH9IgaJpZM4T73wV
.

[corradio]

CA-US and Namibia Zambia

On Wed, May 16, 2018 at 8:43 PM Jakob Buverud [e-mail]
wrote:

Which exchanges are not showing, exactly?

On Wed, 16 May 2018, 21:34 Olivier Corradi, [e-mail]
wrote:

Re-opening as issue is still happening

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/tmrowco/electricitymap/issues/1403#issuecomment-389639529
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AGtu527v7qvxjv8MWYvwFQM_d7ZiwYS9ks5tzH9IgaJpZM4T73wV

.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/tmrowco/electricitymap/issues/1403#issuecomment-389642011,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABlEKPfz98234uUiCazuXJ5U8jsND2wEks5tzIFJgaJpZM4T73wV
.

[corradio]

Actually @maxbellec it seems like this is a backend issue, as the netFlow shows undefined:

[systemcatch]

Is it something to with if an exchange is flowing from a zone that has no parsers/data to a zone with data it is getting ignored? This is the case with the Namibian & California exchanges right now, so if they reverse they should reappear?

CA-BC->US-BPA is flowing from BPA at the moment and showing on the map so that one is fixed in one direction.

[maxbellec]

yes it's probably something like that @systemcatch, though I haven't yet figured out where we do that. Thanks for investigating

[systemcatch]

You found the source of the problem @maxbellec?

[maxbellec]

yeah, I hadn't coded in Javascript for a while and forgot that someObject[keyDoesntExist] is undefined, and does not throw an error :rage:, so US or NA neighbors were labaled as having subzones and ignored (as NO and DK are).