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

Closed
Open
Created Sep 27, 2021 by Elizaveta Lutsenko@LizLutsenkoOwner

Appearance of nodes of the incorrect class in pipelines

Created by: Dreamlone

During compositing (searching for a pipelined structure), graphs (OptGraph class) are converted into pipelines (Pipeline class). Adapters are used for this purpose. At certain points in time, however, nodes that are specific to OptGraph, or Graph, appear in the Pipeline structure. We need to find out why this happens

Graphs and Pipelines consist of nodes peculiar to these classes, PrimaryNode and SecondaryNode for Pipeline, OptNode for OptGraph, GraphNode for Graph.

Check picture for more details: issuу_nodes

Also in place of the field "name" in the content in the node with OptNode is inserted a string - the name of the operation. This too can be fixed.

Assignee
Assign to
Time tracking