GithubHelp home page GithubHelp logo

osemosys / osemosys_global Goto Github PK

View Code? Open in Web Editor NEW
25.0 25.0 14.0 157.26 MB

A global power system model generator for OSeMOSYS

Home Page: https://osemosys-global.readthedocs.io/

License: GNU Affero General Public License v3.0

Jupyter Notebook 62.42% Python 37.58%
energy-model open-source osemosys

osemosys_global's Introduction

OSeMOSYS - Open Source Energy Modelling System

Build Status Documentation Status

Welcome to OSeMOSYS - the Open Source energy MOdelling SYStem. This source code repository contains the Apache-2.0 licensed source-code for the different implementations of OSeMOSYS - GNU MathProg, Pyomo, PuLP and GAMS.

For an in-depth introduction to the underlying model and its structure, you can read the original paper (needs access to Elsevier ScienceDirect).

The different versions are contained in subfolders, together with readme files which provide information of how to install and run the code.

Getting the OSeMOSYS code

Modellers

The OSeMOSYS code packages you need for writing your own models are released on the website, along with a lot of useful information on how to get started.

Developers

OSeMOSYS consists of this repository and several submodules, which contain the different language implementations of the OSeMOSYS formulation.

To obtain all the OSeMOSYS code including the language implementations for development purposes, run the following commands from your command line:

cd <name_of_folder>
git clone https://github.com/OSeMOSYS/OSeMOSYS # obtain the OSeMOSYS repository code
git submodule init # initialize your local submodule configuration file
git submodule update # fetch all the data from project and check out correct commit

If successful, this should download all the code to the folder you specified in the first step.

Alternatively, use the --recurse-submodules argument to the git clone command:

cd <name_of_folder>
git clone https://github.com/OSeMOSYS/OSeMOSYS --recurse-submodules
# obtain the OSeMOSYS repository code and submodules all in one line

Contributing

Please view our separate contributing document to find out how to contribute to the OSeMOSYS community.

Background

OSeMOSYS is a full-fledged systems optimization model generator for long-term energy planning. Unlike long established energy systems models, such as MARKAL/TIMES (ETSAP, 2010), MESSAGE (IAEA, 2010), PRIMES (NTUA, 2010), EFOM (Van der Voort, 1982) and POLES (Enerdata, 2010), OSeMOSYS potentially requires a less significant learning curve and time commitment to build and operate. Additionally, by not using proprietary software or commercial programming languages and solvers, OSeMOSYS requires no upfront financial investment. These two advantages extend the availability of energy modeling to large communities of students, business analysts, government specialists and developing countries energy researchers.

Motivation

OSeMOSYS is designed to fill a gap in the analytical toolbox available to the energy research community and energy planners in developing countries. At present there exists a useful, but limited set of accessible energy system models. These tools often require significant investment in terms of human resources, training and software purchases in order to apply or further develop them. In addition, their structure is often such that integration with other tools, when possible, can be difficult.

Energy Specialists

The OSeMOSYS code is relatively straightforward and transparent and allows for simple refinements and the ability to conduct sophisticated analyses. As models are made to generate insights, OSeMOSYS allows a test-bed for new energy model developments.

Education

Enabling graduate students to build and iteratively develop formal energy models will impart this knowledge base to very wide range of energy market roles and positions. Extending the human capacity of private and public policy makers to use and understand energy models is a key step in the effective use and interpretation of formal analytical tools. And growing human capacity in energy modeling in developing countries – whose institutions have relatively fewer research resources – is particularly important, given the growth of developing countries in energy related emissions, resource use, and demand for energy services.

Community

OSeMOSYS community welcomes professionals and experts from different levels: decision makers, policy officers, energy planners, developers of new model functionalities, programmers.

The OpTIMUS Community, Practice 3

OSeMOSYS is part of the OpTIMUS Community, Practice 3: Open Software, together with other world class, peer reviewed open source tools and data.

OpTIMUS aims at promoting quantitative analysis to inform sustainable development policy, through the coordination of networks to advance open source software, knowledge development and capacity building. It is organized in three practices -modeling and capacity building for policy support, expert review and quality control, and software development. For more information on the OpTIMUS Community, please visit the related website: http://www.optimus.community/.

osemosys_global's People

Contributors

abhishek0208 avatar amanmajid avatar edwardxtg avatar kkuling avatar maartenbrinkerink avatar simone111git avatar tniet avatar trevorb1 avatar willu47 avatar zhanwei-liu avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

osemosys_global's Issues

Work out where to host the data, how to deploy it, and declare licenses etc.

At the moment, data is stored in the data folder in the repository.

