Fabian Hofmann

I am not so sure about that. So the convention should be that an indexing hour (assuming hourly resolution) represents the completed hour. So, a value at 11:00 am represents...

after notifying @gincrement that changing the `port_efficiency` function would lead to quite some problems in the other statistic functions, I added the efficiency calculation to the carbon_emission function directly. Note...

@lkstrp this validator is soo cool!

I am actually not sure, if all the `get` functions are actually "internal". I think that an import from `pypsa.statistics` is not uncommon, as for example here https://github.com/PyPSA/pypsa-eur/pull/921/files#diff-6dafdba3772c0812a6a645c461f092bdbf7e0d7447be19ec5ea4c071e33e5302 Perhaps we...

> You both mean the groupers? I did not make them internal. But there is no reason to have them that often and not consistent in the API: > >...

good point! that's probably the reason

then we can replace the comment here https://github.com/PyPSA/atlite/blob/master/test/test_preparation_and_conversion.py#L672 with an explanation

this is lovely!

I have the feeling this could be a super solid entry point for a dashboard/GUI from where you can trigger snakemake with a given set of configs

> I just realized that there are already optional keys which are not in the default (e.g. #1532). Do the config tables then cover everything? that's also new to me...