Unmet demand only in the netcdf results if not 0
timtroendle opened this issue · comments
Problem description
When ensure_feasability is turned on, unmet_demand usually gets reported within the netcdf results as a variable with the same name. If unmet demand is 0, this variable is deleted.
This behaviour is problematic I think for two reasons. First, it's surprising. For a while I thought I had to calculate unmet demand myself. Second, it makes automatic batch analysis of runs more complicated, as one has to handle the special case unmet_demand == 0. Therefore, I suggest to always report unmet_demand in the netcdf when ensure_feasability is turned on. Maybe even if ensure_feasability is turned off. This would be most consistent to me.
Steps to reproduce the problem
Run a model with ensure_feasability: True which would work without ensure_feasability, too.
Calliope version
0.6.6
Incorporated in 1a09ade