When installing as a Python library, this data is not included, and so all local references to data break. There are a few workarounds:

  1. include all the data inside the Python library so it is installed with the package
  2. host the data on a web-server, or provide links to online sources for all the data
  3. distribute the data in an zip archive, and get users to place somewhere manually

In terms of pros/cons:

  1. a bit of a hack, users cannot see the data (e.g. identify data issues), bulky codebase, and an unhealthy mix of code and data;
  2. potentially brittle, as broken links to other sources would break all installed versions of the package; potential licensing issues if data is not open? However, all users would benefit from central updates to data;
  3. simplest, need to clear data licences, messy install;

ResidualCapacity

Generate ResidualCapacity.csv. Powerplant data (input) from 'PLEXOS World V5'. Output in the following format:

REGION TECHNOLOGY YEAR VALUE
GLOBAL PWRXXXYYYZZ## 2020 99999

Notes:

  • Powerplants which have reached more than 150% of their theoretical lifetimes by 2015 will be retired in 2020.
  • Other powerplants that have exceeded their theoretical lifetimes by 2015 will be retired in 2025.
  • 'CapacityScaler' powerplants - include to scale power generation capacities of specific technologies to known national levels - may appear to be retired all at once.

Review default_values Data

Currently, the default_values.csv is created through the OPG_file_check.py script. It copies the default_values file over from Simplicity. These values may need to be reviewed/updated for osemosys global.

For example, Simplicity has default values for capital cost and variable cost of zero. In the models current form, if these are not changed to a small number (0.001 for example), CPLEX solves for an objective cost of zero.

Soft-link with PLEXOS-World

