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
  • Issues
  • #170

Closed
Open
Created Apr 04, 2022 by Oliver Kirsebom@kirsebomOwner

Storing attributes in HDF5 table when working with multiple audio representations

Ketos provides the option to store multiple audio representations within the same HDF5 table. That is, a single row in the table can contain multiple 'data' fields, for example, a spectrogram and the original waveform.

However, the current implementation only saves attributes (filename,label,offset,etc) pertaining to the first representation: https://gitlab.meridian.cs.dal.ca/public_projects/ketos/-/blob/master/ketos/data_handling/database_interface.py#L496

This is fine if the the various audio representations that are being saved share the same attributes, but not if they differ. In particular, I've run into a case which the representations have different offsets.

One possible solution is to store the audio representations in different tables. However, in its current form the batch generator cannot be easily configured to load from several tables at once. Instead, we could simply add additional offset fields to the table when multiple representations are stored, e.g., offset, offset1, offset2, etc.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking