Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • O OMEGAlpes
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OMEGAlpes
  • OMEGAlpes
  • Issues
  • #74

Closed
Open
Created Nov 15, 2021 by Pierre-Thomas Demars@demarspiReporter

API consistency

Working with a FixedProductionUnit (pv_prod) and a StorageUnit (battery), I thought that the oriented object programmation of objects would be similar. However, I found that pv_prod.p.value gives access to a list of produced power values on the period but battery.p.value gives access to a dictionnary containing the index of the period as key and the charged/discharged power as values. With the StorageUnit, to access a list of power values, the adequate command is battery.p.value.values() .

The question is : could it be possible to achieve an perfect similitude between behaviors of both units ? Furthermore, this problem may exist between other units as well (VariableUnit etc..).

Edited Nov 15, 2021 by Pierre-Thomas Demars
Assignee
Assign to
Time tracking