Data

Tools

Indexes

Applications

Experiments

Open Sustainable Technology

OMEGAlpes

Aims to be an energy systems modeling tool for linear optimization (LP, MILP).
https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes

Category: Energy Systems
Sub Category: Energy System Modeling Frameworks

Last synced: about 19 hours ago
JSON representation

Repository metadata

https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes/blob/master/ 

          OMEGAlpes Lib for linear energy systems modelling
==================================================

**OMEGAlpes** stands for Generation of Optimization Models As Linear Programming for Energy Systems.

**OMEGAlpes** aims to be an energy systems modelling tool for linear optimisation (LP, MILP).

A **web interface** is available at https://mhi-srv.g2elab.grenoble-inp.fr/OMEGAlpes-web-front-end/ to generate scripts


We are happy that you will use or develop the OMEGAlpes library. 

It is an **Open Source** project located on GitLab at https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes


Project Presentation
====================
**OMEGAlpes library :**
Please have a look to OMEGAlpes presentation : https://omegalpes.readthedocs.io/en/latest/  
The library is available at:
    https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes.git


**Examples and article case studies :**
Please have a look to examples : https://omegalpes-examples.readthedocs.io/en/latest/  
The OMEGAlpes Examples folder is available at:
    https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes-examples.git
Some examples and article case studies are avalaible as Notebooks at:
    https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes_notebooks.git

A scientific article presenting OMEGAlpes with a detailed example is available here:
https://hal.archives-ouvertes.fr/hal-02285954v1

**Notebooks :**
Mostly all examples and article case studies are associated to a Notebook.
They can be found in the folder notebooks at : 
    https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes_examples

**OMEGAlpes-web interface :**
An web interface is available at https://mhi-srv.g2elab.grenoble-inp.fr/OMEGAlpes-web-front-end/ 
This interface enable you to generate scripts more easily using the graphical representation detailed 
in https://omegalpes.readthedocs.io/en/latest/OMEGAlpes_grah_representation.html


OMEGAlpes' Community
====================
Please subscribe to our mailing lists :
- for our newsletters: https://groupes.renater.fr/sympa/subscribe/omegalpes-news
- as an OMEGAlpes' developer: https://groupes.renater.fr/sympa/subscribe/omegalpes-users

Please use the git issues system to report an error: https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes.git  
Otherwise you can also contact de developer team using the following email adress: omegalpes-users@groupes.renater.fr 


Installation Help
=================
You can install the library as a user or as a developer. Please follow the corresponding installation steps below.

You can use any development environment
If you use Pycharm, some indications below will help you for the installation
https://www.jetbrains.com/pycharm/

Prerequisite
------------
Please install Python 3.12
https://www.python.org/downloads/

Installation as a user
----------------------
Please install OMEGAlpes Lib with pip using the command prompt.   

If you are admin on Windows or working on a virtual environment
    
    pip install omegalpes

If you want a local installation or you are not admin
    
    pip install --user omegalpes

If you are admin on Linux:
    
    sudo pip install omegalpes

Then, you can download (or clone) the OMEGAlpes Examples folder (repository) at :
https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes-examples

Launch the examples (with Pycharm for instance) to understand how the OMEGAlpes Lib works.
Remember that the examples are detailed at : https://omegalpes-examples.readthedocs.io/en/latest/

Enjoy your time using OMEGAlpes !

Installation as a developer and local branch creation
-----------------------------------------------------
1. Create a new folder in the suitable path, name it as you wish for example : OMEGAlpes

2. Clone the OMEGAlpes library repository
    
    ---
    Command lover:
    
           git clone https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes.git
    
    ---
    Pycharm lover:
    
    Open Pycharm       
    On the Pycharm window, click on "Check out from version control" then choose "Git".   
    A "clone repository" window open.      
    Copy the following link into the URL corresponding area: 
    
        https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes.git
    Copy the path of the new folder created just before.   
    Test if the connection to the git works and if it works click on "Clone".       
    Once OMEGAlpes is cloned, you must be able to see the full OMEGAlpes library on Pycharm 
    or on another development environment.

    -----
    VS Code lover:

    Open Visual Studio Code
    On the welcome screen, click on "Clone Git Repository"
    – If the welcome screen doesn't appear, press Ctrl+Shift+P (or Cmd+Shift+P on Mac) to open the Command Palette, then type and select Git: Clone.

    When prompted for the repository URL, paste the following link:
        https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes.git
    Choose or create a local folder where you want the repository to be cloned.

    VS Code will start cloning the repository. If successful, it will ask if you want to open the cloned folder — click "Open".

    You should now see the full OMEGAlpes library in VS Code's Explorer panel.
    
    -----
    If the connection does not work and if you are working with local protected network,
    please try again with the wifi.

