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

Closed
Open
Created Sep 01, 2022 by Bruno Padovese@bpadoveseOwner

Confusing meaning of the attribute arguments

Several ketos functions use the term attributes. However, this term is being used in two different ways, and leads to confusion.

The first way it is being used (and more commonly), is as "extra columns" that may be optionally passed to a hdf5 database.

This can be seen in functions such as create_database with include_attrs and attrs parameter and internal functions such as get_instance_attrs which retrieves these extra columns from the object.

The second and less common way is as hdf5 table attributes described in write_repres_attrs

Writes the audio representation attributes into the HDF5 database, where they become stored as table attributes. More reading on this can be found on pytables docs.

This becomes very confusing quickly because i am never sure if attrs means hdf5 table attributes or simply extra columns.

I would propose we separate these 2 terms to be more accurate. My solution would be to have attrs be hdf5 table attributes, and rename the other occurrences of attribute such as in the create_database function to "extra_columns" or something along these lines.

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