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
  • #727

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

Hide specifics of new OptNode creation in mutation operators

Created by: gkirgizov

Currently mutation operators are specific to AutoML domain. To abstract them for general Graph optimization problem it's required to hide details (usage of candidate operations etc.) behind something like a graph node factory.

Aim is to allow using the mutation functions form mutation.py for other optimization tasks. Some custom example in the form of tests would be also good to have.

For an example see function _add_intermediate_node. Candidate operations and usage of OptNode class can be encapsulated.

Assignee
Assign to
Time tracking