Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • F FEDOT
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ITMO-NSS-team
  • FEDOT
  • Issues
  • #742

Closed
Open
Created Jun 21, 2022 by Elizaveta Lutsenko@LizLutsenkoOwner

Redesign GraphAdapter functionality given new Graph interface

Created by: gkirgizov

Requirements

  • There must be specific points in the system architecture where adapter is applied automatically
  • Mutations & other evolutionary operators shouldn't worry (or even know) about adapter -- they just must get OptGraph or the domain structure (e.g. Pipeline) that they need automatically
  • Adapter should be optional (e.g. if Pipeline inherits from Graph -- then in fact adapter has nothing to adapt and hence isn't really needed)

(upd) found a fun fact: there was a PEP that proposed adding Adapters at the language level https://peps.python.org/pep-0246/

Assignee
Assign to
Time tracking