Distribution of wind generators / wind dispatch in v0.3.2

[jankaeh]

Hi, I use data from v0.3.0 with generators from v0.3.2 and clip foreign components. I overwrite wind on/offshore with wind. For 2011-09-14 12:00 I get this distribution of dispatch from a merit order simulation:

The two biggest wind inputs confuse me. They don't reflect reality, do they? Do you get similar distributions, or did I mess sth up? (The big coal dispatch is the slack output from pf post lopf calculation)

[ulfmueller]

Looks weird. But it would be good know about the order of magnitude. I would check the p_nom distribution of the wind power plants and see if those are realistic (maybe also check the p_max_pu, if they are reasonable). If yes, then of course it would be possible that in some hours it can make sense to dispatch cheap wind near to the demand more than in other less demanded or/and more restricted regions.

[jankaeh]

All generators with marginal costs = 0 dispatch at p_nom or p_max_pu*p_nom. Only one uranium generator dispatches in the sense of merit order. I'll investigate further when my simulations are done and let you know if I found a mistake I made or if this might be a bug.

[ulfmueller]

ah ok your RE are not flexibly dispatched. Then it is definitely wrongly distributed. Is it possible that somehow your offshore wind is attached falsely? Since they are two and the order of magnitude looks a bit like that. I will check what happens if I use 0.3.2 as a consistent dataset... Btw: why dont you take the entire 0.3.2?

[ulfmueller]

just to be fast. what start_snapshot you used?

[jankaeh]

2011-09-14 12:00 is the timestamp. I use quartals as datasets, so the integer index isn't the same but I guess 6192?
When I find the time, I'll switch to v.0.3.2 entirely. Oh I just realize there is a v.0.4.2 released... So I'll probably upgrade to that version soon.

[ClaraBuettner]

I'm not sure how helpful this is for this issue, but I just committed a bug fix in etrago/.io, that considers the grid version of carrier. So you don't need to overwrite carries manually anymore when you update eTraGo.
openego/eTraGo@9daf093