martinstringer
martinstringer
In the example above, the refinery seems to always produce a fixed ratio of its two output commodities. A real multi-output process may have a fixed ratio of _maximum_ output...
This model has now run successfully on the HPC with 64Gb memory. To close this issue we would ideally: - Find a way for muse to generate an error message...
If we get modify read_global_commodities_csv to rename "commodity" -> "description" how will that script know that the input file was in the old format ? ("commodity" is a correct column...
So do you think this issue will never arise as a problem when running muse in full?
Completely support the proposed solution above. I guess MUSE would ideally still accept the old format though (so that people's established models will still run). Is it time-consuming/problematic to modify...