Aggregating to powerstations from IASR ID

[nick-gorman]

Hey, just remembering @EllieKallmier mentioned using IASR ID as generator key, these are often at the unit level. Should we also be thinking about building in the option to aggregate to the power station level for computational tractability?

[EllieKallmier]

ack - yes, probably! I think this should mostly be pretty straightforward, some things might need to be handled a bit decisively (closure dates is the main one I can think of) but that's not new.

A few things that I'm not sure about/noting here so I don't forget:

• Trace choice - in case there's any power station with units that use different traces (I don't think this is likely but I haven't checked In detail). Also mapping the traces to power stations in case the IASR ID != power station (but also easy to implement).
• Hydro...

[dylanjmcconnell]

I regret to inform you there are a couple of power stations that have multiple traces associated with them.

For example Dundonnell Wind Farm has both IASR ID and traces associated with DUNDWF1, DUNDWF2, and DUNDWF2
(Similar for powerstations Clarke Creek wind Farm, and Snowtown S2 Wind Farm, New England Solar Farm)

There are also some powerstations that have multiple IASR ID associated with it, but each IASR ID maps back to a single trace.

Also IASR ID very frequently doesn't equal power station I think (or at least much more common to not map than map).

The "best" thing to do is probably a capacity weighted trace (since these are known plants). The "easy*" to do (and probably will be like 99% the same) is to just choose one.

(not sure - one way or the other - why hydro might be special here? Maybe it is.. I don't know. Perhaps part of the broader hydro basket-case to solve)

[dylanjmcconnell]

* I don't know if that is infact "easy". Less complicate than capacity weighting at least.