Daniel Huppmann

please see related issue #19 - we attempted to just recompute correct regional prices and this proved far more effort than currently possible

We are working on more and better features for documentation in the `ixmp Scenario Explorer`. The key question for us is usability - where to display additional information in a...

I'm not sure why you think that item 3 depends on item 2?

I would not describe `type_*` and `map_*` as ‘hidden’, ‘implicit’, or ‘auto-generated’. These are two perfectly normal sets to define the mathematical structure of the equations. The `cat_*` feature described...

@khaeru, your summary is correct and the line you reference is the value that the variable is being fixed to - no need for any other data manipulation... My hunch...

Thanks @tzipperle for identifying this issue - it's not directly a bug, more a missing feature at this point. The `nodes` in a Scenario set and the timeseries are not...

This behaviour actually makes sense - currently, there is no mechanism forcing the newly installed capacity to be maintained in the first period, i.e. `CAP_NEW(node, tec, vintage)` does not have...

@ClaraLuisa it would be great if you could give it a try! Thinking about it, you most likely wouldn't even need a new equation, just refine the existing `CAPACITY_MAINTENANCE` to...

Thanks @ClaraLuisa for this question! The logic for keeping these two distinct was the following: 1) `historical_emission` is only used in the constraint `EMISSION_CONSTRAINT` so that it is possible to...

Sorry @jkikstra, but I'm afraid that this is expected behavior. pyam is quite "generous" when it comes to additional data dimensions - it automatically assumes that any column named other...