Co2L... in Documenation

[flo161616]

I am using the 0.8.1 release of PyPSA-eur on WSL.

Description:
The Documentation for the sector-opts wildcard seems to be misleading or wrong. When using a sector-coupled network and using Co2L in sector-opts an error in prepare_sector_network occurs. It seems as if there was no option for Co2L without a float appending. Furthermore, the Documentation says, the Co2L... references co2base. However, this could not be reproduced and an inspection of the code buid_energy_totals.py gave hints, that it uses only the values directly from eea. So when using sector-coupled networks neither co2base nor co2limit have any effects. This was tested using the description below.

On a sidenote: It seems the o in Co2L has to be lowercase, however in the config/test/config.overnight.yaml it is written as CO2L.

How to reproduce:
Tested with Co2L0.25-24H-T-H-B-I-A. Single week, Belgium. Using this when doubeling the co2base the emissions did not double. However they doubled when using Co2L0.5.

[fneum]

Yes, it is currently confusing that the Co2L wildcard has different usage patterns in {sector_opts} and {opts} wildcard, and apologies for the wrong documentation on that. I have adjusted that in a8cd118. In the long term, we will phase out the wildcards with new scenario management and uniformize electricity-only and sector-coupled workflows. This should then also fix the ambiguity here.