We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In OSeMOSYS, TradeRoute is defined by the following, with the double defeniton of REGION causing some issues:
REGION
param TradeRoute {r in REGION, rr in REGION, f in FUEL, y in YEAR} binary;
For example, updating the REGION.csv to be:
REGION.csv
and the TradeRoute.csv to be:
TradeRoute.csv
The datafile from otoole convert datapackage datafile ... is
otoole convert datapackage datafile ...
param default 0.0 : TradeRoute := SIMPLICITY FEL1 2015 DIFFICULTY 1
Which will throw an error when building the model since DIFFICULTY is not indexed correctly.
DIFFICULTY
osemosys_fast_1.0.1.txt:378: TradeRoute[SIMPLICITY,FEL1,2015,DIFFICULTY] out of domain MathProg model processing error
If I try updating the definition of the datapackage so that its indexed over two regions, I get the error:
ValueError: cannot insert REGION, already exists
I'm not sure if the same behaviour will be seen when working on the results side. But I would probably guess yes :(
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In OSeMOSYS, TradeRoute is defined by the following, with the double defeniton of
REGION
causing some issues:For example, updating the
REGION.csv
to be:and the
TradeRoute.csv
to be:The datafile from
otoole convert datapackage datafile ...
isWhich will throw an error when building the model since
DIFFICULTY
is not indexed correctly.If I try updating the definition of the datapackage so that its indexed over two regions, I get the error:
I'm not sure if the same behaviour will be seen when working on the results side. But I would probably guess yes :(
The text was updated successfully, but these errors were encountered: