Amit Moryossef

There was an update to store the data on R2: https://github.com/sign-language-processing/datasets/commit/376a09582089a60866ab01763e7a7e778884a4a0 So not sure why it is trying `firebasestorage`

What exactly are you running? What exactly is the error? If I go to the URL mentioned in - https://github.com/sign-language-processing/datasets/blob/master/sign_language_datasets/datasets/rwth_phoenix2014_t/rwth_phoenix2014_t.py#L39C27-L39C118 It works just fine

Please update to the latest version of the dataset. We moved to a different storage https://github.com/sign-language-processing/datasets/commit/9a9f2d94371bda64a0e4bcda21b8fab7d1805736

I think this could be useful!

All datasets where a pose header is available, have an external download of pose files. The pose header is used when reading the dataset after it is saved to disk....

where is the dataset config?

Please follow the examples https://colab.research.google.com/github/sign-language-processing/datasets/blob/master/examples/load.ipynb#scrollTo=m1XvMTs9Zvx4 ```py from sign_language_datasets.datasets.dgs_corpus import DgsCorpusConfig config = DgsCorpusConfig(name="only-annotations", version="1.0.0", include_video=False, include_pose=None) dgs_corpus = tfds.load('dgs_corpus', builder_kwargs=dict(config=config)) ```

Hi @professorcode1 My thoughts are as follows: Perhaps, similar to MS-ASL, YouTube-ASL and YouTube-SL-25, there should be a `base` dataset called `YouTube`. Then, every implementation should specify the data (`text`,...

I can't tell you all the functionality, since I did not build it, I can just imagine that there needs to be a unified way to download videos from youtube...

Hi! This repository is mainly designed to work with the binary file format, and is mostly agnostic to the specific pose estimation model used. For example, let's say you run...