Ivan Ruiz Manuel

This happens in the following: ```shell ipdb> ch_industry_subsector_energy_use.unstack('year').columns.unique() Index(['2004', '2005', '2006', '2007', '2008', '2009', '2010', '2011', '2012', '2013', '2014', '2015', '2016', '2017', '2018', '2019', '2020', '2021', '2022', '2023', 'FERN', 'nan'],...

Fixes (in `annual_energy_balances.py`) The core problem is how CHE industry data is read over time: it will 'desync' as the document is updated each year. The current values probably correspond...

Hello @hiddegrootes! It is definitely possible, but it might be something that you have to implement on your side within your workflow. Calliope is meant to be a generic framework,...

Facing this issue at the moment. Would love to have this built-in.

Pitching in to say that this would be a fantastic feature to have.

Was about to open an issue on this, but it seems this and #6840 already discuss this. I agree with the suggestion. Just trust us that the excinfo will be...

@brynpickering: - `parameters`->`data` makes sense... although I forget why we did not go for `inputs` instead - we need to avoid `source` as it would reintroduce #673... how about just...

That also works, sure! Either case is intuitive, and going for the option that minimises code changes is OK. So, is this valid, then @brynpickering ? ```yaml data_tables: pv_capacity_factors: table:...

@cpalazzi 0.7 is agnostic to the cost / power unit. It only requires you to be consistent in your definitions in regards to capacity and carrier flow conversions. The examples...

@brynpickering although `pint` would be a nice addition, I think it might add a lot of overhead during processing. It'd leave it as a nice to have for that, and...