Adding loader for TAU Urban Acoustic Scenes 2022

[tanmayy24]

Description

Please include the following information at the top level docstring for the dataset's module mydataset.py:

• Describe annotations included in the dataset
• Indicate the total duration of the dataset in hours, and (optionally) also list the number of individual files
• Mention the origin of the dataset (e.g. creator, institution)
• Describe the type of audio included in the dataset
• Indicate any relevant papers related to the dataset
• Include a description about how the data can be accessed and the license it uses (if applicable)

Dataset loaders checklist:

• Create a script in scripts/, e.g. make_my_dataset_index.py, which generates an index file.
• Run the script on the canonical version of the dataset and save the index in soundata/indexes/ e.g. my_dataset_index.json.
• Create a module in soundata, e.g. soundata/my_dataset.py.
• Create tests for your loader in tests/, e.g. test_my_dataset.py.
• Add your module to docs/source/soundata.rst and docs/source/quick_reference.rst.
• Run black, flake8 and mypy (see Running your tests locally).
• Run tests/test_full_dataset.py on your dataset.
• Check that codecov coverage does not decrease.

[codecov]

Codecov Report

Merging #129 (04ff520) into main (6a5de09) will increase coverage by 0.04%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #129      +/-   ##
==========================================
+ Coverage   98.64%   98.69%   +0.04%     
==========================================
  Files          27       28       +1     
  Lines        2363     2447      +84     
==========================================
+ Hits         2331     2415      +84     
  Misses         32       32              

[genisplaja]

The loaders looks really good to me, testing coverage is high and I couldn't spot any issues. Just a question... do we actually need to have this massive docstring for the loader? Have not checked the others yet but, maybe it's too much to have about 500 lines of code for all the tables and so on... if there was a link or something for more info we could redirect the user there, and keep the basic and most important details of the dataset in the docstring. What do you think about that @magdalenafuentes, @tanmayy24 and @guillemcortes? If it's OK to have it, then everything is rendering really nicely and the loader looks ready to me :)

[genisplaja]

This line is not properly rendered.. maybe becuase of the :? Also I think we are not very consistent with the use of * before listing the attributes, input variables and so on. Sometimes we use it sometimes no. Maybe is not the goal of this PR but would be nice being consistent (unless there is a rule I am missing here).

[guillemcortes]

The loaders looks really good to me, testing coverage is high and I couldn't spot any issues. Just a question... do we actually need to have this massive docstring for the loader? Have not checked the others yet but, maybe it's too much to have about 500 lines of code for all the tables and so on... if there was a link or something for more info we could redirect the user there, and keep the basic and most important details of the dataset in the docstring. What do you think about that @magdalenafuentes, @tanmayy24 and @guillemcortes? If it's OK to have it, then everything is rendering really nicely and the loader looks ready to me :)

I agree that in this case, the docstring seems too large. The link could be a nice solution if it was a static link