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
  • Merge requests
  • !434

Merged
Created Sep 24, 2021 by Elizaveta Lutsenko@LizLutsenkoOwner

Fix decompose operation processing

  • Overview 3
  • Commits 4
  • Changes 5

Created by: Dreamlone

The way to determine the ancestor of data ("Data parent") and the ancestor of predictions ("Model parent") in the decompose operation has been fixed

Now, if the number of visited nodes in the data is equal, preference (for being "Data parent") is given to the lagged operation for example

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: decompose-fix