Skip to content
GitLab
Projects Groups 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
    • Contributors
    • Graph
    • Compare
    • 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
  • #144
Closed
Open
Issue created Aug 07, 2017 by Moritz Robert Lauster@mlausterMaintainer

EnergyConversionSystem as abstract class

Created by: JoachimBenner

In the actual version, we declared _EnergyDistributionSystem and _StorageSystem as abstract classes, because we want to ensure that only the specializations like ThermalDistributionSystem are instanziated in an EnergyADE document. Is there a reason why we treat EnergyConversionSystem in a different manner? There are many specific classes for energy conversion systems being derived from the base class EnergyConversionSystem, but it is still possible to use the base class.

Assignee
Assign to
Time tracking