Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • O OMEGAlpes
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OMEGAlpes
  • OMEGAlpes
  • Issues
  • #15
Closed
Open
Created Jul 25, 2018 by EXT Hodencq@SachaHOwner

Storage units upper and lower bound definitions

In storage units line 67, the upper and lower bounds of the SOC are respectively defined as soc_mincapacity and soc_maxcapacity. Generally speaking the user will define the capacity, but when the objective is to minimize the capacity (such as in the storage_design example), the capacity remains None, and so these upper and lower bounds of the SOC cannot be defined.

An alternative upper and lower bound version should be coded for the SOC.

Assignee
Assign to
Time tracking