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
  • !621

Merged
Created Mar 31, 2022 by Elizaveta Lutsenko@LizLutsenkoOwner

Refactor existing DataMerge functionality (closes #610)

  • Overview 48
  • Commits 10
  • Changes 23

Created by: gkirgizov

Collapse most of the code and branches into one direct 'merge' method with stages. Merge process is almost same for most data types, essentially just concatenating data along last dimension. Stages can be customized for each datatype, instead of branching to separate merge.

Substitute many manual routines with numpy counterparts. Move merge-related stuff from SupplementaryData into separate SupplementaryDataMerger.

Drop InputData.from_predictions in favor of DataMerge.merge that now directly returns InputData.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 610-merge