Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • C citygml-energy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • energyade
  • citygml-energy
  • Issues
  • #166
Closed
Open
Issue created Jun 10, 2019 by Giorgio Agugiaro@gioaguMaintainer

Link SystemOperation to AbstractEnergySystem?

This is a question for the experts. So far we have the SystemOperation class tied to AbstractConversionSystem. It is (my guess) rather for historical reasons, as it was so before we changed the overall structure of the EnergySystem module in v. 0.9.

Now, would it not make more sense to move the SystemOperation class one step higher (hence linked to AbstractEnergySystem? I can imagine that also the other systems might have some operation schedules, not only the conversion ones.

@malhotra, what do you think?

Assignee
Assign to
Time tracking