To be able to assess scenarios coming from OSeMOSYS in PLEXOS-World we need to establish a workflow. An option would be to use the IAMC data template as common data format [https://data.ene.iiasa.ac.at/database/]. The pyam python package is developed by the IAMC that can be used to directly pull data from IAMC databases and can assist with conversion to other data formats (e.g. pandas dataframes).

I'll provide an overview of required input data for the modelling in PLEXOS-World.

File that displays unit information

As a non OSeMOSYS user it feels strange to not have insights in what units are being represented per variable. I suggest to add a file to the model folder that defines all units used per variable. I'm not sure if OSeMOSYS supports use of different units per variable but in that case it would also be good to have a unit input csv/config file that is being read before the model is composed.

OutputActivityRatio

Generate OutputActivityRatio.csv. Powerplant data (input) from 'PLEXOS World V5'. Output in the following format:

REGION TECHNOLOGY FUEL MODE_OF_OPERATION YEAR VALUE
GLOBAL PWRXXXYYYZZ## XXXYYY 1 2020 1

Duplicate Transmission Technology Values Being Created

The following transmission technology has duplicate Output Activity Ratio values being created

OutputActivityRatio :=
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2015 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2015 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2015 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2015 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2016 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2016 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2016 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2016 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2017 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2017 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2017 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2017 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2018 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2018 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2018 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2018 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2019 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2019 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2019 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2019 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2020 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2020 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2020 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2020 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2021 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2021 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2021 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2021 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2022 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2022 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2022 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2022 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2023 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2023 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2023 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2023 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2024 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2024 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2024 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2024 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2025 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2025 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2025 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2025 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2026 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2026 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2026 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2026 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2027 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2027 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2027 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2027 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2028 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2028 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2028 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2028 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2029 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2029 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2029 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2029 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2030 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2030 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2030 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2030 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2031 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2031 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2031 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2031 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2032 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2032 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2032 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2032 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2033 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2033 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2033 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2033 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2034 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2034 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2034 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2034 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2035 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2035 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2035 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2035 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2036 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2036 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2036 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2036 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2037 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2037 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2037 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2037 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2038 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2038 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2038 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2038 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2039 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2039 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2039 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2039 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2040 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2040 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2040 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2040 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2041 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2041 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2041 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2041 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2042 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2042 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2042 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2042 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2043 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2043 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2043 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2043 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2044 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2044 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2044 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2044 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2045 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2045 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2045 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2045 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2046 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2046 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2046 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2046 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2047 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2047 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2047 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2047 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2048 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2048 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2048 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2048 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2049 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2049 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2049 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2049 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2050 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSI01 1 2050 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2050 0.966
GLOBAL TRNCHNSCCHNSI ELCCHNSC01 2 2050 0.966

Operational Life Data not being created

In the data folder, there is a file called "operational_life.csv" which defines the operational life for all technologies except CSP and WOF. The osemosys global data file does not have this data written to the Operational Life parameter and is instead using a default value of 1.0 for all technologies.

Demand projections

Electricity demand by node (SpecifiedAnnualDemand) is currently constant. Future electricity demand will be projected based on factors such as population, GDP/capita, and urbanisation.

CapacityFactor for hydro power plants

Currrently, the script computes CapacityFactor for Concentrating Solar Power (CSP), Solar PV (SPV), Wind - Onshore (WON), and Wind - Offshore (WOF) from hourly data. Hydro resource profiles are available as monthly data by power plant, averaged over 15 years.

Missing Storage Data

This includes:

  • CapitalCostStorage
  • DiscountRateStorage
  • MinStorageCharge
  • OperationalLifeStorage
  • ResidualStorageCapacity
  • StorageLevelStart
  • StorageMaxChargeRate
  • StorageMaxDischargeRate
  • TechnologyFromStorage
  • TechnologyToStorage

Source data transmission expansion

I've uploaded the (updated) dataset with costs and losses for transmission lines based on the PLEXOS-World model to the relevant Harvard Dataverse as created for the soft-link work with MESSAGEix-GLOBIOM. Similar to how we do it with the demand file and the PLEXOS-World 2015 model file, a script can now be linked to the raw datafile. Use of the data requires citation of the journal paper (preprint) as mentioned on the Dataverse page. The 'Interface' tab reflects costs per MW.

The relevant Harvard Dataverse is here

The exact download link for the file is https://dataverse.harvard.edu/api/access/datafile/4551443?format=original&gbrecs=true

Tidy up folder

There are files all over the place!

  • Suggest placing all the Python files in a src/osemosys_global folder
  • Delete all the .ipynb files if they duplicate what is in the script.
  • Alternatively, if the .ipynb files are to be retained (e.g. as a user-friendly option), suggest importing the new Python scripts, deleting the contained code (perhaps you've done this already, and moving all notebooks to a notebooks folder

Add Carbon Price

I suggest to report carbon prices as input and/or output for any model run (unless I missed something and it is already being reported). If it's not included maybe add a default 0 value for clarity?

Add ResidualCapacity for transmission

The present version only includes capacities for all powerplants. Existing capacities of transmission lines - both intra- and inter-country - need to be included.

Note: All lines are considered as bi-directional. Values for each direction is provided and should be allocated to the appropriate MODE_OF_OPERATION.

Add in Renewable and Fossil resource potentials

Solar:
Based on paper:
A script can be directly linked to the supplementary material dataset for the above paper.

Wind:
Based on paper:
Dataset:

Hydro:
Based on paper:
Country level potentials for the 100 countries with highest potential (in TWh). I’ve manually transferred these to a excel file a while back (shared by email). The GW values are derived from TWh values by assuming country level capacity factor values from the PLEXOS-World dataset. So if OSeMOSYS can only handle capacity values then we can use the GW, but ideally the raw TWh values from the original sources would be best.

Add progress messages to scripts

Current scripts don't show their progress on the command line. Add a few print statements that indicate progress to the user.

Geographic filter transmission lines

Right now it seems that the spatial filtering for transmission lines is not working fully accurate, e.g. in a sample model of AFG & IND the results also include e.g. technology "TRNBGDXXINDNE".

Add variable costs for fuels

Add variable costs for the model in a new jupyter notebook. Base costs on World Bank Commodity Outlook.

Fuel production technology names will need to come from the powerplant_data notebook or from the output.csv.

Include small variable cost for international trading hubs for the commodities.

Access Maarten

Could anyone bump up my access to 'maintain' or 'admin'. It's a bit annoying that I can't manage issues etc. and assign myself to a specific issue

OPG_DemandProjections creates input data files

The demand projection script creates new versions of the data/Final_Electricity_Demand_Nodal_Yearly.csv and data/Final_Electricity_Peak_Demand_Nodal_Yearly.csv files. These arn't used anywhere else in the OPG scrips (at least that I saw), and Im a little confused why we are creating input files (data/ folder) from the OPG scripts?

No big issue, but they always pop up as modified by git!

Model file used to run with the python script needs to be edited to run

The model file needed to run OSeMOSYS global is not the same as the fast code at https://github.com/OSeMOSYS/OSeMOSYS_GNU_MathProg/tree/master/src. Do we need to advocate for an additional model file in the OSeMOSYS repo that is setup for the python script or for the OSeMOSYS fast code to be changed to be python script compatible?
My initial view is that we should advocate for the fast code to be migrated to run by default with the script - this is the fastest way to run the model, and the fast code should be the fastest way to run the model.
Other thoughts? If we have a preferred structure we can ask for this on the OSeMOSYS repo.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.