3. First, choose or change your project interpreter
    
    ---
    Pycharm lover:
    
    Click on the yellow warning link or go to "File", "settings...", "Project Interpreter"
    
    You can:
    - either select the "Python 3.12" project interpreter but you may change the version 
    of some library that you could use for another application
    - either create a virtual environment in order to avoid this problem (recommended).  
    Click on the star wheel near the project interpreter box.  Click on "add...".   
    Select "New environment" if it not selected.    
    The location is pre-filled, if not fill it with the path of the folder as folder_path/venv   
    Select "Python 3.12" as your base interpreter   
    Then click on "Ok"
            
    ---
    VS Code lover
    

    Click on the interpreter warning in the bottom-left corner of VS Code, or press ``Ctrl+Shift+P`` and choose "Python: Select Interpreter".

    You can:

    - either select the "Python 3.12" global interpreter from the list, but you may change the version  
    of some library that you could use for another application.

    - either create a virtual environment in order to avoid this problem (recommended). ::

        Open the integrated terminal in VS Code (``Ctrl+` ``).
        Run: ``python3.12 -m venv venv`` (or replace ``python3.12`` with the correct path).
        Activate the environment:
            - On Windows: ``venv\Scripts\activate``
            - On Linux/macOS: ``source venv/bin/activate``

        VS Code should detect and switch to this environment automatically.
        If not, press ``Ctrl+Shift+P``, search "Python: Select Interpreter",  
        and choose the one that ends with ``/venv``.

4. You can install the library on developing mode using the following command in command prompt
once your are located it on the former folder.
If you are calling OMEGAlpes library in another project, the following command enables you to 
refer to the OMEGAlpes library you are developing 

        python setup.py develop

5. If it is not already done, install the library requirements.
    
    ---
    Command lover:
               
            pip install 
            
    If required, the command to upgrade the library is : 
    
            pip install --upgrade 
            
    ---
    Pycharm lover:
    
    You should still have a yellow warning.   
    You can:
    - install automatically the libraries clicking on the yellow bar
    - install automatically the library using pip with Pycharm on "File", "settings...", "Project Interpreter", "+",
    and choosing the required library as indicated in the Library Installation Requirements 
    part.

    ---
    VS Code lover

    You can:

    - install the required library using the integrated terminal.  
    Open the terminal with ``Ctrl+` `` and run:

        pip install ==version

    - upgrade the library (if needed) using:

        pip install --upgrade 

    - if a ``requirements.txt`` file is available, install everything at once with:

        pip install -r requirements.txt

6. Finally, you can create your own local development branch.
    
    ---
    Command lover:
        
        git branch 
            
    ---
    Pycharm lover:
    
    By default you are on a local branch named master.   
    Click on "Git: master" located on the bottom write of Pycharm    
    Select "+ New Branch"   
    Name the branch as you convenience for instance "dev_your_name"


    ---
    VS Code lover

    By default, you are on a local branch named ``master`` or ``main``.  
    Click on the branch name in the bottom-left of VS Code (e.g., ``master``).  
    Select "Create new branch..." from the dropdown.  
    Name the branch as you prefer, for example: ``dev_your_name``.  
    The new branch will be created and checked out automatically.

7. Do not forget to "rebase" regularly to update your version of the library.
    
    ---
    Command lover:
    
        git rebase origin
            
    ---
    Pycharm lover:
    
    To do so, click on "VCS", "Git", "Fetch"
    Then, click on your branch name on the bottom write of the Pycharm window
    select "Origin/master" and click on "Rebase current onto selected"

    ---
    VS Code lover

    To rebase your local branch onto the latest version of the remote:  
    Open the Source Control panel (or use the Git extension).  
    Click on the branch name in the bottom-left.  
    Select "Rebase current branch..." if available, or open the command palette (``Ctrl+Shift+P``) and run ::

        Git: Rebase Current Branch...

    Then select the target branch (usually ``origin/master`` or ``origin/main``).
    
8. For contribution, have a look to CONTRIBUTING.md
Once your code is ready for contribution, do a last rebase (see 7.) and then, 
request for a merge with the master branch in OMEGAlpes gitlab
https://gricad-gitlab.univ-grenoble-alpes.fr/omegalpes/omegalpes.git


If you want to have access to other examples and study cases, 
please have a look to the user's installation.
    
Enjoy your time developing OMEGAlpes!

Library Installation Requirements
---------------------------------
PuLP >= 3.1.1

Matplotlib >= 3.10.3

Numpy >= 2.2.6

Pandas >= 2.2.3

lpfics >= 0.0.1

Partners:
=========
OMEGAlpes is mainly developped in the Grenoble Electrical Engineering 
Laboratory (University Grenoble Alpes, CNRS, Grenoble INP, G2Elab, F-38000 Grenoble, France). 
Other teams took part in the tool development:    
- LOCIE (Laboratoire Optimisation de la Conception et Ingénierie de l’Environnement (LOCIE), CNRS UMR
5271—Université Savoie Mont Blanc, Polytech Annecy-Chambéry, Campus Scientifique, Savoie Technolac,
CEDEX, 73376 Le Bourget-Du-Lac,) in thermal engineering for the exergy package in particular  - in collaboration with Jaume Fito, Julien Ramousse and Benoit Stutz
- PACTE (Université Grenoble-Alpes, UMR 5194 PACTE) in social sciences for 
the actors package in particular  - in collaboration with Gilles Debizet
- MIAGE (Master Méthodes informatiques appliquées à la gestion des entreprises, Université Grenoble-Alpes) master students in computing for the GUI development.  
- LNCMI (Le Laboratoire National des Champs Magnétiques Intenses).

History and Open Source Development:
====================================
The development of OMEGAlpes began in 2015 under the impetus of Vincent Reinbold, and was then taken up again in 2017, particularly in the thesis work of Camille Pajot, who really laid the foundations of the tool, particularly as applied to the challenges of energy flexibility at neighbourhood level. Then Lou Morriet, in partnership with Grenoble’s PACTE social science laboratory, developped a library based on stakeholders and in particular their scope of responsibility. Mathieu Brugeron also used the tool on an optimised predictive controller application, and Sacha Hodencq on the development of a library of case studies. From 2024, the tool has been used in the FlexRICAN european project in Séverin Valla PhD as well as Nana Kofi and Mainak Dan post-doctoral work, to study the energy flexibility of research infrastructures.

The choice of open-source was made when the work was resumed in 2017, with a view to accessibility and maximising the potential for collaboration. A permissive licence, Apache 2.0, was therefore selected to enable collaboration, including with stakeholders who had opted for a proprietary development strategy. The tool has been versioned online since 2018, with examples of use and notebooks on the Gitlab software forge, and archived on Software Heritage. Its documentation is available online. OMEGAlpes leaves the choice of solver to the user via the PuLP package: the use of open-source solvers does not limit accessibility to professionals or academic users, while the possibility of using open-source solvers does not limit accessibility to professionals or academic users.

Acknowledgments:
================
This work has been partially supported by:
- the CDP Eco-SESA receiving fund from the French National Research Agency in the framework of the "Investissements d’avenir" program (ANR-15-IDEX-02)
- the OREBE fund from Auvergne Rhône-Alpes
- the RETHINE fund from the French Agency for ecological transition (ADEME)

The OMEGAlpes is presently being developed under WP6:Energy Flexibility FlexRICAN project that is funded by the European Union.

Licence
=======
This code is under the Apache License, Version 2.0


Notes
=====
This library has been tested using
- Visual Studio Code 1.101.2 (May 2025)
- Python 3.12
- pip 21.3.1
- setuptools 28.8.0

Owner metadata

Committers metadata

Last synced: 2 days ago

Total Commits: 1,515
Total Committers: 18
Avg Commits per committer: 84.167
Development Distribution Score (DDS): 0.674

Commits in past year: 20
Committers in past year: 2
Avg Commits per committer in past year: 10.0
Development Distribution Score (DDS) in past year: 0.15

Name Email Commits
Camille Pajot c****1@g****r 494
hodencqs s****q@g****r 419
lou-morriet l****t@g****g 335
Camille Pajot c****1@g****r 84
brugerma m****a@g****r 53
EXT Jaume Fitó j****z@u****r 39
lou-morriet l****t@g****r 24
Mainak Dan m****n@g****r 17
Etienne Cuisinier e****r@g****r 13
Benoit Delinchant b****t@u****r 11
brugeron m****n@c****r 11
Mathieu Brugeron m****n@g****r 5
Mainak Dan m****n@u****r 3
Nana Kofi Twum-Duah n****h@g****g 2
Sacha Hodencq s****q@g****r 2
Benoit Delinchant b****t@g****r 1
Frederic Wurtz - f****z@g****r 1
twumduan 1****r@92 1

Committer domains:

Issue and Pull Request metadata

Last synced: 4 days ago

Score: -Infinity