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

Closed
Open
Created Jun 29, 2021 by Elizaveta Lutsenko@LizLutsenkoOwner

Freeze in random_chain generation during composing with specific primary model types

Created by: J3FALL

In Composer we have initial population generation stage that uses random_chain function for it. However, if we set GPComposerRequirements(primary=[data_operations_only]) it will probably freeze due to invalid chain configurations.

It happens due to chain validation: if chain contains more than one identical data_operation in primary_nodes it is invalid.

image

Probably, we should improve random_chain function - modify invalid chains if it occurs and log this operation.

Assignee
Assign to
Time tracking