Bryn Pickering
Bryn Pickering
Based on offline discussions, the above structure seems to make sense. One change would be to make 'parameter' its own dimension, so that parameters can be defined within the CSV...
Some places where the format might need refinement are w.r.t links and carriers. The way in which we may now define links and techs as lists of dictionaries (#324, #362)...
One addition: there should be the ability to ignore rows/columns that define comments/references/units that aren't relevant to model dimensions.
And maybe the possibility for a direct SQL connection
This will be possible with the `carrier_con` group constraint (#310), where you could set a total production of a specific carrier to be met by a tech (or group of...
This is a design choice, not to have an arbitrary number of definable costs (+capacities, etc.) for `conversion_plus` technologies. This means that you can only link costs to `primary_carrier_in` and...
Hi @Yannickvtil, this looks like it was a bug in 0.6.6 that should now be fixed in 0.6.7. Could you check this?
@Lingkangjin that's just a feature of linear models: you sacrifice physical representation for computational efficiency. One other option is to not have 'energy_eff' applied to the storage technology. If it...
https://github.com/schollz/poetry-generator https://github.com/kmt901/Poetry-Generator https://eh.bard.edu/2016/11/07/generating-algorithmic-poetry/
I was about to say that "the distances are stored in `model_data`", but I see that they're not... Perhaps we could populate a variable with those values? Units, agreed, should...