Skip to content

balmorelcommunity/Balmorel

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Balmorel

Check out the documentation for tutorials on getting started with the Balmorel energy system model.

Data is included in the Balmorel_data repository, which we recommend cloning to base/ for version control of both base data and framework. Note: The cloned folder should be renamed from "Balmorel_data" to "data" to function properly.

A scenario that's possible to run with an academic trial license of GAMS can be found in the balmorel-demo branch.

What is Balmorel?

Balmorel is a partial equilibrium model for analysing the electricity and combined heat and power sectors in an international perspective. It is highly versatile and may be applied for long range planning as well as shorter time operational analysis. Balmorel is implemented as a mainly linear programming optimisation problem.

The model is developed in a model language, and the source code is readily available under open source conditions, thus providing complete documentation of the functionalities. Moreover, the user may modify the model according to specific requirements, making the model suited for any purpose within the focus parts of the energy system.

What can Balmorel be used for?

The Balmorel model has been applied in projects or other activities in a number of countries, e.g., in Denmark, Norway, Sweden, Estonia, Latvia, Lithuania, Poland, Germany, Austria, Ghana, Mauritius, Canada and China. It has been used for analyses of, i.a., security of electricity supply, the role of flexible electricity demand, hydrogen technologies, wind power development, the role of natural gas, development of international electricity markets, market power, heat transmission and pricing, expansion of electricity transmission, international markets for green certificates and emission trading, electric vehicles in the energy system, environmental policy evaluation.

See "Activities" and "Publications" sections in the menu for description of ongoing and past projects using the Balmorel model.

Who can use Balmorel?

Balmorel is a modelling tool that can be used by energy system experts, energy companies, authorities, transmission system operators, researchers and others for the analyses of future developments of a regional energy sector.

How is Balmorel supported and further developed?

The model is developed and distributed under open source ideals. The source code has been provided on its homepage since 2001 and was assigned the ISC license in 2017. Ample documentation is available in the folder within this repository. We also refer to information on openmod. Presently the model development is mainly project driven, with a users' network around it, supporting the open source development idea.

Procedure for Merging Changes to Master

The Balmorel team of DTU Management, Energy Economics and Modelling has decided on the following procedure for merging new changes to the master:

  1. A decision to merge should be agreed upon in a Balmorel meeting with the admins

  2. Create a new branch from master, which will be used as a temporary branch to do all the changes

  3. Make the desired changes in a new scenario:

    a. Add a new scenario called 'changes', which the following files and folder structure (copy Balmorel.gms and cplex.op4 from base/model if nothing is to be changed in these files):

     Balmorel
     ├── base
     ├── changes
     │   ├── data
     │   └── model
     │       ├── cplex.op4
     │       └── Balmorel.gms 
     ├── simex
     ├── README.md
     ├── .gitignore
     └── .gitattributes
    

    b. Keep the base scenario identical to the current master and apply all changes to the 'changes' scenario

  4. Run the test script, make sure that the model stays feasible and that the results make sense

  5. Consider critically if the tests performed in 4. is enough to verify and validate the changes made

  6. Make a pull request with the changes and report them in general terms, including the KPI outputs from the tests in 4. in ... (todo: check where it makes sense to put these descriptions, as simple as possible)