Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ketos ketos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • public_projects
  • ketosketos
  • Merge requests
  • !201

Merged
Created May 04, 2021 by Oliver Kirsebom@kirsebomOwner

Bug fix in JointBatchGenerator

  • Overview 13
  • Commits 10
  • Pipelines 9
  • Changes 5

I noticed that the next() method of the JointBatchGenerator class assumes that X is a numpy array. This is true as we load objects from a single column in the HDF5 table. If, however, we load multiple objects (e.g. for training a multi-modal model) by specifying a list of x_field values, the next() method brakes.

This merge request generalizes the implementation to be able to handle those cases in which X is a list of numpy arrays.

Edited May 14, 2021 by Oliver Kirsebom
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: joint_batch_gen_multi_modal